agentleFS
Sign inStart free
assaioassaio/unwordy/skills/write/SKILL.md

write

Skill1 starsChanged 53 days agoMITView on GitHub

Follow the team's writing conventions in commits, PRs, reviews, bug reports, design handoffs and work replies. Preserve evidence and personal voice.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use read, hunt and 9 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.
  • MicrosoftSkill

    read

    Read pages from a document. Returns MinerU markdown (preferred) or PyPDF text, with optional page screenshots and sub-image fetching. When markdown is available, a figure_images_meta catalog is included — use the figures parameter to fetch specific sub-image pixels. Triggers include "read page 5", "what does page 12 say", "show me the chart on page 3", "extract pages 3-5".

    Also in 6 projects that use this

  • ninehillsSkill

    hunt

    Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.

    Also in 4 projects that use this

  • vltingSkill

    think

    Lightweight plan-to-execution pipeline. Explores codebase, runs council deliberation, presents plan for approval, then executes via /run.

    Also in 7 projects that use this

  • genomewalkerSkill

    health

    Soul system health check with remediation

    Also in 5 projects that use this

  • AnthropicSkill

    analyze

    Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

    Also in 6 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 4 projects that use this

  • Other versions35 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 35

    1. reactjs/react.dev★ 12ksame name
    2. tw93/claude-health★ 7.5ksame name
    3. tw93/Waza★ 7.5ksame name
    4. docker/docs★ 4.7ksame name
    5. waynesutton/markdown-site★ 628same name
    6. ohad6k/emulo★ 292same name
    7. ninehills/skills★ 280same name
    8. hsantanna88/clo-author★ 262same name
    9. hugosantanna/clo-author★ 262same name
    10. yan-labs/yan-skills★ 232same name

    25 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 3

    Distinctive

    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 for the person who will act on the message.

    line 7
  2. Distinctive:

    Keep the user's Git identity and required disclosure.

    line 28
  3. Distinctive:

    Before rewriting, identify supplied facts and protected strings.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 31 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

Write for the person who will act on the message. Preserve facts, uncertainty, negations, commitments, exact errors and test evidence. Never invent details, experience or testing to make an answer sound natural.

Resolve the voice

Repository requirements (AGENTS.md, CLAUDE.md, CONTRIBUTING, templates and commitlint) win. Then use the active profile supplied at session start. If it is missing, read $UNWORDY_STYLE, else the nearest .unwordy.md up to the git root, else $XDG_CONFIG_HOME/unwordy/style.md (default ~/.config/unwordy/style.md). The first file wins. If the local unwordy CLI is available, unwordy voice prints the resolved instructions. Otherwise interpret the profile directly. With no profile, use a direct, specific voice and enough context for the task. A custom body supplies the voice; role and tone are independent preferences. Respect disabled rules and per-surface limits. Required content wins over brevity. With enabled: false, leave unwordy preferences out and follow the user's request and repository conventions.

Surfaces

  • Commits: follow local subject conventions; add a body for a non-obvious reason. Keep the user's Git identity and required disclosure. Commit only when requested or required by the repository workflow.
  • PRs: retain what changed, why, risk and observed test evidence. Use the repository template. Without one, choose paragraphs or bullets that help review.
  • Reviews: identify the change needed and its reason. Keep a useful acknowledgement in a warm voice; remove praise that does not help the discussion.
  • Bugs and test results: retain reproduction, expected/actual, environment, versions, frequency and exact errors. Numbered steps and descriptive terms help.
  • Design handoffs: retain states, behavior, rationale, accessibility and constraints.
  • Decisions: retain the decision, trade-off, owner and next step when supplied.
  • Code comments: explain constraints, contracts and traps. Public API documentation, algorithm steps and workaround references may be necessary. Remove restatement.
  • Replies: answer first, then enough context. Preserve intentional warmth, casing and punctuation from the profile. Length follows the reader's task.

Before rewriting, identify supplied facts and protected strings. Make only edits that help the reader. Missing details stay missing; ask only when a gap prevents a useful answer. Before sending, compare values, conditions, expected versus actual, negations, commitments and test scope with the source. Keep required sections and executable behavior. Do not change technical strings, quotes or links for style.

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