CtrlK
BlogDocsLog inGet started
Tessl Logo

write

Rewrites and polishes prose in Chinese or English, removes AI-like wording, and reviews product localization copy while preserving intent for drafts, docs, release notes, launch copy, and social posts. Use when users ask in any language to draft, rewrite, proofread, localize, polish release notes, remove AI-like wording, or prepare launch and social copy. Not for code comments, commit messages, or inline docs.

72

Quality

89%

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

The canonical home for this skill is write in tw93/Waza

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The skill body is an efficiently written, opinionated prose-editing guide with concrete pre-flight, mode selection, hard rules, and a validation punctuation gate backed by real reference files and a script. It is actionable and well-structured, with only minor room to tighten elaborated principles.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence with no basic-concept padding, but a few principles (the 'speaker' bullet, several Hard Rules) are elaborated at length and could be tightened without losing the judgment nuance.

4 / 5

Actionability

Concrete guidance throughout: an executable Punctuation Gate bash block with two install-layout candidate paths, a mode-picker table mapping asks to specific files, numbered pre-flight steps, and a gotchas table; minor gaps are the path-substitution placeholders and reliance on reference files for full procedures.

4 / 5

Workflow Clarity

Clear sequence (Pre-flight, Mode Picker, Hard Rules, Punctuation Gate) with an explicit validation checkpoint ('Fix every finding while preserving meaning' before returning); because the validation gate is present, the destructive/batch cap at 3 does not apply, though error-recovery feedback loops are only implicit.

4 / 5

Progressive Disclosure

A well-organized overview pointing one level deep to real reference files (verified: durable-context.md, write-zh.md, mode-*.md, etc. all exist in references/), with the mode table and pre-flight clearly signaling which file loads for which condition; inline mode sections stay as brief pointers.

5 / 5

Total

17

/

20

Passed

Description

100%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.

The description is a strong, third-person statement that names concrete actions, surfaces, natural bilingual trigger terms, and explicit exclusions. It clearly answers both what the skill does and when to use it, with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Rewrites and polishes prose', 'removes AI-like wording', 'reviews product localization copy') across named surfaces (drafts, docs, release notes, launch copy, social posts), with comprehensive coverage; not merely a domain label.

5 / 5

Completeness

Explicitly answers both 'what' (rewrite/polish/de-AI/localize copy preserving intent) and 'when' ('Use when users ask in any language to draft, rewrite, proofread...'), with concrete trigger phrases and an explicit exclusion scope.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms in both languages ('draft, rewrite, proofread, localize, polish release notes, remove AI-like wording') plus Chinese synonyms (去AI味, 审稿, 本地化文案), matching what users would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (prose editing and AI-taste removal, localization copy) with distinct triggers and explicit exclusions ('Not for code comments, commit messages, or inline docs'), minimizing conflict with adjacent skills.

5 / 5

Total

20

/

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.

Validation15 / 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
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.