CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally well-structured instruction-only skill: concrete and executable throughout, with a real validation gate, feedback loops, and clean one-level-deep progressive disclosure verified against the actual bundle. The only notable imperfection is minor redundancy in a couple of Core Stance and Punctuation Gate passages.

DimensionReasoningScore

Conciseness

The body is dense project-specific policy with no padding or explanation of concepts Claude already knows; however, the "catalog, not a checklist" point is stated twice within Core Stance, and the install-layout probing rationale in the Punctuation Gate could be trimmed, so a few tokens do not fully earn their place.

4 / 5

Actionability

Guidance is fully executable: a copy-paste-ready bash block for the punctuation gate with explicit placeholder-replacement instructions, a mode table mapping concrete asks to specific files, exact character rules ("Never produce em-dash (U+2014) or en-dash (U+2013)"), and per-mode activation phrases quoted verbatim.

5 / 5

Workflow Clarity

A clear sequence runs Pre-flight (numbered: locate text, audience lock, language detection) through mode selection to editing to an explicit validation gate with a fix-and-rerun loop ("Fix every finding while preserving meaning"), plus review checklists, batch-fix feedback loops ("Re-review the fix diff itself"), and a done-when Outcome Contract.

5 / 5

Progressive Disclosure

The body is an overview that conditionally routes to all ten existing one-level-deep reference files (verified present in references/), correctly externalizes bulk catalogs (the 648-line write-zh.md), and cross-links between references are siblings rather than nested, with the language-detection rules and mode table making navigation easy.

5 / 5

Total

19

/

20

Passed

Description

92%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 in third-person voice that concretely states what the skill does, when to use it, and what is out of scope. The only weakness is that the description field itself omits several natural trigger synonyms (proofread, polish, sound natural, and Chinese phrases like 润色/去AI味) that the frontmatter's when_to_use field already contains.

DimensionReasoningScore

Specificity

"Rewrites and polishes Chinese or English prose, technical instructions, and product copy" plus "drafting, editing, localizing, or cutting AI tone" lists multiple concrete actions covering every surface the skill handles, matching the comprehensive-coverage anchor with no meaningful gaps.

5 / 5

Completeness

It explicitly answers both what ("Rewrites and polishes Chinese or English prose, technical instructions, and product copy") and when ("Use when drafting, editing, localizing, or cutting AI tone") with concrete trigger phrases, matching the top anchor's pattern.

5 / 5

Trigger Term Quality

"Use when drafting, editing, localizing, or cutting AI tone" gives good natural-term coverage, but common user phrasings like "proofread", "polish", "sound natural", and the Chinese triggers (润色, 去AI味) are missing from the description field even though they appear in when_to_use.

4 / 5

Distinctiveness Conflict Risk

A clear niche (CN/EN prose de-AI-ing) with distinct triggers, and the explicit exclusion "Not for code comments or commit messages" fences off the nearest overlapping skill, leaving minimal conflict risk.

5 / 5

Total

19

/

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