CtrlK
BlogDocsLog inGet started
Tessl Logo

add-macos-statusbar

Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-macos-statusbar/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 concise and well-sequenced with strong validation checkpoints, but its actionability and progressive disclosure are undermined by references to source files (statusbar.swift, REMOVE.md) that are absent from the skill bundle.

Suggestions

Include the referenced Swift source in the bundle (e.g. under add/src/statusbar.swift) so the compile step is fully executable, or inline a minimal statusbar.swift snippet in the body.

Provide the referenced REMOVE.md uninstall guide or remove the dangling link to it.

Keep the lean phased structure; it is the strongest aspect of this skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — every line is a concrete command, plist, or instructional step with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

It provides concrete, copy-paste-ready shell commands and a full launchd plist, but the core compile step relies on a referenced source file ('${CLAUDE_SKILL_DIR}/add/src/statusbar.swift') that is not present in the skill bundle, so the primary action cannot be executed as written.

2 / 3

Workflow Clarity

The three-phase sequence (Pre-flight, Compile and Install, Verify) has explicit validation checkpoints — platform/swiftc/already-installed checks in Phase 1 and a PID check in Phase 3 — with clear feedback on what to do when checks fail.

3 / 3

Progressive Disclosure

The body is reasonably sectioned into phases, but it references bundle files that do not exist ('${CLAUDE_SKILL_DIR}/add/src/statusbar.swift' and [REMOVE.md](REMOVE.md)), so the navigation it signals points at missing material.

2 / 3

Total

10

/

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 specific, concrete, and distinctively scoped to a macOS-only NanoClaw status indicator, but it lacks an explicit 'Use when...' trigger clause, capping completeness and trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants a macOS menu bar indicator for NanoClaw's running status, or asks to start/stop/restart NanoClaw from the menu bar.'

Include natural user phrasings like 'statusbar', 'tray icon', or 'menu bar app' alongside 'menu bar status indicator' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

It lists multiple concrete actions — 'Add a macOS menu bar status indicator', 'Shows a bolt icon with a green/red dot indicating whether NanoClaw is running', 'Start, Stop, and Restart controls' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly answers 'what does this do' but the 'when to use it' guidance is only implied by the feature description with no explicit 'Use when...' trigger, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

It surfaces natural terms like 'menu bar status indicator', 'green/red dot', and 'running', but omits common variations a user might say ('statusbar', 'tray icon', 'menu bar app') and lacks an explicit 'Use when...' trigger clause.

2 / 3

Distinctiveness Conflict Risk

The macOS-only NanoClaw menu-bar niche with bolt-icon/Start-Stop-Restart semantics is highly specific and unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

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

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

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.