CtrlK
BlogDocsLog inGet started
Tessl Logo

writing

General prose doctrine for anything a human will read — clear, concrete, free of ready-made phrases. Use when writing or editing documentation, explanations, summaries, commit messages, reports, or any other prose.

68

Quality

81%

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

82%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, actionable doctrine skill that models the prose discipline it teaches, with concrete swaps, a tells table, and a deliver checklist. Minor gaps are the ornate opening, an implied rather than explicit workflow order, and one unlinked reference file.

Suggestions

Trim the Orwell introduction to a sentence or two so the opening earns every token like the rest of the body.

Make the section-to-section workflow order explicit (e.g., a one-line 'How to use this skill' sequencing method -> rules -> tells -> deliver) so the pipeline is unambiguous.

Link references/politics-and-the-english-language.md from the body (e.g., in the opening or a references section) so all bundle files are navigable one level deep.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence (no basic-concept padding), but the Orwell framing in the opening paragraphs is somewhat ornate and could be trimmed.

4 / 5

Actionability

Highly actionable doctrine with concrete before/after swaps ('did not remember' -> 'forgot'), a specific tells table, and a deliver-time checklist covering common cases.

5 / 5

Workflow Clarity

A clear method->rules->reader->tone->tells->deliver sequence with an explicit validation checklist exists, but the inter-section ordering is partly implied rather than a single explicit pipeline.

4 / 5

Progressive Disclosure

Well-organized sections with references/tropes.md clearly signaled one level deep and worst-offenders summarized inline, but only one of the three reference files is linked from the body.

4 / 5

Total

17

/

20

Passed

Description

80%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 explicitly pairs a clear 'what' with a concrete 'Use when...' trigger clause covering natural terms. Its main weakness is broad scope that raises conflict risk with other writing-oriented skills.

Suggestions

Tighten the trigger scope from 'any other prose' to a bounded list of concrete text types to reduce overlap with general-purpose writing skills and lift distinctiveness.

Consider naming the distinguishing angle (e.g., 'removing machine-generated ready-made phrases') earlier in the 'what' clause to sharpen the niche beyond 'General prose doctrine'.

DimensionReasoningScore

Specificity

Lists several concrete application contexts ('documentation, explanations, summaries, commit messages, reports') with only minor coverage gaps, though the core 'what' is abstract doctrine rather than discrete operations.

4 / 5

Completeness

Explicitly answers both 'what' ('General prose doctrine... clear, concrete, free of ready-made phrases') and 'when' with concrete trigger phrases in the 'Use when...' clause.

5 / 5

Trigger Term Quality

Natural user-facing terms ('writing or editing', 'commit messages', 'summaries', 'reports') with good coverage; a few synonyms and variations are missing, short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The anti-prefabricated-phrase doctrine is a distinct niche, but 'anything a human will read' and 'any other prose' make the trigger surface broad with real overlap risk against general writing skills.

3 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
joshuadavidthomas/agent-skills
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.