Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure.
Install Analyze Trace
$ npx skills add voidhashcom/lensflare --skill analyze-trace -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install voidhashcom/lensflare analyze-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/voidhashcom/lensflare.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/lensflare-desktop/skills/analyze-trace .claude/skills/analyze-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 "analyze-trace" agent skill from https://github.com/voidhashcom/lensflare/tree/main/plugins/lensflare-desktop/skills/analyze-trace into .claude/skills/analyze-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-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/voidhashcom/lensflare/tree/main/plugins/lensflare-desktop/skills/analyze-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 voidhashcom/lensflare --skill analyze-trace -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install voidhashcom/lensflare analyze-trace --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/voidhashcom/lensflare.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/lensflare-desktop/skills/analyze-trace .agents/skills/analyze-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 "analyze-trace" agent skill from https://github.com/voidhashcom/lensflare/tree/main/plugins/lensflare-desktop/skills/analyze-trace into .agents/skills/analyze-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-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 voidhashcom/lensflare --skill analyze-trace -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install voidhashcom/lensflare analyze-trace --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/voidhashcom/lensflare.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/lensflare-desktop/skills/analyze-trace .cursor/skills/analyze-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 "analyze-trace" agent skill from https://github.com/voidhashcom/lensflare/tree/main/plugins/lensflare-desktop/skills/analyze-trace into .cursor/skills/analyze-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-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/voidhashcom/lensflare.git --path plugins/lensflare-desktop/skills/analyze-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 voidhashcom/lensflare --skill analyze-trace -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install voidhashcom/lensflare analyze-trace --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/voidhashcom/lensflare.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/lensflare-desktop/skills/analyze-trace .gemini/skills/analyze-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 "analyze-trace" agent skill from https://github.com/voidhashcom/lensflare/tree/main/plugins/lensflare-desktop/skills/analyze-trace into .gemini/skills/analyze-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-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 voidhashcom/lensflare analyze-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 voidhashcom/lensflare --skill analyze-trace -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/voidhashcom/lensflare.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/lensflare-desktop/skills/analyze-trace .github/skills/analyze-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 "analyze-trace" agent skill from https://github.com/voidhashcom/lensflare/tree/main/plugins/lensflare-desktop/skills/analyze-trace into .github/skills/analyze-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-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 voidhashcom/lensflare --skill analyze-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 voidhashcom/lensflare analyze-trace --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/voidhashcom/lensflare.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/lensflare-desktop/skills/analyze-trace .opencode/skills/analyze-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 "analyze-trace" agent skill from https://github.com/voidhashcom/lensflare/tree/main/plugins/lensflare-desktop/skills/analyze-trace into .opencode/skills/analyze-trace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-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
analyze-trace- GitHub stars
- 100
- Token cost
- ~340 tokens
- SKILL.md length
- 150 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure.
- Works in 6 steps: If the user supplied a traceId, use it.… → Call lensflare:getTrace with the… → Read summary.spanCount and… → …
- The user pastes a trace id
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Asks why is this slow
What it does
Analyze Trace is an agent skill from voidhashcom/lensflare. Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure. Use when the user pastes a trace id, asks "why is this slow", or wants a request-level post-mortem of a real production / dev request captured in Lensflare.
Its SKILL.md is about 340 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 DevOps & Cloud, covering Runbooks and postmortems. The licence is MIT.
When your agent uses it
- The user pastes a trace id
- Asks why is this slow
- Wants a request-level post-mortem of a real production / dev request captured in Lensflare
Example prompts
- “why is this slow”
- “/analyze-trace”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- If the user supplied a traceId, use it. Otherwise call lensflare:queryTelemetry to find a relevant trace (filter by serviceName, time, or…
- Call lensflare:getTrace with the resolved datasetId and traceId. If it returns null, double-check the traceId with queryTelemetry (traceId…
- Read summary.spanCount and summary.erroredSpanCount. If errors exist, lead with them: name + service + durationUs.
- Walk spans in order. Highlight the longest span, the deepest chain, and any span whose status = "error" or whose duration is more than 50%…
- Surface relatedEvents only when they materially explain a failure (e.g. an exception event on the failing span).
- End with a one-line root-cause hypothesis and a suggested follow-up query. Example: _"to see all requests with this error…
What it can do on your machine
Read from SKILL.md and the folder at commit 77af210. 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
Analyze Trace loads about 340 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 150 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 voidhashcom/lensflare at commit 77af210, republished under its MIT licence (© voidhashcom). 150 words, ~340 tokens.
Download SKILL.mdSave it as
.claude/skills/analyze-trace/SKILL.md (or your agent's skills folder).- name
- analyze-trace
- description
- Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure. Use when the user pastes a trace id, asks "why is this slow", or wants a request-level post-mortem of a real production / dev request captured in Lensflare.
Analyze a trace in Lensflare
- If the user supplied a
traceId, use it. Otherwise calllensflare:queryTelemetryto find a relevant trace (filter byserviceName, time, or attributes). Pick the trace whose root span has the highestdurationUsor whosestatus = "error". - Call
lensflare:getTracewith the resolveddatasetIdandtraceId. If it returnsnull, double-check thetraceIdwithqueryTelemetry(traceId = "<id>") before reporting back. - Read
summary.spanCountandsummary.erroredSpanCount. If errors exist, lead with them: name + service +durationUs. - Walk
spansin order. Highlight the longest span, the deepest chain, and any span whosestatus = "error"or whose duration is more than 50% of its parent's. - Surface
relatedEventsonly when they materially explain a failure (e.g. an exception event on the failing span). - End with a one-line root-cause hypothesis and a suggested follow-up query. Example: "to see all requests with this error:
attributes.http.status_code = 500 and serviceName = \"api\"".
© voidhashcom, 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 plugins/lensflare-desktop/skills/analyze-trace of voidhashcom/lensflare.
Open the folder on GitHubat commit 77af210
Compare with similar skills
Analyze 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 |
|---|---|---|---|---|---|---|
| Analyze Trace this skillvoidhashcom/lensflare | 100 | — | ~340 | Automated safety check: Pass | MIT | |
| Trader Memory Coretradermonty/claude-trading-skills | 3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Author Migrationnrwl/nx | 29k | — | ~12k | Automated safety check: Notes | MIT | |
| Write Notes Like Deepseekczm15053/write-notes-like-deepseek | 477 | — | ~1.9k | Automated safety check: Pass | None | |
| OpenRig Upgrade Proceduremvschwarz/openrig | 5.5k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| GreptimeDB Release RunbookGreptimeTeam/greptimedb | 6.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Author Migration
nrwl/nx
Author or scope a first-party Nx migration. An agent skill from nrwl/nx.
Write Notes Like Deepseek
czm15053/write-notes-like-deepseek
A skill your agent uses when a change is non-trivial by DSH standards (behavior, architecture, cross-file contracts, process/tooling, testing strategy, or on-disk/wire/config formats), when choosing…
OpenRig Upgrade Procedure
mvschwarz/openrig
Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.
GreptimeDB Release Runbook
GreptimeTeam/greptimedb
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
Statem
henryqin1997/statem
A skill your agent uses when a long coding or research task should be managed with statem state-machine runbooks, including creating specs, starting or resuming runs, checking current state…
More from voidhashcom/lensflare
Find Error
voidhashcom/lensflare
Find recent errors in a Lensflare dataset and summarise their root cause.
Query Logs
voidhashcom/lensflare
Translate a natural-language question about logs or telemetry into a Lensflare query and return the results.
Related
Categories
Questions about Analyze Trace
What does Analyze Trace do?
Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure. Analyze Trace is an agent skill from voidhashcom/lensflare. Walk a Lensflare trace span-by-span and explain timing, errors, and parent/child structure.
When should I use Analyze Trace?
Analyze Trace fits situations like: the user pastes a trace id; asks why is this slow; wants a request-level post-mortem of a real production / dev request captured in Lensflare.
How do I install Analyze Trace in Claude Code?
Run `npx skills add voidhashcom/lensflare --skill analyze-trace -a claude-code`. Or copy the skill folder (plugins/lensflare-desktop/skills/analyze-trace in voidhashcom/lensflare) into .claude/skills/analyze-trace in your project. Claude Code loads it when a task matches its description.
How do I install Analyze Trace in Codex?
Run `npx skills add voidhashcom/lensflare --skill analyze-trace -a codex`. Or copy the skill folder (plugins/lensflare-desktop/skills/analyze-trace in voidhashcom/lensflare) into .agents/skills/analyze-trace in your project. Codex loads it when a task matches its description.
Can I use Analyze 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 voidhashcom/lensflare --skill analyze-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/analyze-trace, .gemini/skills/analyze-trace, .github/skills/analyze-trace and .opencode/skills/analyze-trace in your project.
What does Analyze Trace need to run?
SKILL.md names no scripts, command-line tools or credentials: Analyze Trace is instructions for the agent only.
Does Analyze 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 Analyze 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 Analyze Trace use?
Analyze 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 Analyze Trace use?
About 340 tokens (SKILL.md is roughly 1.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 Analyze Trace?
Skills that share tags, products or a category with Analyze Trace: Trader Memory Core (tradermonty/claude-trading-skills, 3k stars), Author Migration (nrwl/nx, 29k stars), Write Notes Like Deepseek (czm15053/write-notes-like-deepseek, 477 stars) and OpenRig Upgrade Procedure (mvschwarz/openrig, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyze Trace?
voidhashcom (a GitHub organization) maintains it in voidhashcom/lensflare, which has 100 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on June 25, 2026.
Source: voidhashcom/lensflare on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.