save

Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation, save this analysis, keep this insight, preserve this chat result.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The body is a tight, actionable, well-sequenced save workflow with strong validation and error-recovery checkpoints appropriate to destructive vault writes. The main gaps are a placeholder PRODUCT_ROOT path and references pointing outside the present bundle with no bundle files to validate them.

Suggestions

Provide an executable snippet for resolving PRODUCT_ROOT from the skill's own location instead of a placeholder assignment, so the first code block is fully runnable.

Ship the referenced files (provenance.md, operation-transactions.md) under references/ or document where they live so the one-level-deep references can be verified against the bundle.

Consider a short explicit validation step label (e.g. '**Validate**: inspect the bundle') in the Preview and apply section to mirror the workflow's own checkpoint emphasis.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: it assumes Claude's competence, never explains Obsidian or vault concepts, and every guardrail sentence ('Never run automatically...', 'This skill needs no network egress') carries operational weight.	5 / 5
Actionability	Provides two complete, mostly copy-paste-ready bash blocks (transaction inspect/apply, checkpoint) with concrete flags, but PRODUCT_ROOT is a placeholder path whose resolution is described in prose rather than given as an executable command.	4 / 5
Workflow Clarity	Clear sequence (Prepare -> Preserve evidence -> Build transaction -> Preview and apply) with explicit validation (inspect before apply, SHA-256 preconditions) and feedback loops (exit 75 -> re-read/rebuild/inspect, transaction recover for interrupted apply) for this destructive vault mutation.	5 / 5
Progressive Disclosure	Well-sectioned overview with clearly signaled one-level-deep references (provenance.md, operation-transactions.md, page_schema.py), but no bundle files exist under references/scripts/assets to verify those paths, so the split cannot be fully confirmed against the actual bundle.	4 / 5
	Total	18 / 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.

The description is strong: it states a precise scope, gives a clear use-when clause with an exclusion, and lists natural trigger phrases. Its only minor weakness is that the capability is fundamentally one action (save) applied to several content types rather than several distinct operations.

Dimension	Reasoning	Score
Specificity	Names the Obsidian-vault domain and a concrete action ('Save ... as one reviewed transaction') across multiple specific content types (answer, decision, insight, session summary), but the underlying verb is essentially a single save action rather than multiple distinct operations.	4 / 5
Completeness	Explicitly answers both what (save selected content into an Obsidian vault as a reviewed transaction) and when ('Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrasing with synonyms and a slash command: '/save, save this, save that answer, file this conversation, save this analysis, keep this insight, preserve this chat result'.	5 / 5
Distinctiveness Conflict Risk	Clear Obsidian-vault-save niche with an explicit exclusion ('not when they supply a file or URL to ingest') and distinct triggers, minimizing overlap with ingest or research skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-obsidian
Path: skills/save/SKILL.md
Commit: 32ac5a0

Reviewed: 7 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.