cracked
AGENTS.md5 starsChanged 7 days agoMITView on GitHub
This repo is a pack of Agent Skills for tech placement and interview prep. It's documentation-as-code: every skill is a Markdown file.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository20 other files it gives its agents.
- website/AGENTS.mdAGENTS.md
- company-intelSkill
- cracked-profileSkill
- setup-crackedSkill
- core-vivaSkill
- defend-my-projectSkill
- hr-roundSkill
- mock-interviewSkill
- oa-simSkill
- pattern-coachSkill
- system-design-mockSkill
- github-glowupSkill
- jd-matchSkill
- make-it-hireableSkill
- referral-dmSkill
- resume-blueprintSkill
- roast-my-resumeSkill
- offer-decodeSkill
- prep-planSkill
- rejection-reviewSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Read CONTRIBUTING.md for conventions before editing a skill.
- Very specific: line 6
After any change, run node scripts/validate.mjs.
- Very specific: line 7
Keep version identical in package.json and .claude-plugin/plugin.json, and add a CHANGELOG.md entry.
- Distinctive: line 8
Don't add dependencies. The validator is intentionally zero-dependency.
- Very specific: line 9
Use scripts/link-skills.sh to test skills live, and scripts/release.sh <version> to cut a release.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
Working on this repo
This repo is a pack of Agent Skills for tech placement and interview prep. It's documentation-as-code: every skill is a Markdown file.
- Read
CONTRIBUTING.mdfor conventions before editing a skill. - After any change, run
node scripts/validate.mjs. It must pass. - Keep
versionidentical inpackage.jsonand.claude-plugin/plugin.json, and add aCHANGELOG.mdentry. - Don't add dependencies. The validator is intentionally zero-dependency.
- Use
scripts/link-skills.shto test skills live, andscripts/release.sh <version>to cut a release.
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.