agentleFS
Sign inStart free
franckdjiongofranckdjiongo/claude-skills/create-subagent/SKILL.md

create-subagent

Skill0 starsChanged 4 months agoNo licenceView on GitHub

Use this skill whenever the user wants to create, scaffold, generate, or define a new subagent (also called "agent" or "agent .md") for Claude Code — anything that produces a file in `.claude/agents/` or `~/.claude/agents/`. Triggers on phrases like "create a subagent", "new agent", "add an agent for X", "scaffold an agent", "make me a code-reviewer agent", "build a migration agent", "spawn an isolated worker for Y", "I need an agent that runs in its own context", "agent .md file", "@agent setup", "user-level agent", "project-level agent", "convert this skill into a subagent", "split this work into a fresh agent", or whenever the user describes a recurring specialist task that should run with its own context window. ALSO triggers when the user says they want to "delegate" something repeatable, when they complain that some workflow is flooding their main context, or when they ask "should this be a skill or a subagent". This skill is DISTINCT from skill-creator — skills teach the *current* context how to do something; subagents *delegate* work to a fresh isolated context and return only a summary. The skill first helps the user pick the right primitive (skill vs subagent vs agent team), then produces a single well-formed `.claude/agents/<name>.md` with Opus 4.7-appropriate frontmatter (`tools`, `model`, `effort`, `memory`, `isolation`, `permissionMode`, `hooks`, `mcpServers`, `skills`), warns when the target is a plugin (plugin agents cannot declare `hooks`, `mcpServers`, or `permissionMode`), and generates concrete smoke-test invocation examples. Do NOT use this skill if the user wants a workflow loaded into the current context (use skill-creator) or a long-running multi-session team (point them at agent teams instead).

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use update-cli-config, review-bugbot and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • PandelisZSkill

    update-cli-config

    View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

    Also in 7 projects that use this

  • 0mlkrizzz655335vSkill

    review-bugbot

    缺陷导向代码审查。用 Bugbot 子代理找 bug。

    Also in 4 projects that use this

  • 0mlkrizzz655335vSkill

    origin

    origin CLI 管理。安装、登录、更新、修复 origin.cursor.com 的 CLI。"disabled-environments:

    Also in 3 projects that use this

  • Tsumugii24Skill

    split-to-prs

    Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.

    Also in 6 projects that use this

  • MicrosoftSkill

    create-hook

    Create a hook (.json) to enforce policy or automate agent lifecycle events.

    Also in 7 projects that use this

  • testdino-hqSkill

    shell

    Google's official Shell scripting style guide. Covers Bash scripting, naming conventions, error handling, portability, and shell best practices.

    Also in 7 projects that use this

  • +3 more from 0mlkrizzz655335v

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free