CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

concise-writing

Make supplied prose clearer and shorter while preserving its meaning.

Quality

77%

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 ./src/row_bot/plugins/bundled/local-text-tools/skills/concise-writing/SKILL.md
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.

The body is an exemplar of lean, directive instruction writing: every sentence tells Claude exactly what to do, what to preserve, and what to avoid, with no filler. The only meaningful gap is the absence of a worked before/after example that would make the expected edit style and edit-explanation format fully concrete.

DimensionReasoningScore

Conciseness

The body is four sentences of pure directive ("Keep facts, uncertainty, names and numbers intact", "Prefer familiar words and active verbs", "Remove repeated ideas") with zero padding and no explanation of concepts Claude already knows, matching anchor 5. The closing note "This skill needs no service account or additional tools" is a mild trim candidate but functions as a constraint, so it does not pull the content down to anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

For an instruction-only skill the guidance is concrete and specific (what to preserve: "facts, uncertainty, names and numbers"; what to change: "familiar words and active verbs", "repeated ideas"; constraint: "Do not introduce new claims"), matching anchor 4's mostly-executable guidance with minor gaps. Not 5 because there is no worked before/after example showing what a tightened edit and its "explain any material edit" accounting should look like.

4 / 5

Workflow Clarity

This is a simple single-task skill and the single action is unambiguous: read the supplied text, apply the stated style rules, preserve the listed elements, and explain material edits. Per the simple-skill exception the single action can score 5; the task is also non-destructive and non-batch, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ directories exist, and no bundle paths are cited), and the single short instruction block is appropriately self-contained and trivially navigable. Per the under-50-lines exception, this warrants a 5; nothing is inlined that belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

50%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 communicates a clear, single-purpose 'what' in appropriately concise third-person form, but every dimension lands at the middle anchor: it lacks any explicit 'when to use' trigger guidance, natural trigger synonyms, and a broader enumeration of concrete actions. It is serviceable but would be substantially improved by a trigger clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user supplies text and asks to make it shorter, clearer, more concise, tighter, or to condense/trim/rewrite it."

Include natural synonyms and phrasings users would actually say ("concise", "condense", "tighten", "trim", "rewrite", "cut this down") to improve trigger term coverage.

Enumerate the concrete actions more fully (e.g. "shortens text, simplifies wording, removes repetition, preserves facts, names, numbers, and uncertainty") to raise specificity.

DimensionReasoningScore

Specificity

"Make supplied prose clearer and shorter while preserving its meaning" names the domain (prose editing) and 1-2 concrete actions (clarify, shorten) but is not comprehensive, matching anchor 3. It is not 4 because it does not list several distinct specific actions, and not 2 because it goes beyond a bare domain label.

3 / 5

Completeness

The 'what' is clear (make prose clearer and shorter while preserving meaning), but there is no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Terms like "prose", "clearer", and "shorter" are relevant natural keywords, but common variations users would say — "concise", "condense", "tighten", "trim", "rewrite", "edit" — are missing, matching anchor 3. Not 4 since keyword coverage is thin rather than good-with-a-few-gaps.

3 / 5

Distinctiveness Conflict Risk

"Make supplied prose clearer and shorter" carves out a somewhat specific niche (condensing user-supplied text), but it could still overlap with general writing, editing, grammar, and summarization skills, matching anchor 3. Not 4 because the overlap risk with closely related text skills is more than minor.

3 / 5

Total

12

/

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

siddsachar/row-bot

Path

src/row_bot/plugins/bundled/local-text-tools/skills/concise-writing/SKILL.md

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.