
- Installs
- 756
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/boshu2/agentops --skill provenance- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads provenance automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Provenance Skill
Trace knowledge artifact lineage to sources.
Execution Steps
Given /provenance <artifact>:
Step 1: Read the Artifact
Tool: Read
Parameters:
file_path: <artifact-path>
Look for provenance metadata:
- Source references
- Session IDs
- Dates
- Related artifacts
Step 2: Trace Source Chain
# Check for source metadata in the file
grep -i "source\|session\|from\|extracted" <artifact-path>
# Search for related transcripts using ao
ao search "<artifact-name>" 2>/dev/null
Step 3: Search Session Transcripts with CASS
Use CASS to find when this artifact was discussed:
# Extract artifact name for search
artifact_name=$(basename "<artifact-path>" .md)
# Search session transcripts
cass search "$artifact_name" --json --limit 5
Parse CASS results to find:
- Sessions where artifact was created/discussed
- Timeline of references
- Related sessions by workspace
CASS JSON output fields:
{
"hits": [{
"title": "...",
"source_path": "/path/to/session.jsonl",
"created_at": 1766076237333,
"score": 18.5,
"agent": "claude_code"
}]
}
Step 4: Build Lineage Chain
Transcript (source of truth)
↓
Forge extraction (candidate)
↓
Human review (promotion)
↓
Pattern recognition (tier-up)
↓
Skill creation (automation)
Step 5: Write Provenance Report
# Provenance: <artifact-name>
## Current State
- **Tier:** <0-3>
- **Created:** <date>
- **Citations:** <count>
## Source Chain
1. **Origin:** <transcript or session>
- Line/context: <where extracted>
- Extracted: <date>
2. **Promoted:** <tier change>
- Reason: <why promoted>
- Date: <when>
## Session References (from CASS)
| Date | Session | Agent | Score |
|------|---------|-------|-------|
| <date> | <session-id> | <agent> | <score> |
## Related Artifacts
- <related artifact 1>
- <related artifact 2>
Step 6: Report to User
Tell the user:
- Artifact lineage
- Original source
- Promotion history
- Session references (from CASS)
- Related artifacts
Finding Orphans
/provenance --orphans
Find artifacts without source tracking:
# Files without "Source:" or "Session:" metadata
for f in .agents/learnings/*.md; do
grep -L "Source\|Session" "$f" 2>/dev/null
done
Finding Stale Artifacts
/provenance --stale
Find artifacts where source may have changed:
# Artifacts older than their sources
find .agents/ -name "*.md" -mtime +30 2>/dev/null
Key Rules
- Every insight has a source - trace it
- Track promotions - know why tier changed
- Find orphans - clean up untracked knowledge
- Maintain lineage - provenance enables trust
- Use CASS - find when artifacts were discussed
Examples
Trace Artifact Lineage
User says: /provenance .agents/learnings/2026-01-15-auth-tokens.md
What happens:
- Agent reads artifact and extracts source metadata (session ID, date, references)
- Agent searches session transcripts with
cass search "auth-tokens" --json --limit 5 - Agent parses CASS results to find origin session and timeline
- Agent traces promotion history from forge → learnings → patterns
- Agent builds lineage chain and writes report to markdown
- Agent reports artifact tier, citations, related artifacts
Result: Full provenance chain from transcript to current tier, showing when artifact was created, discussed, and promoted.
Find Orphaned Artifacts
User says: /provenance --orphans
What happens:
- Agent scans
.agents/learnings/,.agents/patterns/for files missing source metadata - Agent greps each file for "Source:" or "Session:" fields
- Agent lists files without provenance tracking
- Agent reports orphan count and recommends adding source references
Result: Untracked knowledge identified, enabling retroactive lineage documentation or archival.
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| No source metadata found | Artifact created before provenance tracking | Use CASS to find origin session retroactively; add Source field manually |
| CASS returns no results | Session not indexed or artifact name mismatch | Check session transcript exists; try broader search terms |
| Stale artifact check fails | find command not available or permission error | Use `ls -lt .agents/ |
| Lineage chain incomplete | Promotion not recorded in artifact metadata | Reconstruct from git history or session transcripts; document gaps |
FAQ
What does the provenance skill do?
Trace artifact provenance.
How do I install provenance?
Run npx skills add https://github.com/boshu2/agentops --skill provenance in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/provenance/ (personal) or .claude/skills/provenance/ (project).
Which AI agents can use provenance?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is provenance safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains provenance?
It is published by boshu2 in boshu2/agentops. It has 756 recorded installs.
More from boshu2/agentops
council
boshu2/agentops
Compare independent opinions from several models or contexts without inflating agreement. Use when: wanting a second opinion or debate, or summarizing several reviewers' results.
doc
boshu2/agentops
Write source-checked docs, READMEs, change descriptions and handoffs. Use when: documenting a change, leaving or resuming a handoff, or drafting a questionnaire for someone else.
research
boshu2/agentops
Answer one cited question on code, history, claims or patterns. Use when: asked how it works, why it changed, if a claim or done/shipped report holds, or a pattern warrants a rule.
plan
boshu2/agentops
Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use when: planning, breaking down or scoping a change.
swarm
boshu2/agentops
Dispatch explicit disjoint packets exactly once through a caller-selected executor. Triggers: "swarm", "dispatch disjoint packets", "parallel explicit tasks".
rpi
boshu2/agentops
Drive one accepted change through implementation and checks to done, with one fresh review only where a mistake is costly. Use when: asked to run or orchestrate work through RPI.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.