agentleFS
georgejiehgeorgejieh/agent-skill-library-public/skills/writing/genre-aware-prose/SKILL.md

genre-aware-prose

Skill1 starsChanged 3 months agoMITView on GitHub

Use when drafting or revising professional prose.

The file

Show its rules and text

We split this skill into the rules it gives an agent

40 rules. About 0 are common, 39 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈39

    Distinctive · estimate

    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. Distinctive:

    Do not use for poetry, fiction, screenplay dialogue, legal advice, or a request to impersonate a named person.

    line 21
  2. Distinctive:

    If the user asks for their own voice, obtain user-provided samples or explicit, scoped permission before inspecting a private source …

    line 28
  3. Distinctive:

    Build the argument or action spine: Write a one-sentence statement of the main answer, finding, recommendation, or request.

    line 36
  4. Distinctive:

    Outline in reader-first order: Put the answer, request, decision, or task before background.

    line 38
  5. Distinctive:

    Draft direct, specific prose: Prefer concrete nouns, active verbs, stated actors, measurable claims, short paragraphs, and varied but …

    line 40
  6. Distinctive:

    Run the humanization pass: Remove generic scene-setting, significance inflation, hype, vague attribution, filler, false certainty, …

    line 44
  7. Distinctive:

    Verify and deliver: Check factual support, citation consistency, quoted wording, names, dates, numbers, links, headings, accessibility, …

    line 48
  8. Distinctive:

    Prefer a simple verb such as "is," "has," "shows," or "uses" over inflated substitutes such as "serves as," "stands as," or "showcases."

    line 56
  9. Distinctive:

    Prefer named sources and concrete evidence to phrases such as "experts say," "industry observers," or "it is widely believed."

    line 57
  10. Distinctive:

    Remove empty significance claims: "pivotal," "transformative," "testament," "vibrant," "evolving landscape," and similar language require …

    line 58
  11. Distinctive:

    Do not use a list of three merely to sound comprehensive.

    line 59
  12. Distinctive:

    Avoid synonym cycling. Repeating a precise term is clearer than inventing near-synonyms for stylistic variety.

    line 60
  13. Distinctive:

    Do not force a metaphor, dramatic fragment, punchline, motivational closer, or reassuring aside where a plain sentence is stronger.

    line 61
  14. Distinctive:

    Avoid chatbot residue such as "Great question," "Here is," "I hope this helps," "Let me know," and knowledge-cutoff disclaimers in finished …

    line 62
  15. Distinctive:

    Use headings, lists, bolding, emoji, and callouts only when they help a reader navigate.

    line 63
  16. Distinctive:

    Do not make up interviews, emotions, observations, quotes, data, case studies, citations, or personal experience to make a passage feel …

    line 64
  17. Distinctive:

    Keep uncertainty proportionate: remove stacked hedges, but retain warranted qualifiers such as "may," "according to," "preliminary," or …

    line 65
  18. Distinctive:

    Use anonymous sources only when the information is materially in the public interest, cannot be obtained on the record, and the source has …

    line 74
  19. Very specific:

    Treat search snippets, social reposts, AI output, and unverified media as leads rather than evidence.

    line 78
  20. Distinctive:

    Write headlines after facts and scope are clear.

    line 79
  21. Distinctive:

    Start from what the reader can learn, decide, or do, not from a topic announcement or promotion.

    line 84
  22. Distinctive:

    Use a single page purpose and a unique H1.

    line 85
  23. Distinctive:

    Use a blog/explainer for a useful perspective, a how-to for one goal, reference material for precise facts/options, and explanation for …

    line 86
  24. Distinctive:

    Use task verbs for task sections and noun phrases for conceptual sections.

    line 87
  25. Distinctive:

    Write ordered, executable steps for procedures.

    line 88
  26. Distinctive:

    Use plain language, direct verbs, consistent terms, defined acronyms, short paragraphs, and active voice where it clarifies actor and …

    line 89
  27. Distinctive:

    Treat accessibility as part of prose: maintain heading order, use meaningful destination-specific links, avoid color/icon-only meaning, …

    line 90
  28. Distinctive:

    Use a call to action only for a natural next task.

    line 92
  29. Distinctive:

    Prefer primary research, datasets, standards, official records, and original reporting for factual claims.

    line 99
  30. Distinctive:

    Write a stand-alone abstract containing the problem/question, approach or corpus/method, principal finding/argument, and implications.

    line 104
  31. Distinctive:

    Use deductive order: purpose/request, essential context, analysis/evidence, recommendation/action, next steps.

    line 118
  32. Distinctive:

    Before sending, verify that the reader can identify the ask, rationale, evidence, risks, owner, deadline, and response channel in one …

    line 124
  33. Distinctive:

    Before finalizing research-backed prose:

    line 128
  34. Distinctive:

    Place citations adjacent to the claims they support.

    line 132
  35. Distinctive:

    Verify quotations against the original wording and identify material omissions/alterations.

    line 134
  36. Distinctive:

    Voice leakage: Do not embed a specific person's voice, private samples, personal facts, or inferred traits in a reusable skill.

    line 140
  37. Distinctive:

    Humanization by fiction: Do not invent a quote, case study, emotion, anecdote, or source to make prose vivid.

    line 145
  38. Distinctive:

    Generic conclusion: Do not end with "the future is bright," "this is a pivotal moment," or another unsupported flourish.

    line 147
  39. Distinctive:

    Before delivery, confirm that:

    line 151
  40. Distinctive:

    every material external claim, number, quote, and citation has been checked against its source.

    line 156

≈ “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

Genre-Aware Prose

Use this skill to draft, revise, or review prose that is clear, evidence-aware, human in cadence, and appropriate to its genre. It is a general writing skill, not a personal voice guide. It never assumes an end user's voice, personal facts, views, or style from private history.

When to Use

  • Drafting or revising a news item, explainer, blog post, technical document, research paper, letter, memo, proposal, grant narrative, or executive brief.
  • Editing text that is padded, generic, overly promotional, vague, mechanically structured, or recognizably machine-produced.
  • Selecting and applying a citation convention required by a publisher, venue, recipient, or user.

Do not use for poetry, fiction, screenplay dialogue, legal advice, or a request to impersonate a named person. For a user's own voice, use authorized samples or the separate consented calibration process. Without that authorization, write in a neutral voice suited to the genre.

Prerequisites

  1. Identify the document genre, audience, purpose, reader's next action, delivery format, and factual-risk level.
  2. Identify binding instructions: publication template, recipient requirements, assignment rubric, funder solicitation, legal policy, house style, length, deadline, and citation style.
  3. Inventory supplied facts, sources, quotations, attachments, and unknowns. Separate verified facts, attributed claims, analysis, assumptions, and recommendations.
  4. If the user asks for their own voice, obtain user-provided samples or explicit, scoped permission before inspecting a private source collection. Do not infer voice from private material silently.

Completion: the reader, intended outcome, governing format, and evidence boundary are known before drafting.

Procedure

  1. Choose the form by reader task. Use a news item for a verified development, an explainer for how or why something works, a blog post for a useful argument or perspective, a how-to for one practical goal, reference documentation for exact options/facts, a research paper for a supported contribution, and a memo/brief/proposal for a decision or action.
    • Completion: the document has one primary reader need and one appropriate form.
  2. Build the argument or action spine. Write a one-sentence statement of the main answer, finding, recommendation, or request. List only the evidence and context needed to support it. State material uncertainty rather than filling gaps with plausible prose.
    • Completion: every section supports the reader's decision, understanding, or action.
  3. Outline in reader-first order. Put the answer, request, decision, or task before background. Use descriptive, front-loaded, sentence-case headings. Keep one main idea or task per section.
    • Completion: a reader scanning the title, opening, headings, lists, links, and call to action can understand the purpose and next step.
  4. Draft direct, specific prose. Prefer concrete nouns, active verbs, stated actors, measurable claims, short paragraphs, and varied but controlled sentence rhythm. Define necessary terms at first useful use and use them consistently.
    • Completion: each sentence informs, supports, explains, or enables an action.
  5. Preserve evidence discipline. Cite or attribute material external facts, data, quotations, methods, and ideas immediately where they appear. Match wording to the evidence's source, scope, date, population, method, and causal strength.
    • Completion: no factual sentence is stronger than its supporting evidence.
  6. Run the humanization pass. Remove generic scene-setting, significance inflation, hype, vague attribution, filler, false certainty, formulaic "challenges/future" sections, rhetorical questions answered immediately, and decorative formatting. Replace them with specific information, clear analysis, or deletion.
    • Completion: the draft sounds deliberate when read aloud without manufacturing a personality.
  7. Run the genre gate below. Apply the requirements that match the chosen form. If forms are combined, label transitions and preserve each form's evidence and structure rules.
    • Completion: the draft meets its genre's actual reader contract.
  8. Verify and deliver. Check factual support, citation consistency, quoted wording, names, dates, numbers, links, headings, accessibility, format constraints, and requested action. Report any unsupported claim, missing source, or unresolved ambiguity honestly.
    • Completion: the final artifact is usable, auditable, and accurately described.

Core Humanization Rules

Human prose does not require theatrical personality. It requires specific thinking, appropriate rhythm, and an honest relationship to evidence.

  • State the point rather than announcing that you will discuss it.
  • Prefer a simple verb such as "is," "has," "shows," or "uses" over inflated substitutes such as "serves as," "stands as," or "showcases."
  • Prefer named sources and concrete evidence to phrases such as "experts say," "industry observers," or "it is widely believed."
  • Remove empty significance claims: "pivotal," "transformative," "testament," "vibrant," "evolving landscape," and similar language require evidence or deletion.
  • Do not use a list of three merely to sound comprehensive. Use the number of points the subject requires.
  • Avoid synonym cycling. Repeating a precise term is clearer than inventing near-synonyms for stylistic variety.
  • Do not force a metaphor, dramatic fragment, punchline, motivational closer, or reassuring aside where a plain sentence is stronger.
  • Avoid chatbot residue such as "Great question," "Here is," "I hope this helps," "Let me know," and knowledge-cutoff disclaimers in finished prose.
  • Use headings, lists, bolding, emoji, and callouts only when they help a reader navigate. Do not use them as visual noise.
  • Do not make up interviews, emotions, observations, quotes, data, case studies, citations, or personal experience to make a passage feel human.
  • Keep uncertainty proportionate: remove stacked hedges, but retain warranted qualifiers such as "may," "according to," "preliminary," or "could not independently verify."

Genre Gates

News and explanatory journalism

  • Lead with the most consequential verified development: who did what, where/when, and why it matters now. Add essential context, evidence, response, background, and remaining uncertainty in descending importance.
  • For explainers, start with the live development or reader question, provide a plain-language answer, then explain how it works, limits, examples, and what remains uncertain.
  • Attribute material facts not directly observed, especially allegations, forecasts, documents, data, casualty figures, and claims of intent. Prefer named, on-the-record sources with relevant roles.
  • Use anonymous sources only when the information is materially in the public interest, cannot be obtained on the record, and the source has direct knowledge. Explain the source's position and reason for anonymity enough for readers to judge credibility.
  • Seek and report a meaningful response from people or institutions facing serious criticism. Do not create false balance by giving unsupported claims equal weight.
  • Contextualize statistics with their source, timeframe, geography/population, denominator or method where material, and limitations.
  • Quote only wording whose speaker, context, and attribution are known. Do not alter meaning. Use paraphrase when exact language is not the point.
  • Treat search snippets, social reposts, AI output, and unverified media as leads rather than evidence. Authenticate consequential documents/images/video before relying on them.
  • Write headlines after facts and scope are clear. Match certainty to evidence and label News, Explainer, Analysis, Opinion, Fact Check, or Live accurately.
  • Correct material errors transparently: distinguish an update, clarification, correction, and retraction; say what was wrong and what is correct.

Blog posts, product writing, and technical documentation

  • Start from what the reader can learn, decide, or do, not from a topic announcement or promotion.
  • Use a single page purpose and a unique H1. Open with a short orienting summary. Keep one task or idea per section.
  • Use a blog/explainer for a useful perspective, a how-to for one goal, reference material for precise facts/options, and explanation for concepts/rationale. Do not blur these forms without signposting.
  • Use task verbs for task sections and noun phrases for conceptual sections. Keep headings specific, front-loaded, and meaningful out of context.
  • Write ordered, executable steps for procedures. State prerequisites and expected outcomes. Put conceptual detail where it does not interrupt the task flow.
  • Use plain language, direct verbs, consistent terms, defined acronyms, short paragraphs, and active voice where it clarifies actor and action.
  • Treat accessibility as part of prose: maintain heading order, use meaningful destination-specific links, avoid color/icon-only meaning, introduce tables in text, and describe informative images appropriately.
  • Support material claims with directly relevant sources. Separate fact, attribution, analysis, and recommendation. Do not imply results, endorsements, testing, certification, or scarcity that did not occur.
  • Use a call to action only for a natural next task. Make its action/outcome explicit, limit competing actions, and do not use urgency or promises the destination cannot honor.
  • Edit in passes: reader need/scope, structure/headings, evidence/claim strength, clarity/terminology, accessibility/links, then final mechanics.

Academic and research writing

  • Obey the journal, conference, department, instructor, funder, or template first. Select one citation system early and apply it consistently.
  • Build a claim ledger before drafting: claim, source, exact supporting passage/data, scope or qualification, and citation location.
  • Prefer primary research, datasets, standards, official records, and original reporting for factual claims. Use reviews for synthesis and identify commentary accurately.
  • Separate a reported finding ("Study X found"), a synthesis/inference ("Taken together, the evidence suggests"), and the author's analysis/recommendation.
  • Paraphrase by reading, understanding, then independently writing. Cite the source beside the paraphrase. Do not patchwrite by retaining source syntax while swapping words.
  • Quote selectively when exact wording matters. Introduce the quotation, reproduce it accurately, cite it, and explain its relevance. Use a page/section/table/figure/timestamp locator when available and useful.
  • Include a table or figure only when it aids comprehension. Number it consistently, give it a descriptive title/caption, define labels/units, cite it in the prose, and attribute reproduced/adapted material. A citation does not replace required permissions.
  • Write a stand-alone abstract containing the problem/question, approach or corpus/method, principal finding/argument, and implications. Follow venue limits; avoid citations, footnotes, unexplained abbreviations, and undeveloped claims unless the venue says otherwise.

Citation-style selection

  • APA 7: author-date citations in text and an alphabetized References list. Appropriate when the target requires APA or when an author-date research convention is specified.
  • MLA 9: concise in-text citations that lead readers to an alphabetized Works Cited list. Use the author/title key and locator needed to find the cited passage.
  • Chicago: choose either Notes and Bibliography or Author-Date at the outset. Do not mix their in-text/end-list mechanics.
  • IEEE: numbered bracket citations in order of first mention and a numbered References list. Preserve first-citation numbering and use the venue template for source-type details.
  • A citation formatter formats metadata; it does not establish source quality or prove a claim. Validate names, dates, titles, DOI/URL, source type, and evidence against the original item.

Letters, memos, proposals, grants, and executive briefs

  • Identify the primary reader, their authority, relevant knowledge, likely objection, and required next action.
  • State the purpose or request early and repeat a concrete response path near the close. Be direct, respectful, and proportionate to relationship and stakes.
  • Use deductive order: purpose/request, essential context, analysis/evidence, recommendation/action, next steps. Prefer short sections and descriptive headings for busy readers.
  • A letter or email opens with the reason for writing and needed action, provides only necessary context, and closes with a polite, concrete response path.
  • A memo uses To, From, Date, and Subject, then organizes around the recipient's decision or operational need rather than chronology.
  • A proposal or grant follows the solicitation's headings, evaluation criteria, format, and limits. Show a traceable chain: documented need, objectives/outcomes, activities/method, evaluation, work plan/capacity, and an itemized budget aligned to activities.
  • An executive brief leads with the conclusion or recommendation, gives only decision-relevant evidence, states material limitations, and connects every recommendation to a finding.
  • Surface decision-relevant uncertainty, dependencies, alternatives, capacity constraints, costs, and data limits. Do not overstate causation, certainty, or benefits.
  • Before sending, verify that the reader can identify the ask, rationale, evidence, risks, owner, deadline, and response channel in one reading.

Citation and Evidence Verification

Before finalizing research-backed prose:

  1. Confirm that each material factual claim is directly supported by a source the writer actually read.
  2. Confirm that the source supports the claim's exact scope, population, timeframe, comparison, and causal strength.
  3. Place citations adjacent to the claims they support. Do not use a source list that forces the reader to guess.
  4. Confirm that every in-text citation resolves to a complete end-list entry and that every entry is used unless the target form permits uncited bibliography entries.
  5. Verify quotations against the original wording and identify material omissions/alterations.
  6. Label what is fact, attribution, analysis, assumption, recommendation, and uncertainty.
  7. For high-stakes, disputed, legal, medical, financial, or safety claims, seek independent corroboration or state the limitation and require appropriate human review.

Pitfalls

  • Voice leakage: Do not embed a specific person's voice, private samples, personal facts, or inferred traits in a reusable skill.
  • Silent history mining: Past conversation history is not consent. History-based voice calibration requires explicit user permission and is available only where the runtime supports it.
  • Genre confusion: A blog post is not a research paper, a news item is not an opinion essay, and an executive brief is not a chronological diary.
  • Citation theater: A formatted citation does not prove that the cited source supports the sentence.
  • False precision: Exact numbers, dates, quotations, and causal claims require exact support.
  • Humanization by fiction: Do not invent a quote, case study, emotion, anecdote, or source to make prose vivid.
  • Accessibility afterthought: Heading structure, link wording, image description, and table context are part of the content, not a final visual polish.
  • Generic conclusion: Do not end with "the future is bright," "this is a pivotal moment," or another unsupported flourish. End with the supported implication, next action, or a clean stop.

Verification

Before delivery, confirm that:

  • the genre, audience, purpose, and binding requirements were identified;
  • the opening answers the reader's primary question or states the requested action;
  • headings and section order work for a scanning reader;
  • every material external claim, number, quote, and citation has been checked against its source;
  • the draft separates evidence, attribution, analysis, recommendation, and uncertainty;
  • genre-specific requirements, citation style, accessibility, and format limits are satisfied;
  • humanization removed padding and hype without deleting warranted nuance; and
  • any style matching used authorized samples or explicit permission for the identified source collection, or else the draft used a neutral default.

Public Standards Consulted

This skill synthesizes, rather than reproduces, public guidance from Reuters Journalistic Standards, BBC Editorial Guidelines, the Society of Professional Journalists Code of Ethics, GOV.UK content guidance, U.S. Web Design System guidance, Google developer documentation style, W3C accessibility guidance, Divio documentation guidance, APA Style, MLA Style Center, Chicago Manual of Style quick guidance, IEEE Editorial Style Manual, Digital.gov plain-language guidance, Purdue OWL, and U.S. Government Accountability Office guidance.

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.