CtrlK
BlogDocsLog inGet started
Tessl Logo

add-dashboard

Add a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

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 content is highly actionable and well-structured, with executable commands, explicit validation checkpoints, and lean rationale that earns its tokens. Progressive disclosure is handled cleanly through a single organized document with clearly signaled bundled resources.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; prose passages (build-before-tests rationale, colocation design) justify non-obvious ordering and design choices rather than padding with concepts Claude already knows.

3 / 3

Actionability

Every step gives executable, copy-paste-ready guidance: pnpm install, exact resource→src copy paths, a precise code block to insert, a secret-generation command, and build/test/restart/verify/removal commands.

3 / 3

Workflow Clarity

A clearly numbered 1–6 sequence with explicit validation checkpoints (build guards the dependency via TS2307, wiring+behavior tests assert the edit, step 6 smoke-checks the live endpoint) and a feedback loop for error recovery.

3 / 3

Progressive Disclosure

A single well-organized doc with clearly signaled one-level-deep resource paths (the three .ts files with exact source→dest mappings) and no nested reference chains; sections (Architecture, Steps, Pages, Troubleshooting, Removal) aid navigation.

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 is concrete and tightly scoped to NanoClaw, with specific actions and low conflict risk. Its main weakness is the absence of explicit 'when to use' trigger guidance, which caps completeness.

Suggestions

Add a 'Use when …' clause stating the natural trigger (e.g. 'Use when the user wants monitoring, a dashboard, or live status for a NanoClaw deployment').

Broaden trigger-term coverage with everyday phrasings like 'monitoring', 'live status', or 'observability' alongside 'dashboard'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots' — naming the exact package and the pusher's behavior rather than vague abstraction.

3 / 3

Completeness

Clearly states what the skill does, but provides no explicit 'Use when…' trigger guidance, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

'monitoring dashboard' is a natural term a user might say, but coverage is thin and dominated by technical jargon ('@nanoco/nanoclaw-dashboard', 'pusher') with no common variations.

2 / 3

Distinctiveness Conflict Risk

Scoped tightly to NanoClaw ('Add a monitoring dashboard to NanoClaw'), giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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
nanocoai/nanoclaw
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.