rse/ase / plugin/skills/ase-docs-refine
ase-docs-refine
VerifiedRefine the sentence structure and style of the documents: shorten long sentences, replace cumbersome nominal constructions with verbs, make enumerations parallel, strike filler words and redundancy, fix awkward transitions, and adjust voice, while content, numbers, and technical terms stay exactly as they are. Use when the user wants to "refine", "tighten", or "polish" the wording of a document.
help.md
View on GitHub
## NAME
`ase-docs-refine` - Refine Document Wording
## SYNOPSIS
`ase-docs-refine`
[`--help`|`-h`]
[`--auto`|`-a`]
*docs-reference*
## DESCRIPTION
The `ase-docs-refine` skill performs a *light rewriting* of awkward or
unclear sentences in the referenced documents, *without reshaping the
argument*: restructuring sentences for rhythm and clarity, making
enumerations parallel, cutting filler and redundancy, fixing awkward
transitions, and adjusting voice. *Content, numbers, and technical
terms stay exactly as they are.* The investigation is dispatched to a
sub-agent (`ase:ase-docs-refine`) so that scanning details do not leak
into the user-visible transcript.
The checked refinement types are:
1. *Structure*: overlong, convoluted, or awkwardly built sentences,
split or restructured for rhythm and clarity.
2. *Nominalization*: cumbersome nominal constructions, replaced with
plain verbs.
3. *Parallelism*: non-parallel enumerations, brought into one
grammatical shape - a list whose items mix noun phrases,
imperatives, and full sentences, a heading set mixing gerunds and
nouns, or an inline series whose members do not share their form.
4. *Filler*: filler words, empty intensifiers, and redundant
restatements, struck.
5. *Transition*: abrupt or misleading transitions between sentences or
paragraphs, smoothed. An existing transition is only smoothed or
removed - a connective is *never* inserted where the original
asserted no such relation, as that would add a logical claim.
6. *Voice*: needless passive voice turned active, needless hedging
struck, and shifts in grammatical person or mood aligned with the
rest of the document.
The rewriting always stays *within* a sentence. Dropping a whole
sentence, paragraph, example, or list item for the sake of brevity is
*length reduction*, not refinement, and belongs to
[`ase-docs-shorten`](../ase-docs-shorten/help.md). The recommended order
over one document is `ase-docs-shorten` first (cut the bulk), then
`ase-docs-refine` (polish what survives), then `ase-docs-proofread`
(final correctness pass), so no polishing effort is spent on text which
is later dropped.
For each detected problem, the skill renders a unified-diff
*REFINEMENT* preview and either asks the user to `ACCEPT` or `REJECT`
the proposed refinement interactively (or refine it via a free-text
hint, which re-proposes the refinement without limit) or - with
`--auto` - applies all refinements automatically. A proposal which
shifts the meaning even slightly - a lost negation, a changed
qualifier, a renamed technical term - is dropped instead of applied.
For a project with `grey` boxing, the preview shows only a condensed
one-line form instead of the full unified diff, and for a project with
`black` boxing, the documents are not refined at all.
## OPTIONS
- `--auto`|`-a`:
Automatically apply every proposed refinement without asking the
user via the interactive dialog.
## ARGUMENTS
- *docs-reference*:
A file, directory, or other reference to the documents to
refine.
## SCENARIOS
- You want long, convoluted sentences broken into readable ones
- You want nominal style like "perform a validation of" turned into verbs
- You want a bullet list of mixed noun phrases and sentences made parallel
- You want filler words and redundant restatements struck
- You want abrupt transitions between paragraphs smoothed
- You want needless passive voice or hedging adjusted
- You want the wording polished without touching facts or figures
## EXAMPLES
Refine a single document interactively:
```text
❯ /ase-docs-refine README.md
```
Refine an entire documentation directory automatically:
```text
❯ /ase-docs-refine --auto docs/
```
## SEE ALSO
[`ase-docs-shorten`](../ase-docs-shorten/help.md), [`ase-docs-proofread`](../ase-docs-proofread/help.md), [`ase-docs-distill`](../ase-docs-distill/help.md).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |