BC json-schema-manual
JSON Schema Manual: draft 2020-12 validation schema from a confirmed field list, with required and enum values only where confirmed. Use for an API or import contract.
Generates JSON Schema for draft 2020-12 based on a field list, adding required and enum constraints only where confirmed. Designed for API contracts and data imports. Seven files in the package, no critical errors, code quality at 83 percent. Tests found no broken references or syntax issues.
In practice: works as a templating tool for rapid schema generation. Without model runs, it's unclear how well it infers required fields from raw input or handles nested objects. The 64 percent process score hints at gaps in documentation or examples. Install if you already have a clean field inventory and can validate the output schema manually before production use.
JSON Schema Manual: draft 2020-12 validation schema from a confirmed field list, with required and enum values only where confirmed.
As a process C 64/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 167 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "source_repo"
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 2 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 15 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3092 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 167: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (3 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.