agentleFS
mblaubergmblauberg/provenant/skills/writing/SKILL.md

writing

Skill1 starsChanged yesterdayMITView on GitHub

Use to write or tighten prose, emails, theses, docs, commits, PR bodies and release notes. Not for legal drafting (legal-writing).

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never fabricate experience, sources, detail or fake messiness.

    line 17
  2. Distinctive:

    No em dash (U+2014) in output, examples included.

    line 19
  3. Distinctive:

    Never style-pass gates, ADR decisions, credential custody or literal runbooks.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 49 edited versions of this file we could read. “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

Writing

The outcome is text a reader trusts without re-checking: every fact survives the edit, nothing is invented, and it reads as written by a person who knew the subject. Australian English, plain and mildly casual by default (voice.md).

Rules

  • Facts don't move. Style passes are where they drift, so lock them first and audit against the lock.
  • Never fabricate experience, sources, detail or fake messiness. Mark each gap [FLAG: cite source] or [FLAG: verify].
  • No em dash (U+2014) in output, examples included. Recast the sentence; a colon or spaced hyphen that keeps the same pivot moves the tell.
  • A supplied voice sample beats these defaults.
  • Edit for the reader, never a detector score. Formal prose isn't proof of AI authorship.
  • One term per concept: repeat the precise noun, don't cycle endpoint, route and URL for variety.
  • Never style-pass gates, ADR decisions, credential custody or literal runbooks. Edit them by hand, and check whether a test matches their exact wording first.

Procedure

Pick the lightest pass: repair named defects, rewrite (default) or diagnose (findings only). If the draft already reads well, say so and touch little.

  1. Lock facts, numbers, names, quotes, citation keys, defined terms, modals and negations. List them.
  2. Diagnose by mechanism (mechanisms.md), not by phrase. Name the two or three that cost the reader most.
  3. Rewrite once, restating each claim directly and adding only anchors the source holds.
  4. Audit independently. Compare the lock list with the result; revert any sentence that lost or strengthened a claim. For high-stakes text, a clean-context reviewer sees only the before and after. For number-heavy text, script the check (claims.md).
  5. Report the text first, with notes only for material flags.

provenant check writing PATH flags em dashes and lexical hints. Its silence is necessary, not sufficient.

References

  • voice.md: register, punctuation and Australian English. Load before any write or rewrite.
  • mechanisms.md: the defects, with before/after pairs.
  • claims.md: claim classes, comparatives, number audit and the condense pass.
  • engineering.md: READMEs, PRs, commits, error text, runbooks, release notes and process-language leaks. Specs and issue bodies go to scope and tracker; where a doc lives is engineering-docs.
  • academic.md: thesis and paper register, citations, LaTeX invariants.

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.