Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ar9av/copilot-history-ingest
Ingest GitHub Copilot CLI session history into an Obsidian wiki as distilled knowledge pages.
Passed 14 of 20 test cases with the skill, and 6 of 20 without it.
and 8 more in the full report
11 fixed7 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/18/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
If the QMD_CLI environment variable is set to /usr/local/bin/custom-qmd, which command binary should be called to refresh the search index?
| Checked | Without skill | With skill |
|---|---|---|
| Executes the binary path specified in QMD_CLI. | Missed | Passed |
The instructions your model reads when the skill loads.
You are extracting knowledge from the user's past GitHub Copilot CLI conversations and distilling it into the Obsidian wiki. Conversations are rich but messy — your job is to find the signal and compile it.
This skill can be invoked directly or via the wiki-history-ingest router (/wiki-history-ingest copilot).
Writing profile: Before drafting or rewriting natural-language Markdown, read and apply the Writing Profile Resolution section in llm-wiki/SKILL.md. Framework schema, provenance, safety, and operation-specific requirements take precedence.
WRITING.md preferences apply only to newly drafted or rewritten natural-language Markdown; preserve source content and structured records.
llm-wiki/SKILL.md (inline @name override → walk up CWD for .env → global config → prompt setup). This gives OBSIDIAN_VAULT_PATH, COPILOT_HISTORY_PATH (defaults to ~/.copilot/session-state), and COPILOT_VSCODE_STORAGE_PATH (VS Code workspaceStorage; platform-specific — ask the user if absent).manifest.json at the vault root to check what's already been ingestedindex.md at the vault root to know what the wiki already containsCheck .manifest.json for each source file (events JSONL, transcript JSONL, checkpoint, session-store DB). Only process:
updated_at is newer than their ingested_at in the manifestThis is usually what you want — the user ran a few new sessions and wants to capture the delta.
Process everything regardless of manifest. Use after a wiki-rebuild or if the user explicitly asks.
Copilot stores data in three locations. Scan all three.
~/.copilot/session-state/ (CLI sessions)~/.copilot/session-state/
├── <session-uuid>/
│ ├── workspace.yaml # Session metadata (id, cwd, summary_count, created_at, updated_at)
test cases passed, vs 6 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.