CtrlK
BlogDocsLog inGet started
Tessl Logo

humanizer

Tone enforcement patterns for external-facing community responses

48

Quality

52%

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

Fix and improve this skill with Tessl

tessl review fix ./.squad/skills/humanizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a well-structured, actionable tone guide with concrete templates and examples. Its main weakness is redundancy across the patterns, examples, and anti-patterns sections, and it could tighten token usage and split the example templates into a reference file.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the patterns, examples, and anti-patterns sections repeat overlapping ideas (e.g. link-dumping and passive voice each appear multiple times), so it is mostly efficient but could be tightened.

3 / 5

Actionability

Concrete, copy-paste-ready templates with placeholders ({author}, {explanation}) and specific phrase examples like 'Thanks for reporting this' and 'We're looking into this' provide mostly executable guidance with only minor gaps.

4 / 5

Workflow Clarity

As a simple single-purpose tone skill the action is unambiguous and well-sequenced through patterns then examples; it is not a destructive/batch operation so the validation cap does not apply, though there are no explicit checkpoints, keeping it just below 5.

4 / 5

Progressive Disclosure

The body is well-organized into Context, Patterns, Examples, and Anti-Patterns sections with no bundle files to reference; at ~90 lines it slightly exceeds the under-50-line simple-skill threshold and could offload the example templates to a separate file, so it is mostly well-placed.

4 / 5

Total

15

/

20

Passed

Description

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

The description identifies a domain but lacks concrete actions, natural trigger terms, and an explicit 'Use when' clause. It is distinguishable but only modestly specific, with completeness capped by the missing trigger guidance.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural phrases users say (e.g. 'Use when drafting replies to community issues, discussions, or support threads in a warm, human tone').

Replace the generic 'Tone enforcement patterns' with concrete actions (e.g. 'Draft warm, human-sounding replies to community issues and discussions').

Include natural trigger terms like 'community replies', 'issue comments', or 'support responses' instead of abstract phrasing.

DimensionReasoningScore

Specificity

The phrase 'Tone enforcement patterns' names the domain but the action ('enforcement patterns') is generic and does not list concrete capabilities; closer to the score-2 anchor than score-3 since it does not enumerate 1-2 specific actions.

2 / 5

Completeness

A 'what' is weakly present (tone enforcement for external responses) but there is no explicit 'Use when...' trigger clause, which per the judging guidelines caps completeness at 3; the 'when' is only weakly implied by 'for external-facing community responses'.

3 / 5

Trigger Term Quality

'Tone enforcement patterns' and 'external-facing community responses' are unlikely phrases a user would naturally say when they need this skill, and no common trigger synonyms are present; matches the 'one or two generic keywords; missing natural phrases' anchor.

2 / 5

Distinctiveness Conflict Risk

The niche (external-facing community tone) is somewhat specific but 'tone enforcement' could overlap with other communication/brand skills, so it sits at the 'somewhat specific but could still overlap' anchor.

3 / 5

Total

10

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
bradygaster/squad
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.