external-skill
Skill1 starsChanged 5 months agoMITView on GitHub
Example skill demonstrating the isolated sandbox-marker level. Use as a template when authoring third-party or marketplace skills. When you are about to install or reference a third-party skill from a marketplace or external source. This skill shows the canonical frontmatter pattern for sandbox.level: isolated.
In this repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- advanced-orchestrationSkill
- architect-agentSkill
- implementer-agentSkill
- quality-councilSkill
- reviewer-agentSkill
- tester-agentSkill
- writer-critic-pairSkill
- authoring-skillsSkill
- api-endpoint-qualitySkill
- async-job-qualitySkill
- auth-qualitySkill
- db-migration-qualitySkill
- frontend-state-qualitySkill
- acceptance-criteriaSkill
- adaptive-flowSkill
- adaptive-prompt-selectionSkill
- adversarial-code-reviewSkill
- architecture-decision-recordsSkill
- brainstormingSkill
- brownfield-spec-enhancementSkill
- bug-fix-lifecycleSkill
- checkpoint-validationSkill
- cicd-integrationSkill
- clarify-before-codeSkill
- claude-code-hooks-packSkill
- code-context-packSkill
- code-intelligence-reviewSkill
- context-policySkill
- context-rich-implementationSkill
- crash-proof-planningSkill
- critique-pass-protocolSkill
- dependency-aware-task-orderingSkill
- deprecation-migrationSkill
- disciplined-diagnosisSkill
- docs-authorSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- git-guardrailsSkill
- goal-driven-executionSkill
- grill-user-before-buildingSkill
- guard-bypass-protocolSkill
- improve-codebase-architectureSkill
- incremental-reviewSkill
- issue-slicingSkill
- lessons-learned-dbSkill
- loop-engineeringSkill
- model-aware-configSkill
- model-weakness-memorySkill
- multi-repo-learningSkill
- orchestration-workflowsSkill
- plan-driven-executionSkill
- plan-from-specSkill
- prd-from-contextSkill
- project-constitutionSkill
- prompt-architectureSkill
- prototype-before-commitmentSkill
- quality-engineSkill
- quality-execution-contractSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
When you are about to install or reference a third-party skill from a marketplace or external source.
- Distinctive: line 35
Verify the marketplace URL matches an allowlisted source.
- Very specific: line 36
Check the license (permissive/copyleft/proprietary).
- Very specific: line 38
Run npm run validate:sandbox-marker to confirm compliance.
- Very specific: line 39
Run npm run validate:injection to scan the imported content.
- Very specific: line 40
Run vibe-license-surface to update the project's NOTICE file.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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: External Skill (Example)
Purpose
Example skill demonstrating the isolated sandbox-marker level. Use as a template when authoring third-party or marketplace skills.
When to use
When you are about to install or reference a third-party skill from a marketplace or external source. This skill shows the canonical frontmatter pattern for sandbox.level: isolated.
Inputs
- Marketplace URL
- License metadata
- Provenance chain (signatures, hashes)
Workflow
- Verify the marketplace URL matches an allowlisted source.
- Check the license (permissive/copyleft/proprietary).
- Apply
sandbox: { level: isolated, isolation: network=block,fs=read-only,exec=none,audit=on }. - Run
npm run validate:sandbox-markerto confirm compliance. - Run
npm run validate:injectionto scan the imported content. - Run
vibe-license-surfaceto update the project's NOTICE file.
Outputs
- A sandboxed, licensed, audited external skill ready for use.
Failure modes
- Missing sandbox marker — gate FAIL. Apply the frontmatter above.
- Missing isolation policy — gate FAIL.
isolatedlevel requiresisolation:field. - Missing license — flag in NOTICE. Add
license:to frontmatter. - Provenance gap — refuse to import.
Verification checklist
- Frontmatter has
sandbox: { level: isolated, ... } content_sourcesis a YAML list of source patternsisolation:policy is setvalidate:sandbox-markerexits 0- License is declared and compatible
- Provenance is verified (signatures, hashes)
- NOTICE file is updated via
vibe-license-surface
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.

