CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

text-review

Review supplied prose using a packaged checklist and optional local text statistics.

Quality

74%

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/text-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, well-structured overview that correctly pushes the review detail into a real one-level-deep reference and states concrete deliverables. Its only weakness is the vague handling of the text-stats MCP tool — "after its setup is ready" names a prerequisite without explaining what setup entails, which costs it the top actionability and workflow-clarity scores.

Suggestions

Replace "after its setup is ready" with the concrete precondition or invocation for the text-stats MCP tool (e.g., the exact tool name and a sample call), or drop the qualifier.

State how to surface the checklist results (e.g., format edits as a numbered list quoting the original phrase followed by the suggested edit) so the reporting step is fully executable.

DimensionReasoningScore

Conciseness

The four-sentence body contains no concept explanations and no padding: "Read references/checklist.md beside this skill before reviewing the user's text. Report concrete edits and unresolved questions..." Every sentence directs behavior. This matches anchor 5 ('Lean and efficient; assumes Claude's competence; every token earns its place') — even the final boundary note ("it reads no files and contacts no service") conveys scope, not filler, so it does not drop to 4.

5 / 5

Actionability

Mostly executable guidance: a concrete file to read (references/checklist.md, which exists in the bundle), a concrete deliverable ("Report concrete edits and unresolved questions"), and a named tool (text-stats MCP) with its trigger condition (word/line/character counts). It falls short of anchor 5 because "after its setup is ready" gives no concrete setup or invocation detail — a minor gap, placing it at anchor 4 ('Mostly executable guidance; concrete code or commands with minor gaps') rather than 3, where key details would be broadly missing.

4 / 5

Workflow Clarity

The sequence is explicit and correctly ordered — read the checklist "before reviewing", review the text, report edits and unresolved questions, and use the stats tool only on request. This is a simple, non-destructive single-task skill, so no validation checkpoint is required, but the unexplained "after its setup is ready" leaves one ambiguous step, holding it at anchor 4 rather than the simple-skill 5.

4 / 5

Progressive Disclosure

The body is a genuinely progressive overview: the review detail lives in the real, existing references/checklist.md (verified in the bundle), referenced one level deep by explicit path, with the body retaining only orchestration. This matches anchor 5 ('Clear overview with well-signaled one-level-deep references; content appropriately split') — the reference is signaled by full path, is not buried, and no content that belongs in a separate file is inlined, so it is above anchor 4.

5 / 5

Total

18

/

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 is concise and states a clear 'what', but it omits any explicit 'when to use this skill' guidance and lacks the natural trigger phrases (proofread, edit, word count) users would actually say. It sits at the midpoint across all dimensions: serviceable but not discoverable.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user supplies prose to review, proofread, or edit, or asks for word/line/character counts."

Include natural synonyms users would say — "proofread", "edit my writing", "word count" — alongside "review" and "prose".

Name 1-2 concrete review outcomes (e.g., "flags unsupported claims and ambiguity") so the capability is more specific than 'review prose with a checklist'.

DimensionReasoningScore

Specificity

"Review supplied prose using a packaged checklist and optional local text statistics" names the domain (prose review) with 1-2 concrete actions (checklist-based review, text statistics), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is above score 2 because the actions go beyond a bare generic verb, and below score 4 because it never lists what the review actually checks (e.g., clarity, factual accuracy) or which statistics are produced.

3 / 5

Completeness

The 'what' is clear (review supplied prose via checklist plus optional statistics), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'when' is only weakly implied by 'supplied prose'. Per the judging guidelines a missing 'Use when...' clause caps completeness at 3, which is exactly the anchor 'Has a clear what but when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

Relevant keywords exist — "review", "prose", "checklist", "text statistics" — but common variations users naturally say ("proofread", "edit my writing", "word count", "check my essay") are missing. This fits anchor 3 ('Some relevant keywords but missing common variations or synonyms') rather than 4, since more than just a few natural terms are absent.

3 / 5

Distinctiveness Conflict Risk

"Review supplied prose" carves out a niche distinct from code-review skills, but the generic verb "review" plus reliance on checklist/stats means it could still overlap with general writing, editing, or summarization skills. This matches anchor 3 ('Somewhat specific but could still overlap with similar skills') rather than 4, which would require more distinct trigger phrasing.

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/text-review/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.