agentleFS
FiredMosquito831FiredMosquito831/my-writing-companion/skills/llm-writing/SKILL.md

llm-writing

Skill2 starsChanged 25 days agoApache-2.0View on GitHub

Load before writing or revising human-facing text. Choose words deliberately, ground the piece in the reader's context, and remove default LLM phrasing before the final draft.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 producing a written artifact:

    line 13
  2. Distinctive:

    Ground: Check any relevant source material, references, or notes before writing, and make sure they align.

    line 16
  3. Distinctive:

    Draft: Write a full draft to disk so you can edit it piece by piece.

    line 17

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

LLM Writing

Load /intent-modeling if it isn't already loaded. Load /information-hierarchy when the piece grows beyond a short answer.

Write Intentionally

Before producing a written artifact:

  1. Scope. What does the reader know when they start, and what should they know when they finish? What do they not need to know? Before writing, break the piece into beats: each beat is one move in the reader's journey, carrying one idea, purpose, or turn.
  2. Ground. Check any relevant source material, references, or notes before writing, and make sure they align.
  3. Draft. Write a full draft to disk so you can edit it piece by piece.
  4. Revise. Start with the whole artifact, then move inward: structure, beats, paragraphs, sentences, words. At each scale, ask what the writing is doing: is it correct, does it follow from what came before, and does the reader need it? Delete or rewrite anything that does not serve a purpose or give the reader something they need to understand or know. Move back and forth between scales: after a local change, zoom back out through the surrounding beat, larger structure, and full artifact; the change should still connect, and the rhythm should still vary. Check disclosure tiers: the answer still leads, depth hasn't crept forward, sources sit at the end.

What to Delete

  • Writing to fill a section because it exists. Delete it or merge its content where it belongs.
  • Labeling concepts without explaining how they work. Explain the mechanism or cut the label.
  • Stating conclusions without evidence. Show the evidence or drop the claim.
  • Hiding uncertainty behind confident language. Say what you don't know.
  • Softening every claim with qualifiers ("it's worth noting," "it's important to consider"). Say it or don't.
  • Repeating what you already said in different words, or summarizing the body as a conclusion ("In summary," "Overall"). Delete it.
  • Connecting ideas with transition words instead of meaning ("Moreover," "Furthermore," "Additionally"). If the relationship isn't clear without the word, restructure.
  • Pairing clauses where one half already carries the meaning ("It's not X, it's Y"). Keep the half that carries it.
  • Writing for the person who asked for the document instead of the person who will read it. Write for the reader.

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.