CtrlK
BlogDocsLog inGet started
Tessl Logo

copilot-history-ingest

Ingest GitHub Copilot CLI session history into an Obsidian wiki as distilled knowledge pages. Use this skill when the user wants to capture their Copilot CLI sessions into a personal wiki — extracting architecture decisions, debug notes, and patterns into searchable Obsidian pages. Triggers on phrases like "ingest my copilot sessions into obsidian", "add my copilot history to my wiki", "pull my copilot session history into the vault", "capture what I've learned from copilot into obsidian", "just the new sessions since last time", or "mine patterns across my copilot sessions". Also triggers when the user mentions session-store.db, ~/.copilot/session-state, or VS Code copilot-chat transcripts in the context of building a wiki or knowledge base. Does NOT trigger for general copilot usage questions, searching sessions, or backing up history.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with executable SQL/bash/python, a clear multi-step workflow with idempotency and QMD feedback loops, and clean one-level-deep reference splitting. Slight conciseness and explicit-vault-write-validation gains keep it from a perfect score.

Suggestions

Consolidate the 'Key data sources ranked by value' list with the three Source sections to remove overlap and tighten token use.

Add an explicit validate-then-proceed checkpoint after Step 5 (e.g., verify each new/updated page renders and its summary frontmatter is present) before updating the manifest in Step 6.

Tighten the Step 1 survey comments — several inline comments repeat info already given in the GitHub Copilot Data Layout section.

DimensionReasoningScore

Conciseness

Largely lean — directory trees, SQL, and tables assume Claude's competence with little concept padding — though the ranked-by-value list and data-layout section carry some redundancy that could be tightened.

4 / 5

Actionability

Fully executable guidance: concrete SQL queries with schemas, bash scan snippets, a python base64 decoder, and a precise what-goes-where mapping table; placeholder paths are appropriately parameterized rather than pseudocode.

5 / 5

Workflow Clarity

Clear Step 1–6 sequence with idempotency (manifest delta check), append/full modes, and explicit QMD-refresh verification feedback loop; vault-write validation is largely implicit via the manifest rather than an explicit validate-then-proceed checkpoint, keeping it just below a 5.

4 / 5

Progressive Disclosure

Body acts as an overview with a single clearly-signaled one-level-deep reference to the real file references/copilot-data-format.md (cited inline and in a Reference section); detailed data format is correctly deferred.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capabilities, comprehensive natural trigger phrases, explicit when-to-use guidance, and clear negative triggers to avoid mis-invocation. Third person throughout, no fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'extracting architecture decisions, debug notes, and patterns into searchable Obsidian pages' across three named data sources — giving comprehensive coverage rather than generic phrasing.

5 / 5

Completeness

Explicitly answers both 'what' (ingest Copilot CLI history into an Obsidian wiki as distilled pages) and 'when' ('Use this skill when...') with concrete trigger phrases and explicit negative triggers.

5 / 5

Trigger Term Quality

Six natural trigger phrases ('ingest my copilot sessions into obsidian', 'add my copilot history to my wiki', 'just the new sessions since last time', etc.) plus technical synonyms (session-store.db, ~/.copilot/session-state, copilot-chat transcripts) cover how users actually ask.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Copilot CLI → Obsidian) with distinct triggers and an explicit 'Does NOT trigger for...' exclusion list, minimizing overlap with adjacent skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Ar9av/obsidian-wiki
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.