CtrlK
BlogDocsLog inGet started
Tessl Logo

status

Quick read-only health check — session context, workspace mounts, tool availability, and task snapshot. Use when the user asks for system status or runs /status.

69

Quality

84%

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

81%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 well-structured, mostly executable read-only status skill with an explicit gating check and clean report format. Slight gains possible by tightening prose and making the MCP task-snapshot call fully concrete.

Suggestions

Replace the prose line 'Adapt based on what you actually find. Keep it concise...' with a one-line directive or remove it to tighten conciseness.

Make the task-snapshot step concrete with an actual invocation example for mcp__nanoclaw__list_tasks rather than a descriptive sentence.

Consider moving the full report-format template into a referenced file or condensing it so the overview stays lighter.

DimensionReasoningScore

Conciseness

Largely lean with directly useful bash snippets; minor padding such as 'Adapt based on what you actually find. Keep it concise...' could be trimmed. Fits anchor 4 rather than 5.

4 / 5

Actionability

Mostly executable copy-paste bash commands across the gather steps; the task-snapshot section ('Call mcp__nanoclaw__list_tasks to get scheduled tasks') is less concrete, keeping it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

Clear sequence (gate → numbered gather sections → report template) with an explicit validation gate ('If NOT_MAIN... stop — do not generate the report'); as a read-only simple skill the simple-skill exception supports anchor 5.

5 / 5

Progressive Disclosure

Self-contained with well-organized sections and one 'See also' link; no bundle files to reference, but the full inline report template is content that could warrant separation, fitting anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

87%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 both capability and trigger, tied to a distinct command. Minor room to broaden trigger synonyms and frame check areas as concrete actions.

DimensionReasoningScore

Specificity

Names the domain ('read-only health check') and lists several concrete check areas — 'session context, workspace mounts, tool availability, and task snapshot' — matching anchor 4; not 5 because these are check categories rather than a comprehensive list of actions.

4 / 5

Completeness

Explicitly answers both 'what' ('Quick read-only health check — session context, workspace mounts, tool availability, and task snapshot') and 'when' ('Use when the user asks for system status or runs /status') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user-facing terms 'system status' and '/status' with an explicit 'Use when...' clause; not 5 because it lacks synonyms/variations beyond those two phrases.

4 / 5

Distinctiveness Conflict Risk

Clear niche tied to the '/status' command and 'system status' trigger, with minimal overlap risk against other skills.

5 / 5

Total

18

/

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
jbaruch/nanoclaw-telegram
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.