skill-boilerplate
Skill12 starsChanged 9 months agoMITView on GitHub
Define a standard per-skill local data layout at <project_root>/.skills-data/<skill-name> and required SKILL.md guidance for env/config/deps/tools. Use when starting a new skill and you must specify where to store data, env files, local binaries, and dependencies.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- colomet/skill-boilerplatetheir own version, first seen Sep 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- colomet/skill-boilerplate★ 0same name
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 repository81 other files it gives its agents.
- ab-test-setupSkill
- agent-browserSkill
- analytics-trackingSkill
- brainstormingSkill
- browser-useSkill
- c4-architectureSkill
- code-reconSkill
- competitor-alternativesSkill
- copy-editingSkill
- copywritingSkill
- crafting-effective-readmesSkill
- dflowSkill
- drift-protocolSkill
- email-sequenceSkill
- enterprise-readinessSkill
- epub-translateSkill
- example-skillSkill
- form-croSkill
- free-tool-strategySkill
- git-workflowSkill
- heliusSkill
- hugging-face-cliSkill
- hugging-face-tool-builderSkill
- hugging-face-evaluationSkill
- hugging-face-paper-publisherSkill
- kaminoSkill
- launch-strategySkill
- magicblockSkill
- marketing-ideasSkill
- marketing-psychologySkill
- mermaid-diagramsSkill
- meteoraSkill
- hugging-face-model-trainerSkill
- n8n-code-javascriptSkill
- n8n-code-pythonSkill
- n8n-expression-syntaxSkill
- n8n-mcp-tools-expertSkill
- n8n-node-configurationSkill
- n8n-validation-expertSkill
- n8n-workflow-patternsSkill
- obsidian-vault-managerSkill
- onboarding-croSkill
- openai-knowledgeSkill
- page-croSkill
- paid-adsSkill
- paywall-upgrade-croSkill
- pinocchio-developmentSkill
- popup-croSkill
- pricing-strategySkill
- programmatic-seoSkill
- raydiumSkill
- referral-programSkill
- remotion-best-practicesSkill
- schema-markupSkill
- seo-auditSkill
- signup-flow-croSkill
- social-contentSkill
- solana-agent-kitSkill
- solana-kit-migrationSkill
- solana-kitSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 10
Document the mandatory local data layout and instructions to embed in new skills.
- Very specific: line 15
If <skill-root>/.. is skills, guess project_root as two levels above the skills folder (i.e.
- Distinctive: line 17
Ask the user to confirm the guess.
- Very specific: line 18
If the skill is not under a skills directory, do not guess.
- Very specific: line 41
Write these keys into .skills-data/<skill-name>/.env:
- Very specific: line 61
If a skill needs setup automation, add helper scripts under that skill's scripts/ directory.
- Very specific: line 65
If a skill needs system utilities (rg, jq, git), document manual install commands and reference references/os-install.md.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Boilerplate
Purpose
Document the mandatory local data layout and instructions to embed in new skills. This skill does not create any folders or files.
Determine project_root and data dir
- Let
<skill-root>be the folder containing SKILL.md. - If
<skill-root>/.. isskills, guess project_root as two levels above theskillsfolder (i.e.<skill-root>/../../..). - This works when skills are stored as <project_root>/
<container>/skills/<skill-name>, where<container>can be .codex, .claude, .github, or any other parent. - Ask the user to confirm the guess; if it is wrong, request project_root.
- If the skill is not under a
skillsdirectory, do not guess; ask the user for project_root. - Data dir: <project_root>/.skills-data/
<skill-name>/.
Mandatory SKILL.md section (copy into every new skill)
## Local data and env
- Store all mutable state under <project_root>/.skills-data/<skill-name>/.
- Keep config and registries in .skills-data/<skill-name>/ (for example: config.json, <feature>.json).
- Use .skills-data/<skill-name>/.env for SKILL_ROOT, SKILL_DATA_DIR, and any per-skill env keys.
- Install local tools into .skills-data/<skill-name>/bin and prepend it to PATH when needed.
- Install dependencies under .skills-data/<skill-name>/venv:
- Python: .skills-data/<skill-name>/venv/python
- Node: .skills-data/<skill-name>/venv/node_modules
- Go: .skills-data/<skill-name>/venv/go (modcache, gocache)
- PHP: .skills-data/<skill-name>/venv/php (cache, vendor)
- Write logs/cache/tmp under .skills-data/<skill-name>/logs, .skills-data/<skill-name>/cache, .skills-data/<skill-name>/tmp.
- Keep automation in <skill-root>/scripts and read SKILL_DATA_DIR (default to <project_root>/.skills-data/<skill-name>/).
- Do not write outside <skill-root> and <project_root>/.skills-data/<skill-name>/ unless the user requests it.Environment variables
Write these keys into .skills-data/<skill-name>/.env:
- SKILL_ROOT: absolute path to the skill directory
- SKILL_NAME: skill name
- SKILL_DATA_ROOT: absolute path to <project_root>/.skills-data
- SKILL_DATA_DIR: absolute path to <project_root>/.skills-data/
<skill-name>
Optional language-specific keys (use only if the skill needs that runtime):
- PYTHON_VENV
- NODE_PATH
- NPM_CONFIG_CACHE
- GOMODCACHE
- GOCACHE
- COMPOSER_CACHE_DIR
- COMPOSER_VENDOR_DIR
- COMPOSER_HOME
Boilerplate helper functions
If a skill needs setup automation, add helper scripts under that skill's scripts/ directory. Keep them opt-in and document them in that skill's SKILL.md. Use references/boilerplate-functions.md for copy-ready snippets.
OS utilities (optional)
If a skill needs system utilities (rg, jq, git), document manual install commands and reference references/os-install.md.
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.

