writing-style

writing-style is a skill for Claude Code from DheerG/swarms. It costs 29 tokens per session (1,949 once invoked), scanned A, original, MIT.

A writing-review tool that breaks text into paragraph structures and counts repeated patterns across a whole piece.

In plain words
What is it for?
Use it during editing to review articles, reports, or other long text and produce a pattern report for an editor to assess.
Why use it?
It finds repetition that is easy to miss when reading one paragraph at a time, helping prevent writing from sounding mechanical.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the swarms plugin — 13 skills, 10 commands, 2 agents, 2 hooks shipped together

Good fit Use it during editing to review articles, reports, or other long text and produce a pattern report for an editor to assess.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dheerg/swarms/writing-style
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.

Any agent
npx skills add DheerG/swarms --skill writing-style
Clone the repo
git clone --depth 1 https://github.com/DheerG/swarms

Made for: Claude Code.

Or install swarms, the plugin that ships this one along with the rest of its 13 skills, 10 commands, 2 agents, 2 hooks.

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 writing-style

README.md
[![agentmods](https://agentmods.dev/badge/skills/dheerg/swarms/writing-style.svg)](https://agentmods.dev/skills/dheerg/swarms/writing-style)
Your own site
<a href="https://agentmods.dev/skills/dheerg/swarms/writing-style"><img src="https://agentmods.dev/badge/skills/dheerg/swarms/writing-style.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,949 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00029 $0.01949
Opus 5 $0.00015 $0.00975
Sonnet 5 $0.00006 $0.00390
Haiku 4.5 $0.00003 $0.00195

Measured 8d ago against content hash a0a7e8315896, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

writing-style 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 8d 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.

skills/writing-style/SKILL.md · 180 lines

How it starts

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

Writing Style — Structural Pattern Analysis

Purpose

A sentence or paragraph can look fine in isolation. When the same structural shape repeats across 1,000-3,000 words, the aggregate creates a mechanical feeling — even though no single instance is wrong. Linear readers miss this because they process sequentially and each paragraph clears the "is this well-written?" bar individually.

This analysis solves the forest-vs-trees problem. It decomposes every paragraph's structure, then aggregates the fingerprints to surface repetition invisible to linear reading.

How to Use

Invoke this skill using the Skill tool: swarm:writing-style. Pass the piece's text or file path as the args parameter. The skill returns a structured report. The lead relays the report to the editor for interpretation. Invoke during the review phase (required) or optionally during drafting.

The report is advisory, never gating. The editor applies editorial judgment to the data. The Economist escape clause applies: if a flagged pattern serves the piece, keep it and note why.

Analysis Process

Exclude from analysis: Table cells, comparison tables, and structured list items with deliberately parallel construction (numbered checklists, step-by-step procedures). These are exempt from construction density calculation but still included in named pattern counts. Report construction density both with and without these items so the editor has both numbers.

Introductory and concluding paragraphs adjacent to lists are NOT exempt — only the parallel list items themselves.

Pass 1: Structural Decomposition

For each body paragraph, classify:

1. Opening move — how the paragraph begins:

  • claim: declarative assertion
  • scenario: narrative with actors or concrete situation
  • question: interrogative opening
  • data: leads with a statistic or cited fact
  • contrast: opens with negation or opposition
  • definition: introduces or defines a term
  • transition: bridges from previous section
  • imperative: directive opening

Read the full file on GitHub · 180 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. 8d ago First seen · 180 lines · 29 tokens per session scan A a0a7e8315896

Subscribe to this mod's changes

writing-style is a skill published in the GitHub repository DheerG/swarms (85 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 1,949 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-30.

Related

Other skills, from other repositories

pocket-development

Use when executing implementation plans of one or more tasks. Trigger on execute plan, delegate tasks, dispatch subagents. Combines delegate handoff discipline with prompt-engineering attention mechanics.

rfxlamia/pocketto · 40 tokens

pocket-planning

Converts a pocket-grinding spec into a TDD-structured execution plan of full Pocket Packets. Use when pocket-grinding handoff arrives (spec path + acceptance criteria). Trigger on "create plan", "build plan", "pocket-planning", or when pocket-grinding skill invokes this. Outputs tasks ready to dispatch via…

rfxlamia/pocketto · 76 tokens

pocket-closing

Terminal pocket stage. User invokes after pocket-development's phase-level pass writes verdicts. Reconciles reviews against log.json, gates on REVIEWFAIL/REVIEWBLOCKED, advances REVIEW→DONE, runs log close, and emits a closeout summary. Trigger on "pocket-closing", "close the plan", "close out", "finalize plan", or…

rfxlamia/pocketto · 92 tokens

pocket-grinding

BDD-driven feature/fix discovery before any implementation. Use when planning a feature, designing a fix, or exploring options before building. Trigger on "pocket-grinding", "brainstorm", "think through", "plan this", "before we build". Invokes pocket-planning at handoff.

rfxlamia/pocketto · 65 tokens

pocket-help

Onboarding and routing guide for the Pocket skill ecosystem. Use when someone asks what Pocket is, which Pocket skill to use, how the end-to-end flow works, or when Pocket is better than lighter Superpowers-style flows. Trigger on "what is pocket", "how do I use pocket", "which pocket skill", "explain pocket"…

rfxlamia/pocketto · 112 tokens

structured-research

Standalone skill for validating an explicit assumption with structured research. Use when a user holds a belief that is still an assumption — a technical claim, a library's behavior, a "this is probably how X works" — and wants it investigated methodically before it leaks into planning or code. Recommends a research…

rfxlamia/pocketto · 147 tokens