CtrlK
BlogDocsLog inGet started
Tessl Logo

chatto-checkup

Run a documentation-focused maintenance checkup of the Chatto codebase. Fans out to /fdr, /adr, and /chatto-architecture-inventory, then compiles a single consolidated report. Always propose-only; no changes are applied without explicit user approval. At the end, points the human at other maintenance skills (/update-project-dependencies, /chatto-security-review) they may want to run themselves.

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A concise, well-structured meta-skill body with a clear workflow, explicit propose-only checkpoint, and concrete report format. It is an instruction-only skill with actionable guidance rather than code, which fits its purpose well.

DimensionReasoningScore

Conciseness

Lean, well-organized body that assumes Claude's competence; no padding, no explanation of concepts Claude already knows, every section earns its place.

5 / 5

Actionability

Provides concrete, executable guidance (invoke three audits in parallel, compile a single report with three named sections, report format fields) with only minor gaps — it delegates audit specifics to the sub-skills rather than duplicating them.

4 / 5

Workflow Clarity

Clear numbered sequence (parallel audits -> compile consolidated report -> present sections -> recommended next step -> other-skills pointers -> wait for user) with an explicit validation/feedback checkpoint ('Wait for user direction before applying anything') and an Anti-Patterns guardrail.

5 / 5

Progressive Disclosure

Well-structured with clear section headers and appropriately split content; no bundle files exist, and the sub-skill fan-out acts as one-level-deep references, though those references are slash-commands rather than bundled files.

4 / 5

Total

18

/

20

Passed

Description

76%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.

A highly specific, well-scoped description with strong distinctiveness and concrete actions. Its main weakness is the absence of an explicit 'Use when...' trigger clause and reliance on skill-name invocations rather than natural user phrases.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases (e.g., 'Use when the user wants a routine Chatto docs health check or asks what FDRs/ADRs are stale').

Include natural-language synonyms users might say (e.g., 'docs drift', 'architecture review', 'stale decisions') alongside the slash-command names.

DimensionReasoningScore

Specificity

Names the domain (Chatto codebase docs checkup) and multiple concrete actions: fans out to /fdr, /adr, /chatto-architecture-inventory, compiles a consolidated report, propose-only, and points to other skills — comprehensive coverage.

5 / 5

Completeness

Clearly answers 'what' (run a docs checkup, fan out, compile report) and implies 'when' via 'maintenance checkup', but lacks an explicit 'Use when...' clause with concrete trigger phrases, capping completeness per the missing-trigger-clause rule.

4 / 5

Trigger Term Quality

Uses skill names (/fdr, /adr) as triggers but these are technical skill invocations rather than natural phrases a user would say; terms like 'maintenance checkup' and 'documentation' are present but common variations/synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

Clear niche (Chatto-specific docs maintenance) with distinct named skill triggers and explicit boundary (propose-only, not dependency/security work); minimal conflict risk.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
chattocorp/chatto
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.