New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Provenance Trace

by JetXu-LLM in JetXu-LLM/DocMason

Trace published DocMason knowledge objects or answer text back to evidence units and provenance records.

Apache-2.0Auto-check passedKnowledge Management

Install Provenance Trace

skills CLI
$ npx skills add JetXu-LLM/DocMason --skill provenance-trace -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JetXu-LLM/DocMason provenance-trace --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JetXu-LLM/DocMason.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/canonical/provenance-trace .claude/skills/provenance-trace && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
provenance-trace
GitHub stars
147
Token cost
~1.1k tokens
SKILL.md length
542 words
Files
2
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Trace published DocMason knowledge objects or answer text back to evidence units and provenance records.

  • Works in 7 steps: Use current as the default… → For citation-first tracing, run → For answer-first tracing, run → …
  • Knowledge Management work in your project
  • SKILL.md covers Required Capabilities, Procedure, Escalation Rules and Completion Signal, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Provenance Trace is an agent skill from JetXu-LLM/DocMason. Trace published DocMason knowledge objects or answer text back to evidence units and provenance records.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `workflow.json`).

It sits in Knowledge Management. The repository describes itself as: DocMason is a repo-native agent that turns your complex office files into a local LLM knowledge base and your second brain. The repo is the app. Codex is the runtime. The licence is Apache-2.0.

When your agent uses it

  • Knowledge Management work in your project

Example prompts

  • “/provenance-trace”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Use current as the default knowledge-base target unless the task explicitly says otherwise.
  2. For citation-first tracing, run
  3. For answer-first tracing, run
  4. Inspect
  5. If any segment is only partially grounded or unresolved, say so explicitly and avoid pretending stronger provenance than the trace supports.
  6. Return the final provenance or groundedness judgment to the main agent instead of treating trace output as a final user answer by itself.
  7. If you need to export a scratch trace note and the user did not specify a destination, place it under runtime/agent-work/.

What it can do on your machine

Read from SKILL.md and the folder at commit 37ea2f1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Provenance Trace loads about 1.1k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 542 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JetXu-LLM/DocMason at commit 37ea2f1, republished under its Apache-2.0 licence (© JetXu-LLM). 542 words, ~1,089 tokens.

Download SKILL.mdSave it as .claude/skills/provenance-trace/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
provenance-trace
description
Trace published DocMason knowledge objects or answer text back to evidence units and provenance records.

Provenance Trace

Use this skill when the task is to prove where a knowledge object or answer came from.

Use it directly for explicit provenance or citation requests, or let ask route here automatically.

Direct public trace remains a legal operator provenance surface. It does not substitute for canonical ask when the user is really asking for ordinary answer completion.

Required Capabilities

  • local file access
  • shell or command execution
  • ability to inspect structured JSON output

If the agent cannot inspect the local trace artifacts or source evidence, stop and explain that reliable provenance tracing is not possible.

Procedure

  1. Use current as the default knowledge-base target unless the task explicitly says otherwise.
  2. For citation-first tracing, run:
    • docmason trace --source-id <source_id> --json --compact
    • optionally add --unit-id <unit_id> for unit-level detail
    • if you genuinely need nested support objects or detailed render metadata, rerun full --json to a local file and inspect it selectively instead of pasting the raw payload into chat
    • keep DocMason workspace commands sequential inside the same workspace session; do not overlap trace, retrieve, sync, status, or validate-kb while a lease-owning command is still active
  3. For answer-first tracing, run:
    • docmason trace --answer-file <path> --json --compact
    • or docmason trace --session-id <session_id> --json --compact
    • do not invent a new freeform --source-ref surface in this phase; public trace remains ID-first
  4. Inspect:
    • payload_detail
    • any inherited reference_resolution block on answer-first traces
    • answer_state
    • source provenance
    • unit consumers
    • incoming and outgoing relations
    • grounding status for each answer segment
    • compact supporting_source_ids
    • compact supporting_unit_ids
    • supporting_artifact_ids
    • supporting_overlay_unit_ids
    • segment support_lane_counts
    • segment artifact_support_count
    • segment semantic_support_count
    • artifact focus_render_assets when present
    • render-inspection requirements
    • if the provenance judgment depends on nested artifact_supports, semantic_supports, overlay consumed inputs, covered slots, blocked slots, render refs, render_page_span, bbox, normalized_bbox, or sidecar paths, inspect a file-first full trace capture instead of the raw chat payload
  5. If any segment is only partially grounded or unresolved, say so explicitly and avoid pretending stronger provenance than the trace supports.
  6. Return the final provenance or groundedness judgment to the main agent instead of treating trace output as a final user answer by itself.
  7. If you need to export a scratch trace note and the user did not specify a destination, place it under runtime/agent-work/.
Show full SKILL.md (176 more words)Show less

Escalation Rules

  • If render_inspection_required is true, inspect the cited render assets before claiming a confident conclusion.
  • If the trace cannot resolve the requested source, session, or answer path, surface the not-found failure directly.
  • If the traced answer state is not grounded, qualify or abstain rather than overclaiming support.
  • If answer-first trace inherits an approximate or unresolved reference-resolution block, preserve that boundary in the provenance summary instead of silently upgrading it.

Completion Signal

  • The workflow is complete when the main agent has a clear provenance summary, including any answer_state, unresolved segments, and render-escalation requirements.

Notes

  • Phase 4 tracing reads knowledge_base/current/trace/ by default.
  • Answer-first tracing stores structured local logs under runtime/logs/.
  • --session-id works only for sessions that contain a reusable final answer.
  • In Phase 6b2, answer-first trace reuses the same shared reference-resolution contract already attached to the originating ask turn or retrieval session.
  • When a trace says render inspection is needed, inspect the render assets before claiming a confident conclusion.
  • Ordinary natural questions should usually begin at ask, which can route here when provenance is the real intent.

© JetXu-LLM, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/canonical/provenance-trace of JetXu-LLM/DocMason.

  • SKILL.md
  • workflow.json

Open the folder on GitHubat commit 37ea2f1

Compare with similar skills

Provenance Trace next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Provenance Trace compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Provenance Trace this skillJetXu-LLM/DocMason147—~1.1kAutomated safety check: PassApache-2.0
Logseq Review Workflow Evallogseq/logseq45k—~1kAutomated safety check: PassAGPL-3.0
Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill2.5k2 repos~3.2kAutomated safety check: PassNone
Obsidian CLIAtmosphere/atmosphere3.8k13 repos~795Automated safety check: PassApache-2.0
Esm Cjs Risk Scanlogseq/logseq45k—~3.3kAutomated safety check: PassAGPL-3.0
Knowledge Searchdataelement/bisheng12k—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Logseq Review Workflow Eval

    logseq/logseq

    Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…

    45k GitHub stars~1k tokensUpdated today
    Knowledge ManagementAuto-check passed

  • Baoyu URL To Markdown

    sdyckjq-lab/llm-wiki-skill

    Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.

    2.5k GitHub starsUsed in 2 repos~3.2k tokens
    Knowledge ManagementAuto-check passed

  • Obsidian CLI

    Atmosphere/atmosphere

    Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.

    3.8k GitHub starsUsed in 13 repos~795 tokens
    Knowledge ManagementAuto-check passed

  • Esm Cjs Risk Scan

    logseq/logseq

    Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.

    45k GitHub stars~3.3k tokensUpdated today
    Knowledge ManagementAuto-check passed

  • Knowledge Search

    dataelement/bisheng

    Search the user's knowledge bases and knowledge spaces (企业知识库检索).

    12k GitHub stars~1.1k tokensUpdated yesterday
    Knowledge ManagementAuto-check passed

  • Capture Conversation

    outline/outline

    Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.

    41k GitHub stars~474 tokensUpdated today
    Knowledge ManagementAuto-check passed

More from JetXu-LLM/DocMason

All 15 skills in this repo

  • Ask

    JetXu-LLM/DocMason

    Accept an ordinary user question inside a DocMason workspace, route it to the right inner workflow, and preserve conversation-native logs automatically.

    147 GitHub stars~7.1k tokensUpdated yesterday
    Auto-check passed

  • Adapter Sync

    JetXu-LLM/DocMason

    Generate or refresh the local Claude adapter surface for DocMason from canonical committed sources.

    147 GitHub stars~684 tokensUpdated yesterday
    Auto-check passed

  • Grounded Answer

    JetXu-LLM/DocMason

    Answer a user question through DocMason's canonical grounded workflow using retrieval, provenance tracing, render escalation, and a final answer-state check.

    147 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • Grounded Composition

    JetXu-LLM/DocMason

    Produce evidence-backed research, planning, drafting, or composition output from the published DocMason knowledge base while preserving provenance and answer-file discipline.

    147 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Knowledge Base Sync

    JetXu-LLM/DocMason

    Stage, incrementally refresh, validate, and publish the DocMason knowledge base from the local source corpus.

    147 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Knowledge Construction

    JetXu-LLM/DocMason

    Write bilingual Phase 3 knowledge objects for staged DocMason sources from rendered evidence and extracted structure.

    147 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Provenance Trace

What does Provenance Trace do?

Trace published DocMason knowledge objects or answer text back to evidence units and provenance records. Provenance Trace is an agent skill from JetXu-LLM/DocMason. Trace published DocMason knowledge objects or answer text back to evidence units and provenance records.

When should I use Provenance Trace?

Provenance Trace fits situations like: knowledge Management work in your project.

How do I install Provenance Trace in Claude Code?

Run `npx skills add JetXu-LLM/DocMason --skill provenance-trace -a claude-code`. Or copy the skill folder (skills/canonical/provenance-trace in JetXu-LLM/DocMason) into .claude/skills/provenance-trace in your project. Claude Code loads it when a task matches its description.

How do I install Provenance Trace in Codex?

Run `npx skills add JetXu-LLM/DocMason --skill provenance-trace -a codex`. Or copy the skill folder (skills/canonical/provenance-trace in JetXu-LLM/DocMason) into .agents/skills/provenance-trace in your project. Codex loads it when a task matches its description.

Can I use Provenance Trace in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JetXu-LLM/DocMason --skill provenance-trace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/provenance-trace, .gemini/skills/provenance-trace, .github/skills/provenance-trace and .opencode/skills/provenance-trace in your project.

What does Provenance Trace need to run?

SKILL.md names no scripts, command-line tools or credentials: Provenance Trace is instructions for the agent only.

Does Provenance Trace access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Provenance Trace safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Provenance Trace use?

Provenance Trace is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Provenance Trace use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Provenance Trace?

Skills that share tags, products or a category with Provenance Trace: Logseq Review Workflow Eval (logseq/logseq, 45k stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars), Obsidian CLI (Atmosphere/atmosphere, 3.8k stars) and Esm Cjs Risk Scan (logseq/logseq, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Provenance Trace?

JetXu-LLM (a GitHub user) maintains it in JetXu-LLM/DocMason, which has 147 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.

Source: JetXu-LLM/DocMason on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.