BC nex-skillmon
Health monitoring and cost optimization tool for OpenClaw skill ecosystems and power users managing multiple skills. Track all installed skills with real-time health scoring, detect stale skills (unused for 30+ days), identify skills with security flags or vulnerabilities, and monitor for available updates. View comprehensive cost dashboards showing API usage, estimated monthly costs, and spending per skill to identify expensive skills and optimize budget allocation. Set monthly cost budgets and receive alerts when approaching limits. Scan skill installation directories to discover all active skills and build baseline health metrics. Perform security checks for file integrity, vulnerability detection, and suspicious patterns. View usage statistics including trigger counts, execution duration, success rates, and trends over time. Generate detailed reports in markdown or JSON format for stakeholder communication and compliance documentation. Perfect for power users, development teams, and organizations managing complex skill infrastructures who need visibility into skill health, costs, and security posture.
As a process C 63/100 · Has gaps — weak spots: result and completion, running it twice, progress reporting
How to improve
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1122 chars, limit 1024
Process rating: all ten parameters 63/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1420 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1122: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 15 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (18 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.