agent-skills / rules
Cursor rule0 starsChanged 2 months agoMITView on GitHub
Try PAT/SSH/API/MCP before asking the user for manual browser or terminal steps
- Reads credentials
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,329 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 repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/finish-task-dev-server.mdcCursor rule
- brainstormingSkill
- caveman-commitSkill
- find-skillsSkill
- semantic-versionSkill
- systematic-debuggingSkill
- verification-before-completionSkill
- writing-plansSkill
- ask-before-architectureSkill
- automate-before-manualSkill
- caveman-commitSkill
- diagrams-mermaidSkill
- dont-be-lazySkill
- dont-forgetSkill
- find-jobSkill
- finish-with-dev-serverSkill
- google-calendar-mcpSkill
- init-fmzSkill
- instagram-chrome-postSkill
- project-initSkill
- recapSkill
- semantic-versionSkill
- skills-sh-maintainerSkill
- ui-change-e2eSkill
- validate-before-shareSkill
The file
We split this automate-before-manual.mdc into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 8
Before asking the user to click, log in, configure DNS, or run something in their terminal:
- Distinctive: line 16
Never send a manual checklist without trying API, vault, and MCP first.
≈ “Common” is an estimate: at least 1 in 5 of the 6,873 Cursor rule 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
--- description: Try PAT/SSH/API/MCP before asking the user for manual browser or terminal steps alwaysApply: true --- # Automate before manual Before asking the user to click, log in, configure DNS, or run something in their terminal: 1. **Read skill** `automate-before-manual` (`.agents/skills/`) — if the user says lazy or "you do it", also follow `dont-be-lazy`. 2. **Try automation** — `gh`, scripts in `docs/` and `scripts/`, MCP (`GetDynamicTools`), official APIs. 3. **Secrets vault** (relative to project root): `../secrets/github/pat.txt`, `../secrets/vps/ssh/`, `../secrets/projects/<app>.env`. Check `AGENTS.md` or `secrets.local.md` if the layout differs. 4. **Scope before asking** — state which role/scope unlocks full automation (GitHub repo scope, Azure Contributor, etc.). 5. **Escalate once** — only for OAuth, 2FA, captcha, or billing; then use `dont-be-lazy` browser fallback. Never send a manual checklist without trying API, vault, and MCP first.
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.

