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.

69

Quality

83%

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.

The body is a tight, well-structured orchestration skill: it names exactly what to run, how to compile the report, and where to stop for user approval, with no padding and clear validation checkpoints.

DimensionReasoningScore

Conciseness

The body is lean and instruction-dense — it never explains what FDRs, ADRs, or architecture inventories are, and every section earns its tokens — matching the 'every token earns its place' anchor above the mostly-efficient level.

3 / 3

Actionability

It gives concrete executable guidance: the exact three skills to run in parallel, the report structure (What/Where/Suggested action), and the explicit 'Wait for user direction' step; as an instruction-only orchestration skill its guidance is specific and copy-ready rather than vague.

3 / 3

Workflow Clarity

The numbered 1–6 sequence is explicit with an explicit checkpoint (step 6: wait for user direction before applying anything) reinforced by the Anti-Patterns, satisfying the clear-sequence-with-validation anchor rather than the implicit-checkpoint level.

3 / 3

Progressive Disclosure

Under 50 lines with no external references and well-organized sections (What It Runs, How To Run, Report Format, Anti-Patterns), which per the rubric's simple-skills note earns a 3 without separate bundle files.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and distinctive, naming concrete sub-skills and the propose-only constraint, but it omits any explicit 'when to use' trigger guidance, which caps its completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a documentation checkup, drift audit, or maintenance review of the Chatto codebase.'

Include natural conversational trigger terms a user would actually say (e.g. 'docs checkup', 'documentation drift', 'FDR/ADR review') alongside the capability description.

Keep the propose-only framing but pair it with a one-line 'Use when...' so the what and when are both explicit.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Fans out to /fdr, /adr, and /chatto-architecture-inventory', 'compiles a single consolidated report', and 'points the human at other maintenance skills' — matching the multiple-specific-actions anchor rather than the domain-and-some-actions level below.

3 / 3

Completeness

It clearly answers 'what' (audit, fan out, compile, propose-only, point at other skills) but never states when to invoke it; per the rubric guidelines a missing 'Use when...' clause caps completeness at 2.

2 / 3

Trigger Term Quality

Contains real keywords a user might say ('maintenance checkup', 'documentation-focused', 'Chatto codebase') but lacks common conversational trigger variations and any 'Use when...' phrasing, so it sits at the some-relevant-keywords level rather than broad natural-term coverage.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche — a Chatto-specific documentation maintenance checkup that deliberately excludes heavier skills like dependency upgrades — so it is unlikely to trigger for the wrong skill, matching the clear-niche anchor.

3 / 3

Total

10

/

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