humanizer
Draft or revise prose a person will read (documentation, README text, ADR and spec bodies, runbooks, pull-request descriptions, commit messages, delivery summaries, briefs and reports for the owner) so it reads as deliberate writing by a competent author, without changing what it says. Use when a draft came out of a model and shows the tells (empty contrasts, staged openers, one-line closers, forced triads, dash dependence, inflated significance, bold labels on every item, chatbot residue), when drafting finished prose from notes, or as the last pass before such text is handed off. Preserves facts, numbers, conditions, requirement levels, citations and voice; adds no fact; never fakes a human author or chases a detector score. The doctrine is method.prose-posture; docs/graph/prose-lint.py is the mechanical floor and the fact-preservation check.
llopresto87 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add llopresto87/Cypress --skill humanizer技能说明
name: humanizer description: Draft or revise prose a person will read (documentation, README text, ADR and spec bodies, runbooks, pull-request descriptions, commit messages, delivery summaries, briefs and reports for the owner) so it reads as deliberate writing by a competent author, without changing what it says. Use when a draft came out of a model and shows the tells (empty contrasts, staged openers, one-line closers, forced triads, dash dependence, inflated significance, bold labels on every item, chatbot residue), when drafting finished prose from notes, or as the last pass before such text is handed off. Preserves facts, numbers, conditions, requirement levels, citations and voice; adds no fact; never fakes a human author or chases a detector score. The doctrine is method.prose-posture; docs/graph/prose-lint.py is the mechanical floor and the fact-preservation check. id: skill.humanizer tier: 2 kind: skill origin: seed title: humanizer — prose a person will read is drafted or revised by judgment, with every fact intact owns:
- humanizer.method
- humanizer.document-contract
- humanizer.progressive-execution
- humanizer.fact-preservation
- humanizer.modes
- humanizer.scope requires:
- method.prose-posture peers:
- skill.holistic-editing
- skill.adr-writer
- skill.spec-author
- agent.docs-librarian
- protocol.deliver load_when:
- "this reads like it was written by an AI, remove the AI tells, humanize this text, it sounds like a chatbot"
- "rewrite the documentation so it reads naturally, plain-language pass on the docs, make the README sound human"
- "draft the report, brief, or memo from these notes; turn the bullets into finished prose"
- "not X but Y, one-line closer, forced triad, too many em dashes, bold labels on every bullet, decorative headings"
- "polish the pull-request description, commit message, or delivery summary before hand-off"
- "did the rewrite drop a fact, prose-lint --against, fact preservation after a prose edit"
- "audit this document for prose quality without rewriting it" est_tokens: 3300
humanizer
This skill drafts or revises expository prose whose value depends on the
reader understanding and trusting it. Its doctrine is
docs/graph/method/prose-posture.md: meaning governs style, the information
contract is preserved, structure carries emphasis, genre outranks generic
advice, voice is a constraint, and editing stops when the prose does its
job. This node holds the procedure that applies the doctrine and the tool
that floors it.
Two halves do the work. The skill is the judgment: what the document must
cause the reader to understand or do, which claims must survive, which
diagnostics apply, what the voice is. The tool docs/graph/prose-lint.py
(seed home tools/prose-lint.py) is the floor under that judgment: it
reports the tells a pattern can catch, and with --against <rev> it proves
that a rewrite added and dropped nothing.
When to apply this skill
- A document, README, runbook, or node body is being written or refreshed for people, and the draft came out of a model or from notes.
- An ADR or spec body is about to flip to
acceptedoractive(docs/graph/skills/adr-writer.md,docs/graph/skills/spec-author.md). The record is prose someone reads in a year. - The
deliverprotocol's full-form summary, a pull-request description, or a commit message is being prepared. Other people read these most and edit them least. - A reviewer or the owner says the text "sounds like an AI".
- Text imported from outside the project (a harvest import, a vendored guide) will be read as the project's own voice.
Out of scope: code, commands, frontmatter, owns: and load_when: lists,
generated tables, the kernel, and the seed's own machinery prompts. The
machinery is edited by grill and holistic-editing, never by a prose
pass. Fiction is out of scope; invented detail is its task.
The document contract
Before drafting or revising substantial prose, settle a compact contract. For a short edit, infer it in a moment and proceed; for long, high-stakes, or multi-source work, let it govern every section. It is internal unless the owner asks for the reasoning or an audit.
- Purpose: what must this document cause the reader to understand, decide, approve, do, or remember?
- Audience: what does the reader know, what terminology can they handle, what do they care about, what is their likely next action?
- Genre: which profile in
prose-posture.genre-outranksapplies? - Substance: which claims, evidence, instructions, and caveats must survive?
- Priority: which one to three ideas matter most?
- Authority: which statements are facts, attributed claims, inferences,
assumptions, recommendations, unknowns, or contested
(
prose-posture.claim-classes)? - Voice: the owner's sample if one exists; otherwise the restrained default
for the genre, in the plant's declared
deliverable_language. - Constraints: length, format, required sections, terminology, headings other documents anchor to.
- End state: what should a competent reader be able to say or do after reading?
Progressive execution
Use the lightest process that reliably fits the task.
Level 1, local edit (a paragraph, a commit message, a summary): infer purpose and voice; preserve the claims; revise the weak sentences or paragraph; run the fidelity and naturalness checks; return the prose.
Level 2, document revision (a README, a runbook, a node body, a multi-section document): settle the contract; map sections and claims; find the structural defects; revise section by section; harmonize voice and terminology; audit repetition across sections; verify facts, citations, and conditions; return the document.
Level 3, high-stakes synthesis (a long technical or legal-adjacent document, a multi-source report, an owner brief that will drive a decision): settle the contract; keep a claim and source ledger; classify authority an
阅读完整来源 ↗