CtrlK
BlogDocsLog inGet started
Tessl Logo

reporting-progress

What to say while long work is still running, and what a legal mid-task stop looks like. Use during any run over a few minutes — migrations, sweeps, babysit loops, automations, deploys — and at the moment you are tempted to stop and ask, report a blocker, or answer "how's it going?".

69

Quality

87%

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

93%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 tight, highly actionable instruction skill with concrete templates, checkpoints, and a clear two-shape terminal model. The only minor gap is the vague recovery directive when a stall is detected.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with no explanation of concepts Claude already knows; the measured-data opener earns its place as motivation rather than padding.

5 / 5

Actionability

It provides a copy-paste BLOCKED line template, a concrete five-item exhaust list, and specific delta examples (rows copied, files swept, checks green) with a cadence, making the guidance fully executable.

5 / 5

Workflow Clarity

The Done/Blocked terminal shapes and the five-step exhaust sequence are clearly laid out, and the two-consecutive-notes rule is an explicit checkpoint, but the recovery action ("change the approach") is left slightly underspecified.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear sections, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

78%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 strong description that clearly states what the skill governs and when to apply it, with natural conversational triggers. It is slightly less specific in enumerating concrete actions and has minor overlap risk with broad comms guidance.

DimensionReasoningScore

Specificity

The description names the domain and conveys two actions ("what to say while long work is still running" and "what a legal mid-task stop looks like") but does not enumerate multiple concrete actions, so it sits at the named-domain-plus-1-2-actions level rather than a list of several specific actions.

3 / 5

Completeness

It explicitly answers both what (what to say while running and what a valid mid-task stop looks like) and when ("Use during any run over a few minutes ... at the moment you are tempted to stop and ask, report a blocker, or answer 'how's it going?'") with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes natural scenario triggers ("migrations, sweeps, babysit loops, automations, deploys") plus conversational phrases ("how's it going?", "report a blocker", "stop and ask"), giving good coverage with only a few synonyms missing.

4 / 5

Distinctiveness Conflict Risk

The trigger is a distinct behavioral niche tied to long-running work and blocker moments, with mostly distinct triggers and only minor overlap risk against general communication skills.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
BuilderIO/agent-native
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.