super-skill
Skill1 starsChanged 7 months agoMITView on GitHub
Domain expert layer. Loads full context, methodology, and operational knowledge for the defined domain. Gives any AI agent complete understanding before any action is taken.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- grooverLab/stashtheir own version, first seen Oct 20, 2026
- sdsrss/super-skilltheir own version, first seen Jul 12, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- grooverLab/stash★ 0same name
- sdsrss/super-skill★ 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- template/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- template/CLAUDE.mdCLAUDE.md
- super-skillSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Read these files in this order:
- Distinctive: line 21
Never skip this sequence. Context before action, always.
- Very specific: line 29
After reading the three required files above, load the remaining layer files as needed for the current task: DOMAIN_MAP.md - structure and …
- Distinctive: line 46
Before proposing any change, load the files most likely to contain relevant evidence for your task type.
- Distinctive: line 64
All prompts live in ONBOARDING.md.
≈ “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
Super Skill - Agent Entry Point
<!-- Replace this header with your own project/organization name -->Before Any Action
Read these files in this order:
- CONTEXT.md - who owns this, what domain, what goals
- CURRENT_STATE.md - what the domain looks like right now
- PENDING.md - what is waiting for user approval
Never skip this sequence. Context before action, always.
Operating Principle
Iron Principle: propose → PENDING.md → user decides → system executes.
Domain Files
After reading the three required files above, load the remaining layer files as needed for the current task: DOMAIN_MAP.md - structure and sub-domain relationships EVALUATION.md - criteria for evaluating new entrants DECISIONS.md - decisions made and reasoning MONITORING.md - sources to watch for drift LEARNING.md - NotebookLM integration structure LOG.md - change log and audit trail experts/COUNCIL.md - active expert council and debates traces/ - execution traces for causal reasoning wiki/graph.json - domain structure map (optional; run /ss-graph to generate)
Individual expert profiles (experts/[name].md) load on demand only, not by default. Load them when a specific expert's perspective is needed.
Evidence Routing
Before proposing any change, load the files most likely to contain relevant evidence for your task type. This prevents blind proposals.
| Task type | Evidence files (load in order) |
| Evaluate a new tool/method | EVALUATION.md, CURRENT_STATE.md, DECISIONS.md |
| Propose architecture change | DECISIONS.md, DOMAIN_MAP.md, CURRENT_STATE.md |
| Investigate drift or breakage | MONITORING.md, CURRENT_STATE.md, traces/ |
| Resolve a PENDING item | PENDING.md, DECISIONS.md, EVALUATION.md |
| Generate learning content | LEARNING.md, CONTEXT.md, CURRENT_STATE.md |
| Root-cause analysis | traces/, DECISIONS.md, LOG.md |
| Cross-domain impact check | DOMAIN_MAP.md, CURRENT_STATE.md, DECISIONS.md |
| Expert disagreement | experts/COUNCIL.md, DECISIONS.md, experts/[name].md |
Load the minimum set. Do not load files not listed for your task type.
How Prompts Work
All prompts live in ONBOARDING.md. Claude Code reads and runs them automatically. Users do not copy prompts after the initial Bootstrap setup.
Slash commands: see CLAUDE.md
Capabilities
Operating rules and capabilities: see CLAUDE.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.