CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write

Rewrites and polishes Chinese or English prose, technical instructions, and product copy. Use when drafting, editing, localizing, or cutting AI tone. Not for code comments or commit messages.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable instruction skill with excellent progressive disclosure and explicit validation steps. Its main weakness is density: several judgment rules run long with stacked clauses and could be materially tightened, and the overall workflow order is implicit across sections.

Suggestions

Split multi-clause rules (e.g., "A piece has a speaker" and "Material gate before drafting long-form") into short lead sentences plus sub-bullets, cutting each by roughly half while preserving the policy.

Add one compact end-to-end sequence (Pre-flight, Mode Picker, Hard Rules, Punctuation Gate, Output) near the top so the reader does not have to reassemble the pipeline from separate sections.

Move the per-mode "Activate when" trigger lists into the existing mode table or the frontmatter when_to_use field to avoid duplicating trigger phrases in two places.

DimensionReasoningScore

Conciseness

The body avoids known-concept padding and offloads heavy catalogs to references, but several rules stack three or four caveats apiece (the ~120-word "A piece has a speaker" bullet and the ~160-word "Material gate before drafting long-form" paragraph) that could be tightened without losing policy content.

3 / 5

Actionability

Concrete guidance throughout: a mode-picker table mapping asks to specific files, language-detection load rules, and a runnable punctuation-gate script with fallback paths. The bash block requires placeholder substitution (<skill-base-dir>, <lang>) and no inline before/after edit example is given, so it is not copy-paste ready.

4 / 5

Workflow Clarity

Explicit validation checkpoints exist (Punctuation Gate before returning text, batch reconciliation, scoped diff plus verification for repo edits) and Gotchas defines a re-review feedback loop, but the end-to-end sequence (Pre-flight, Mode Picker, Hard Rules, Gate, Output) must be assembled by the reader across separate sections rather than presented as one pipeline.

4 / 5

Progressive Disclosure

SKILL.md acts as a clean router: every referenced file exists (11 reference files and the gate script), references are one level deep with explicit load conditions and markdown links, and large catalogs (e.g., 55KB write-zh.md) are appropriately split out.

5 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states capabilities, an explicit "Use when" trigger clause, and a scope exclusion. Trigger coverage is good though a few natural synonyms are missing, and the capability verbs could be more distinct from each other.

DimensionReasoningScore

Specificity

"Rewrites and polishes Chinese or English prose, technical instructions, and product copy" plus "cutting AI tone" names several concrete actions with a defined bilingual scope, but "rewrites" and "polishes" are near-synonymous verbs rather than distinct operations, leaving minor coverage gaps.

4 / 5

Completeness

It explicitly answers both "what" (rewrites and polishes prose, technical instructions, and product copy; cuts AI tone) and "when" ("Use when drafting, editing, localizing, or cutting AI tone") with concrete trigger phrases, and adds an exclusion boundary ("Not for code comments or commit messages").

5 / 5

Trigger Term Quality

"drafting, editing, localizing, or cutting AI tone" (plus "rewrites", "polishes") are natural phrases users would say, but common synonyms like "proofread", "sound natural/human", and "tweet/social post" are absent from the description.

4 / 5

Distinctiveness Conflict Risk

The bilingual prose de-AI-ification niche and the explicit exclusion of code comments and commit messages make it mostly distinct, but "drafting, editing" still carries minor overlap risk with generic writing/editing skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

tw93/Waza

Path

skills/write/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.