import-plans

Bulk import existing Claude Code plan files from ~/.claude/plans/ into the Obsidian vault. Triggers: "import plans", "bulk import plans", "sync old plans", "bring in my plans", "migrate plans", "copy plans to vault", "load plans into obsidian".

Quality

88%

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

87%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 content is concise and highly actionable with a clear single-command workflow and concrete output/error handling. The main gap is the absence of a post-import verification step for this batch operation, which caps workflow clarity.

Suggestions

Add a verification step after the import runs (e.g., spot-check that a few imported plan files exist at Notes/plan/<slug>.md in the vault and that the imported count matches files in ~/.claude/plans/) to satisfy the batch-operation validation requirement.

Make the pre-flight check in step 1 an explicit validation checkpoint with a stop condition (e.g., 'If $CLAUDE_PLUGIN_OPTION_VAULT_PATH is empty, stop and instruct the user to configure vault_path before proceeding').

Clarify how to interpret a non-zero 'Skipped (no title)' count, since the current step 3 only defines the duplicate-skip remedy.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a numbered workflow, one executable command, and a tight 'What the Script Does' list with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Provides a copy-paste-ready command (node "${CLAUDE_SKILL_DIR}/../../scripts/bulk-import-plans.js"), specifies the exact output line format to parse, and gives concrete handling for duplicate-skip and error cases.	5 / 5
Workflow Clarity	Steps are clearly sequenced with a pre-flight config check (step 1) and error reporting (step 5), but this is a batch operation with no post-run verification that files landed correctly in the vault, so the batch-operation cap of 3 applies.	3 / 5
Progressive Disclosure	Under 50 lines, single-purpose, self-contained, and well-organized into 'Workflow' and 'What the Script Does' sections with no need for external reference files, meeting the simple-skill exception for a 5.	5 / 5
	Total	18 / 20 Passed

Description

90%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 concrete action with specific source/destination, uses third person, and provides a comprehensive set of natural trigger phrases that clearly answer both what and when. Its only limitation is that it describes a single action rather than enumerating multiple capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and a single concrete action ("Bulk import existing Claude Code plan files from ~/.claude/plans/ into the Obsidian vault") with specific source and destination, but lists only one action rather than several, so it does not reach the 'several specific actions' bar of 4.	3 / 5
Completeness	Explicitly states what the skill does (bulk import plan files from ~/.claude/plans/ into the Obsidian vault) and when to use it via a dedicated "Triggers:" clause with concrete phrases, satisfying both what and when.	5 / 5
Trigger Term Quality	Includes seven natural trigger phrases ("import plans", "bulk import plans", "sync old plans", "bring in my plans", "migrate plans", "copy plans to vault", "load plans into obsidian") covering synonyms and variations a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Claude Code plans → Obsidian vault) with distinct, specific triggers, making overlap with other skills minimal.	5 / 5
	Total	18 / 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: seanGSISG/claude-depot
Path: plugins/vault-tools/skills/import-plans/SKILL.md
Commit: 48bf6a4

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