agentleFS
Sign inStart free
blixvipblixvip/skills/1/SKILL.md

1

Skill4 starsChanged 3 months agoMITView on GitHub

Fast execution timebox for small, well-defined tasks. Use when the user invokes /1 and target completion within 3 minutes without reducing quality.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Use the simplest correct solution.

    line 17
  2. Distinctive:

    Do not over-plan or over-explain.

    line 18
  3. Distinctive:

    Avoid unnecessary exploration, refactors, research, or optional improvements.

    line 19
  4. Distinctive:

    Prefer editing directly over discussing intended edits.

    line 21
  5. Distinctive:

    Test the exact behavior changed.

    line 22
  6. Distinctive:

    Do not expand the task beyond the request.

    line 24
  7. Distinctive:

    If several valid approaches exist, choose the strongest straightforward option and execute it.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/1 — Quick

Complete the task as quickly as possible while preserving the normal quality bar.

Timebox

Target completion in under 3 minutes. This command changes execution strategy, not expected quality.

Behavior

  • Start immediately.
  • Use the simplest correct solution.
  • Do not over-plan or over-explain.
  • Avoid unnecessary exploration, refactors, research, or optional improvements.
  • Make reasonable assumptions when low-risk.
  • Prefer editing directly over discussing intended edits.
  • Test the exact behavior changed.
  • Fix obvious issues discovered during testing.
  • Do not expand the task beyond the request.

If several valid approaches exist, choose the strongest straightforward option and execute it. Finish with a very short summary of what changed and whether verification passed.

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.

Check your setup, free