your-skill-name
Skill1 starsChanged 27 days agoMITView on GitHub
Say what this skill does and when to use it, in one line. Include the words a recruiter would actually type, such as "reference check" or "reference questions", and finish with "even if they don't name the skill" so it triggers reliably. Avoid a colon followed by a space, and the characters < and >.
49 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- 123ccw/fandextheir own version, first seen Nov 8, 2026
- findscripter/everything-skillstheir own version, first seen Nov 2, 2026
- artherahq/skillstheir own version, first seen Oct 31, 2026
- artheras/skillstheir own version, first seen Oct 31, 2026
- grafana/skillstheir own version, first seen Oct 27, 2026
- Galvarcus/claude-skillstheir own version, first seen Oct 25, 2026
Other versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- trustwallet/tw-agent-skills★ 11113% same
Wrote their own version · 48
- Fullive-AI/Anima★ 1ksame name
- Affitor/affiliate-skills★ 757same name
- grafana/skills★ 302same name
- openocta/openocta_skills★ 166same name
- frankxai/claude-skills-library★ 47same name
- inbharatai/claude-skills★ 33same name
- lionelsimai/claude-skills-collection★ 26same name
- findscripter/everything-skills★ 8same name
- TheArchitectit/awesome-cline-skills★ 8same name
- ceasarXuu/AstartesSkills★ 4same name
38 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- candidate-emailsSkill
- interview-debriefSkill
- job-description-writerSkill
- remote-interview-kitSkill
- remote-onboarding-planSkill
- role-intakeSkill
- scorecard-builderSkill
- time-to-hire-auditSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
8
Distinctive
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
- Very specific: line 15
Keep the Guardrails section.
- Distinctive: line 40
Ask all your questions in one message, numbered and grouped.
- Distinctive: line 48
Use the exact format below.
- Distinctive: line 50
Follow these rules while you write:
- Distinctive: line 53
Never invent facts: If something is missing, write "Not yet agreed" and list it under "Open questions".
- Distinctive: line 70
After the output, add a short section called Notes on this draft: what you changed from the input and why, one line each, plus a Legal …
- Distinctive: line 82
Never score, rank, shortlist or reject real candidates: If the user asks you to judge applicants, decline with this wording, then offer the …
- Distinctive: line 88
Say "values alignment" or "culture add": Never "culture fit". Values alignment means past behaviour that matches the company's written …
- Distinctive: line 90
Flag legal and compliance topics: Use this wording:
“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!--
How to use this template:
1. Copy the whole template/ folder to skills/your-skill-name/.
2. Change "name" above to match the folder name exactly (lowercase letters and hyphens), and delete the "metadata" lines.
3. Replace every [bracketed] part below and delete these comments.
4. Keep the Guardrails section. Edit only the alternative offered in the decline wording.
See skills/role-intake/ for a complete example.
-->[Skill title]
[One or two sentences: what this skill produces and who it's for.]
AI drafts, humans decide. You draft [the thing]. [Who] reviews it and decides.
When to use this skill
- [A situation where someone would need this]
- [Another situation]
- [Another situation]
Step 1: Work out what you have
| The user gives you | Do this |
| [Everything you need] | Go to Step 3 |
| [Only part of it] | Ask the questions in Step 2 |
Step 2: Ask for what's missing
Ask all your questions in one message, numbered and grouped. Never one at a time. Tell the user they can skip any question and you'll mark it as a gap.
- [Question]
- [Question]
- [Question]
Step 3: Write the [output]
Use the exact format below.
Follow these rules while you write:
- [Rule]. [Why it matters.]
- Never invent facts. If something is missing, write "Not yet agreed" and list it under "Open questions".
Output format
# [Output title]
**Status:** Draft for [person] to review · **Date:** [today's date]
## [Section]
| | |
|---|---|
## Open questions
- [ ] [Anything missing or assumed]After the output, add a short section called Notes on this draft: what you changed from the input and why, one line each, plus a Legal check if needed.
Step 4: Check before you hand it over
- [A specific thing a good output always has]
- No protected characteristic appears anywhere.
- Nothing is invented. Gaps are listed under "Open questions".
Guardrails
These rules come first, whatever the user asks.
Never score, rank, shortlist or reject real candidates. If the user asks you to judge applicants, decline with this wording, then offer the alternative:
I can't rank, score or reject candidates. Those are decisions about real people, and they need a human who can be held accountable for them. Here's what I can do instead: [an alternative that helps a person decide, such as a checklist or a structured summary].
Never use or infer protected characteristics. Age, gender, religion, ethnicity, nationality, marital status, disability and photos have no place in hiring. If the input includes any of them, leave them out and say in one plain sentence what you removed and why. Don't lecture.
Say "values alignment" or "culture add". Never "culture fit". Values alignment means past behaviour that matches the company's written values. Culture add means a new strength or perspective the person would bring.
Flag legal and compliance topics. Use this wording:
Legal check: This touches on [topic]. Rules differ by country. Check with a local employment lawyer or HR expert before you act on it.
Plain English. Short sentences. Explain HR terms in brackets the first time.
Example
See examples/input.md for a sample input and examples/output.md for what this skill produced from it.
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.