القائمة
Cancel a follow-up trigger previously created with `schedule-followup` or `watch-for-event`, by trigger id or by team-scoped name.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | cancel-followup |
| description | Cancel a follow-up trigger previously created with `schedule-followup` or `watch-for-event`, by trigger id or by team-scoped name. |
| version | 1.0.0 |
| category | followup |
| skillType | claude-skill |
| tags | ["followup","trigger","lifecycle"] |
| execution | {"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":15000}} |
Cancel a follow-up trigger you previously created with schedule-followup or
watch-for-event. Accepts either the trigger id (returned at creation time)
or the stable name.
The moment you confirm the work is done. maxIdleFires will eventually
auto-cancel idle watchers, but relying on it wastes fire cycles and pollutes
the task pool with no-op checks. Be explicit.
followup:verify-rex-draft), anyone on your team can resolve it
without needing the opaque UUID. The lookup never touches another team's
triggers, even if names collide.# By id — most common when you still have the POST response
bash execute.sh --id 123e4567-e89b-12d3-a456-426614174000
# By name — useful when the id is long gone
bash execute.sh --name "followup:verify-rex-draft"
success:false with a
human-readable reason — it does not error out loudly.exhausted or cancelled is a no-op
(the API handles this idempotently).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.