No Tropes
OutThisLife/brooklyn-skills
Detect and eliminate common AI writing tropes from generated text.
Contains well-defined rules for creating natural, accurate, and readable writing.
$ npx skills add a2ui-project/a2ui --skill natural-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install a2ui-project/a2ui natural-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "natural-writing" agent skill from https://github.com/a2ui-project/a2ui/tree/main/.agents/skills/natural-writing into .claude/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/a2ui-project/a2ui/tree/main/.agents/skills/natural-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add a2ui-project/a2ui --skill natural-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install a2ui-project/a2ui natural-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/a2ui-project/a2ui.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/natural-writing .agents/skills/natural-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "natural-writing" agent skill from https://github.com/a2ui-project/a2ui/tree/main/.agents/skills/natural-writing into .agents/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add a2ui-project/a2ui --skill natural-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install a2ui-project/a2ui natural-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/a2ui-project/a2ui.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/natural-writing .cursor/skills/natural-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "natural-writing" agent skill from https://github.com/a2ui-project/a2ui/tree/main/.agents/skills/natural-writing into .cursor/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/a2ui-project/a2ui.git --path .agents/skills/natural-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add a2ui-project/a2ui --skill natural-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install a2ui-project/a2ui natural-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/a2ui-project/a2ui.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/natural-writing .gemini/skills/natural-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "natural-writing" agent skill from https://github.com/a2ui-project/a2ui/tree/main/.agents/skills/natural-writing into .gemini/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install a2ui-project/a2ui natural-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add a2ui-project/a2ui --skill natural-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/a2ui-project/a2ui.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/natural-writing .github/skills/natural-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "natural-writing" agent skill from https://github.com/a2ui-project/a2ui/tree/main/.agents/skills/natural-writing into .github/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add a2ui-project/a2ui --skill natural-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install a2ui-project/a2ui natural-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/a2ui-project/a2ui.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/natural-writing .opencode/skills/natural-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "natural-writing" agent skill from https://github.com/a2ui-project/a2ui/tree/main/.agents/skills/natural-writing into .opencode/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
natural-writingContains 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. 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.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 03b77ae. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
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.
.claude/skills/natural-writing/SKILL.md (or your agent's skills folder).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.
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.
Do not replace simple "is" or "are" verbs with flowery equivalents.
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.
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.
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."
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.
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.
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.
Do not treat a descriptive article title (like a list or broad topic) as a proper noun in the first sentence.
Do not populate "See Also" sections with broad, generic terms. Links must be directly relevant and specific to the subject.
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.
Avoid sentences that structure a contrast unnecessarily.
Avoid listing exactly three adjectives or three noun phrases to sound "comprehensive."
Do not use "from X to Y" unless X and Y are endpoints of a logical scale (like time or size).
Use sentence case for headers (e.g., "Early life," not "Early Life"). Do not use title case in headers.
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.
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.
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.
?plain=1 so a line anchor such as #L10-L20 works.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
Just SKILL.md in .agents/skills/natural-writing of a2ui-project/a2ui.
Open the folder on GitHubat commit 03b77ae
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Natural Writing this skilla2ui-project/a2ui | 17k | 1 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| No TropesOutThisLife/brooklyn-skills | 199 | — | ~455 | Automated safety check: Pass | MIT | |
| Writerrileyhilliard/claude-essentials | 130 | — | ~2k | Automated safety check: Pass | MIT | |
| Opik Documentation Patternscomet-ml/opik | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Ss DocsSerial-Studio/Serial-Studio | 7.2k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Tech Writerstacklok/mecatl | 250 | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
OutThisLife/brooklyn-skills
Detect and eliminate common AI writing tropes from generated text.
rileyhilliard/claude-essentials
Writing style and tone guide for human-sounding content. An agent skill from rileyhilliard/claude-essentials.
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
Serial-Studio/Serial-Studio
Write, update, or review Serial Studio's user-facing documentation: the doc/help manual, README.md, and examples READMEs.
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…
frappe/skills
Write prose in "Simplified Technical English". An agent skill from frappe/skills.
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…
a2ui-project/a2ui
Automates the triage of GitHub issues in the A2UI repository.
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.
a2ui-project/a2ui
Iterative benchmarking, evaluation, and algorithmic optimization of alternative A2UI inference formats (such as Express, Atom, and Elemental).
a2ui-project/a2ui
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.).
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…
Categories
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.
Natural Writing fits situations like: authoring longer text; including reports; PR descriptions; analysis documents.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Natural Writing is instructions for the agent only.
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.
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.
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.
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.
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.
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.