replace-with-directory-name
Skill3 starsChanged 54 days agoMITView on GitHub
State the matching task, paths, required preconditions, and important non-matching tasks.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 11
Stop when any required item is missing.
- Distinctive: line 15
Read the named source and tests.
- Distinctive: line 18
Run the verified focused check.
- Distinctive: line 27
Stop outside the stated scope.
- Distinctive: line 29
Do not claim success when validation did not run.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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 name
Preconditions
- Name required repository state, inputs, permissions, and reviewer.
- Stop when any required item is missing.
Procedure
- Read the named source and tests.
- Map acceptance criteria to results you can inspect.
- Make the smallest permitted change.
- Run the verified focused check.
- Report results and request review.
Validation
Name the exact test, manual check, and results needed for success.
Failure behavior
- Stop outside the stated scope.
- Report command failures.
- Do not claim success when validation did not run.
Maintenance
Name the owner, failure behavior, and events that require review.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- sessions/session-m2-03-spaces-and-context/lab/solution/ecommerce-project/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m2-03-spaces-and-context/lab/solution/instructions-lab/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m3-02-cloud-agent/lab/starter/copilot-instructions.mdCopilot instructions
- sessions/session-m5-03-hve-core-challenge/lab/solution/decision-api/.github/copilot-instructions.mdCopilot instructions
- baoyu-infographicSkill
- diagram-creatorSkill
- docxSkill
- excalidraw-diagramSkill
- humanize-contentSkill
- impeccableSkill
- pdfSkill
- pptxSkill
- rvap-brandSkill
- skill-creatorSkill
- xlsxSkill
- impeccableSkill
- session-format-validatorSkill
- deploymentSkill
- api-designSkill
- grillingSkill
- grill-meSkill
- deploymentSkill
- decision-interviewSkill
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.

