skill-package-builder
Skill2 starsChanged 4 months agoMITView on GitHub
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- Academic Paper SummarizationSkill
- Accessibility WCAG AuditSkill
- API Error TroubleshootingSkill
- CI/CD Pipeline TroubleshootingSkill
- Competitor Analysis SynthesisSkill
- Customer Onboarding AssistanceSkill
- Dependency Audit ResolutionSkill
- Docker Image OptimizationSkill
- GDPR Data MappingSkill
- genome-analyzerSkill
- incident-distillerSkill
- Kubernetes Pod DebuggingSkill
- nve-genome-explorerSkill
- OWASP Input ValidationSkill
- repo-auditorSkill
- research-packagerSkill
- rule-patcherSkill
- Secret Leak RemediationSkill
- skill-curatorSkill
- SOC2 Policy VerificationSkill
- tama-community-summarizerSkill
- Technology Stack EvaluationSkill
- Ticket Triage and RoutingSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 19
Check for overlapping or conflicting scopes.
- Distinctive: line 20
Write a small package JSON with activation policy and included skills.
- Distinctive: line 26
Keep the published runtime skill short and operational.
≈ “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
Skill Package Builder
Purpose
Compose admitted skills into compact, task-oriented packages that can be published to .agents/skills/.
Use when
- several admitted skills routinely co-activate,
- a maintainer needs a runtime-ready package,
- or metadata-first retrieval should resolve to a small operational surface.
Inputs
- admitted skill IDs,
- target package goal,
- guardrails for the task domain,
- optional publish target under
.agents/skills/.
Procedure
- Select only admitted skills.
- Check for overlapping or conflicting scopes.
- Write a small package JSON with activation policy and included skills.
- Publish a concise
SKILL.mdonly if the package is stable enough for runtime use. - Record
belong_to_packagerelations in the relation graph.
Guardrails
- Packages are for composition, not for hiding unresolved candidate skills.
- Keep the published runtime skill short and operational.
- Preserve metadata-first loading: package first, full skills only on match.
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.

