CtrlK
BlogDocsLog inGet started
Tessl Logo

clawsweeper-status

ClawSweeper status: URLs, workflow health, active workers, ops snapshot.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

96%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.

The content is an exemplar of lean, actionable, well-structured operational guidance: executable commands, a precise output contract, and clean sectioning with implementation pushed into a bundled script. The only notable gap is the absolute, machine-specific path used to invoke the bundled script.

Suggestions

Reference the bundled script via a relative path (e.g. scripts/clawsweeper-status.sh) instead of the hardcoded /Users/steipete/... absolute path so the skill is portable.

Briefly note the presence of the test script and fixture as supporting bundle files so reviewers/users can discover them.

Consider adding a one-line note on what to do if the script exits non-zero (e.g. missing gh auth), since it is the single entry point.

DimensionReasoningScore

Conciseness

The body is lean and operational with no concept-explaining padding, assumes Claude's competence, and nearly every token (script flags, section contract, interpretation rules) earns its place.

5 / 5

Actionability

It provides copy-paste-ready executable invocations with real flags (--hours, --repo, --limit) plus a concrete output contract with exact section names and prescribed phrasing, covering the common cases.

5 / 5

Workflow Clarity

This is a single-action read-only skill (run the script, then report sections) with an unambiguous sequence and explicit reporting rules; no destructive/batch operation is involved, so the simple-skill exception applies and no validation loop is required.

5 / 5

Progressive Disclosure

The SKILL.md is a concise overview that delegates implementation to the bundled script (one level deep) with well-organized sections, but it references the script via a machine-specific absolute path rather than a relative bundle path, a minor navigation/portability gap.

4 / 5

Total

19

/

20

Passed

Description

70%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.

The description is concise and clearly names a distinctive niche with concrete facets, but it lacks any explicit "Use when..." trigger guidance, which caps its completeness. Adding a short usage-trigger clause would lift the description toward the top anchors.

Suggestions

Append an explicit trigger clause, e.g. "Use when checking ClawSweeper operational health, worker capacity, or the review/publication queue."

Add a couple of natural synonyms a user might say (e.g. "queue health", "Codex jobs") to broaden trigger-term coverage.

Reframe the facet list slightly toward actions ("reports", "surfaces") to strengthen the specificity of capabilities.

DimensionReasoningScore

Specificity

Names the domain ("ClawSweeper status") and lists several concrete facets ("URLs, workflow health, active workers, ops snapshot") with only minor coverage gaps, fitting between the anchor-4 and anchor-5 examples.

4 / 5

Completeness

It gives a clear "what" (a status snapshot of URLs/workflow/workers/ops) but provides no explicit "Use when..." trigger clause, so the "when" is only weakly implied; the rubric caps completeness at 3 for missing trigger guidance.

3 / 5

Trigger Term Quality

Includes natural operator terms like "status", "workflow health", "active workers", and "ops snapshot" that a user would plausibly say, though it leans slightly jargon-heavy and misses common synonyms.

4 / 5

Distinctiveness Conflict Risk

The proper noun "ClawSweeper" carves out a distinct niche with minimal overlap risk, making it unlikely to trigger for the wrong skill even without an explicit trigger phrase.

5 / 5

Total

16

/

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
steipete/agent-scripts
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.