provenance-validate
Validate provenance records and chains for completeness and consistency
Best use case
provenance-validate is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
It is a strong fit for teams already working in Codex.
Validate provenance records and chains for completeness and consistency
Teams using provenance-validate should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/provenance-validate/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How provenance-validate Compares
| Feature / Agent | provenance-validate | Standard Approach |
|---|---|---|
| Platform Support | Codex | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Validate provenance records and chains for completeness and consistency
Which AI agents support this skill?
This skill is designed for Codex.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# Provenance Validate Command Validate provenance records against the PROV schema and verify chain integrity. ## Instructions When invoked, validate provenance: 1. **Load records** - Scan `.aiwg/research/provenance/records/` for all `.prov.yaml` files - If specific path provided, validate only that record 2. **Schema validation** - Validate each record against `@$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/schemas/provenance/prov-record.yaml` - Check required fields: entity.id, activity.id, agent.id - Verify URN format compliance - Verify timestamps are valid ISO-8601 3. **Entity resolution** - For each entity URN, verify the referenced file exists - Flag orphaned records (file deleted but provenance remains) - Detect untracked artifacts (files in tracked directories without provenance) 4. **Chain integrity** - Verify wasDerivedFrom sources exist and have their own provenance - Check bidirectional links (forward references have matching back-references) - Detect broken chains (missing intermediate records) 5. **Completeness check** - Scan `.aiwg/` directories for artifacts without provenance records - Calculate coverage percentage - List untracked artifacts 6. **Fix mode (--fix)** - Remove orphaned provenance records - Create stub records for untracked artifacts - Add missing bidirectional references 7. **Report** - Display validation results table - Show pass/fail/warning counts - List specific issues with remediation steps ## Arguments - `[path]` - Specific record or directory to validate (default: all records) - `--all` - Validate all records and check completeness - `--strict` - Treat warnings as errors - `--fix` - Auto-fix issues where possible - `--report [path]` - Save validation report to file ## References - @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/agents/provenance-manager.md - Provenance Manager agent - @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/schemas/provenance/prov-record.yaml - PROV record schema - @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/rules/provenance-tracking.md - Provenance tracking rules
Related Skills
Provenance Tracking
W3C PROV-O patterns for tracking media derivation chains and production history
validate-metadata
Validate AIWG extension definitions against the metadata schema and report errors with field names, line numbers, and remediation hints
validate-component
Validate a single AIWG component (skill, agent, or command) for completeness and correctness
validate-addon
Validate an entire AIWG addon package for completeness and release readiness
soul-validate
Validate a SOUL.md file against community best practices and quality criteria
setup-validate
Validate a `setup.aiwg.io/v1` SetupManifest file against the schema and run cons
research-provenance
Query provenance chains and artifact relationships
reproducibility-validate
Run a workflow multiple times and compare outputs to produce a similarity score and pass/fail verdict
provenance-report
Generate provenance coverage dashboard and statistics
provenance-query
Query provenance chains to trace artifact derivation and impact
provenance-create
Create a W3C PROV-compliant provenance record for an artifact
prose-validate
Validate an OpenProse program file against Prose contract grammar without executing it — checks frontmatter, contract structure, service references, and strategy syntax