CtrlK
BlogDocsLog inGet started
Tessl Logo

review-docs

Review and fix ChatJS Blume documentation and MDX files. Use when checking docs for correctness, broken links, stale examples, unclear prose, or consistency with the implementation.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured review workflow that tells Claude exactly what to verify, what to fix autonomously, and what to escalate. It respects the context budget and is appropriately scoped for a simple instruction-only skill with no bundle files.

DimensionReasoningScore

Conciseness

Lean instruction-only body with no concept explanation or filler; every line (verify, fix-when-clear list, report-only-decisions) earns its place and assumes Claude's competence.

3 / 3

Actionability

Concrete, specific guidance on what to verify ("code examples, paths, terminology, and behavior against the repository"), which fixes to apply directly, and what to escalate; absence of code is not penalized for an actionable instruction-only skill per the scoring notes.

3 / 3

Workflow Clarity

Clear three-phase sequence (verify against repo -> fix directly when the change is clear -> report only decisions) with an explicit escalation gate; for a simple single-purpose skill this is unambiguous, satisfying the simple-skills note.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, and well-organized into an intro, a fix-when-clear list, and reporting instructions; the simple-skills note allows a 3 with well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-scoped description that states concrete capabilities and an explicit 'Use when' trigger with natural terms. Third-person voice is maintained and it is clearly distinguishable from generic skills.

DimensionReasoningScore

Specificity

Names a concrete domain ("ChatJS Blume documentation and MDX files") and multiple specific actions/issues it addresses ("correctness, broken links, stale examples, unclear prose, or consistency with the implementation"), matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ("Review and fix ChatJS Blume documentation and MDX files") and when ("Use when checking docs for correctness, broken links..."), satisfying the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered ("docs", "broken links", "stale examples", "MDX files", "consistency"), which a user would plausibly say when requesting this skill.

3 / 3

Distinctiveness Conflict Risk

Scoped to a named product ("ChatJS Blume") with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
FranciscoMoretti/chat-js
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.