CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-agent

Query-driven targeted ingest from a specific AI agent's raw history. Use this skill when the user invokes /wiki-claude, /wiki-codex, /wiki-hermes, /wiki-openclaw, /wiki-copilot, /wiki-pi — with or without a search topic. Different from wiki-history-ingest (which bulk-ingests everything new): this skill finds sessions about a SPECIFIC TOPIC in a specific agent's history and ingests just those, then returns a synthesized answer immediately usable in the current session. Primary use case: you're working in agent A and want to pull in how you solved X in agent B's history. Cross-referencing, not archiving. Also trigger on: "what did I work on in codex about X", "search my claude sessions for Y", "pull in hermes knowledge about Z", "find that conversation where I did X in codex".

71

Quality

86%

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

78%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 highly actionable, well-sequenced skill body: every step gives executable commands, per-agent specifics, and error paths, with a strong feedback loop around the locked tracking-file update. The main weaknesses are the absence of any bundle references (forcing ~300 lines of per-agent detail inline) and a slightly repetitive use-patterns section, plus no post-write validation before the manifest sync.

Suggestions

Move the per-agent tables from Steps 2 and 4 (history paths, index formats, extraction strategies — ~120 lines) into references/agents.md, keeping only the routing and scoring logic in SKILL.md so the body stays a lean overview.

Trim "Cross-Agent Use Patterns" to the 2–3 genuinely distinct scenarios; the Pi examples duplicate the Claude pattern and the no-query example repeats the routing table's default-mode rule.

Add a validation checkpoint after Step 5 (e.g., re-read each written/updated page and verify its frontmatter and cross-links parse before running the manifest sync) so the batch write loop has an explicit verify step.

DimensionReasoningScore

Conciseness

The body is dense with tables, commands, and an exact scoring formula, and the one justification it gives ("The 0.35 floor is deliberate: an old session that matches the query exactly must still outrank a recent one that barely matches") earns its tokens. Below 5 because "Cross-Agent Use Patterns" repeats the command-routing table (the two Pi examples duplicate the Claude pattern nearly verbatim) and the QMD section repeats `${QMD_CLI:-qmd}` blocks that could be condensed.

4 / 5

Actionability

Everything is executable: per-agent history paths and config overrides, exact index formats with signal fields, `rg -i "<query terms>"` commands with window sizes (10 before + 20 after), a concrete decay formula, the wiki-page frontmatter template, the locked `obsidian-wiki memory sync` command with arguments, and a fill-in output template. Specific commands cover the common cases for every agent.

5 / 5

Workflow Clarity

A clear 7-step sequence with real checkpoints: missing history root → exact user-facing message; no matches → explicit "No sessions about '<query>' found…" response; "Never hand-edit index.md, log.md, or hot.md — the command takes the lock"; and QMD failure handling ("do not roll back the vault changes; report the QMD status separately"). Below 5 because there is no validation of the written/updated wiki pages before the manifest sync — a batch-write operation whose only pre-write guard is the existing-page check.

4 / 5

Progressive Disclosure

No references/, scripts/, or assets/ files exist in the bundle, so everything is inlined in a ~300-line body — notably the per-agent index tables (Step 2) and extraction strategies (Step 4), roughly 120 lines of agent-specific detail that would fit a single references/agents.md. Section structure and headers are clear and external pointers (llm-wiki/SKILL.md, .skills/llm-wiki/references/MEMORY.md) are named, which lifts it above anchor 2's "minimal structure", but the missing split keeps it below anchor 4's "most content is appropriately placed".

3 / 5

Total

16

/

20

Passed

Description

95%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.

A strong description: it states concrete actions, gives explicit trigger conditions in both slash-command and natural-language form, and explicitly draws the boundary against the sibling bulk-ingest skill. Its only deduction is the second-person phrasing in the primary-use-case sentence, which violates the rubric's third-person voice rule.

DimensionReasoningScore

Specificity

Concrete actions — "finds sessions about a SPECIFIC TOPIC", "ingests just those", "returns a synthesized answer immediately usable in the current session" — give comprehensive coverage, matching the anchor-5 example pattern. Reduced by 1 per the rubric's voice penalty for the second-person phrasing "you're working in agent A and want to pull in how you solved X in agent B's history".

4 / 5

Completeness

Both questions answered explicitly: what ("finds sessions… ingests just those, then returns a synthesized answer") and when ("Use this skill when the user invokes /wiki-claude, /wiki-codex, /wiki-hermes, /wiki-openclaw, /wiki-copilot, /wiki-pi — with or without a search topic" plus natural-language triggers). Matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Explicitly enumerates natural user phrases ("what did I work on in codex about X", "search my claude sessions for Y", "pull in hermes knowledge about Z", "find that conversation where I did X in codex") alongside all six slash-command triggers, covering synonyms and variations comprehensively. Not 4 because no common variation is missing; not below 5 since the trigger list is exhaustive for this niche.

5 / 5

Distinctiveness Conflict Risk

Explicitly differentiates from the nearest sibling skill ("Different from wiki-history-ingest (which bulk-ingests everything new): this skill… ingests just those") and frames a distinct niche ("Cross-referencing, not archiving"), with trigger phrases that name specific agents. Clear niche, minimal conflict risk.

5 / 5

Total

19

/

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.

Validation — 16 / 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.