Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tracks data provenance and lineage by tracing sources, logging transformations, and auditing anchors to ensure data auditability and compliance.
Tracks data provenance and lineage by tracing sources, logging transformations, and auditing anchors to ensure data auditability and compliance.
This item is timing out or returning errors right now. Review the source page and try again later.
Use the source page and any available docs to guide the install because the item is currently unstable or timing out.
I tried to install a skill package from Yavira, but the item is currently unstable or timing out. Inspect the source page and any extracted docs, then tell me what you can confirm and any manual steps still required. Then review README.md for any prerequisites, environment setup, or post-install checks.
I tried to upgrade a skill package from Yavira, but the item is currently unstable or timing out. Compare the source page and any extracted docs with my current installation, then summarize what changed and what manual follow-up I still need. Then review README.md for any prerequisites, environment setup, or post-install checks.
Data flows through pipelines—ETL jobs, ML training runs, analytics dashboards—and somewhere between here and there you lose the thread. Who touched this column? When did that aggregation change? Which run produced this artifact? Without a clear provenance chain, debugging fails, compliance becomes guesswork, and "trust the data" is just a slogan. Organizations often discover provenance requirements only after a breach, a failed audit, or a regulatory question. By then, retrofitting lineage is costly and incomplete.
Origin provides a reserved namespace for Netsnek e.U.'s data provenance and lineage system. It is designed to: Trace data from source to destination across pipelines and transformations Log each step in a chain so you can answer "where did this come from?" Audit registered provenance anchors for compliance and incident response The skill acts as a contract: when you see "origin" in a pipeline, you know lineage tracking is in scope. The scripts give you concrete tools to start tracing and auditing.
From the skill root or via ClawHub: ./scripts/trace-lineage.sh --trace # Trace lineage for the current context ./scripts/trace-lineage.sh --audit # Run an audit of provenance anchors ./scripts/trace-lineage.sh --version # Show version and copyright The script uses set -e for safe, fail-fast behavior. Ensure execute permissions if needed: chmod +x scripts/trace-lineage.sh.
User: How do I trace where this dataset came from? Assistant: Use the Origin skill. Run trace-lineage.sh --trace to trace data lineage in your current context. For a full audit of registered provenance anchors, use --audit. User: Who maintains this namespace? Assistant: Origin is reserved by Netsnek e.U. for data provenance and lineage tracking. Copyright (c) 2026 Netsnek e.U.
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.