Writing Claude Skills
1 882 writing skills from 445 authors. They draft and edit prose. Half of them fit into 1 924 tokens or less — that is what one costs your context window when the agent loads it. 283 ship runnable scripts rather than instructions alone. We also found 239 copies of these same skills sitting in other people's repositories — counted once here, not 239 times.
1 882 unique 445 authors 185 from vendors
Build evidence-backed software/product roadmaps from repo state, tickets, ideas, audit findings, or user goals — prioritize and sequence work across Now/Next/Later, milestones, dependencies, risks, and handoffs. Use when asked for a roadmap, feature roadmap, technical roadmap, release plan, milestone plan, backlog prioritization, sequencing, what to build next, or to turn improve/ideate/brainstorm/design-discussion outputs into an execution sequence. Not for implementing code or writing PR-level plans.
Use when writing, reviewing, or rewriting user-facing error messages, validation messages, form errors, empty/error states, auth errors, failure notifications, retry/support copy, CLI errors, or API errors humans will read. Helps make errors specific, actionable, non-blaming, accessible, and safe without leaking sensitive details.
Use when authoring an agent skill that wraps a command-line tool — covers hands-on tool exploration, required vs. recommended sections, installation/usage structure, trigger-rich descriptions, task-grouped commands, progressive disclosure, and a pre-publish checklist. Triggers for CLI / command-line / terminal / shell-command tools and binary wrappers; for review, run the Checklist section.
General prose doctrine for anything a human will read — clear, concrete, free of ready-made phrases. Use when writing or editing documentation, explanations, summaries, commit messages, reports, or any other prose.
Write self-contained implementation plan files that a fresh, possibly weaker executor can run without the author's context — splitting work into PR-sized plans, with verification gates, STOP conditions, and a memo protocol for design forks. Use when asked to write/create a plan, turn a decided design or ticket into plans, or when another skill hands off plan-writing. Not for deciding what to build or executing plans.
去除中文文本中的 AI 生成痕迹，使其更符合中国 MBA 毕业论文的自然写作风格。当用户提到"去 AI 痕迹"、"去除 AI 写作痕迹"、"MBA 论文改写"、"让这段文字更像人写的"、"去除机器感"等关键词时触发。适用于需要降低文本 AI 特征、提升学术写作自然度的场景。
Use when assembling the AEA Data and Code Availability deposit for an AER, AER:Insights, or AEJ acceptance, writing the README, or auditing a replication package before the AEA Data Editor review. Implements the current AEA policy, including the February 2026 Data and Code Availability Policy.
Use when evaluating whether a research idea clears the AER top-5 bar, when routing between AER, AER:Insights, and the AEJ family, or when sharpening a fuzzy contribution sentence into one publishable claim. Apply before any writing begins.
| Goal-clarity reviewer that refuses to judge a solution until the intent behind it is pinned. Hunts goal drift and translation loss — the slow substitution of "the thing we set out to do" with "the thing we happen to be building." Sounds like a patient, relentless interrogator of "why are we doing this?" who will not be hurried past the question. Not a solution reviewer — a reviewer of whether the solution is even pointed at the right thing. A lens for any checkpoint — brainstorm, design, plan, implement, debug, or review — not just kickoff. nobody can say in one sentence what success looks like — any time the worry is "is this still the real goal?"
> Use with root `twg` for Confluence content, spaces, hierarchy, authoring, editing, comments, versions, permissions, exports, and CQL. Applies Confluence semantics and safe write rules.