Agent skill

Natural Writing

by a2ui-project in a2ui-project/a2ui

Contains well-defined rules for creating natural, accurate, and readable writing.

Apache-2.0Auto-check passedDevelopment

Install Natural Writing

skills CLI
$ npx skills add a2ui-project/a2ui --skill natural-writing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install a2ui-project/a2ui natural-writing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/a2ui-project/a2ui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/natural-writing .claude/skills/natural-writing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
natural-writing
GitHub stars
17k
Used in
1 other repo
Token cost
~2.1k tokens
SKILL.md length
1,194 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
Apache-2.0

At a glance

Contains well-defined rules for creating natural, accurate, and readable writing.

  • Works in 6 steps: Vocabulary & phrasing controls → Content & tone → Sentence structure → …
  • Authoring longer text
  • SKILL.md covers 1. Vocabulary & phrasing…, 2. Content & tone, 3. Sentence structure and 4. Structure & formatting, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Natural Writing is an agent skill from a2ui-project/a2ui. Contains well-defined rules for creating natural, accurate, and readable writing. Use this skill whenever authoring longer text, including reports, PR descriptions, READMEs, system designs, analysis documents, or general documentation.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Humanizing AI text, Pull requests and Technical documentation. The licence is Apache-2.0.

When your agent uses it

  • Authoring longer text
  • Including reports
  • PR descriptions
  • Analysis documents

Example prompts

  • “Use the natural-writing skill to contain well-defined rules for creating natural, accurate, and readable writing”
  • “/natural-writing”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Vocabulary & phrasing controls
  2. Content & tone
  3. Sentence structure
  4. Structure & formatting
  5. Citations & integrity
  6. Communication (chat context)

What it can do on your machine

Read from SKILL.md and the folder at commit 03b77ae. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Natural Writing loads about 2.1k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 1,194 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from a2ui-project/a2ui at commit 03b77ae, republished under its Apache-2.0 licence (© a2ui-project). 1,194 words, ~2,105 tokens.

Download SKILL.mdSave it as .claude/skills/natural-writing/SKILL.md (or your agent's skills folder).
name
natural-writing
description
Contains well-defined rules for creating natural, accurate, and readable writing. Use this skill whenever authoring longer text, including reports, PR descriptions, READMEs, system designs, analysis documents, or general documentation.

Rules for natural writing

This document outlines strict rules to avoid common "AI-isms": stylistic and structural patterns that language models typically fall into. Follow these rules to produce content that is more understandable, and reads as natural, human-authored text.

1. Vocabulary & phrasing controls

The "banned" list

Avoid words that are statistically overrepresented in AI text. Use simpler, more direct alternatives.

Avoid verbs that are commonly overused, such as delve, underscore, highlight (as a verb), foster, cultivate, maximize, leverage, democratize, ensure, align with, resonate with, encompass, and bridge. Also avoid adverbs like seamlessly and extensively.

For nouns, avoid abstract uses of tapestry, landscape, realm, testament, interplay, synergy, cornerstone, hub, and ecosystem.

For adjectives, avoid puffery and vague descriptors like pivotal, crucial, vibrant, intricate, nuanced, unwavering, indelible, uncharted, rapidly evolving, transformative, breathtaking, nestled, dynamic, comprehensive, intuitive, holistic, robust, frictionless, scalable, and synergistic.

Avoid "copula" substitutions

Do not replace simple "is" or "are" verbs with flowery equivalents.

  • Instead of: "The library serves as a center for learning."
  • Write: "The library is a center for learning."
  • Instead of: "The statue stands as a monument to..."
  • Write: "The statue is a monument to..."
Eliminate "elegant variation"

Do not use synonyms just to avoid repeating a subject's name (e.g., "the eponymous character," "the titular protagonist," "the celebrated author"). It is acceptable to repeat the name or use pronouns naturally.

Prefer literal words to idioms

Choose the word that states the meaning directly over an idiom whose meaning depends on context. Idioms are harder to read for non-native speakers and for anyone skimming instructions.

  • Instead of: "Leave the version alone."
  • Write: "Leave the version untouched."

2. Content & tone

No "puffery" or forced significance

Do not inflate the importance of a topic with vague praise. If a subject is important, the facts should demonstrate it without help.

Avoid phrases like "serves as a testament to," "marking a pivotal moment," "underscoring the importance of," "leaving an indelible mark," or "shaping the landscape."

  • Instead of: "The founding of the institute marked a pivotal moment in the evolution of regional statistics, representing a significant shift toward independence."
  • Write: "The institute was founded in 1989 to collect regional statistics."
No superficial analysis

Avoid attaching "dangling" present-participle phrases that offer vague commentary.

Delete clauses starting with "highlighting," "emphasizing," "reflecting," "showcasing," or "demonstrating" if they just restate the obvious or add fluff.

  • Instead of: "The building uses blue glass, reflecting the region's natural beauty and symbolizing unity."
  • Write: "The building uses blue glass."
Avoid promotional language

Maintain a neutral tone. Avoid "advertisement" words like boasts, features (as a verb), offers, premier, leading, state-of-the-art, committed to, and dedicated to.

  • Instead of: "Nestled in the heart of the city, the hotel boasts a vibrant atmosphere."
  • Write: "The hotel is located in the city center."
No "challenges and future outlook" formula

Language models often end articles with a generic "Despite challenges... remains important" conclusion. Do not end with a summary paragraph starting with "Despite [X], [Subject] continues to..." or speculating on the future. End with the last fact.

  • Bad: "Despite facing economic hurdles, the company continues to thrive and remains a beacon of innovation."
No "title as proper noun" leads

Do not treat a descriptive article title (like a list or broad topic) as a proper noun in the first sentence.

  • Instead of: "The List of songs about Mexico is a curated compilation..."
  • Write: "This list contains songs about Mexico..."

Do not populate "See Also" sections with broad, generic terms. Links must be directly relevant and specific to the subject.

  • Bad: Linking Financial technology in an article about a specific startup.
  • Good: Linking a competitor or specific related technology.
Attribution precision

Avoid vague "weasel words" like "Experts argue," "Observers have noted," or "Several sources indicate" unless you cite specific people immediately. Do not claim a subject interacts with a "broader" history or trend unless a source explicitly says so.

3. Sentence structure

No negative parallelism

Avoid sentences that structure a contrast unnecessarily.

  • Instead of: "It is not only a painting, but also a representation of..."
  • Instead of: "It is not just about X; it is about Y."
  • Write: "It is a painting that represents..."
No "rule of three"

Avoid listing exactly three adjectives or three noun phrases to sound "comprehensive."

  • Bad: "The event brings together marketers, engineers, and designers." (Unless those specific three groups are the only ones).
  • Bad: "It is bold, innovative, and unique."
Show full SKILL.md (461 more words)Show less
No false ranges

Do not use "from X to Y" unless X and Y are endpoints of a logical scale (like time or size).

  • Instead of: "The book covers everything from biology to space travel." (These are just two random topics, not a range).
  • Write: "The book covers topics including biology and space travel."

4. Structure & formatting

Headers

Use sentence case for headers (e.g., "Early life," not "Early Life"). Do not use title case in headers.

Formatting avoidance

Do not use inline-header lists (such as * **Header:** Description...). Instead, use prose or simple lists.

Avoid excessive bolding of keywords, "key takeaways," or names in the body text, except for the first mention in the lead.

Do not use emojis (🚀, 🧠) or unusual bullets (#, -) in lists. Use standard bullets (*).

Avoid creating tables for simple information that easily fits in a sentence.

Ensure markup is context-appropriate; do not use Markdown (like ##) in formats that do not support it (like Wikitext) unless it is explicitly converted.

Punctuation

Use straight quotes (", ') and straight apostrophes ('). Do not use curly or smart quotes (“, ’).

Use em dashes sparingly, as language models often overuse them for emphasis. Prefer commas or parentheses instead.

5. Citations & integrity

No hallucinations

Never generate a citation unless you are looking at the source. Do not invent URLs or DOIs. Do not assume a book exists or contains a specific fact without verification.

Link everything the reader may want to open: files, functions, test and conformance cases, packages, issues, pull requests, and external pages. How precise a link should be depends on how long the text lives.

  • In short-lived text, such as review comments, PR descriptions, and issues, link to the exact lines. Pin the link to a commit SHA rather than a branch, so it keeps pointing at the lines you meant after the branch moves. For a Markdown file, add ?plain=1 so a line anchor such as #L10-L20 works.
  • In long-lived documents, such as READMEs, documentation, skills, and code comments, link to the file or its section, without line ranges. A line range in one long-lived document has to be updated every time the document it points to changes.
  • Link only to what the reader can see at the link target. If your change is not pushed yet, link to the current version, or post the text after the push.
  • Before posting, check that every link resolves.

6. Communication (chat context)

Avoid collaborative filler at the start of responses, such as "Certainly!", "Here is the information," or "I hope this helps." State the content directly.

Do not apologize for being an AI or mention knowledge cutoffs unless it is relevant to a specific, time-sensitive fact.

Do not preface responses with subject lines.

Keep edit summaries concise and informal, avoiding verbose paragraphs.

© a2ui-project, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/natural-writing of a2ui-project/a2ui.

Open the folder on GitHubat commit 03b77ae

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in a2ui-project/a2ui, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Natural Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Natural Writing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Natural Writing this skilla2ui-project/a2ui17k1 repos~2.1kAutomated safety check: PassApache-2.0
No TropesOutThisLife/brooklyn-skills199—~455Automated safety check: PassMIT
Writerrileyhilliard/claude-essentials130—~2kAutomated safety check: PassMIT
Opik Documentation Patternscomet-ml/opik22k—~1.3kAutomated safety check: PassApache-2.0
Ss DocsSerial-Studio/Serial-Studio7.2k—~1.6kAutomated safety check: PassCustom licence
Tech Writerstacklok/mecatl250—~2.2kAutomated safety check: PassApache-2.0

Similar skills

  • No Tropes

    OutThisLife/brooklyn-skills

    Detect and eliminate common AI writing tropes from generated text.

    199 GitHub stars~455 tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Writer

    rileyhilliard/claude-essentials

    Writing style and tone guide for human-sounding content. An agent skill from rileyhilliard/claude-essentials.

    130 GitHub stars~2k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.

    22k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Ss Docs

    Serial-Studio/Serial-Studio

    Write, update, or review Serial Studio's user-facing documentation: the doc/help manual, README.md, and examples READMEs.

    7.2k GitHub stars~1.6k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Tech Writer

    stacklok/mecatl

    A skill your agent uses when writing or substantively editing user-facing documentation: drafting a new page, rewriting or restructuring an existing one, adding a major section, or turning…

    250 GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Technical Writing

    frappe/skills

    Write prose in "Simplified Technical English". An agent skill from frappe/skills.

    147 GitHub stars~1.1k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

More from a2ui-project/a2ui

All 20 skills in this repo
  • A2ui Remediate Problem

    a2ui-project/a2ui

    Remediates a specific recommendation from an A2UI compliance report issue, or resolves any general GitHub issue, by inspecting context, implementing minimal targeted fixes, verifying tests, creating…

    17k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • A2ui Issue Triage

    a2ui-project/a2ui

    Automates the triage of GitHub issues in the A2UI repository.

    17k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • A2ui Audit

    a2ui-project/a2ui

    Main coordination skill to run the blueprint compliance, documentation synchronization, and test quality audits, posting the combined results as a labeled GitHub issue.

    17k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Iterative benchmarking, evaluation, and algorithmic optimization of alternative A2UI inference formats (such as Express, Atom, and Elemental).

    17k GitHub stars~985 tokensUpdated yesterday
    Auto-check passed
  • Automated generator for strongly typed Pydantic v2 data models and basic catalogs across any A2UI protocol version (v0.8, v0.9, v0.9.1, v1.0, etc.).

    17k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed
  • A2ui Python Development

    a2ui-project/a2ui

    Grounding, architectural standards, Python best practices, package facade conventions, testing, and verification workflows for developing any Python code across the entire A2UI repository (core…

    17k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Questions about Natural Writing

What does Natural Writing do?

Contains well-defined rules for creating natural, accurate, and readable writing. Natural Writing is an agent skill from a2ui-project/a2ui. Contains well-defined rules for creating natural, accurate, and readable writing.

When should I use Natural Writing?

Natural Writing fits situations like: authoring longer text; including reports; PR descriptions; analysis documents.

How do I install Natural Writing in Claude Code?

Run `npx skills add a2ui-project/a2ui --skill natural-writing -a claude-code`. Or copy the skill folder (.agents/skills/natural-writing in a2ui-project/a2ui) into .claude/skills/natural-writing in your project. Claude Code loads it when a task matches its description.

How do I install Natural Writing in Codex?

Run `npx skills add a2ui-project/a2ui --skill natural-writing -a codex`. Or copy the skill folder (.agents/skills/natural-writing in a2ui-project/a2ui) into .agents/skills/natural-writing in your project. Codex loads it when a task matches its description.

Can I use Natural Writing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add a2ui-project/a2ui --skill natural-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/natural-writing, .gemini/skills/natural-writing, .github/skills/natural-writing and .opencode/skills/natural-writing in your project.

What does Natural Writing need to run?

SKILL.md names no scripts, command-line tools or credentials: Natural Writing is instructions for the agent only.

Does Natural Writing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Natural Writing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Natural Writing use?

Natural Writing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Natural Writing use?

About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Natural Writing?

Skills that share tags, products or a category with Natural Writing: No Tropes (OutThisLife/brooklyn-skills, 199 stars), Writer (rileyhilliard/claude-essentials, 130 stars), Opik Documentation Patterns (comet-ml/opik, 22k stars) and Ss Docs (Serial-Studio/Serial-Studio, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Natural Writing?

a2ui-project (a GitHub organization) maintains it in a2ui-project/a2ui, which has 16,638 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 9, 2026.

Source: a2ui-project/a2ui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.