skills.rest
shenmuxing
shenmuxingCOMMUNITY
Explore all skills by this author →
GitHub

style-review

Review Markdown prose against a 21-rule agent style system.

2|1|Updated May 7, 2026
Search Tags:#markdown#prose polishing#style review#writing audit#draft comparison
One-click install
npx skills add https://github.com/shenmuxing/EtaSkill --skill style-review-shenmuxing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: style-review
Source: https://github.com/shenmuxing/EtaSkill/tree/main/skill-examples/style-review
Command: npx skills add https://github.com/shenmuxing/EtaSkill --skill style-review-shenmuxing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-style, and includes references (resource) components.

What problem does it solve?

This Skill reviews Markdown prose after it has been drafted and identifies rule-based writing issues that need cleanup, helping you turn a rough first pass into a more polished version.

Core Features & Use Cases

  • Rule-by-rule audit: Checks prose against a 21-rule style system and reports concrete violations with line-level detail when possible.
  • Single-file polishing workflow: Reviews one Markdown file, then produces a revised sibling copy after user confirmation.
  • Draft comparison: Compares two drafts and reports per-rule differences without rewriting either file.
  • Use case: A teammate asks for a cleaner project update, and you want an automated second pass that flags verbosity, jargon, unsupported claims, and structural writing issues before sharing it.

Quick Start

Ask the Skill to review a Markdown file for style-rule violations and, if needed, produce a polished copy beside the original.

Frequently Asked Questions about style-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Markdown prose against writing style rules?▼

To audit Markdown prose, the Skill reviews your draft against a 21-rule agent style system and reports concrete violations with line-level detail, identifying style issues for cleanup.

Can I compare two Markdown drafts to see style differences?▼

Yes, you can compare two Markdown drafts to report per-rule style differences without rewriting either file, using side-by-side draft comparison to identify revision variations.

Do I need the agent-style CLI to run a writing audit?▼

Yes, you need the agent-style CLI dependency to perform style audits, generate compare output, and verify revisions when polishing your Markdown drafts.

How do I polish a Markdown file and generate a revised copy?▼

You can polish a Markdown file by requesting a style review, then the Skill produces a revised sibling copy beside the original draft after you confirm the suggested changes.

What kind of writing issues does a Markdown style review catch?▼

A Markdown style review catches verbosity, jargon, unsupported claims, and structural writing issues by applying deterministic and semantic checks to your drafted prose.

When should I use a post-hoc style review instead of rewriting?▼

Use a post-hoc style review when you have a rough first pass and need an automated second pass to flag writing-rule violations before sharing a cleaner project update.

Related Skills

Explore More Content & Communication Skills→
shenmuxingshenmuxing
2

muxing-style-review

Review Markdown, plain text, and LaTeX prose for clarity and evidence discipline.

Community
Advanced
adrianliechtiadrianliechti
4

brand-review

Identify brand-voice deviations in marketing content and propose before/after fixes.

Community
Advanced
joshkellett87joshkellett87

docs-write

Format Markdown and MDX docs with Metabase style using Prettier.

Community
Basic
htlin222htlin222
77

vale

Run Vale prose linter on markdown and text files to identify and auto-fix writing issues.

Community
Intermediate