Validate
Dry-run GAUNTLEX validation — parses the spec, resolves policy playbooks, checks model availability, and runs the AVF golden fixture gate. No attacks are fired. Exit 1 if any check fails.From its SKILL.md
npx -y skills add sanjoy1234/gauntlex --skill validateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, as published. Nobody here has run it
/gauntlex:validate
Validates the GAUNTLEX environment and spec WITHOUT firing any real attacks.
Usage
/gauntlex:validate [--spec <file>]
Execution
gauntlex validate --spec "$SPEC_FILE"
What It Checks
- AVF gate: Breaker must find >75% of seeded vulnerabilities in the 5 golden CVE fixtures
- Model reachability: GAUNTLEX never assumes a provider — it checks whichever provider was explicitly configured (Anthropic, OpenRouter, HuggingFace, OpenAI-compatible, or local Ollama, set via
gauntlex setup,MODEL_PROVIDER, or.gauntlex.yml). If nothing is configured, this fails with "not configured — rungauntlex setup" - ChromaDB: Knowledge Forge writable at
.gauntlex/forge/ - Playbook resolution: All domains listed in
.gauntlex.ymlhave corresponding YAML files - Spec parseable: The spec file (if provided) can be read and is non-empty
Output to User
Report each check as PASS/FAIL with a reason, using the exact Detail text from the command output for the model check — do not assume or guess a provider. If any FAIL:
- Explain the specific failure
- Give the fix command shown in the output (
gauntlex setupif no provider is configured at all; otherwise the provider-specific fix, e.g.ollama pull llama3.1:8bonly if Ollama is the provider actually configured)
If all pass: "Environment validated — ready to run."