CtrlK
BlogDocsLog inGet started
Tessl Logo

govuk-style

Write and edit in GOV.UK / GDS house style: plain English, active voice, front-loaded content, sentence case, and no bold or italics for emphasis. Use when the user asks for GOV.UK or GDS style, or when writing reports, research write-ups, or guidance for external readers. Not for repo docs, UI strings, commit messages, or code comments; those follow writing-voice.

76

Quality

96%

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.

A lean, well-structured style reference that gives concrete, executable guidance and closes with a validation self-check. The only minor weakness is slight rhetorical repetition in the opener and closing scope note.

DimensionReasoningScore

Conciseness

The body is a dense, rule-based reference with little padding about concepts Claude already knows, but the rhetorical opener ('The goal is to open up, not to dumb down') and the repetition of scope and the bold/italic rule in the closing note are minor tokens that could be trimmed.

4 / 5

Actionability

Highly actionable for an instruction-only skill: concrete do/don't word substitutions ('use, not utilise or leverage'), explicit formatting rules, and worked examples like 'select Save' cover the common cases.

5 / 5

Workflow Clarity

The 'Before you finish: self-check' section provides an explicit validation checklist — a feedback loop confirming the single action (apply the style) was done correctly, satisfying the simple-skill exception.

5 / 5

Progressive Disclosure

No bundle files exist, but the body is well-organized into clearly headed sections (Content design principles, Plain English, Formatting, self-check, scope note) with no nested references, so the well-organized-sections exception applies.

5 / 5

Total

19

/

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.

A strong description that states concrete capabilities, gives natural trigger terms, answers both what and when, and explicitly disambiguates from a sibling skill. It uses an imperative/third-person voice with no first- or second-person drift.

DimensionReasoningScore

Specificity

The description lists multiple concrete style actions and attributes — 'plain English, active voice, front-loaded content, sentence case, and no bold or italics for emphasis' — giving comprehensive coverage of what the skill does rather than vague language.

5 / 5

Completeness

It explicitly answers both 'what' ('Write and edit in GOV.UK / GDS house style...') and 'when' ('Use when the user asks for GOV.UK or GDS style...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases a user would actually say are present — 'GOV.UK or GDS style', 'reports, research write-ups, or guidance for external readers' — with good synonym coverage.

5 / 5

Distinctiveness Conflict Risk

A clear niche is reinforced by an explicit exclusion clause — 'Not for repo docs, UI strings, commit messages, or code comments; those follow writing-voice' — which resolves overlap with a related skill.

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
EpicenterHQ/epicenter
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.