create-agent
Skill0 starsChanged 7 months agoMITView on GitHub
Use this skill when creating, modifying, or debugging a custom Copilot agent (.agent.md file). Provides detailed patterns for agent orchestration, handoffs, sub-agent invocation, tool configuration, variable extraction, and prompt structure. Invoke when the user says "create an agent", "add a new agent", "agent handoffs", "sub-agent", or "orchestrate agents".
38 other projects use a version of this.
Adopted by
Most recently taken up by
- lalulali/vespyrtheir own version, first seen Nov 6, 2026
- cognitedata/builder-skillstheir own version, first seen Nov 4, 2026
- harness/harness-skillstheir own version, first seen Nov 1, 2026
- fxmartin/claude-code-configtheir own version, first seen Oct 31, 2026
- agno-agi/agentos-dockertheir own version, first seen Oct 30, 2026
- agno-agi/agentos-flytheir own version, first seen Oct 30, 2026
Used with
Projects with it also use deploy-platform, setup-platform and 9 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.
agno-agiSkilldeploy-platform
Deploy this AgentOS using its own provider instructions, configure JWT verification, and verify the public service. Use for first deployment, redeployment, or production configuration changes.
Also in 5 projects that use this
agno-agiSkillsetup-platform
Set up this AgentOS from a fresh clone — confirm Docker, configure .env, boot the containers, prove the MCP endpoint live, connect the AgentOS UI, then build the user's first agent. Use when the user asks to set up the platform, get started, or bring this repo up on a new machine.
Also in 5 projects that use this
ElasticSkillcreate-integration
Use when creating a new Elastic integration package, scaffolding data streams, answering package layout or structure questions, or running the end-to-end integration build workflow. Covers package topology, scaffold commands, post-scaffold edits, and full orchestration of CEL/pipeline/test subagents.
Also in 3 projects that use this
MicrosoftSkillcreate-hook
Create a hook (.json) to enforce policy or automate agent lifecycle events.
Also in 5 projects that use this
AnasX7Skillimprove
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
Also in 5 projects that use this
ElasticSkillcreate-skill
Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.
Also in 13 projects that use this
- +3 more from agno-agi
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
- microsoft/vscode★ 195ksame name
- gnekt/My-Brain-Is-Full-Crew★ 3.9ksame name
- EvolutionAPI/evo-nexus★ 545same name
- evolution-foundation/evo-nexus★ 535same name
- openma-ai/open-managed-agents★ 348same name
- luanmorenommaciel/agentspec★ 256same name
- harness/harness-skills★ 127same name
- microsoft/copilot-studio-plugin★ 82same name
- Azure-Samples/art-voice-agent-accelerator★ 74same name
- TOKTOKHAN-DEV/agent-company★ 74same name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/tta-dev.mdcCursor rule
- build-test-verifySkill
- core-conventionsSkill
- create-atomic-noteSkill
- create-pull-requestSkill
- git-commitSkill
- sdd-workflowSkill
- self-review-checklistSkill
- session-startSkill
- build-test-verifySkill
- core-conventionsSkill
- create-atomic-noteSkill
- create-pull-requestSkill
- Feature DevelopmentSkill
- git-commitSkill
- Incident ResponseSkill
- Package ReleaseSkill
- sdd-workflowSkill
- self-review-checklistSkill
- session-startSkill
- ttadev-llmSkill
- ttadev-primitivesSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Create .github/agents/my-agent.agent.md with frontmatter
- Distinctive: line 28
Write the body following the Role → Responsibilities → Constraints pattern
- Very specific: line 29
Add entry to .github/copilot-catalog.yml with skill_refs and workflow_refs
“Common” is measured: kept by at least 6 in 10 of the 35 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.
Files
Create Agent
Detailed reference for building custom Copilot agents in TTA.dev.
For atomic rules (naming, frontmatter, registration), see the agents instruction.
When to Use This Skill
- Creating a new
.agent.mdfile from scratch - Adding handoffs between agents for workflow transitions
- Setting up sub-agent orchestration (multi-step pipelines)
- Configuring tool access and MCP server integration
- Designing agent prompt structure with dynamic variables
Prerequisites
- Understand the composition model
- Know which skills and workflows your agent needs (check
.github/copilot-catalog.yml) - Have the target agent's role and responsibilities defined
Quick Start
- Create
.github/agents/my-agent.agent.mdwith frontmatter - Write the body following the Role → Responsibilities → Constraints pattern
- Add entry to
.github/copilot-catalog.ymlwithskill_refsandworkflow_refs - Validate:
uv run python scripts/validate-catalog.py
Reference Docs
- Handoffs and Orchestration — workflow transitions, sub-agent patterns
- Tool Configuration — aliases, MCP namespaces, strategies
- Prompt Patterns — variables, body structure, best practices
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
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.

