القائمة
List the recurring cron tasks the orchestrator has scheduled FOR you — call before self-scheduling so you don't create duplicates that fire N× reports.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | list-my-crons |
| description | List the recurring cron tasks the orchestrator has scheduled FOR you — call before self-scheduling so you don't create duplicates that fire N× reports. |
| version | 1.0.0 |
| category | followup |
| skillType | claude-skill |
| tags | ["cron","schedule","audit"] |
| execution | {"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":15000}} |
List the recurring cron tasks that target you — i.e. schedules the
orchestrator (or you) registered with you as the targetAgent. Call this
before creating a cron or a schedule-followup, so you can confirm whether
you are already scheduled instead of stacking a duplicate.
Cron tasks and follow-up triggers live in two different stores:
| What | Store | List it with |
|---|---|---|
| Recurring cron the orchestrator set for you | cron-tasks (per-team file) | list-my-crons (this skill) |
| Follow-up timers you created | triggers (TriggerEngine) | list-my-followups |
list-my-followups will not show the orchestrator's crons — they are in a
separate store. If you only check followups, you can wrongly conclude "I have
no schedule" and self-create a duplicate cron. That duplicate then fires every
trigger N× (N identical reports/PDFs). Always check both before scheduling.
Note: "cron API shows 0" is not a reliable "no schedule exists" signal on its own — historically agents misread it and self-duplicated (#621). Check the actual list here, and if unsure, ask the orchestrator rather than re-creating.
# All crons targeting you
bash execute.sh
# Only enabled ones
bash execute.sh --enabled true
| Flag | Meaning |
|---|---|
--enabled <true|false> | Filter by enabled state (optional) |
--target <session> | Query a different agent's crons (default: yourself) |
--json, -j | Raw JSON payload (legacy) |
{ "success": true, "count": <n>, "data": [ CronTask, ... ] }