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

92%

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

88%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, highly actionable skill body with clear multi-step workflows, strong validation checkpoints for destructive/immutable operations, and a real one-level-deep reference. It is slightly long and keeps several large templates inline that could be factored into references.

Suggestions

Move the large correction-mode YAML template and/or the four body-type templates into a reference file (e.g. references/NOTE-TEMPLATES.md) and link to them, tightening the SKILL.md overview and improving progressive disclosure.

Trim framing prose like "The goal is to extract the substance — the knowledge itself — not a summary of what was said" and reduce repeated trigger-phrase lists between the modes to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and task-relevant with direct instructions and templates rather than padded concept explanations, though the three-mode structure introduces some repetition and a few framing sentences (e.g., "The goal is to extract the substance...") that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready frontmatter templates, per-type body structures, concrete file-path conventions, kebab-case slug rules, and executable QMD commands (`qmd update`, `qmd embed`, `qmd ls`, `qmd get`) covering the common cases.	5 / 5
Workflow Clarity	Multi-step processes are clearly sequenced (Quick mode steps 1–7, Full mode Steps 1–7) with explicit validation checkpoints — the KEEP/SKIP gate, the correction-mode SHA256 pre/post verification with abort-on-mismatch, and a closing Quality Checklist — plus feedback loops for error recovery.	5 / 5
Progressive Disclosure	Good structure with clearly signaled one-level-deep references ("Read references/RAW-FORMAT.md for the full frontmatter spec" — a real file), but the bulk of content (correction YAML template, four body-type templates) is inlined in SKILL.md and could arguably be split out, leaving minor organization gaps.	4 / 5
	Total	18 / 20 Passed

Description

96%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, third-person description that concretely states capabilities, exhaustively lists natural trigger phrases, and explicitly answers both what and when. Its only weakness is that the bare trigger "save this" is somewhat generic, risking minor overlap with adjacent wiki skills.

Suggestions

Tighten the generic "save this" trigger (e.g., "save this to my wiki") to reduce overlap with unrelated save intents and sibling skills like /wiki-ingest.

Consider trimming length slightly — the quick-mode trigger list duplicates phrases already implied by naming the mode, and verbosity risks diluting the core trigger signal.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across modes — "classifies the content, rewrites it as declarative knowledge (not a chat transcript), and places it in the correct vault category", "drops findings to the `_raw/` staging area in under 60 seconds", and "Accepts inline named-vault routing like @research save this" — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both what ("Save the current conversation as a permanent, structured wiki note") and when ("Use this skill when the user says...") with concrete trigger phrases, matching the 5-anchor example closely.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural trigger phrases including synonyms and the slash command: "save this", "/wiki-capture", "capture this", "file this conversation", "preserve this", "add this to my wiki", plus quick-mode variants like "save this bug fix", "drop this to raw", "quick save to wiki".	5 / 5
Distinctiveness Conflict Risk	The wiki-capture niche is clear and mostly distinct, but the generic trigger "save this" and proximity to sibling skills like `/wiki-ingest` create minor overlap risk, so it sits below the 5 anchor rather than at it.	4 / 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: 52c9f2b

Reviewed: about 23 hours 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.