openspec-ff-change

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

Quality

68%

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 ./.agent/skills/openspec-ff-change/SKILL.md

Quality

Content

75%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.

A strongly actionable, well-sequenced workflow skill: commands are complete and executable, validation checkpoints are present, and structure is easy to navigate. The main weakness is repetition between the Steps and the Artifact Creation Guidelines/Guardrails sections, and the absence of error-recovery guidance.

Suggestions

Consolidate the duplicated context/rules and dependency-reading guidance into one section to trim tokens.

Add a brief error-recovery step for what to do when an openspec command fails or returns unexpected JSON.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (command + purpose, no concept explanations Claude already knows), but the context/rules "do NOT include in output" guidance and the dependency-reading rule are each stated twice (step 4a and again in Artifact Creation Guidelines/Guardrails), which could be tightened into one place.	3 / 5
Actionability	All commands ("openspec new change", "openspec status --change <name> --json", "openspec instructions <artifact-id> --change <name> --json") are copy-paste ready with flags, the returned JSON fields are enumerated, and artifact content is explicitly delegated to the CLI's template — fully executable guidance.	5 / 5
Workflow Clarity	A clear five-step dependency-ordered sequence with validation checkpoints (re-run status after each artifact, check applyRequires completion, "Verify each artifact file exists after writing") and an escalation path for unclear input, but there is no error-recovery loop for command failures, keeping it below the feedback-loop anchor 5.	4 / 5
Progressive Disclosure	A well-organized single-file skill with clear sections (Input, Steps, Output, Guidelines, Guardrails) and no external references needed — no bundle files exist to offload to — but the ~97-line body duplicates guidance across the Steps and Artifact Creation Guidelines sections, a minor organization gap versus the cleanly split anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

62%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.

A concise, distinct description with an explicit 'Use when' clause, but it describes only a single composite action and omits natural trigger terms and synonyms. It is solid but noticeably above-mid rather than exemplary.

Suggestions

Enumerate the concrete artifacts produced (e.g., specs, design, tasks) so the 'what' is specific rather than a single 'all artifacts' action.

Add natural trigger phrases and synonyms users would actually say, such as "spec", "proposal", or "OpenSpec change", to the 'Use when' clause.

Mention the OpenSpec CLI dependency in the description itself so it is distinguishable from generic scaffolding skills.

Dimension	Reasoning	Score
Specificity	Names the domain ("OpenSpec artifact creation") and one concrete action ("quickly create all artifacts needed for implementation"), but never enumerates which artifacts are produced, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Both what ("Fast-forward through OpenSpec artifact creation") and when ("Use when the user wants to quickly create all artifacts... without stepping through each one individually") are explicitly stated, but the 'what' side is thin and lacks concrete artifact names, so it does not reach the fully explicit anchor 5.	4 / 5
Trigger Term Quality	Relevant keywords like "OpenSpec", "artifacts", and "implementation" are present, but the trigger is framed as a behavioral condition rather than natural user phrases, and common variations such as "spec", "proposal", or "tasks" are missing.	3 / 5
Distinctiveness Conflict Risk	"OpenSpec artifact creation" carves a clear niche with minimal conflict against unrelated skills, though it could overlap with a sibling step-by-step OpenSpec creation skill ("without stepping through each one" is the only differentiator).	4 / 5
	Total	14 / 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: Draculabo/AntigravityManager
Path: .agent/skills/openspec-ff-change/SKILL.md
Commit: ccea788

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