CtrlK
BlogDocsLog inGet started
Tessl Logo

status

Show current goal-plan status at a glance - phases, progress, checklist, verification, and risks.

64

Quality

78%

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/status/SKILL.md
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 tightly organized, actionable single-purpose skill: a concise task list, status-icon map, exact output template, and fallback, with no padding and clear navigation via section headers.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: a brief 'What to Show' list, an icon map, and a compact output template, with no padded explanation of concepts Claude already knows.

3 / 3

Actionability

It gives concrete, copy-ready guidance — an exact output-format template, a status-icon mapping, and a fallback command — that tells Claude precisely what to produce.

3 / 3

Workflow Clarity

As a simple single-purpose skill the single action (read the plan, render the summary) is unambiguous, with an explicit disambiguation step and a fallback path; per the simple-skills note this can score 3.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, the body is well organized into clearly headed sections; per the guidelines this satisfies progressive disclosure at the top level.

3 / 3

Total

12

/

12

Passed

Description

57%

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 occupies a clear niche, but it omits an explicit 'Use when...' trigger clause and natural keyword variations, leaving completeness and trigger-term coverage at the mid level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants a quick status check on the current goal plan or asks where they are.'

Broaden natural trigger terms to include everyday phrasings like 'status', 'progress', or 'where am I'.

DimensionReasoningScore

Specificity

It names the domain (goal-plan status) and lists several concrete elements ("phases, progress, checklist, verification, and risks") but states no distinct actions beyond 'Show', so it is not comprehensive of multiple specific actions.

2 / 3

Completeness

It answers 'what' (show goal-plan status with the listed elements) but provides no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

"status at a glance" and "goal-plan status" are reasonably natural, but it lacks the common variations a user would say (e.g. 'status', 'progress check', 'where am I'), so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and specific to goal-plan status review, with distinct framing unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

12

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
udecode/plate
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.