Name: arn-code-save-plan
Rating: 66.4 (1 reviews)
Author: AppsVortex

arn-code-save-plan

This skill should be used when the user says "save plan", "save the plan", "arness code save plan", "structure this plan", "create project from plan", "export plan", "export project plan", "organize this plan", "set up project structure", "turn this into a project", "generate project structure", "finalize the plan", or wants to convert a planning conversation into an actionable phased project structure with implementation and testing plans.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/arn-code/skills/arn-code-save-plan/SKILL.md

Quality

Content

70%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, clearly sequenced workflow with strong validation checkpoints and clean progressive disclosure into real reference files. Its main weaknesses are conciseness and actionability: several sections are verbose, and much of the guidance is procedural prose leaning on Claude's judgment rather than concrete inline examples.

Suggestions

Tighten the verbose prose in the legacy-migration offer and the Step 3 sketch-artifact fallback into compact bullet logic, or move the full detail into the reference files alongside template-versioning.md.

For Step 4 phase-plan generation, add a small concrete example of the expected Implementation/Testing section structure (or link directly to the relevant section of templates.md) so the guidance is copy-paste-ready rather than purely descriptive.

Replace 'Use Claude's intelligence to interpret' / 'intelligently split it into phases' phrasing with a short explicit heuristic list, reducing reliance on judgment where a concrete rule would do.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but the legacy-migration dialog, sketch-artifact fallback logic, and template-versioning prose are verbose and could be tightened into shorter bullet logic or offloaded to the reference files.	2 / 3
Actionability	It supplies one executable bash command and concrete file paths, JSON field names, and a source-mapping table, but most guidance is procedural prose with deliberate reliance on Claude's interpretive judgment ('Use Claude's intelligence to interpret...', 'intelligently split it into phases') rather than copy-paste-ready examples throughout.	2 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced with explicit validation checkpoints (validate paths exist on disk; 'Do not proceed to Step 3 until the project structure is successfully created'; Step 6 verification checklist) and feedback loops for error recovery.	3 / 3
Progressive Disclosure	SKILL.md acts as a workflow overview with well-signaled, one-level-deep references to real bundle files (references/templates.md, references/template-versioning.md, scripts/save_plan.sh), with detailed template and versioning content appropriately split out rather than inlined.	3 / 3
	Total	10 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 excels at trigger-term coverage, completeness, and distinctiveness, with explicit natural-language triggers and a clear what/when structure. Its only weakness is specificity, since it describes one core action with elaboration rather than a list of multiple distinct concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete outputs ('convert a planning conversation into an actionable phased project structure with implementation and testing plans') but is fundamentally a single action rather than a list of multiple distinct concrete actions, so it sits at the 2 anchor rather than 3.	2 / 3
Completeness	Clearly answers both what ('convert a planning conversation into an actionable phased project structure...') and when ('This skill should be used when the user says...') with explicit triggers, in third-person voice.	3 / 3
Trigger Term Quality	Explicitly enumerates a broad set of natural phrases users would actually say ('save plan', 'structure this plan', 'turn this into a project', 'generate project structure', 'finalize the plan'), giving strong coverage of trigger variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (planning conversation to phased project structure) with highly specific triggers ('arness code save plan', 'create project from plan') unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AppsVortex/arness
Path: plugins/arn-code/skills/arn-code-save-plan/SKILL.md
Commit: 7f87870

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