Name: arn-spark-prototype-lock
Rating: 71.2 (1 reviews)
Author: AppsVortex

arn-spark-prototype-lock

This skill should be used when the user says "prototype lock", "lock prototype", "arn prototype lock", "freeze prototype", "preserve prototype", "snapshot prototype", "protect prototype", "archive prototype", "save the prototype", "don't overwrite the prototype", "lock the design", "freeze the design", or wants to create a frozen snapshot of the validated prototype before development begins, preventing production code from overwriting the validated reference artifact.

Quality

87%

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

85%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 body is a well-structured, highly actionable nine-step workflow with explicit validation feedback loops and clean progressive disclosure into verified reference templates. Its single weakness is conciseness — the quoted dialog templates and stack table add bulk that could be trimmed.

Suggestions

Tighten the quoted user-facing dialog blocks (e.g. the Step 1 inventory and Step 2 plan prompts) to essential fields, or move the full templates into a reference file like the other bulky content.

Consider compressing the framework stack table to the non-obvious differences (excluded build dirs) since Claude already knows standard framework layouts.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence (no tutorials on what git, prototypes, or build tools are) and is mostly instructional, but it carries bulk that could be tightened — lengthy quoted user-facing dialog templates and a full stack-detection table. Not 3 because it is not lean (not every token earns its place); not 1 because there is no concept-explanation filler.	2 / 3
Actionability	Concrete, executable commands throughout — `cp -r` with exclusions, `cd [dest] && [pm] install && [pm] run build`, `git tag -a prototype-lock-[date] -m "..."`, `chmod +x .claude/hooks/prototype-lock-guard.sh` — plus explicit template file paths to read. Placeholders are clearly defined variables, not pseudocode.	3 / 3
Workflow Clarity	Nine numbered, well-sequenced steps with an explicit validate→fix→retry feedback loop in Step 4 ("After 3 failures" escalation) and an uncommitted-changes checkpoint in Step 6. Matches the top anchor for clear sequence with explicit validation and error-recovery loops.	3 / 3
Progressive Disclosure	Bulky material is split into three real, one-level-deep reference templates (lock-report-template.md, prototype-guardrail-rules.md, pretooluse-hook-template.json — all present in references/) that are clearly signaled via `Read ${CLAUDE_PLUGIN_ROOT}/...`. The SKILL.md stays an overview pointing to them.	3 / 3
	Total	11 / 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 is trigger-rich and clearly answers both what and when in third person, with strong natural-language triggers and a distinct niche. Its only weakness is that the capability description is thinner than its trigger list, so specificity is good rather than comprehensive.

Dimension	Reasoning	Score
Specificity	Names the prototype-lock domain and concrete actions ("create a frozen snapshot", "preventing production code from overwriting the validated reference artifact"), but the field is dominated by trigger phrases rather than a comprehensive list of specific actions. Not 3 because it does not enumerate multiple distinct concrete actions; not 1 because the actions stated are concrete rather than vague.	2 / 3
Completeness	Explicitly answers both "what" (create a frozen snapshot before development, prevent production code overwriting the validated reference) and "when" (a long explicit "when the user says... or wants to..." trigger clause). Uses third person ("This skill should be used"), so no voice penalty.	3 / 3
Trigger Term Quality	Extensive coverage of natural phrases users would actually say ("prototype lock", "lock prototype", "freeze prototype", "preserve prototype", "snapshot prototype", "lock the design"). Matches the top anchor for good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	A clear niche (arn prototype locking) with highly specific triggers like "arn prototype lock" and "freeze prototype" that are unlikely to fire for unrelated skills. Matches the distinct-triggers top anchor.	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-spark/skills/arn-spark-prototype-lock/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.