insta-snapshots

Guide for working with and updating insta snapshot tests in Oxc without terminal interaction.

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/insta-snapshots/SKILL.md

Quality

Content

67%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 delivers actionable, executable commands in a clearly sequenced workflow with verification steps, well-organized into sections. Its main weaknesses are redundancy (the same workflow appears three times) and a small amount of background explanation Claude does not need.

Suggestions

Consolidate the workflow into one canonical sequence and drop the duplicate 'Common Workflows' and 'Example: Complete Workflow' sections to reduce repetition.

Trim or remove the 'What are Insta Snapshots?' preamble, keeping only the Oxc-specific snapshot directory locations Claude would not know.

Add an explicit feedback loop for incorrect snapshots (e.g. if a .snap.new output is wrong, fix the source code and re-run cargo test before accepting) to push workflow clarity higher.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the workflow is repeated three times (Reviewing Snapshots, Common Workflows, Example) and the "What are Insta Snapshots?" section explains a library Claude already knows, fitting the 3 anchor of mostly-efficient with some unnecessary content.	3 / 5
Actionability	Provides concrete executable commands (cargo test -p, cargo insta pending-snapshots/accept/reject, git diff) covering common cases, with only minor gaps such as the likely-nonexistent 'accept --snapshot' flag, matching the 4 anchor of mostly-executable guidance.	4 / 5
Workflow Clarity	Clear sequenced workflow (run tests, list pending, read, accept/reject, verify with git, re-run tests) with verification checkpoints and a manual-review warning; not a 5 because there is no explicit error-recovery feedback loop for incorrect snapshots.	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and no need for external references (no bundle files present); the overlapping repeated workflow sections are a minor organization gap keeping it at 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

53%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 clearly identifies a specific niche (insta snapshot tests in Oxc, non-interactive) but lacks an explicit "Use when..." trigger clause and comprehensive keyword/variation coverage. It is specific enough to avoid most conflicts but is capped on completeness by the missing trigger guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when tests fail due to snapshot mismatches or after changing code that affects insta snapshot outputs in Oxc.'

Include natural synonyms and file extensions users might say (snapshots, .snap, .snap.new, pending snapshots) to improve trigger term coverage.

Replace the generic 'working with' with concrete actions like 'review, accept, and reject pending snapshot files' to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("insta snapshot tests in Oxc") and two actions ("working with" and "updating"), but "working with" is generic and coverage is not comprehensive, fitting the 3 anchor rather than the multi-action 4.	3 / 5
Completeness	Has a clear "what" (guide for working with/updating insta snapshot tests) but no "Use when..." trigger clause; per the rubric guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant natural keywords ("insta snapshot tests", "Oxc", "terminal interaction") but omits common variations/synonyms and file extensions (.snap, .snap.new), matching the 3 anchor of partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The Oxc + insta niche is specific and "without terminal interaction" distinguishes it from a generic insta skill, giving minor overlap risk (4); not a 5 because it lacks explicit distinct trigger phrases.	4 / 5
	Total	13 / 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: oxc-project/oxc
Path: .agents/skills/insta-snapshots/SKILL.md
Commit: 1aa5ec1

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