CtrlK
BlogDocsLog inGet started
Tessl Logo

structured-progress-update

Use this skill when summarizing progress on an ongoing project or multi-step task. Give a clear, scannable status report whenever asked for an update or at the end of a work session.

68

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%Weight 40%Scale 1-3

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-organized instruction set that gives Claude an exact structure to follow plus a concrete good/bad example, with no unnecessary explanation. As a simple skill under 50 lines it cleanly meets the top anchors for workflow clarity and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and efficient — a format template, a few principles, and one concrete example — assuming Claude's competence without explaining what progress reporting is, matching the score-3 anchor where every token earns its place.

3 / 3

Actionability

Provides a concrete, copy-paste-ready structure (Done / In progress / Blocked / Next) plus a specific contrastive example ("Completed API integration for /users endpoint" vs "worked on API"), matching the score-3 anchor of specific executable guidance.

3 / 3

Workflow Clarity

For a simple single-task skill the single action (produce a structured report) is unambiguous and clearly laid out; per the rubric's simple-skills note, workflow clarity can score 3 when the single action is clear, and no destructive or batch operation requires validation checkpoints here.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, the body is well-organized into a Format section and a Principles section; per the rubric's simple-skills note, progressive disclosure can score 3 with just well-organized sections and no bundle files are present or needed.

3 / 3

Total

12

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 cleanly answers both what the skill does and when to use it with explicit trigger language, which is its main strength. It is slightly held back by only naming a general action (status report) rather than several concrete capabilities, and by trigger-term coverage that misses common phrasings.

Suggestions

Enumerate concrete actions the skill performs (e.g., list completed items, surface blockers, identify next steps) to raise specificity toward the score-3 anchor.

Broaden trigger terms with natural user phrasings such as "status", "check-in", or "where are we" to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

Names the domain and the core action ("summarizing progress", "Give a clear, scannable status report") but does not enumerate multiple distinct concrete actions, matching the score-2 anchor rather than the multi-action score-3 example.

2 / 3

Completeness

Explicitly states both what it does ("summarizing progress... scannable status report") and when to use it ("Use this skill when...", "whenever asked for an update or at the end of a work session"), matching the score-3 anchor that answers what AND when with explicit triggers.

3 / 3

Trigger Term Quality

Includes relevant natural phrases ("asked for an update", "at the end of a work session", "progress") but misses common variations like "status", "check-in", or "where are we", fitting the score-2 anchor of some-but-not-full keyword coverage.

2 / 3

Distinctiveness Conflict Risk

The progress-reporting niche is reasonably specific but could overlap with general summarization or planning skills, matching the score-2 anchor rather than a clearly non-conflicting score-3 niche.

2 / 3

Total

9

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
aiming-lab/MetaClaw
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.