Trace knowledge artifact lineage to sources.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionprovenanceExecute the skills CLI command in your project's root directory to begin installation:
Fetches provenance from boshu2/agentops and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate provenance. Access via /provenance in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
243
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
243
stars
Trace knowledge artifact lineage to sources.
Given /provenance <artifact>:
Tool: Read
Parameters:
file_path: <artifact-path>
Look for provenance metadata:
# 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
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:
CASS JSON output fields:
{
"hits": [{
"title": "...",
"source_path": "/path/to/session.jsonl",
"created_at": 1766076237333,
"score": 18.5,
"agent": "claude_code"
}]
}
Transcript (source of truth)
↓
Forge extraction (candidate)
↓
Human review (promotion)
↓
Pattern recognition (tier-up)
↓
Skill creation (automation)
# 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>
Tell the user:
/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
/provenance --stale
Find artifacts where source may have changed:
# Artifacts older than their sources
find .agents/ -name "*.md" -mtime +30 2>/dev/null
User says: /provenance .agents/learnings/2026-01-15-auth-tokens.md
What happens:
cass search "auth-tokens" --json --limit 5Result: Full provenance chain from transcript to current tier, showing when artifact was created, discussed, and promoted.
User says: /provenance --orphans
What happens:
.agents/learnings/, .agents/patterns/ for files missing source metadataResult: Untracked knowledge identified, enabling retroactive lineage documentation or archival.
| 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 |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
provenance fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
provenance is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: provenance is focused, and the summary matches what you get after install.
Registry listing for provenance matched our evaluation — installs cleanly and behaves as described in the markdown.
provenance has been reliable in day-to-day use. Documentation quality is above average for community skills.
provenance reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend provenance for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
provenance is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
provenance fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
provenance has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 44