crewly 1.0.8 → 1.0.11

package/config/skills/agent/core/report-progress/instructions.md

@@ -0,0 +1,25 @@
+# Report Progress
+
+Report progress on your current task. Includes a completion percentage, what you are currently working on, completed items, and next steps.
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `sessionName` | Yes | Your agent session name |
+| `progress` | Yes | Completion percentage (0-100) |
+| `current` | Yes | Description of what you are currently working on |
+| `completed` | No | Array of completed items |
+| `nextSteps` | No | Description of planned next steps |
+| `blockers` | No | Description of any blockers encountered |
+| `ticketId` | No | Associated ticket or task ID |
+
+## Example
+
+```bash
+bash config/skills/agent/report-progress/execute.sh '{"sessionName":"dev-1","progress":60,"current":"Writing unit tests","completed":["Implemented API endpoint","Added validation"],"nextSteps":"Integration tests and code review","blockers":""}'
+```
+
+## Output
+
+JSON confirmation that the progress report has been recorded.

package/config/skills/agent/core/report-progress/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "agent-report-progress",
+  "name": "Report Progress",
+  "description": "Report progress on the current task with percentage, completed items, and next steps.",
+  "category": "task-management",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 15000
+    }
+  },
+  "assignableRoles": ["developer", "qa", "tpm", "designer", "frontend-developer", "backend-developer", "fullstack-dev", "qa-engineer", "product-manager", "architect", "generalist", "sales", "support"],
+  "triggers": ["report progress", "status update", "progress update", "sync status"],
+  "tags": ["task", "progress", "status", "sync"],
+  "version": "1.0.0"
+}

package/config/skills/agent/core/report-status/execute.sh

@@ -0,0 +1,35 @@
+#!/bin/bash
+# Report task status to the orchestrator
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../../_common/lib.sh"
+
+INPUT="${1:-}"
+[ -z "$INPUT" ] && error_exit "Usage: execute.sh '{\"sessionName\":\"dev-1\",\"status\":\"done\",\"summary\":\"Finished implementing auth module\",\"taskPath\":\"/path/to/task.md\"}'"
+
+SESSION_NAME=$(echo "$INPUT" | jq -r '.sessionName // empty')
+STATUS=$(echo "$INPUT" | jq -r '.status // empty')
+SUMMARY=$(echo "$INPUT" | jq -r '.summary // empty')
+TASK_PATH=$(echo "$INPUT" | jq -r '.taskPath // empty')
+require_param "sessionName" "$SESSION_NAME"
+require_param "status" "$STATUS"
+require_param "summary" "$SUMMARY"
+
+# Build the message the orchestrator will receive
+STATUS_UPPER=$(echo "$STATUS" | tr '[:lower:]' '[:upper:]')
+MESSAGE="[${STATUS_UPPER}] Agent ${SESSION_NAME}: ${SUMMARY}"
+
+# Send the status message to the orchestrator session via the chat API
+BODY=$(jq -n --arg content "$MESSAGE" --arg senderName "$SESSION_NAME" \
+  '{content: $content, senderName: $senderName, senderType: "agent"}')
+
+api_call POST "/chat/agent-response" "$BODY"
+
+# If task is done and taskPath provided, move task file to done folder
+if [ "$STATUS" = "done" ] && [ -n "$TASK_PATH" ]; then
+  COMPLETE_BODY=$(jq -n \
+    --arg taskPath "$TASK_PATH" \
+    --arg sessionName "$SESSION_NAME" \
+    '{taskPath: $taskPath, sessionName: $sessionName}')
+  api_call POST "/task-management/complete" "$COMPLETE_BODY" || true
+fi

package/config/skills/agent/core/report-status/instructions.md

@@ -0,0 +1,36 @@
+# Report Status
+
+Proactively notify the orchestrator when a task is done, blocked, or failed. Use this skill to keep the orchestrator informed without waiting for a scheduled check-in.
+
+When `status` is `done` and a `taskPath` is provided, the task file is automatically moved from `in_progress/` to `done/` in the project's `.crewly/tasks/` directory.
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `sessionName` | Yes | Your agent session name |
+| `status` | Yes | Current status: `done`, `blocked`, or `failed` |
+| `summary` | Yes | Brief description of what happened or what is needed |
+| `taskPath` | No | Path to the task MD file; when provided with `status=done`, moves it to the `done/` folder |
+
+## Example
+
+```bash
+bash config/skills/agent/report-status/execute.sh '{"sessionName":"dev-1","status":"done","summary":"Finished implementing auth module and all tests pass","taskPath":"/path/to/project/.crewly/tasks/delegated/in_progress/implement_auth_1234.md"}'
+```
+
+### Reporting a blocker
+
+```bash
+bash config/skills/agent/report-status/execute.sh '{"sessionName":"dev-1","status":"blocked","summary":"Waiting on API credentials from ops team"}'
+```
+
+### Reporting a failure
+
+```bash
+bash config/skills/agent/report-status/execute.sh '{"sessionName":"dev-1","status":"failed","summary":"Build fails due to missing dependency in package.json"}'
+```
+
+## Output
+
+JSON confirmation that the status notification was sent to the orchestrator. If `taskPath` was provided with `done` status, also returns the task completion result.

package/config/skills/agent/core/report-status/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "agent-report-status",
+  "name": "Report Status",
+  "description": "Proactively notify the orchestrator when a task is done, blocked, or failed.",
+  "category": "task-management",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 15000
+    }
+  },
+  "assignableRoles": ["developer", "qa", "tpm", "designer", "frontend-developer", "backend-developer", "fullstack-dev", "qa-engineer", "product-manager", "architect", "generalist", "sales", "support"],
+  "triggers": ["report status", "notify orchestrator", "task done", "task blocked", "task failed"],
+  "tags": ["task", "status", "notification", "orchestrator"],
+  "version": "1.0.0"
+}

package/config/skills/agent/core/send-chat-response/execute.sh

@@ -0,0 +1,26 @@
+#!/bin/bash
+# Send a chat response visible in the Crewly chat UI
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../../_common/lib.sh"
+
+INPUT="${1:-}"
+[ -z "$INPUT" ] && error_exit "Usage: execute.sh '{\"content\":\"Task completed successfully\",\"senderName\":\"dev-1\"}'"
+
+CONTENT=$(echo "$INPUT" | jq -r '.content // empty')
+SENDER_NAME=$(echo "$INPUT" | jq -r '.senderName // empty')
+SENDER_TYPE=$(echo "$INPUT" | jq -r '.senderType // empty')
+CONVERSATION_ID=$(echo "$INPUT" | jq -r '.conversationId // empty')
+require_param "content" "$CONTENT"
+require_param "senderName" "$SENDER_NAME"
+
+BODY=$(jq -n \
+  --arg content "$CONTENT" \
+  --arg senderName "$SENDER_NAME" \
+  --arg senderType "$SENDER_TYPE" \
+  --arg conversationId "$CONVERSATION_ID" \
+  '{content: $content, senderName: $senderName} +
+   (if $senderType != "" then {senderType: $senderType} else {} end) +
+   (if $conversationId != "" then {conversationId: $conversationId} else {} end)')
+
+api_call POST "/chat/agent-response" "$BODY"

package/config/skills/agent/core/send-chat-response/instructions.md

@@ -0,0 +1,22 @@
+# Send Chat Response
+
+Send a chat response that appears in the Crewly chat UI. Use this to communicate results, status updates, or answers directly to the user.
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `content` | Yes | The message content to display in chat |
+| `senderName` | Yes | Your agent name (displayed as the message sender) |
+| `senderType` | No | Sender type (e.g., `"agent"`, `"system"`) |
+| `conversationId` | No | Target conversation ID. Uses the active conversation if omitted |
+
+## Example
+
+```bash
+bash config/skills/agent/send-chat-response/execute.sh '{"content":"Login feature implemented and all tests passing.","senderName":"dev-1"}'
+```
+
+## Output
+
+JSON confirmation that the chat message was delivered.

package/config/skills/agent/core/send-chat-response/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "agent-send-chat-response",
+  "name": "Send Chat Response",
+  "description": "Send a chat response visible in the Crewly chat UI.",
+  "category": "communication",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 15000
+    }
+  },
+  "assignableRoles": ["developer", "qa", "tpm", "designer", "frontend-developer", "backend-developer", "fullstack-dev", "qa-engineer", "product-manager", "architect", "generalist", "sales", "support"],
+  "triggers": ["send chat", "reply chat", "chat response", "respond to user"],
+  "tags": ["chat", "communication", "response"],
+  "version": "1.0.0"
+}

package/config/skills/agent/core/send-message/execute.sh

@@ -0,0 +1,17 @@
+#!/bin/bash
+# Send a direct message to another agent's terminal session
+set -euo pipefail
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../../_common/lib.sh"
+
+INPUT="${1:-}"
+[ -z "$INPUT" ] && error_exit "Usage: execute.sh '{\"to\":\"agent-session\",\"message\":\"Can you review my PR?\"}'"
+
+TO=$(echo "$INPUT" | jq -r '.to // empty')
+MESSAGE=$(echo "$INPUT" | jq -r '.message // empty')
+require_param "to" "$TO"
+require_param "message" "$MESSAGE"
+
+BODY=$(jq -n --arg data "$MESSAGE" --arg mode "message" '{data: $data, mode: $mode}')
+
+api_call POST "/terminal/${TO}/write" "$BODY"

package/config/skills/agent/core/send-message/instructions.md

@@ -0,0 +1,20 @@
+# Send Message
+
+Send a direct message to another agent's terminal session. The message is written to the target agent's PTY using the two-step message mode for reliable delivery.
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `to` | Yes | Target agent's PTY session name |
+| `message` | Yes | The message text to send |
+
+## Example
+
+```bash
+bash config/skills/agent/send-message/execute.sh '{"to":"qa-1","message":"PR #42 is ready for review. I added unit tests for the auth module."}'
+```
+
+## Output
+
+JSON confirmation of message delivery.

package/config/skills/agent/core/send-message/skill.json

@@ -0,0 +1,20 @@
+{
+  "id": "agent-send-message",
+  "name": "Send Message",
+  "description": "Send a direct message to another agent's terminal session.",
+  "category": "communication",
+  "skillType": "claude-skill",
+  "promptFile": "instructions.md",
+  "execution": {
+    "type": "script",
+    "script": {
+      "file": "execute.sh",
+      "interpreter": "bash",
+      "timeoutMs": 30000
+    }
+  },
+  "assignableRoles": ["developer", "qa", "tpm", "designer", "frontend-developer", "backend-developer", "fullstack-dev", "qa-engineer", "product-manager", "architect", "generalist", "sales", "support"],
+  "triggers": ["send message", "message agent", "tell agent", "dm agent"],
+  "tags": ["communication", "agent", "message", "terminal"],
+  "version": "1.0.0"
+}

package/config/skills/orchestrator/delegate-task/execute.sh

@@ -18,7 +18,7 @@ require_param "task" "$TASK"
 # Build a structured task message
 TASK_MESSAGE="[TASK] Priority: ${PRIORITY}\n\n${TASK}"
 [ -n "$CONTEXT" ] && TASK_MESSAGE="${TASK_MESSAGE}\n\nContext: ${CONTEXT}"
-TASK_MESSAGE="${TASK_MESSAGE}\n\nWhen done, report back using: bash config/skills/agent/report-status/execute.sh '{\"sessionName\":\"${TO}\",\"status\":\"done\",\"summary\":\"<brief summary>\"}'"
+TASK_MESSAGE="${TASK_MESSAGE}\n\nWhen done, report back using: bash config/skills/agent/core/report-status/execute.sh '{\"sessionName\":\"${TO}\",\"status\":\"done\",\"summary\":\"<brief summary>\"}'"
 
 BODY=$(jq -n --arg message "$TASK_MESSAGE" '{message: $message}')
 

package/config/skills/orchestrator/schedule-check/instructions.md

@@ -33,3 +33,9 @@ bash config/skills/orchestrator/schedule-check/execute.sh '{"minutes":10,"messag
 ## Output
 
 JSON with the scheduled check ID and fire time.
+
+## Best Practices
+
+- **Always validate relevance** before acting on a scheduled check. If the agent or task it references is no longer active, cancel the schedule instead of performing the check.
+- **Include context in the message** — mention the agent name and task so the orchestrator can quickly determine relevance when the check fires.
+- **Use `maxOccurrences`** for time-bounded tasks to prevent stale schedules from running indefinitely.