cursor-agent-supervisor
Offloading tasks with a well-defined scope to sub-agents, for instance to use a sub-agent to implement a set of specs. Use this skill whenever a task should not need a broad knowledge of the whole project
- Installs
- 68
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/ypares/agent-skills --skill cursor-agent-supervisor- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads cursor-agent-supervisor automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Agent Supervisor
You can start subagents (e.g. to work on a specific JJ revision) with:
# Create a conversation with a sub-agent:
cursor-agent --print --model <model-name> create-chat # Prints a conversation uuid
# Give a task to the sub-agent: (command will finish when sub-agent is done)
cursor-agent --print --resume <conversation-uuid> "...description of the subagent's task..."
Model Selection
cursor-agent --print --model unknown-model will print an error that will list available models.
Unless you know which model is best for the task, just use sonnet-4.5 by default.
Invocation
Important: Sub-agent tasks can take several minutes. Always use a longer timeout:
# In your Shell tool call, set timeout to 10 minutes
timeout: 600000
The --print flag makes the sub-agent run on its own, and reply only once it is done.
Setting Things up for the Sub-agent
Prepare things up so the agent can focus on its task (eg. if using JJ, don't ask them to run jj commands unless really necessary.
Notably run jj edit yourself first to get into the revision where the work should be done).
Ideally, the sub-agent should only have to read your instructions, hack on code, run build/tests, hack on code, etc.
until your instructions are implemented, and then reply with a final answer.
YOU are in charge of bookkeeping, not them. YOU have the big picture, they don't.
Giving Good Instructions
Give the subagent the instructions they will need to complete the task, but do not overwhelm them.
Do:
- Provide a clear, specific goal
- List key files to read/modify
- Specify what "done" looks like
- Include relevant patterns to follow or reference implementations
- Tell them which skills to load if needed
Don't:
- Dump or link to entire skills when they only need a subset
- Include irrelevant context
- Leave success criteria ambiguous
Task Description Template
Work on [specific task] in [repo/directory].
**Setup:**
- Skills to load or files to read IN FULL
- Summarized instructions from skills or files, tailored to the task
**Goal:**
[Clear description of what to implement/fix]
**Key files:**
- path/to/main/file.ts - [why it matters]
- path/to/reference.ts - [pattern to follow]
**Requirements:**
- [Specific requirement 1]
- [Specific requirement 2]
**Done when:**
- [Testable criterion 1]
- [Testable criterion 2]
- [e.g., "pnpm -F @pkg lint passes"]
After Sub-agent Completes
Always verify the sub-agent's work:
- Check what changed: check the commit/revision diff, and adequation with the task
- Review the actual code if the changes are non-trivial
- Run verification commands (tests, type-check, lint)
- Update task status based on results (if using jj-todo-workflow)
When Things Go Wrong
If the sub-agent:
- Fails or errors out: Read the output, fix any blocking issues, retry with more context
- Produces incomplete work: Continue the work yourself or spawn another sub-agent with clarified instructions
- Goes off track: Review what happened, potentially revert changes, retry with tighter constraints
- Gets stuck on tooling: May need to provide explicit commands or paths
FAQ
What does the cursor-agent-supervisor skill do?
Offloading tasks with a well-defined scope to sub-agents, for instance to use a sub-agent to implement a set of specs. Use this skill whenever a task should not need a broad knowledge of the whole project
How do I install cursor-agent-supervisor?
Run npx skills add https://github.com/ypares/agent-skills --skill cursor-agent-supervisor in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/cursor-agent-supervisor/ (personal) or .claude/skills/cursor-agent-supervisor/ (project).
Which AI agents can use cursor-agent-supervisor?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is cursor-agent-supervisor safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains cursor-agent-supervisor?
It is published by ypares in ypares/agent-skills. It has 68 recorded installs.
More from ypares/agent-skills
searxng-search
ypares/agent-skills
Enhanced web and package repository search using local SearXNG instance
textual-builder
ypares/agent-skills
Open the skill to read its SKILL.md instructions.
typst-writer
ypares/agent-skills
Open the skill to read its SKILL.md instructions.
github-pr-workflow
ypares/agent-skills
Open the skill to read its SKILL.md instructions.
working-with-jj
ypares/agent-skills
Open the skill to read its SKILL.md instructions.
nushell-usage
ypares/agent-skills
Essential patterns, idioms, and gotchas for writing Nushell code. Use when writing Nushell scripts, functions, or working with Nushell's type system, pipelines, and data structures. Complements plugin development knowledge with practical usage patterns.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available