agentleFS
sithumdgomezsithumdgomez/claude-skills/.claude/skills/agent-creator/SKILL.md

agent-creator

Skill0 starsChanged 56 days agoNo licenceView on GitHub

Create, configure, and error-test a custom Claude Code subagent (a `.claude/agents/*.md` definition) through a guided goal → plan → build → test loop. Use whenever the user wants to build or create a new agent/subagent, says "make an agent that…", wants to turn a repeated job into a reusable worker, scaffold a specialist (reviewer, researcher, builder, store-builder, content agent), or set up custom `.claude/agents` definitions — trigger even if they only describe a recurring job without saying the word "agent". Writes the frontmatter (name, description, least-privilege tools, model) and an engineered system prompt, then spawns the new agent on sample tasks to confirm it triggers correctly and stays in its lane. NOT for creating Skills (use `skill-creator`) or API/hosted "Managed Agents" (that's the Claude API surface).

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use crypto-intelligence, heart 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.
  • Arcanea-LabsSkill

    crypto-intelligence

    Vertical-tier skill for Crypto Intelligence Domain Sub-Stack. Auto-activates inside verticals/crypto-intelligence/ or on /crypto-* commands. Enforces R5 non-advisory clause, voice (architect), refusal patterns, composition with Wealth IS umbrella per Board 2026-05-17. Loads verticals/crypto-intelligence/SKILL.md wrapper for full doctrine.

    Also in 3 projects that use this

  • Arcanea-LabsSkill

    heart

    Ops health monitor for the machine substrate. Checks Memory Bus, brain_watchdog, Voice Operator, dashboard, audit-log freshness, and scheduled tasks. Cross-cutting skill that any repo can invoke when daemons feel off or before starting a heavy work session.

    Also in 3 projects that use this

  • +10 more from Arcanea-Labs

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    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 27 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.