agent-style

Featured

Literature-backed English technical-prose writing rules (agent-style, 21 rules). Its lane is FORMAL technical prose (papers, design docs, proposals, READMEs, commit messages). Use ONLY when the user explicitly asks for agent-style by name (e.g. "apply agent-style", "write/revise this per agent-style rules", "iterate until agent-style clean"). NOT for de-AI-ing casual or voiced text — use remove-ai-patterns for that. Do not auto-trigger for ordinary prose or documentation tasks.

AI & Automation 1,997 stars 130 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- SPDX-License-Identifier: CC-BY-4.0 --> # agent-style agent-style is a literature-backed English technical-prose writing ruleset for AI agents. The rules are curated in *The Elements of Agent Style* (https://github.com/yzhao062/agent-style), CC BY 4.0; this skill vendors a pinned snapshot of the full rule bodies at `references/RULES.md` (pin recorded in `references/UPSTREAM-PIN`). Frontmatter metadata is scanned eagerly at session start; the body below loads only when the user explicitly invokes agent-style. ## Self-Verification Handshake When asked "is agent-style active?" or "what writing rules apply here?", answer: `agent-style active: 21 rules (RULE-01..12 canonical + RULE-A..I field-observed); full bodies at references/RULES.md; pin in references/UPSTREAM-PIN.` ## The 21 Rules (Compact Directives) Canonical rules (from Strunk & White 1959, Orwell 1946, Pinker 2014, Gopen & Swan 1990): - **RULE-01 Curse of knowledge**: Name your intended reader; do not assume they share your tacit knowledge. - **RULE-02 Passive voice**: Prefer active voice when the agent is known and worth naming. - **RULE-03 Concrete language**: Prefer concrete, specific terms over abstract category words like "factors" or "aspects". - **RULE-04 Needless words**: Cut filler phrases like "in order to", "due to the fact that", "may potentially". - **RULE-05 Dying metaphors**: Delete clichés like "pushes the boundaries", "paradigm shift", or "state of the art". - **RULE-06 Plain English**: Prefer...

Details

Author
pchalasani
Repository
pchalasani/claude-code-tools
Created
1 years ago
Last Updated
3 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

agent-rules

Rewrites or audits text so it reads plainly: answer first, no preamble, no hype adjectives, no marketing voice, sentences short enough to read once. Applies a named ruleset plus ASD-STE100 Simplified Technical English. Use when asked to clean up, tighten, de-slop, or humanise a draft, a README, a release note, a commit message, a PR description, or any AI-generated prose. Also use when asked to check text against the rules without changing it. Do not use for code changes, and do not use to shorten something the user asked to be thorough.

12 Updated 1 months ago
tornikegomareli
AI & Automation Featured

writing-rules

Write or review anything an agent reads — a core rule, a profile gate, a SKILL.md description, an instruction-file line, a subagent prompt, a handoff note, a verify-phase label. Part of the Agentsmith harness; supplies the levers that decide whether a line changes behaviour or only costs tokens — the two loads, context pointers, the ladder, completion criteria, leading words, the no-op test. Its default move is deletion, so it earns most on a draft that already exists.

185 Updated 1 weeks ago
PromptPartner
AI & Automation Listed

writing-for-agents

Create or edit agent-facing instructions such as AGENTS.md, CLAUDE.md, skills, roles, and workflow documents. Use when triggers, completion criteria, context pointers, instruction hierarchy, or duplication affect whether an agent can execute the document reliably.

2 Updated yesterday
HECer