_template
Skill1 starsChanged 4 months agoMITView on GitHub
Describe who this AI is acting as, in 2-4 sentences. This is the identity that persists across every task the skill is used for. You can inject {{VARIABLES}} here to make the persona adaptable (e.g., "You are an expert in {{DOMAIN}}."). Anything else a future maintainer needs to know: known failure modes, edge cases, or model-specific quirks. Remember to list all {{VARIABLES}} used in this file inside the config.yaml's variables: array.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- apify/awesome-skillstheir own version, first seen Nov 6, 2026
- 0xSneaks/grok-skills-marketplacetheir own version, first seen Nov 1, 2026
- modimihir07/agentic-ostheir own version, first seen Oct 25, 2026
- DevelopmentFinanceObservatory/skillstheir own version, first seen Oct 17, 2026
- spectrayan/carefoldtheir own version, first seen Oct 2, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- apify/awesome-skills★ 293same name
- modimihir07/agentic-os★ 209same name
- ishandutta2007/Awesome-Claude-Skills★ 16same name
- selic/skills★ 2same name
- spectrayan/carefold★ 2same name
- Yedidyar/agent-skills★ 2same name
- an-lee/agentic-commands★ 1same name
- andrewluxem/klaviyo-lifecycle-skills★ 1same name
- gokhanamal/ai-context★ 1same name
- jiriforman/skills★ 1same name
7 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 repository45 other files it gives its agents.
- accessibility-auditorSkill
- adr-chroniclerSkill
- api-translatorSkill
- brand-voice-cloneSkill
- chaos-simulatorSkill
- cli-compilerSkill
- code-reviewerSkill
- commit-historianSkill
- compliance-wardenSkill
- conceptual-brainstormerSkill
- context-janitorSkill
- cot-auditorSkill
- cynical-copy-editorSkill
- data-parserSkill
- data-scientistSkill
- dependency-hunterSkill
- devils-advocateSkill
- devops-engineerSkill
- executive-summarizerSkill
- feynman-tutorSkill
- general-assistantSkill
- historical-analystSkill
- icp-simulatorSkill
- interaction-designerSkill
- jailbreak-redteamerSkill
- meta-prompt-engineerSkill
- onboarding-guideSkill
- orchestration-agentSkill
- product-managerSkill
- refactoring-specialistSkill
- regex-expertSkill
- reverse-engineerSkill
- security-auditorSkill
- self-correction-criticSkill
- senior-architectSkill
- socratic-guideSkill
- sql-optimizerSkill
- state-machineSkill
- synthesis-engineSkill
- taxonomy-builderSkill
- technical-writerSkill
- ui-ux-designerSkill
- unit-test-generatorSkill
- vc-screenerSkill
- vector-query-optimizerSkill
The file
Files
Skill Name
Persona
Describe who this AI is acting as, in 2-4 sentences. This is the identity that persists across every task the skill is used for. You can inject {{VARIABLES}} here to make the persona adaptable (e.g., "You are an expert in {{DOMAIN}}.").
Scope
- IS for: What this skill is designed to handle (e.g., parsing, reviewing, writing).
- NOT for: Explicit boundaries of what the skill must never do.
System Instructions
<Paste the exact system prompt text here. This is what goes in the "system" role of the API call, separate from any per-task user input.>
### Core Directives:
1. Directive one.
2. Directive two.
### Context:
<Use {{VARIABLE_NAME}} placeholders here to inject dynamic requirements from the config.yaml file>
### Output Format:
<Explicitly define how the AI should structure its output, ideally using XML tags like <thought_process> and <final_result> to ensure reasoning before answering.>Notes
Anything else a future maintainer needs to know: known failure modes, edge cases, or model-specific quirks. Remember to list all {{VARIABLES}} used in this file inside the config.yaml's variables: array.
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.

