Evolving The Data Model
TriliumNext/Trilium
A skill your agent uses when adding a DB migration or a new column/field to a Becca entity in Trilium ("add a migration", "new column on notes/attributes", "ALTER TABLE", "add a field to…
Show the provenance trace, linking every reported number to the SQL that produced it with a confidence badge.
Install Trace
$ npx skills add ai-analyst-lab/ai-analyst --skill trace -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ai-analyst-lab/ai-analyst trace --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/trace .claude/skills/trace && rm -rf skills-srcUse ~/.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/
Install the "trace" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/trace into .claude/skills/trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/traceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ai-analyst-lab/ai-analyst --skill trace -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ai-analyst-lab/ai-analyst trace --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/trace .agents/skills/trace && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "trace" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/trace into .agents/skills/trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ai-analyst-lab/ai-analyst --skill trace -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ai-analyst-lab/ai-analyst trace --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/trace .cursor/skills/trace && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "trace" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/trace into .cursor/skills/trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ai-analyst-lab/ai-analyst.git --path .claude/skills/trace--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ai-analyst-lab/ai-analyst --skill trace -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ai-analyst-lab/ai-analyst trace --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/trace .gemini/skills/trace && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "trace" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/trace into .gemini/skills/trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ai-analyst-lab/ai-analyst traceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ai-analyst-lab/ai-analyst --skill trace -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/trace .github/skills/trace && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "trace" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/trace into .github/skills/trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ai-analyst-lab/ai-analyst --skill trace -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ai-analyst-lab/ai-analyst trace --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/trace .opencode/skills/trace && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "trace" agent skill from https://github.com/ai-analyst-lab/ai-analyst/tree/main/.claude/skills/trace into .opencode/skills/trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
trace- GitHub stars
- 304
- Token cost
- ~851 tokens
- SKILL.md length
- 445 words
- Files
- 1
- Skills in repo
- 43
- Repo updated
- First seen
- Licence
- MIT
At a glance
Show the provenance trace, linking every reported number to the SQL that produced it with a confidence badge.
- Works in 5 steps: Resolve the analysis. Read the current… → Verify the findings manifest. If… → Build + render the trace. Use the… → …
- Tasks that involve SQL
- SKILL.md covers Steps and Notes
- Calls python3
What it does
Trace is an agent skill from ai-analyst-lab/ai-analyst. Show the provenance trace, linking every reported number to the SQL that produced it with a confidence badge. Use after an analysis when someone asks "where did that number come from?"
Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases, covering SQL. It works with SQL. The repository describes itself as: AI Product Analyst — Claude Code-powered data analysis toolkit. The licence is MIT.
When your agent uses it
- Tasks that involve SQL
Example prompts
- “where did that number come from?”
- “/trace”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Resolve the analysis. Read the current analysis record
- Verify the findings manifest. If reported numbers were not registered,
- Build + render the trace. Use the lifecycle command so all inputs come
- Open and share it. Open the HTML locally when the environment supports
- Read it out. Walk the findings top to bottom: the number, its badge, the SQL. Call out anything
What it can do on your machine
Read from SKILL.md and the folder at commit 52c0744. 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
Shell commands in SKILL.md call:
python3
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
Trace loads about 851 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 445 words of instructions outside code blocks.
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 ai-analyst-lab/ai-analyst at commit 52c0744, republished under its MIT licence (© ai-analyst-lab). 445 words, ~851 tokens.
Download SKILL.mdSave it as
.claude/skills/trace/SKILL.md (or your agent's skills folder).- name
- trace
- description
- Show the provenance trace, linking every reported number to the SQL that produced it with a confidence badge. Use after an analysis when someone asks "where did that number come from?"
/trace: expose the query logic behind every number
Renders and shares one self-contained HTML that ties each reported number (a finding) back to the query
that produced it, labeled by confidence: cited (the agent named the query), value-match (a
query's captured result_value equals the number), or inferred (nearest query in time). Unmatched
findings and orphan queries are shown, not hidden. An unverified number is the most important thing to
surface. This is the on-demand artifact for any "prove it" moment.
It reads the analysis record, query log, bounded result previews, findings manifest, action log, and reconciler.
Steps
Resolve the analysis. Read the current analysis record:
bash python3 -c " import sys; sys.path.insert(0, '.') from helpers.knowledge.analysis_context import current_analysis print(current_analysis() or '') "If there is no current analysis, there is nothing to trace yet. Say so and stop (or, for a past run, point
build_traceat that analysis_id explicitly).Interactive analysis provenance always remains under the repository's top-level
working/directory. The analysis output directory is only where the shareable HTML and written review go. Do not create or copy anothercurrent-analysis.json, and do not relocate the query log.Verify the findings manifest. If reported numbers were not registered, do not pretend a trace exists. Read the saved analysis and query log, then register each reported number with the exact supporting query IDs. Record derived values with their formula and source finding IDs. Never label a timestamp-only guess as a verified link.
Build + render the trace. Use the lifecycle command so all inputs come from the canonical provenance store and the HTML goes to the recorded output directory:
bash python3 scripts/analysis_trace.py buildThis also writes
working/provenance_<analysis_id>.jsonandworking/trace_receipt_<analysis_id>.json.Open and share it. Open the HTML locally when the environment supports that action. Always report the exact path as a deliverable so the user can open or share it. Do not merely say that the trace was generated. It is self-contained and projection-friendly, with large type, collapsible SQL, and colored confidence badges.
Leave the active marker in place. The next
startcommand replaces it with a fresh id. Do not delete it at the end of the trace.Read it out. Walk the findings top to bottom: the number, its badge, the SQL. Call out anything unmatched (a number with no query behind it). That is the honesty check and the thing to fix.
Show full SKILL.md (69 more words)Show less
Notes
- Confidence is itself provenance. A
citedlink is strongest because the finding names the query. Avalue-matchis supporting evidence because the captured scalar or structured result contains the number.inferredis a hint, not proof, so say so when reading it out. - Teaching tie-in. This is the concrete answer to "how do I know the agent didn't make the number up?" Pair it with the provenance-chain diagram.
© ai-analyst-lab, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/trace of ai-analyst-lab/ai-analyst.
Open the folder on GitHubat commit 52c0744
Compare with similar skills
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Trace this skillai-analyst-lab/ai-analyst | 304 | — | ~851 | Automated safety check: Pass | MIT | |
| Evolving The Data ModelTriliumNext/Trilium | 38k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| SQL Optimization Patternsynulihao/AgentSkillOS | 617 | 10 repos | ~3.3k | Automated safety check: Pass | None | |
| SQL PortabilityHL7/sql-on-fhir | 150 | — | ~512 | Automated safety check: Pass | Custom licence | |
| DB Migrationskurealnum/dotfiles | 290 | — | ~820 | Automated safety check: Pass | None | |
| Contact FilterChatbotXIO/ChatbotX | 878 | — | ~2.5k | Automated safety check: Pass | Custom licence |
Similar skills
SQL Optimization Patterns
ynulihao/AgentSkillOS
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries.
SQL Portability
HL7/sql-on-fhir
Analyse whether a SQL query is portable across database implementations using sqlglot transpilation.
DB Migrations
kurealnum/dotfiles
A skill your agent uses when generating or regenerating Drizzle migration files, changing database schema tables or columns, resolving migration sequence conflicts after rebase, reviewing migration…
Contact Filter
ChatbotXIO/ChatbotX
Work with the ChatbotX contact filter system — the shared filter model behind the contacts list, conversations, and broadcast audiences.
Add Utils Function
MichealWayne/fe-tools
Add or modify utility functions in fe-tools. An agent skill from MichealWayne/fe-tools.
More from ai-analyst-lab/ai-analyst
All 43 skills in this repoAlways Compare
ai-analyst-lab/ai-analyst
Never present a metric or number in isolation; anchor every number to a comparison (prior period, benchmark, or another segment) or state that none is available.
Archaeology
ai-analyst-lab/ai-analyst
Retrieve proven SQL patterns, table cheatsheets, and join patterns from .knowledge/query-archaeology/ so past work gets reused.
Archive Analysis
ai-analyst-lab/ai-analyst
Save completed analyses to the knowledge system's analysis archive for future reference.
Auth Preflight
ai-analyst-lab/ai-analyst
Verify Google Workspace MCP authentication at the start of any session that needs Google APIs (Docs, Slides, Drive).
Causal
ai-analyst-lab/ai-analyst
Causal inference toolkit for when experiments are not possible: estimate treatment effects from observational data with assumption checks and mandatory caveats.
Chart To Drive
ai-analyst-lab/ai-analyst
Standardized workflow for uploading local chart PNGs to Google Drive and making them available for insertion into Google Docs and Slides.
Related
Works with
Categories
Questions about Trace
What does Trace do?
Show the provenance trace, linking every reported number to the SQL that produced it with a confidence badge. Trace is an agent skill from ai-analyst-lab/ai-analyst. Show the provenance trace, linking every reported number to the SQL that produced it with a confidence badge.
When should I use Trace?
Trace fits situations like: tasks that involve SQL.
How do I install Trace in Claude Code?
Run `npx skills add ai-analyst-lab/ai-analyst --skill trace -a claude-code`. Or copy the skill folder (.claude/skills/trace in ai-analyst-lab/ai-analyst) into .claude/skills/trace in your project. Claude Code loads it when a task matches its description.
How do I install Trace in Codex?
Run `npx skills add ai-analyst-lab/ai-analyst --skill trace -a codex`. Or copy the skill folder (.claude/skills/trace in ai-analyst-lab/ai-analyst) into .agents/skills/trace in your project. Codex loads it when a task matches its description.
Can I use 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 ai-analyst-lab/ai-analyst --skill 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/trace, .gemini/skills/trace, .github/skills/trace and .opencode/skills/trace in your project.
What does Trace need to run?
Going by SKILL.md and its folder, Trace needs the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does 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 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 Trace use?
Trace is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Trace use?
About 851 tokens (SKILL.md is roughly 3.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 Trace?
Skills that share tags, products or a category with Trace: Evolving The Data Model (TriliumNext/Trilium, 38k stars), SQL Optimization Patterns (ynulihao/AgentSkillOS, 617 stars), SQL Portability (HL7/sql-on-fhir, 150 stars) and DB Migrations (kurealnum/dotfiles, 290 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trace?
ai-analyst-lab (a GitHub organization) maintains it in ai-analyst-lab/ai-analyst, which has 304 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on September 30, 2026.
Source: ai-analyst-lab/ai-analyst on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.