CtrlK
BlogDocsLog inGet started
Tessl Logo

mcclowes/writing-style

Max's house writing style and grammar for any prose you generate for him - docs, READMEs, PR descriptions, commit messages, Slack, emails, code comments, error messages, blog posts, and replies in chat. Use this whenever you are writing or editing English prose meant for Max or sent on his behalf, even when he doesn't explicitly ask for a particular style. Apply it by default to anything wordier than a one-line answer; favour warm-but-blunt, concise writing, US English, sentence case, the Oxford comma, and zero AI jargon. Do not use it for code itself, config, or data formats.

72

Quality

90%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable writing style guide with excellent concrete examples and clear rules. Its main weakness is moderate verbosity — several sections over-explain rationale that Claude doesn't need (e.g., why contractions sound natural, extended discussion of mic-drop cadence). The content would benefit from trimming explanatory prose while keeping the rules, lists, and examples intact.

Suggestions

Trim explanatory rationale throughout — keep the rules and examples but cut sentences that explain *why* a rule matters when the reason is obvious to Claude (e.g., 'They're how people actually talk' after saying contractions are preferred).

Consider extracting the banned words/phrases list into a separate reference file to reduce the main skill's token footprint and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The skill is well-written and mostly efficient, but it's longer than it needs to be for Claude. Some sections explain concepts Claude already understands (e.g., why contractions sound natural, why padding is bad). The banned words list and examples are valuable, but the explanations around them could be tighter. The 'mic-drop cadence' section, while useful, spends considerable tokens elaborating a point that could be made in two sentences.

2 / 3

Actionability

Highly actionable with concrete before/after examples, explicit banned word lists, specific rules (Oxford comma, sentence case, US English), and calibration guidance by context type. Claude can directly apply every rule without ambiguity.

3 / 3

Workflow Clarity

For a writing style skill, there is no multi-step destructive workflow requiring validation checkpoints. The single task (apply this voice to prose) is unambiguous, with clear hard rules, a priority hierarchy (hard rules → banned words → padding → rhythm), and context-specific calibration. This is a simple skill with clear guidance.

3 / 3

Progressive Disclosure

The content is well-structured with clear headings and logical sections, but it's all in one file with no references to external resources. Given the length (~200+ lines), the banned words list or the examples section could reasonably be split into separate reference files. However, for a standalone skill with no bundle, the internal organization is solid.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly defines its purpose (personal writing style guide), provides comprehensive trigger terms across many content types, explicitly states when to apply and when not to apply, and is highly distinctive. The description is concise yet thorough, covering capabilities, triggers, style rules, and exclusions in a single well-structured paragraph.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and contexts: docs, READMEs, PR descriptions, commit messages, Slack, emails, code comments, error messages, blog posts, and chat replies. Also specifies concrete style rules like warm-but-blunt, concise, US English, sentence case, Oxford comma, and no AI jargon.

3 / 3

Completeness

Clearly answers both 'what' (writing style and grammar rules for prose) and 'when' ('Use this whenever you are writing or editing English prose meant for Max or sent on his behalf, even when he doesn't explicitly ask'). Also specifies when NOT to use it (code, config, data formats), which strengthens the 'when' guidance.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms a user or Claude would encounter: docs, READMEs, PR descriptions, commit messages, Slack, emails, code comments, error messages, blog posts, prose, writing, editing. These are all terms that naturally arise in user requests.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive as a personal writing style guide for a specific person (Max). The explicit scope (prose only, not code/config/data) and the specific style preferences (warm-but-blunt, Oxford comma, no AI jargon) make it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

10

/

11

Passed

Reviewed

Table of Contents