agentleFS
cwhited26cwhited26/pocket-agent-starter-skills/skills/voice/lead-with-the-action/SKILL.md

lead-with-the-action

Skill0 starsChanged 4 months agoMITView on GitHub

Put the claim, the finding, or the ask in the first sentence — then explain. Never bury the point in the middle. Every draft, every reply, every brief. The longer the piece, the more it matters.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Write the point first. The claim, the answer, the thing you need them to do — sentence one.

    line 20
  2. Distinctive:

    Put the reasoning after, not before.

    line 21
  3. Distinctive:

    If there's an ask, it lives in the first or last sentence — never the middle, never after a hedge.

    line 22
  4. Distinctive:

    Read the first sentence alone.

    line 24

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

Lead With the Action

Declare before you explain. The first sentence of a paragraph is the point; the next two or three are the why. The reader should know the conclusion by sentence one.

The technique

  • Write the point first. The claim, the answer, the thing you need them to do — sentence one.
  • Put the reasoning after, not before. Context that leads up to a point makes the reader wait; context that follows a point makes sense.
  • If there's an ask, it lives in the first or last sentence — never the middle, never after a hedge.
  • Cut the runway. "I wanted to reach out because" and "After giving this some thought" are throat-clearing. Delete them and start at the point.
  • Read the first sentence alone. If it doesn't carry the message, you buried it — move the real point up.

Do this, not that

Do: "The roof passed inspection — we're clear to invoice." Then the detail: what was checked, what's next.

Don't: "So I went out this morning and spent some time looking at a few things on the property, and after walking the whole roof and checking the flashing, I think we're probably in good shape to move forward with billing."

Why this works

People skim. They read the first sentence of every paragraph and stop when they have what they need. If the point is in the middle, half your readers never reach it. Leading with the action respects that — they get the conclusion immediately and read the why only if they want it.

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.