SKILLEMALL.ai

AB output-contract-enforcer

Validates that a DAG node's output matches its declared JSON schema before passing to downstream nodes. The glue that makes multi-agent DAGs reliable. Use when checking output contract compliance, generating validation schemas from descriptions, or debugging contract mismatches between nodes. Activate on "validate output", "output contract", "schema validation", "contract mismatch", "output doesn't match". NOT for content quality assessment (use dag-quality), skill grading (use skill-grader), or general JSON schema work outside DAG context.

curiositech/some_claude_skills Claude Code author: curiositech 2 files body ≈ 1 255 tokens Open the sourcegithub.com↗ analyzed 39 min ago

Validates that a DAG node's output matches its declared JSON schema before passing to downstream nodes.

As a process B 65/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, progress reporting

AnalyzerSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
96
Run on models
none yet
Process rating
B
65/100
Nearly there
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

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: 2. 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 65/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 50When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 11 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1255 tokens
    • 100Running it twice. No mutating operations

    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

    • +1No license
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 546: enough signal without eating the budget
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 11 items
    • +3Output format is stated explicitly
    • +4Has examples (4 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.