How do I install the Storm Polish skill?

Run npx skillmds@latest add fradser/storm-polish in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Storm Polish safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Storm Polish?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Storm Polish free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Storm Polish?

FradSer (@fradser) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Storm Polish by fradser — Agent Skill

Name: Storm Polish
Rating: 4.2 (5 reviews)
Author: FradSer

Storm Polish

Run STORM phase 4 — article polishing. This skill should be used when the user asks to "polish the storm article", "finalize the article", or invokes /storm:polish. Adds a summary section, removes duplicate content, and verifies citation integrity.

FradSer Updated Aug 19, 2026 580 repo stars

File contents

/storm:polish

Phase 4 of the STORM pipeline. Adds a summary/intro section, removes duplicate content across sections, and verifies every inline [n] citation resolves to a References entry and vice versa.

CRITICAL: Prerequisites

Load storm-engine via the Skill tool.
article.md MUST exist (phase 3 complete). If absent, stop and instruct the user to run /storm:write first.

Completion Contract

This phase is complete iff article-polished.md exists. If --force is not set and it exists, skip and exit early.

Procedure

Resolve output dir.
Read article.md, outline.md, and research/sources.json.
Summary section — if outline.md had an "Introduction" or "Summary" placeholder, write a summary section synthesizing the article's main points (1-2 paragraphs). Do not introduce new claims or citations not already in the body.
Duplicate removal (default on; --remove-duplicate is explicit but the behavior is the default) — detect near-duplicate paragraphs across sections and remove the later occurrence, keeping the one in the more topically-appropriate section.
Citation integrity — build the set of [n] keys present in the body. Append a ## References section listing exactly those sources, numbered to match, each as n. title — url (accessed YYYY-MM-DD). Drop any [n] in the body that has no source (replace with ). Drop any source not cited (do not list uncited sources in References).
Write article-polished.md.
Update run-config.json: phases.polish = "completed", final word count, source count, any integrity warnings.

Output

Report: final word count, number of cited sources, number of duplicate paragraphs removed, any integrity warnings (missing sources / TODO sections), and the absolute path to article-polished.md.

---name: storm-polishdescription: Run STORM phase 4 — article polishing. This skill should be used when the user asks to "polish the storm article", "finalize the article", or invokes /storm:polish. Adds a summary section, removes duplicate content, and verifies citation integrity.---# /storm:polishPhase 4 of the STORM pipeline. Adds a summary/intro section, removes duplicate content across sections, and verifies every inline `[n]` citation resolves to a References entry and vice versa.## CRITICAL: Prerequisites- Load `storm-engine` via the Skill tool.- `article.md` MUST exist (phase 3 complete). If absent, stop and instruct the user to run `/storm:write` first.## Completion ContractThis phase is complete iff `article-polished.md` exists. If `--force` is not set and it exists, skip and exit early.## Procedure1. Resolve output dir.2. Read `article.md`, `outline.md`, and `research/sources.json`.3. **Summary section** — if `outline.md` had an "Introduction" or "Summary" placeholder, write a summary section synthesizing the article's main points (1-2 paragraphs). Do not introduce new claims or citations not already in the body.4. **Duplicate removal** (default on; `--remove-duplicate` is explicit but the behavior is the default) — detect near-duplicate paragraphs across sections and remove the later occurrence, keeping the one in the more topically-appropriate section.5. **Citation integrity** — build the set of `[n]` keys present in the body. Append a `## References` section listing exactly those sources, numbered to match, each as `n. title — url (accessed YYYY-MM-DD)`. Drop any `[n]` in the body that has no source (replace with ``). Drop any source not cited (do not list uncited sources in References).6. Write `article-polished.md`.7. Update `run-config.json`: `phases.polish = "completed"`, final word count, source count, any integrity warnings.## OutputReport: final word count, number of cited sources, number of duplicate paragraphs removed, any integrity warnings (missing sources / TODO sections), and the absolute path to `article-polished.md`.

Frequently asked questions