improve-writing

improve-writing is a skill for Claude Code, Codex from pilotspace/pilot-space. It costs 17 tokens per session (1,791 once invoked), scanned A, original, Apache-2.0.

A writing editor for technical documentation, issue descriptions, and notes.

In plain words
What is it for?
It helps rewrite drafts so they are clearer, shorter, more specific, and easier to read.
Why use it?
It removes vague wording, unnecessary length, and unclear structure while keeping the technical meaning.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/pilotspace/pilot-space/improve-writing
Any agent
npx skills add pilotspace/pilot-space --skill improve-writing
Clone the repo
git clone --depth 1 https://github.com/pilotspace/pilot-space

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for improve-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/pilotspace/pilot-space/improve-writing.svg)](https://agentmods.dev/skills/pilotspace/pilot-space/improve-writing)
Your own site
<a href="https://agentmods.dev/skills/pilotspace/pilot-space/improve-writing"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/improve-writing.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,791 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.01791
Opus 5 $0.00009 $0.00896
Sonnet 5 $0.00003 $0.00358
Haiku 4.5 $0.00002 $0.00179

Measured 5d ago against content hash 34c1e3c70c6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

improve-writing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

backend/src/pilot_space/ai/templates/skills/improve-writing/SKILL.md · 208 lines

How it starts

The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Improve Writing Skill

Enhance technical writing clarity, conciseness, and readability while preserving technical accuracy.

Quick Start

Use this skill when:

  • Drafting issue descriptions, documentation, or notes
  • User requests writing improvement (/improve-writing)
  • AI detects unclear or verbose text

Example:

Original: "The thing is that when users are trying to log in to the system,
they sometimes get errors and it doesn't work properly."

Improved: "Users encounter login errors intermittently. Root cause unknown."

Confidence: RECOMMENDED
Changes: Removed filler words, made specific, added action item

Workflow

  1. Analyze Text

    • Identify issues:
      • Clarity: Vague terms ("thing", "sometimes", "properly")
      • Conciseness: Filler words ("the thing is", "trying to")
      • Structure: Long sentences, lack of paragraphs
      • Technical accuracy: Imprecise terminology
  2. Apply Improvements

    • Clarity:
      • Replace vague terms with specifics
      • Use active voice over passive
      • Define acronyms on first use
    • Conciseness:
      • Remove filler words and redundancy
      • Shorten long sentences (max 25 words)
      • Use bullet points for lists
    • Structure:
      • Add headers for sections
      • Break into digestible paragraphs (3-4 sentences)
      • Use consistent formatting
  3. Preserve Technical Content

    • Keep all technical terms and specifics
    • Maintain code examples verbatim
    • Don't alter user intent or meaning
  4. Tag Confidence

    • RECOMMENDED: Clear improvement, no ambiguity
    • DEFAULT: General enhancement, maintains meaning
    • ALTERNATIVE: Multiple valid approaches, style preference

Output Format

{
  "original": "Original text...",
  "improved": "Improved text...",
  "confidence": "RECOMMENDED",
  "changes": [
    {"type": "clarity", "description": "Replaced 'thing' with 'authentication module'"},
    {"type": "conciseness", "description": "Removed filler phrase 'the thing is that'"},
    {"type": "structure", "description": "Split into two sentences for readability"}
  ],
  "readability_score": {
    "original": 45,
    "improved": 68,
    "metric": "Flesch Reading Ease"
  },
  "suggestions": [
    "Consider adding code example for login flow",
    "Specify browser/environment for reproducibility"
  ]
}

Read the full file on GitHub · 208 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 208 lines · 17 tokens per session scan A 34c1e3c70c6e

Subscribe to this mod's changes

improve-writing is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,791 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens