CtrlK
BlogDocsLog inGet started
Tessl Logo

technical-writing

Four-layer standard for technical prose: Diataxis document modes, Google developer style sentences, Simplified Technical English instruction rules, Global English disambiguation. Use when writing or reviewing docs, RFCs, README files, PR descriptions, or commit messages.

71

Quality

86%

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

90%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 lean, highly actionable style guide that sequences four writing layers and validates with a worked example and review checklist. It is concisely written and well-structured, with only minor room to tighten the workflow into an explicit validate-fix-retry loop.

DimensionReasoningScore

Conciseness

Dense, rule-packed prose where every line earns its place: terse rules, inline mini-examples, and no explanation of concepts Claude already knows — lean and assumes competence.

5 / 5

Actionability

Concrete, executable rules ('In order to' is 'to'; 'Use', not 'utilize'; 'only fails on growth' vs 'fails only on growth') plus a before/after worked example annotated by layer give copy-applicable guidance covering common cases.

5 / 5

Workflow Clarity

Sequences the four layers and closes with an 8-item review checklist as a validation step ('Apply all four, then run the unslop skill'), but the workflow is a holistic framework rather than a rigid numbered procedure with explicit fix-retry feedback loops.

4 / 5

Progressive Disclosure

Well-organized into clear sections (intro, three rules, Layer 1-4, worked example, checklist, sources) with no content that clearly belongs in a separate file; good structure though above the 50-line simple-skill threshold, so not a clean 5.

4 / 5

Total

18

/

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 well-crafted description that clearly states a four-layer standard and provides concrete trigger terms for when to apply it. It is comprehensive on the what/when axis and largely distinct, with only minor gaps in synonym/extension coverage and framework-versus-action framing.

DimensionReasoningScore

Specificity

Names four concrete frameworks (Diataxis, Google developer style, Simplified Technical English, Global English) plus six artifact types, but the 'what' is framed as a standard rather than action verbs, leaving minor coverage gaps versus a fully action-verb description.

4 / 5

Completeness

Explicitly answers both 'what' (Four-layer standard for technical prose with four named layers) and 'when' (concrete trigger phrase listing docs, RFCs, READMEs, PR descriptions, commit messages), matching the top anchor.

5 / 5

Trigger Term Quality

'Use when writing or reviewing docs, RFCs, README files, PR descriptions, or commit messages' gives strong natural keyword coverage, but lacks synonyms (documentation, design docs, release notes) and file extensions.

4 / 5

Distinctiveness Conflict Risk

The named-standards niche for technical prose is mostly distinct with minimal conflict risk, though explicit reference to the sibling 'unslop' skill signals minor overlap with closely related writing skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.