BC analyze-json-data
Use when (1) Analyze JSON data and generate a structured API design document or OpenAPI specification.
This skill solves the specific engineering problem described in the trigger conditions.
As a process C 60/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationData and analyticsWriting and documentstype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- 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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 593 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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 102: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 10 headings
- +3Step-by-step instructions: 14 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: suspicious
This looks like a local JSON-to-OpenAPI helper, but it asks for an unexplained API key that does not fit the visible implementation.
LLM: suspicious (medium) · VirusTotal: · 28 May 2026