agentleFS
cwhited26cwhited26/pocket-agent-starter-skills/skills/voice/specific-over-generic/SKILL.md

specific-over-generic

Skill0 starsChanged 4 months agoMITView on GitHub

Name the person, the dollar amount, the date, the file. Replace \"stakeholders,\" \"soon,\" and \"several\" with the real thing. Always. Every claim, every plan, every follow-up. If a real detail exists, use it.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you don't have the specific, name the gap plainly: "I don't have the close date yet" — not a fuzzy stand-in.

    line 24

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

Specific Over Generic

Specificity is the difference between writing that lands and writing that evaporates. If a number, a name, or a date exists, use it. If it doesn't, say so — don't paper over the gap with "many" or "several."

The technique

  • Swap vague nouns for real ones: not "the stakeholders," but "Sarah and the two crew leads."
  • Swap vague time for real time: not "soon" or "shortly," but "Thursday" or "by the 15th."
  • Swap vague quantity for the count: not "several leads," but "four leads," or pull the actual number from the brain.
  • Cite the source inline: the customer's name, the dollar figure, the date of the call. Receipts beat adjectives.
  • When you don't have the specific, name the gap plainly: "I don't have the close date yet" — not a fuzzy stand-in.

Do this, not that

Do: "Dana signed the 12-month plan on the 3rd; her first invoice goes out on the 1st."

Don't: "The client made a significant payment and there are some ongoing costs that will recur periodically."

Why this works

Generic writing could be about anyone, so it convinces no one. A specific number or name proves you actually know the situation — it's a receipt, not a claim. The owner trusts work that names things, because vagueness is what people hide behind when they don't have the facts.

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.