SKILL (orchestrator / agent prompt overlays)
For **implementation tasks** (code changes, refactors, fixes, new features): recommend **CURSOR_AGENT** so the orchestrator uses `CURSOR_AGENT: <prompt>` with the task description, then appends the result and sets the task status to finished. Prefer CURSOR_AGENT over RUN_CMD for coding tasks when cursor-agent is available.
Best use case
SKILL (orchestrator / agent prompt overlays) is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
For **implementation tasks** (code changes, refactors, fixes, new features): recommend **CURSOR_AGENT** so the orchestrator uses `CURSOR_AGENT: <prompt>` with the task description, then appends the result and sets the task status to finished. Prefer CURSOR_AGENT over RUN_CMD for coding tasks when cursor-agent is available.
Teams using SKILL (orchestrator / agent prompt overlays) should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/.mac-stats/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How SKILL (orchestrator / agent prompt overlays) Compares
| Feature / Agent | SKILL (orchestrator / agent prompt overlays) | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
For **implementation tasks** (code changes, refactors, fixes, new features): recommend **CURSOR_AGENT** so the orchestrator uses `CURSOR_AGENT: <prompt>` with the task description, then appends the result and sets the task status to finished. Prefer CURSOR_AGENT over RUN_CMD for coding tasks when cursor-agent is available.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# SKILL (orchestrator / agent prompt overlays) For **implementation tasks** (code changes, refactors, fixes, new features): recommend **CURSOR_AGENT** so the orchestrator uses `CURSOR_AGENT: <prompt>` with the task description, then appends the result and sets the task status to finished. Prefer CURSOR_AGENT over RUN_CMD for coding tasks when cursor-agent is available. See also: orchestrator skill (`~/.mac-stats/agents/agent-000/skill.md`), `docs/012_cursor_agent_tasks.md`.
Related Skills
world-sufficiency-prompt
First-interaction system prompt generator for Gemini, Codex, and Claude. Detects hierarchical user intent (implicit and explicit) and loads GF(3)-balanced skill triads to achieve World -> World' sufficiency before any model response. Bridges dynamic-sufficiency theory to concrete systemInstruction/system-message payloads across all three providers.
triadic-skill-orchestrator
Orchestrates multiple skills in GF(3)-balanced triplets. Assigns MINUS/ERGODIC/PLUS trits to skills ensuring conservation. Use for multi-skill workflows, parallel skill dispatch, or maintaining GF(3) invariants across skill compositions.
smack-label-orchestrator
Manages SMACK label assignments across apps and kernel. Coordinates mandatory access control labels with process isolation.
detecting-ai-model-prompt-injection-attacks
Detects prompt injection attacks targeting LLM-based applications using a multi-layered defense combining regex pattern matching for known attack signatures, heuristic scoring for structural anomalies, and transformer-based classification with DeBERTa models. The detector analyzes user inputs before they reach the LLM, flagging direct injections (system prompt overrides, role-play escapes, instruction hijacking) and indirect injections (encoded payloads, multi-language obfuscation, delimiter-based escapes). Based on the OWASP LLM Top 10 (LLM01:2025 Prompt Injection) and Simon Willison's prompt injection taxonomy. Activates for requests involving prompt injection detection, LLM input sanitization, AI security scanning, or prompt attack classification.
prompt-injection-defense
Defend the agent's instruction surface against adversarial content - hidden-Unicode prompt injection (Trojan Source bidi reordering, U+E0000 tag-block ASCII smuggling, zero-width text), homoglyph confusables, and poisoned context that a human reviewer can't see but the model obeys. Scan CLAUDE.md / AGENTS.md / SKILL.md / .cursorrules and MCP tool descriptions; sanitize fetched web pages, issue/PR bodies, and dependency READMEs before they enter context. Triggers on: prompt injection, hidden unicode, invisible characters, zero-width space, bidi override, Trojan Source, ASCII smuggling, tag characters, homoglyph, confusable, unicode steganography, poisoned CLAUDE.md, malicious tool description, MCP tool poisoning, instruction injection, jailbreak in file, is this file safe, sanitize untrusted content, scan for hidden text.
backlog-execution-orchestrator
Use when executing backlog-driven work, multi-PR initiatives, recommendation-gated implementation, or one-backlog-per-PR workflows. Orchestrates owner skills without duplicating their detailed procedures.
customaize-agent:prompt-engineering
Use this skill when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing production prompt templates.
empirical-prompt-tuning
agent 向けテキスト指示(skill / slash command / task プロンプト / CLAUDE.md 節 / コード生成プロンプト)を、バイアスを排した実行者に動かしてもらい、両面(実行者の自己申告 + 指示側メトリクス)で評価して反復改善する手法。改善が頭打ちになるまで回す。プロンプトや skill を新規作成・大幅改訂した直後、またはエージェントの挙動が期待通りにならない原因を指示側の曖昧さに求めたいときに使う。
self-healing-orchestrator
Proposes patches for F2 (local-logic) and F3 (local-design) failures. NEVER applies without user approval. Confidence ≥0.7 to propose; below that, escalates raw findings. Counts toward replan_budget. Per-task: max 1; per-session: max 5.
run-orchestrator
Execute 5-phase TDD workflow for complex features. Use when the user invokes /run, asks to build/create/implement a feature, requests a complex multi-file change, or types 'fasttrack:'. Enforces phase gates, sprint contracts, and builder!=reviewer discipline.
prompt-evaluator
Evaluate how you use Claude Code — analyze prompt patterns, feature utilization, and get improvement suggestions. Trigger: /prompts:evaluate, prompt analysis, usage evaluation, how am I using Claude
plan-orchestrator
Route hierarchical-planning intents to the correct backing script. Use when the user invokes /aura-frog:plan (with or without subcommand), mentions plan verbs (expand/next/replan/promote/archive/freeze/thaw/undo/status/conflicts), or types a plan-vocabulary bare word with .claude/plans/active.json present. Owns verb table, intent classifier, and 3-stage routing pipeline.