implement-claude-extensions
Skill1 starsChanged 9 months agoApache-2.0View on GitHub
Choose and implement the right Claude extension type by comparing hooks, skills, sub-agents, agent teams, and plugin packaging patterns.
In this repository8 other files it gives its agents.
- implement-agent-skillsSkill
- implement-agent-teamsSkill
- implement-hooksSkill
- implement-pluginSkill
- implement-sub-agentsSkill
- lint-fixSkill
- plugin-implementation-deprecatedSkill
- plugin-verificationSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this umbrella skill to choose the correct extension type and route implementation to the appropriate component skill.
- Distinctive: line 10
Core Principle: Start simple. Use the decision framework to score task complexity (0-10) and match to the simplest component type that …
- Distinctive: line 37
Validate choice: Ask "Can this be done more simply?"
- Distinctive: line 41
Apply lifecycle checks: Follow design → implement → evaluate → verify
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Implement Claude Extensions
Use this umbrella skill to choose the correct extension type and route implementation to the appropriate component skill.
Core Principle: Start simple. Use the decision framework to score task complexity (0-10) and match to the simplest component type that meets requirements.
Complexity-Based Selection
| Score | Component Type | When to Use |
| 1-3 | Simple Skill | Single deterministic task, no branching logic |
| 4-6 | Workflow Skill | Multi-step with some conditional logic |
| 7-8 | Sub-Agent | Model-driven decisions, flexible approach needed |
| 9-10 | Agent Team | Multiple specialized domains, complex coordination |
See references/decision-framework.md for detailed scoring guide.
Comparison
| Extension Type | Best For | Primary Artifacts | Component Skill |
| Hooks | Event-driven automation/guardrails | hooks/hooks.json, hook scripts | ../implement-hooks/SKILL.md |
| Agent Skills | Reusable task playbooks | skills/<name>/SKILL.md | ../implement-agent-skills/SKILL.md |
| Sub-Agents | Specialized delegated roles | agents/*.md | ../implement-sub-agents/SKILL.md |
| Agent Teams | Coordinated multi-agent execution | team config + coordination docs | ../implement-agent-teams/SKILL.md |
| Plugins | Packaging/distribution + wiring | .claude-plugin/plugin.json | ../implement-plugin/SKILL.md |
Workflow
- Assess complexity: Score task complexity using decision framework (0-10)
- Start simple: Choose simplest component type that meets requirements
- Validate choice: Ask "Can this be done more simply?"
- Identify constraints: Determine specific requirements and boundaries
- Plan evaluations: Define 20-50 test cases for validation
- Route implementation: Hand off to appropriate component skill
- Apply lifecycle checks: Follow design → implement → evaluate → verify
Progressive Disclosure
Best Practices (Anthropic Guidelines)
- START HERE - Complexity scoring & decision framework:
references/decision-framework.md - Context management patterns:
references/context-management.md - Evaluation strategy:
references/evaluation-strategy.md
Component Selection
- Extension comparison details:
references/extension-types.md - Decision guide:
references/when-to-use.md - Cross-component patterns:
references/cross-component-patterns.md - Lifecycle from design to verification:
references/extension-lifecycle.md
Component Skills
../implement-hooks/SKILL.md../implement-agent-skills/SKILL.md../implement-sub-agents/SKILL.md../implement-agent-teams/SKILL.md../implement-plugin/SKILL.md
Sources
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.

