Workthreads
specstoryai/getspecstory
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more).
Enumerate the real schema of VS Code Copilot Chat's debug logs (workspaceStorage//GitHub.copilot-chat/debug-logs//main.jsonl) from files on the current machine — every event type and field, flagged…
Install Discover Debug Log Schema
$ npx skills add rajbos/ai-engineering-fluency --skill discover-debug-log-schema -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rajbos/ai-engineering-fluency discover-debug-log-schema --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/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/discover-debug-log-schema .claude/skills/discover-debug-log-schema && 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 "discover-debug-log-schema" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/discover-debug-log-schema into .claude/skills/discover-debug-log-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-debug-log-schema", 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/rajbos/ai-engineering-fluency/tree/main/.claude/skills/discover-debug-log-schemaType 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 rajbos/ai-engineering-fluency --skill discover-debug-log-schema -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rajbos/ai-engineering-fluency discover-debug-log-schema --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/discover-debug-log-schema .agents/skills/discover-debug-log-schema && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "discover-debug-log-schema" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/discover-debug-log-schema into .agents/skills/discover-debug-log-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-debug-log-schema", 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 rajbos/ai-engineering-fluency --skill discover-debug-log-schema -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rajbos/ai-engineering-fluency discover-debug-log-schema --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/discover-debug-log-schema .cursor/skills/discover-debug-log-schema && 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 "discover-debug-log-schema" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/discover-debug-log-schema into .cursor/skills/discover-debug-log-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-debug-log-schema", 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/rajbos/ai-engineering-fluency.git --path .claude/skills/discover-debug-log-schema--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 rajbos/ai-engineering-fluency --skill discover-debug-log-schema -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rajbos/ai-engineering-fluency discover-debug-log-schema --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/discover-debug-log-schema .gemini/skills/discover-debug-log-schema && 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 "discover-debug-log-schema" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/discover-debug-log-schema into .gemini/skills/discover-debug-log-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-debug-log-schema", 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 rajbos/ai-engineering-fluency discover-debug-log-schemaInstalls 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 rajbos/ai-engineering-fluency --skill discover-debug-log-schema -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/discover-debug-log-schema .github/skills/discover-debug-log-schema && 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 "discover-debug-log-schema" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/discover-debug-log-schema into .github/skills/discover-debug-log-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-debug-log-schema", 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 rajbos/ai-engineering-fluency --skill discover-debug-log-schema -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rajbos/ai-engineering-fluency discover-debug-log-schema --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/discover-debug-log-schema .opencode/skills/discover-debug-log-schema && 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 "discover-debug-log-schema" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/discover-debug-log-schema into .opencode/skills/discover-debug-log-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-debug-log-schema", 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
discover-debug-log-schema- GitHub stars
- 116
- Token cost
- ~1.3k tokens
- SKILL.md length
- 561 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Enumerate the real schema of VS Code Copilot Chat's debug logs (workspaceStorage//GitHub.copilot-chat/debug-logs//main.jsonl) from files on the current machine — every event type and field, flagged…
- Works in 2 steps: Is the billing contract intact? Are the… → What are we leaving on the table? Every…
- Development work in your project
- SKILL.md covers What it answers, Usage, Where it looks and Privacy, plus 2 more sections
- Calls node
What it does
Discover Debug Log Schema is an agent skill from rajbos/ai-engineering-fluency. Enumerate the real schema of VS Code Copilot Chat's debug logs (workspaceStorage//GitHub.copilot-chat/debug-logs//main.jsonl) from files on the current machine — every event type and field, flagged by whether this repo reads it — and verify the exact-AIU billing contract the extension depends on is still intact. Use after a Copilot Chat update, when exact costs look wrong or have silently become estimates, or to find event types and fields we could start using.
Its SKILL.md is about 1.3k 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 Development. It works with Visual Studio Code. The repository describes itself as: Extension that shows information about the estimated token usage and more of AI in editors/CLI's. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/discover-debug-log-schema”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Is the billing contract intact? Are the five llm_request attrs that
- What are we leaving on the table? Every event type and field path in the log,
What it can do on your machine
Read from SKILL.md and the folder at commit 64b51e6. 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:
node
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
Discover Debug Log Schema loads about 1.3k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 561 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 rajbos/ai-engineering-fluency at commit 64b51e6, republished under its MIT licence (© rajbos). 561 words, ~1,261 tokens.
Download SKILL.mdSave it as
.claude/skills/discover-debug-log-schema/SKILL.md (or your agent's skills folder).- name
- discover-debug-log-schema
- description
- Enumerate the real schema of VS Code Copilot Chat's debug logs (workspaceStorage/*/GitHub.copilot-chat/debug-logs/*/main.jsonl) from files on the current machine — every event type and field, flagged by whether this repo reads it — and verify the exact-AIU billing contract the extension depends on is still intact. Use after a Copilot Chat update, when exact costs look wrong or have silently become estimates, or to find event types and fields we could start using.
Discover Debug Log Schema Skill
Reads VS Code Copilot Chat's debug logs on this machine and reports what is actually in them.
The extension reads copilotUsageNanoAiu out of these logs to bill VS Code Chat
sessions exactly rather than estimating — see
docs/logFilesSchema/vscode-chat-debug-log-format.md.
That format is undocumented by Microsoft, we parse exactly one of its event types,
and validate-session-schemas does not cover it. This skill closes that gap.
What it answers
- Is the billing contract intact? Are the five
llm_requestattrs that_eatdlProcessLlmRequest()insrc/tokenEstimation.tsdepends on (inputTokens,outputTokens,cachedTokens,model,copilotUsageNanoAiu) still present? This matters because a rename fails silently: the parser still returns a result,copilotNanoAiubecomes0, and every affected session quietly falls back to estimated pricing. No test fails, no error surfaces. - What are we leaving on the table? Every event type and field path in the log,
marked
PARSED/IGNOREDper type and*per field for what the repo reads today. We consumellm_requestonly;request_startandrequest_endare known to exist and are parsed by nothing. If those carry timings, per-call latency would be available with no user configuration — nobody has checked.
Usage
Run from the repository root. Dependency-free Node, no build step:
# Default: last 30 days, 10 most-recent logs
node .github/skills/discover-debug-log-schema/discover-debug-log-schema.js
# Every log regardless of age, more files
node .github/skills/discover-debug-log-schema/discover-debug-log-schema.js --days 0 --max 50
# Machine-readable
node .github/skills/discover-debug-log-schema/discover-debug-log-schema.js --jsonOptions
| Flag | Meaning |
|---|---|
--days N | Only files modified within the last N days (default 30; 0 = no limit) |
--max N | Analyze at most N most-recent log files (default 10) |
--include-examples | Include truncated example values — may contain prompts and file paths |
--json | Emit JSON only |
--help | Usage |
Exit codes
0— billing contract intact, or no debug logs found on this machine1—DRIFT: a field the parser depends on is missing from observed records2— bad arguments
NOT_OBSERVED (no llm_request events in the sampled files) is not drift — it
means the window caught no LLM calls. Widen it with --days 0 before concluding
anything.
Show full SKILL.md (259 more words)Show less
Where it looks
<vscode-user>/workspaceStorage/<hash>/<ext-folder>/debug-logs/<sessionId>/main.jsonlacross every VS Code variant the extension supports (Code, Insiders, Exploration,
VSCodium, Cursor, and the .vscode-server* remote roots) and all four extension-folder
spellings (GitHub.copilot-chat, github.copilot-chat, GitHub.copilot,
github.copilot) — mirroring readTokensFromDebugLog() in
vscode-extension/src/extension.ts.
No logs found means Copilot Chat has not written any on this machine, not that
the format changed. The script exits 0 in that case so it is safe in CI, where a
runner has no local sessions.
Privacy
Field values are never printed by default — only paths, JSON types and counts.
These logs contain prompts, responses and absolute file paths. Use
--include-examples only on your own machine, and never paste that output into an
issue or PR without reading it first.
Acting on results
- DRIFT → exact billing is broken right now. Open a real log, find what the field
was renamed to, and fix
_eatdlProcessLlmRequest()insrc/tokenEstimation.tsplus theCONSUMEDmap in this skill's script. Update the format doc. - New event types or fields → check them against the format doc. Anything useful (timings, tool durations, edit outcomes) is a candidate for a real feature, and needs no user configuration because this log is always written.
- Either way → fold what you learn into
docs/logFilesSchema/vscode-chat-debug-log-format.md. That page exists because this path was undocumented once already and caused a wrong conclusion.
Keeping it honest
The CONSUMED map at the top of the script is the list of fields the repo actually
reads. If you change what _eatdlProcessLlmRequest() parses, change that map in the
same PR — otherwise this skill reports a contract that no longer matches the code.
© rajbos, 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/discover-debug-log-schema of rajbos/ai-engineering-fluency.
Open the folder on GitHubat commit 64b51e6
Compare with similar skills
Discover Debug Log Schema 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 |
|---|---|---|---|---|---|---|
| Discover Debug Log Schema this skillrajbos/ai-engineering-fluency | 116 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Workthreadsspecstoryai/getspecstory | 1.3k | — | ~1.3k | Automated safety check: Notes | Apache-2.0 | |
| Excalidraw Diagram Studiotech-leads-club/agent-skills | 7k | — | ~3.6k | Automated safety check: Pass | CC-BY-4.0 | |
| Git Worktree Managermicrosoft/WindowsAppSDK | 4.7k | — | ~2k | Automated safety check: Pass | MIT | |
| Roo Conflict Resolutionzgsm-ai/costrict | 4.4k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Interactive Extension TestingPowerShell/vscode-powershell | 1.9k | — | ~824 | Automated safety check: Pass | MIT |
Similar skills
Excalidraw Diagram Studio
tech-leads-club/agent-skills
Generates Excalidraw diagram files from plain descriptions, choosing among flowcharts, mind maps, architecture, swimlane, class, sequence and ER diagrams.
- Official
Git Worktree Manager
microsoft/WindowsAppSDK
Creates and manages Git worktrees with PowerShell scripts so separate issues and Copilot sessions each get an isolated branch, build and test environment.
Roo Conflict Resolution
zgsm-ai/costrict
Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context.
Interactive Extension Testing
PowerShell/vscode-powershell
Guide for setting up the multi-root PowerShell VS Code extension/PSES dev workspace.
Release
PowerShell/vscode-powershell
Guide for preparing a release of the PowerShell VS Code extension.
More from rajbos/ai-engineering-fluency
All 21 skills in this repoCheck Urls
rajbos/ai-engineering-fluency
Find all hardcoded URLs in TypeScript source files and verify they resolve (return HTTP 2xx/3xx).
Create Issue
rajbos/ai-engineering-fluency
Create a well-scoped GitHub issue in this repo. An agent skill from rajbos/ai-engineering-fluency.
Deduplicate Code
rajbos/ai-engineering-fluency
Detect copy-pasted code blocks across the shared source (vscode-extension/src, the repo-root src/, cli/src) with the dependency-free check-code-duplication.js detector, then pick one duplicate group…
Improve Tool Families
rajbos/ai-engineering-fluency
Analyze coverage of the vscode-extension's tool-family definitions (DEFAULTTOOLFAMILIES in vscode-extension/src/toolFamilies.ts) against the canonical tool-name list in src/toolNames.json and/or a…
Load Cache Data
rajbos/ai-engineering-fluency
Load and display the last 10 cache entries as raw JSON output.
PR Risk Review
rajbos/ai-engineering-fluency
Assess the risk of a changeset (a PR, a branch, or the working tree) and classify it as low, medium, or high with a written rationale.
Related
Works with
Categories
Questions about Discover Debug Log Schema
What does Discover Debug Log Schema do?
Enumerate the real schema of VS Code Copilot Chat's debug logs (workspaceStorage//GitHub.copilot-chat/debug-logs//main.jsonl) from files on the current machine — every event type and field, flagged…. Discover Debug Log Schema is an agent skill from rajbos/ai-engineering-fluency.jsonl) from files on the current machine — every event type and field, flagged by whether this repo reads it — and verify the exact-AIU billing contract the extension depends on is still intact.
When should I use Discover Debug Log Schema?
Discover Debug Log Schema fits situations like: development work in your project.
How do I install Discover Debug Log Schema in Claude Code?
Run `npx skills add rajbos/ai-engineering-fluency --skill discover-debug-log-schema -a claude-code`. Or copy the skill folder (.claude/skills/discover-debug-log-schema in rajbos/ai-engineering-fluency) into .claude/skills/discover-debug-log-schema in your project. Claude Code loads it when a task matches its description.
How do I install Discover Debug Log Schema in Codex?
Run `npx skills add rajbos/ai-engineering-fluency --skill discover-debug-log-schema -a codex`. Or copy the skill folder (.claude/skills/discover-debug-log-schema in rajbos/ai-engineering-fluency) into .agents/skills/discover-debug-log-schema in your project. Codex loads it when a task matches its description.
Can I use Discover Debug Log Schema 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 rajbos/ai-engineering-fluency --skill discover-debug-log-schema -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/discover-debug-log-schema, .gemini/skills/discover-debug-log-schema, .github/skills/discover-debug-log-schema and .opencode/skills/discover-debug-log-schema in your project.
What does Discover Debug Log Schema need to run?
Going by SKILL.md and its folder, Discover Debug Log Schema needs the command-line tools its instructions call (node).
Does Discover Debug Log Schema 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 Discover Debug Log Schema 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 Discover Debug Log Schema use?
Discover Debug Log Schema 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 Discover Debug Log Schema use?
About 1.3k tokens (SKILL.md is roughly 5k 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 Discover Debug Log Schema?
Skills that share tags, products or a category with Discover Debug Log Schema: Workthreads (specstoryai/getspecstory, 1.3k stars), Excalidraw Diagram Studio (tech-leads-club/agent-skills, 7k stars), Git Worktree Manager (microsoft/WindowsAppSDK, 4.7k stars) and Roo Conflict Resolution (zgsm-ai/costrict, 4.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Discover Debug Log Schema?
rajbos (a GitHub user) maintains it in rajbos/ai-engineering-fluency, which has 116 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.
Source: rajbos/ai-engineering-fluency on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.