CtrlK
BlogDocsLog inGet started
Tessl Logo

tone-adapter

Transform content tone to match any audience — professional, casual, witty, or formal.

60

Quality

70%

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 ./apps/desktop/electron/default-skills/tone-adapter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 body is a well-structured, lean instruction-only skill with actionable calibration guidance, a clear sequenced workflow including a validation checkpoint, and clean sectioning appropriate for its size. Its main gap is the absence of a concrete before/after example and an explicit batch verification step.

Suggestions

Add one short before/after rewrite example to make the tone shift concrete and copy-paste illustrative.

Add an explicit verification step for batch jobs (e.g. 'after the batch, spot-check each piece against its source for lost facts').

Trim minor asides like 'use wit sparingly; it ages badly and can undercut credibility' to keep every token load-bearing.

DimensionReasoningScore

Conciseness

The body is efficient and avoids explaining concepts Claude already knows; guidance like the tone axes and preserve-meaning list each earn their tokens, with only minor trimmable asides (e.g. 'it ages badly and can undercut credibility').

4 / 5

Actionability

It gives concrete calibration axes with specific sub-features (contractions, sentence length, hedging vs. directness), a 3-step procedure, and a defined output format; it falls short of 5 only because no before/after rewrite example is shown.

4 / 5

Workflow Clarity

The 'How to work' section sequences three clear steps including an explicit validation checkpoint ('Re-read against the original to confirm no fact or commitment changed'); the batch-jobs note lacks an explicit per-item verification, keeping it just below 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed and is organized into well-signaled sections (When to use, Preserve meaning, tone palette, How to work, Output format), matching the simple-skill exception for a 5.

5 / 5

Total

17

/

20

Passed

Description

61%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 is clear and reasonably specific about what the skill does, with natural trigger terms, but it omits any explicit 'when to use' guidance and lists only one core action. Adding a 'Use when...' clause with concrete trigger phrases would raise both completeness and distinctiveness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to change the tone, voice, or register of existing text — e.g. make a memo more casual, formalize a draft, or add wit.'

Broaden trigger term coverage with synonyms users actually say: 'rewrite', 'rephrase', 'change the voice', 'soften', 'punch up'.

Add one more concrete action (e.g. 'rewrite for a new channel') to push specificity beyond a single named action.

DimensionReasoningScore

Specificity

The description names the domain ('Transform content tone') and one concrete action with enumerated audience variants ('professional, casual, witty, or formal'), but stops at a single action rather than a comprehensive set, matching the '1-2 concrete actions' anchor.

3 / 5

Completeness

It clearly answers 'what' (transform tone to match an audience) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural user-facing terms like 'tone', 'audience', 'professional', 'casual', 'witty', and 'formal' are present and would naturally be said, though common paraphrases like 'rewrite', 'rephrase', or 'change the voice' are missing.

4 / 5

Distinctiveness Conflict Risk

Tone/voice adaptation is a fairly distinct niche with concrete tonal anchors that separate it from generic writing skills, with only minor overlap risk against content-writing or editing skills.

4 / 5

Total

14

/

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
holaboss-ai/holaOS
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.