ase-docs-proofread
SolidAnalyze the documents for spelling, punctuation, or grammar errors. Use when the user wants to "proofread" or "spellcheck" a document.
Code & Development 42 stars
4 forks Updated yesterday Apache-2.0
Install
Quality Score: 80/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
@${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md
@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
<skill name="ase-docs-proofread">
Analyze documents for spelling, punctuation, or grammar errors
</skill>
<expand name="getopt"
arg1="ase-docs-proofread"
arg2="--auto|-a">
$ARGUMENTS
</expand>
<objective>
*Proofread* the documents of `<getopt-arguments/>` for problems in their
*spelling*, *punctuation*, or *grammar* and propose corrections.
</objective>
<flow>
1. <step id="STEP 1: Investigation">
<if condition="<ase-project-boxing/> is equal `black`">
The project source artifacts are classified as a *black box*, so
the user does *not* want them inspected or their problems surfaced.
*Skip* the entire investigation and reporting: do *not* invoke any
`Glob` or `Agent` tool and do *not* read any document, only output
the following <template/> and then *SKIP* the remaining steps STEP 2
and STEP 3:
<template>
<ase-tpl-bullet-normal/> **PROOFREAD**: *suppressed* (`project.boxing` is `black`)
</template>
</if>
First, use the following <template/> to give a hint on this step:
<template>
<ase-tpl-bullet-secondary/> **PROOFREADING INVESTIGATION**
</template>
Dispatch the investigation to *sub-agents* via the `Agent`
tool so that *no* investigation details leak into the user-visible
transcript. The sub-agents pe...
Details
- Author
- rse
- Repository
- rse/ase
- Created
- 3 months ago
- Last Updated
- yesterday
- Language
- TypeScript
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
Code & Development Solid
ase-code-analyze
Analyze the source code for problems in either the logic and semantics and its related control flow, performance and efficiency, or security.
42 Updated yesterday
rse Code & Development Solid
ase-docs-distill
Distill a provided document into a flat, importance-ranked list of its key points, each with a salience rank, a rationale, and a verbatim line-cited evidence snippet. Use when the user wants to "distill", "summarize the key points", or "extract the essence" of a document or pasted text.
42 Updated yesterday
rse Code & Development Solid
ase-code-lint
Lint source code for potential code quality problems. Use when the user wants to "lint" or "check" source code.
42 Updated yesterday
rse