CtrlK
BlogDocsLog inGet started
Tessl Logo

sweep

Audit the current Fallow session for missed work, incomplete verification, stale documentation, companion drift, or cleanup before final completion.

62

Quality

72%

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 ./.agents/skills/sweep/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 content is an exemplary lean, well-structured audit checklist that assumes Claude's competence and includes verification checkpoints. Its only soft spot is a lack of explicit error-recovery feedback loops and a couple of slightly abstract directives.

DimensionReasoningScore

Conciseness

The body is a lean ~18-line checklist with zero padding and no explanations of concepts Claude already knows; every line is actionable instruction and the closing line reinforces intent, so every token earns its place.

5 / 5

Actionability

Steps give concrete, specific guidance (exact categories to check: 'missed consumers, output formats, filters, docs, skills, schemas, CI scripts, companion repositories, and private/public boundaries'), but a few directives like 'authoritative evidence' and 'weak or stale verification' are slightly abstract with no example, leaving minor gaps.

4 / 5

Workflow Clarity

A clear six-step sequence with validation checkpoints present (step 4 re-run verification, step 6 verify clean, closing 'Prove every requested outcome'), but no explicit validate->fix->retry feedback loop is spelled out for what to do if verification still fails.

4 / 5

Progressive Disclosure

This is a sub-50-line single-purpose skill with no need for external references and no bundle files; the body is well-organized into a header, numbered checklist, and closing emphasis, which satisfies the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

58%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 specific and tied to a clear niche (Fallow session audits), but it lacks an explicit 'Use when...' trigger clause and leans on some domain jargon, capping completeness and trigger-term quality. Adding a concrete trigger phrase would lift the weaker dimensions.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when finishing a Fallow session to confirm nothing was missed before marking work complete.'

Soften or gloss domain jargon like 'companion drift' with a more natural synonym so users are more likely to trigger the skill by saying it.

Add a few natural trigger variations or synonyms ('final review', 'pre-completion check') to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description lists several concrete audit categories ('missed work, incomplete verification, stale documentation, companion drift, or cleanup') rather than vague language, though they are category labels rather than fully fleshed-out actions, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clear ('Audit the current Fallow session for...'), but the 'when' is only weakly implied by 'before final completion' and there is no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

It includes some relevant domain terms ('Fallow session', 'missed work', 'cleanup', 'final completion') but leans on jargon ('companion drift') and lacks common synonyms or a natural 'Use when...' phrasing a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

Scoping to 'the current Fallow session' gives it a distinct niche with low overlap risk against unrelated skills; it is not a 5 only because the surrounding audit vocabulary is broadly reusable across review-style skills.

4 / 5

Total

14

/

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
fallow-rs/fallow
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.