Menu
Proactively notify the orchestrator when a task is done, blocked, or failed.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | Report Status |
| description | Proactively notify the orchestrator when a task is done, blocked, or failed. |
| version | 1.0.0 |
| category | task-management |
| skillType | claude-skill |
| 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"] |
| execution | {"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":15000}} |
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.
| Flag | JSON Field | Required | Description |
|---|---|---|---|
--session / -s | sessionName | Yes | Your agent session name |
--status / -S | status | Yes | Status: done, blocked, failed, in_progress, active, milestone. milestone = a SHIPPED artifact inside an open goal (PR merged / spec finalized / build pass); emits a [MILESTONE] envelope that orc's Smart Notification Protocol always forwards to the owner. See config/sops/common/mid-flight-milestone-surface.md (#435). Summary must be ≥30 chars. |
--summary / -m | summary | Yes | Brief description (or pipe via stdin) |
--summary-file | — | No | Read summary from a file path |
--project / -p | projectPath | No | Project path for auto-remember on completion |
--task-path | taskPath | No | Task file path; auto-moves to done/ on completion |
--task-id | taskId | No | Task ID (for structured StatusReport format) |
--progress | progress | No | Progress percentage 0-100 |
--structured | structured | No | Use structured StatusReport format |
# Report done
bash execute.sh --session dev-1 --status done --summary "Finished auth module, all tests pass" --project /path/to/project
# Report a blocker
bash execute.sh --session dev-1 --status blocked --summary "Waiting on API credentials from ops team"
# Report failure
bash execute.sh --session dev-1 --status failed --summary "Build fails due to missing dependency"
# Surface a milestone (#435) — a SHIPPED artifact inside an open goal.
# Emits the [MILESTONE] envelope orc's Smart Notification table always
# forwards to the owner. Summary must carry both WHAT shipped AND
# WHAT-IT-MEANS-FOR-OWNER (≥30 chars).
bash execute.sh --session dev-1 --status milestone \
--summary "PR #420 merged — agent state file is now corruption-resistant + auto-snapshots every 30s"
# Multi-line summary via stdin (avoids shell escaping)
echo "Fixed the bug — it's working now" | bash execute.sh --session dev-1 --status done --project /path
# Summary from file
bash execute.sh --session dev-1 --status done --summary-file /tmp/summary.txt --project /path
bash execute.sh '{"sessionName":"dev-1","status":"done","summary":"Finished implementing auth module","taskPath":"/path/.crewly/tasks/delegated/in_progress/implement_auth_1234.md"}'
JSON confirmation that the status notification was sent to the orchestrator. If taskPath was provided with done status, also returns the task completion result.
Plan and create a NESTED team hierarchy (parent coordination team + per-stream child teams) for a complex multi-stream goal. Use INSTEAD of recommend-team/materialize-team when the goal names 2+ parallel work-streams (e.g. frontend + backend + DevOps). Onboarding-only.
Search the live web for a query and return ranked results (title, URL, snippet) as JSON. Works with no API key (DuckDuckGo HTML fallback) and uses the Brave Search API or SerpAPI automatically when BRAVE_API_KEY / SERPAPI_KEY is set. Any agent can call it for research, competitor analysis, market/trend lookups, fact-checking, finding sources to cite, or grounding a non-software goal (marketing, growth, commerce) in real-world information.
Transcribe a local audio (or video) file to text with timestamps using Whisper. Defaults to local whisper.cpp (free, offline, word/segment-level timestamps) and automatically falls back to the OpenAI Whisper API (whisper-1) when the local engine is not installed. Any agent can call it for meetings, podcasts, voice notes, interviews, or video audio tracks.
Accept and take the next available task from the task queue. Use when an agent is idle and ready to pick up the highest-priority unassigned task. For assigning tasks to specific agents, use assign-task instead.
Register the agent as active with the Crewly backend on startup. Use when an agent first launches and needs to join the team and become visible to the orchestrator. For confirming responsiveness after registration, use heartbeat instead.
Analyze git changes and produce a structured code review with automated checks for missing tests, debug statements, potential secrets, large changes, and dependency modifications. Use when reviewing staged changes, unstaged diffs, recent commits, or branch comparisons before submitting a pull request. For task-level quality gates, use check-quality-gates instead.