@deimoscloud/coreai 0.1.17 → 0.1.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deimoscloud/coreai",
-  "version": "0.1.17",
+  "version": "0.1.18",
   "description": "A configurable, team-ready AI agent orchestration platform",
   "type": "module",
   "main": "dist/index.js",
@@ -11,6 +11,7 @@
   "files": [
     "dist",
     "agents",
+    "skills",
     "schemas"
   ],
   "repository": {

package/skills/core/check-inbox/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: check-inbox
+description: Check your inbox for new tasks and process them
+argument-hint: [optional: and work on ticket]
+allowed-tools: Read, Write, Bash, Glob, Grep
+---
+
+# Check Inbox
+
+You have been invoked to check your inbox and process any pending tasks.
+
+## Instructions
+
+1. **Read your inbox directory:** `/KnowledgeLibrary/[your-agent-name]/inbox/`
+   - Ignore the `processed/` subdirectory
+   - Look for `.md` files from other agents (especially engineering-manager)
+
+2. **For each unprocessed message:**
+   - Read the task details
+   - If it's a task assignment, begin work following the workflow in `WORKFLOWS.md`
+   - If it's a review request, perform the review
+
+3. **When you complete work:**
+   - Move processed inbox messages to `inbox/processed/` with prefix `PROCESSED_YYYYMMDD_HHMM_`
+   - Write completion summary to the sender's inbox (usually engineering-manager)
+   - Update any referenced tickets or PRs using your available tools
+   - End with "Please invoke @[next-agent]" instruction for the user
+
+4. **If inbox is empty:**
+   - Report "No pending tasks in inbox"
+   - Optionally check for assigned work using your available tools
+
+## Additional Context
+
+$ARGUMENTS
+
+Now check your inbox and proceed.

package/skills/core/delegate/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: delegate
+description: Delegate a task to an agent using inbox-based delegation (NOT Task tool)
+argument-hint: <ticket-or-task> to <agent-name>
+allowed-tools: Read, Write, Bash, Glob, Grep
+---
+
+# Delegation Request
+
+You are the Engineering Manager. Delegate this task: **$ARGUMENTS**
+
+## CRITICAL RULES - READ FIRST
+
+1. **DO NOT USE THE TASK TOOL** - You must NOT invoke agents directly
+2. **USE INBOX FILES ONLY** - Write task details to the agent's inbox directory
+3. **TELL USER TO INVOKE** - End your response telling the user which agent(s) to invoke
+
+## Why No Task Tool?
+
+When YOU invoke an agent via the Task tool, they run in a subprocess without MCP access.
+When the USER invokes them via `@agent-name`, they get full MCP access to project tools.
+Always delegate via inbox so the user can invoke with full capabilities.
+
+## Steps
+
+1. **Parse the request** - identify the target agent and task details
+2. **Look up context** - if a ticket, PR, or issue is referenced, use your available tools to gather details
+3. **Write task file** to `/KnowledgeLibrary/[agent-name]/inbox/YYYYMMDD_HHMM-engineering-manager-[topic].md`
+4. **Save copy** to your outbox at `/KnowledgeLibrary/engineering-manager/outbox/`
+5. **End with invocation instruction** for the user
+
+## Inbox Message Format
+
+```markdown
+## Task Assignment
+**From:** engineering-manager
+**Date:** [today's date]
+**Priority:** [high/medium/low]
+
+### Task
+[Clear description of what needs to be done]
+
+### Context
+[Any relevant ticket numbers, PR links, or background information]
+
+### Acceptance Criteria
+- [What "done" looks like]
+
+### Workflow
+Follow your standard workflow in WORKFLOWS.md
+```
+
+## End Your Response With
+
+```
+---
+**Next Action Required:**
+Please invoke: `@[agent-name] check your inbox`
+```
+
+Now proceed with the delegation.

package/skills/core/review/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: review
+description: Request PR review from agents using inbox-based delegation
+argument-hint: PR #<number> by <agent-name(s)>
+requires: [git]
+allowed-tools: Read, Write, Bash, Glob, Grep
+---
+
+# PR Review Request
+
+You are the Engineering Manager. Assign this review: **$ARGUMENTS**
+
+## CRITICAL RULES - READ FIRST
+
+1. **DO NOT USE THE TASK TOOL** - You must NOT invoke agents directly
+2. **USE INBOX FILES ONLY** - Write review requests to agent inbox directories
+3. **TELL USER TO INVOKE** - End your response telling the user which agent(s) to invoke
+
+## Steps
+
+1. **Get PR details** using your available tools (e.g. `gh pr view`, `glab mr view`)
+2. **Identify reviewer agent(s)** from the arguments or based on the PR's domain
+3. **For EACH reviewer agent**, write a review request to their inbox:
+   `/KnowledgeLibrary/[agent-name]/inbox/YYYYMMDD_HHMM-engineering-manager-review-PR-XX.md`
+4. **Save copies** to your outbox
+5. **End with invocation instructions** for the user
+
+## Review Request Template
+
+```markdown
+## PR Review Request
+**From:** engineering-manager
+**Date:** [date]
+**PR:** #[number] - [title]
+**PR URL:** [url from PR details]
+
+### Review Focus
+- [Architecture alignment / Security / Test coverage - based on agent role]
+
+### Workflow Requirements
+Follow Code Review workflow in WORKFLOWS.md:
+1. Review the PR thoroughly
+2. Post your review as a PR comment using your available tools
+3. State APPROVED or CHANGES_REQUESTED with your decision
+4. Send summary to my inbox
+```
+
+## End Your Response With
+
+```
+---
+**Next Action Required:**
+Please invoke the reviewers:
+- `@[agent-name] check your inbox and review PR #XX`
+```
+
+Now proceed with the review delegation.