wiki-capture

Save the current conversation as a permanent, structured wiki note. Use this skill when the user says "save this", "/wiki-capture", "capture this", "file this conversation", "preserve this", "add this to my wiki", or wants to turn what was just discussed into lasting knowledge. The skill classifies the content, rewrites it as declarative knowledge (not a chat transcript), and places it in the correct vault category. Also supports a fast QUICK MODE (`/wiki-capture --quick`, "quick capture", "capture this finding", "save this bug fix", "save this gotcha", "drop this to raw", "quick save to wiki") that drops findings to the `_raw/` staging area in under 60 seconds with no manifest or index writes — used by the session-end Stop hook to auto-preserve findings. Accepts inline named-vault routing like "@research save this" via the shared Config Resolution Protocol.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

The body is a well-organized, three-mode skill with explicit validation checkpoints, real code/template blocks, and a genuine one-level-deep reference file. Its chief weaknesses are mild repetition of provenance guidance that already lives in RAW-FORMAT.md and a few template placeholders that keep some guidance abstract.

Suggestions

Defer the per-cluster provenance/confidence calibration detail in Quick Mode step 6 entirely to references/RAW-FORMAT.md instead of restating it inline, reducing duplication.

Replace remaining abstract placeholders in the correction-mode template with one fully-worked example so the atomic-claim structure is unambiguous.

Trim the KEEP/SKIP gate criteria in Quick Mode step 2 into a tighter checklist; the current prose restates overlapping conditions.

Dimension	Reasoning	Score
Conciseness	Largely efficient and free of explaining concepts Claude already knows, with minor over-explanation in the KEEP/SKIP gate criteria and provenance guidance that could be tightened slightly.	4 / 5
Actionability	Provides concrete frontmatter templates, exact target paths, log/index/hot update formats, and real bash commands, with minor gaps such as template placeholders left for the model to fill.	4 / 5
Workflow Clarity	All three modes are explicitly sequenced with validation checkpoints (SHA-256 pre/post immutability check in correction mode, the KEEP/SKIP gate in quick mode, the quality checklist, and QMD skip-on-empty guard), satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	Body is well-structured into mode-specific sections and pushes the full raw-format spec to a real one-level-deep reference (references/RAW-FORMAT.md), though it repeats some provenance/confidence guidance inline rather than deferring entirely to the reference.	4 / 5
	Total	17 / 20 Passed

Description

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

The description is strong: it explicitly states what the skill does, gives concrete actions, and lists abundant natural trigger phrases for both full and quick modes. Its only minor weakness is mild density from listing many quick-mode triggers, but this does not pad with fluff.

Dimension	Reasoning	Score
Specificity	Names several concrete actions (classifies content, rewrites as declarative knowledge, places in vault category, drops findings to _raw/) across two modes, with minor gaps in enumerating full-mode steps.	4 / 5
Completeness	Explicitly answers both what (save conversation as a structured wiki note, classify, rewrite declaratively, place in category) and when (named trigger phrases, /wiki-capture invocation, and automatic Stop-hook usage).	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including synonyms and variants ('save this', 'capture this', 'file this conversation', 'preserve this', 'add this to my wiki', 'capture this finding', 'save this bug fix', 'drop this to raw') plus the /wiki-capture invocation and @vault routing.	5 / 5
Distinctiveness Conflict Risk	Clear wiki-capture niche with distinctive trigger vocabulary ('add this to my wiki', 'file this conversation', 'drop this to raw') and explicit routing that separates it from generic note or file skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: .skills/wiki-capture/SKILL.md
Commit: 58aba18

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.