agentleFS
farukzahrafarukzahra/agent-skills/.cursor/rules/automate-before-manual.mdc

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

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
  1. Distinctive:

    Before asking the user to click, log in, configure DNS, or run something in their terminal:

    line 8
  2. Distinctive:

    Never send a manual checklist without trying API, vault, and MCP first.

    line 16

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
automate-before-manual.mdc
---
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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.