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

77%

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 ./eval/local/skills/benchmarks/dependency/openspec/openspec-ff-change/SKILL.md

Quality

Content

92%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 is a tight, executable workflow with concrete commands, explicit JSON parsing guidance, and validation feedback loops appropriate for a batch artifact-creation skill. The only minor weakness is light redundancy between the step-by-step and guidelines sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with no concept explanations Claude already knows; minor redundancy between Step 4's inline guidance and the later 'Artifact Creation Guidelines' section keeps it just shy of 5.	4 / 5
Actionability	Provides copy-paste-ready commands (openspec new, status --json, instructions) and explicitly enumerates the JSON fields to parse, fully covering the common case.	5 / 5
Workflow Clarity	Five clearly sequenced steps with explicit validation checkpoints (re-run status --json to confirm applyRequires are 'done', verify each file exists after writing) and feedback loops, satisfying the batch-operation validation requirement.	5 / 5
Progressive Disclosure	Self-contained skill with no bundle files and no content that belongs in separate references; sections (Input, Steps, Output, Guidelines, Guardrails) are well-organized and navigable.	5 / 5
	Total	19 / 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.

The description clearly names its niche and includes an explicit 'Use when' trigger, satisfying both what and when. It is somewhat thin on action specificity and trigger-term variety, keeping it in the mid-to-upper range.

Suggestions

List 1-2 more concrete actions (e.g., 'scaffold a change and generate its tasks/specs') to lift specificity.

Add natural synonyms users might say (scaffold, bootstrap, set up a change) to broaden trigger coverage.

Tighten the 'when' clause with a concrete trigger phrase such as 'Use when the user wants to start implementation without stepping through each artifact individually.'

Dimension	Reasoning	Score
Specificity	Names the domain ('OpenSpec artifact creation') and a concrete action ('create all artifacts needed for implementation'), but coverage is limited to that single action rather than a comprehensive list.	3 / 5
Completeness	Explicitly states what it does ('Fast-forward through OpenSpec artifact creation') and when to use it ('Use when the user wants to quickly create all artifacts...'), though the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes relevant phrases like 'create all artifacts needed for implementation', but lacks synonyms or natural variations a user might say (e.g., 'scaffold', 'bootstrap', 'set up change').	3 / 5
Distinctiveness Conflict Risk	The OpenSpec-specific niche is clear and unlikely to fire for unrelated skills, with only minor overlap risk against a generic openspec 'apply' companion skill.	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: rpamis/comet
Path: eval/local/skills/benchmarks/dependency/openspec/openspec-ff-change/SKILL.md
Commit: f329b48

Reviewed: about 24 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.