CtrlK
BlogDocsLog inGet started
Tessl Logo

tone-shifter

Rewrite any text in a different tone — formal, casual, friendly, bold, or concise.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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 model of a lean, well-structured simple skill: it gives concrete tool instructions, illustrative examples, and clear organization without any wasted tokens.

DimensionReasoningScore

Conciseness

The body is lean and efficient — a one-line intro, concise illustrative examples, and exact tool parameters with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

It names the exact tool (`run_js`) and specifies the precise data schema (field names, types, and constraints such as truncating to 120 characters), giving concrete executable guidance.

3 / 3

Workflow Clarity

This is a simple single-task skill under 50 lines with an unambiguous action (call run_js with the data payload); per the simple-skills note, workflow clarity scores 3 and no validation checkpoint is required.

3 / 3

Progressive Disclosure

The content is well-organized into clear sections (intro, Examples, Instructions) and, as a simple under-50-line skill with no need for external documentation references, qualifies for a 3 per the scoring notes.

3 / 3

Total

12

/

12

Passed

Description

65%Weight 40%Scale 1-3

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 clearly states what the skill does and uses natural tone-related trigger terms, but it lacks an explicit "Use when…" clause, leaving the triggering context implied rather than stated.

Suggestions

Add a "Use when…" clause, e.g. "Use when the user asks to rewrite or rephrase text in a specific tone (formal, casual, friendly, bold, or concise)."

Broaden the stated actions beyond a single "rewrite" verb to reduce overlap with general editing skills and clarify the niche.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ("Rewrite any text in a different tone") with tone variants, but it is a single action rather than multiple distinct concrete actions like the anchor-3 examples.

2 / 3

Completeness

The "what" is clear (rewrite text in a different tone), but there is no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Natural terms users would actually say are well covered — "rewrite", "tone", and the concrete tone names (formal, casual, friendly, bold, concise) match phrasings like "make this more formal".

3 / 3

Distinctiveness Conflict Risk

Tone rewriting is a reasonably distinct niche, but without explicit trigger guidance it could still overlap with general writing or editing skills, matching the anchor-2 level.

2 / 3

Total

9

/

12

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
mergisi/awesome-openclaw-agents
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.