intent-solutions-io/nixtla-universal-validator
003-skills/.claude/skills/nixtla-universal-validator/SKILL.md
Validate Nixtla skills and plugins with deterministic evidence bundles and strict schema gates. Use when auditing changes or enforcing compliance. Trigger with 'run validation' or 'audit validators'.
$ install --global
skillsauthnpx skillsauth add intent-solutions-io/plugins-nixtla nixtla-universal-validatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 11:14 PM5.5s21 files scanned
SKILL.md
- name:
- nixtla-universal-validator
- description:
- Validate Nixtla skills and plugins with deterministic evidence bundles and strict schema gates. Use when auditing changes or enforcing compliance. Trigger with 'run validation' or 'audit validators'.
- allowed-tools:
- Read,Write,Bash(python:*),Bash(bash:*),Bash(pytest:*)
- version:
- 1.0.0
- author:
- Jeremy Longshore <[email protected]>
- license:
- MIT
Nixtla Universal Validator
Purpose
Produce deterministic, reviewable validation evidence (reports + JSON + logs) for a repo, plugin, or skill.
Overview
This skill combines two layers:
- A multi-phase subagent workflow (for human-readable analysis + reconciliation)
- A deterministic validator runner (for ground-truth logs and machine-readable summaries)
Validation runs as a pipeline with deterministic gates:
- Discover what changed and what should be validated
- Validate schemas/structure (skills + plugins) using canonical repo validators
- Run behavioral checks (tests) when requested
- Reconcile results into a single evidence bundle with pass/fail and next actions
This pattern generalizes beyond Nixtla by swapping the check catalog (a list of commands + expected artifacts).
Prerequisites
- Python 3.11+
- Repo validators available:
004-scripts/validate_skills_v2.py004-scripts/validate-all-plugins.sh
- Optional for plugin validation:
jq
Instructions
Step 1: Create a run directory
Use the built-in runner to create a timestamped evidence bundle under reports/<project>/<timestamp>/.
Step 2: Pick a target scope
Choose one:
- Repo root: validate everything
- A plugin folder:
005-plugins/<plugin> - A skill folder:
.claude/skills/<skill>or003-skills/.claude/skills/<skill>
Step 3: Run the deterministic validator suite
python {baseDir}/scripts/run_validator_suite.py \
--target . \
--project nixtla \
--out reports/nixtla
List built-in profiles:
python {baseDir}/scripts/run_validator_suite.py \
--list-profiles \
--target . \
--project nixtla \
--out reports/nixtla
To validate a single plugin:
python {baseDir}/scripts/run_validator_suite.py \
--target 005-plugins/nixtla-baseline-lab \
--project nixtla-baseline-lab \
--out reports/nixtla-baseline-lab
Step 4: (Optional) Include tests
python {baseDir}/scripts/run_validator_suite.py \
--target . \
--project nixtla \
--out reports/nixtla \
--run-tests
Step 4b: (Optional) Run an enterprise profile
python {baseDir}/scripts/run_validator_suite.py \
--target . \
--project nixtla \
--out reports/nixtla \
--profile enterprise \
--fail-on-warn \
--run-tests
Step 5: (Optional) Use the multi-phase subagent workflow
Run phases in order using the prompts in {baseDir}/agents/ and procedures in {baseDir}/references/.
Each phase must write a report file under the run directory and return strict JSON per the phase contract.
Output
Each run creates a timestamped evidence bundle:
reports/<project>/<timestamp>/summary.jsonreports/<project>/<timestamp>/report.mdreports/<project>/<timestamp>/checks/*.log
Error Handling
-
Error: Validator command not found
Solution: Confirm repo scripts exist and run from the repo root. -
Error: Plugin validation fails due to
jq
Solution: Installjqor run only skill validation. -
Error: Tests fail after schema passes
Solution: Treat this as a behavioral regression; fix tests or code, then re-run.
Examples
Common validations:
# Strict schema/structure gates
python 004-scripts/validate_skills_v2.py --fail-on-warn
bash 004-scripts/validate-all-plugins.sh .
Generate an evidence bundle (profile-driven):
# Generate a single evidence bundle for a PR
python {baseDir}/scripts/run_validator_suite.py \
--target . \
--project pr-1234 \
--out reports/pr-1234 \
--run-tests
Resources
- Subagent orchestration pattern:
000-docs/000a-planned-skills/templates/verification-pipeline/README.md - Canonical skills validator:
004-scripts/validate_skills_v2.py - Canonical plugin validator:
004-scripts/validate-all-plugins.sh - Subagent prompts:
{baseDir}/agents/ - Phase procedures:
{baseDir}/references/
Related Skills
intent-solutions-io/managing-test-environments
testing
VerifiedTrustedCommunity
This skill enables Claude to manage isolated test environments using Docker Compose, Testcontainers, and environment variables. It is used to create consistent, reproducible testing environments for software projects. Claude should use this skill when the user needs to set up a test environment with specific configurations, manage Docker Compose files for test infrastructure, set up programmatic container management with Testcontainers, manage environment variables for tests, or ensure cleanup after tests. Trigger terms include "test environment", "docker compose", "testcontainers", "environment variables", "isolated environment", "env-setup", and "test setup".
6SKILL.mdUpdated Jun 5, 2026
intent-solutions-io/generating-test-doubles
tools
VerifiedTrustedCommunity
This skill uses the test-doubles-generator plugin to automatically create mocks, stubs, spies, and fakes for unit testing. It analyzes dependencies in the code and generates appropriate test doubles based on the chosen testing framework, such as Jest, Sinon, or others. Use this skill when you need to generate test doubles, mocks, stubs, spies, or fakes to isolate units of code during testing. Trigger this skill by requesting test double generation or using the `/gen-doubles` or `/gd` command.
6SKILL.mdUpdated Jun 5, 2026
intent-solutions-io/generating-test-data
tools
VerifiedTrustedCommunity
This skill enables Claude to generate realistic test data for software development. It uses the test-data-generator plugin to create users, products, orders, and custom schemas for comprehensive testing. Use this skill when you need to populate databases, simulate user behavior, or create fixtures for automated tests. Trigger phrases include "generate test data", "create fake users", "populate database", "generate product data", "create test orders", or "generate data based on schema". This skill is especially useful for populating testing environments or creating sample data for demonstrations.
6SKILL.mdUpdated Jun 5, 2026
intent-solutions-io/analyzing-test-coverage
development
VerifiedTrustedCommunity
This skill analyzes code coverage metrics to identify untested code and generate comprehensive coverage reports. It is triggered when the user requests analysis of code coverage, identification of coverage gaps, or generation of coverage reports. The skill is best used to improve code quality by ensuring adequate test coverage and identifying areas for improvement. Use trigger terms like "analyze coverage", "code coverage report", "untested code", or the shortcut "cov".
6SKILL.mdUpdated Jun 5, 2026