openspec-propose

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

Quality

92%

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

100%

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 tightly written, executable workflow with concrete commands, JSON field guidance, and explicit validation feedback loops. Organization is clean and self-contained with no unnecessary reference indirection.

Dimension	Reasoning	Score
Conciseness	The body is lean and instruction-focused: concrete commands and structured numbered steps with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Provides fully executable commands (`openspec new change`, `openspec status --change --json`, `openspec instructions ... --json`) with the exact JSON fields to parse and output paths, matching the 'fully executable; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Clear numbered sequence with an explicit feedback loop (re-run `openspec status --json` after each artifact to check `applyRequires`), plus a verify-file-exists guardrail, matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	No bundle files exist; the single SKILL.md body is well-organized into Input/Steps/Output/Guidelines/Guardrails sections, and per the simple-skill scoring note a self-contained skill with no external-reference need can score 3 with well-organized sections.	3 / 3
	Total	12 / 12 Passed

Description

85%

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 specific and complete, clearly stating both the capability and an explicit 'Use when' trigger with a distinct niche. Trigger-term coverage is adequate but could include more natural keyword variations a user might say.

Suggestions

Broaden trigger terms to include phrases users commonly say, e.g. 'Use when the user asks to propose, plan, or scope a new feature/change, or wants a design + spec + task breakdown before implementation.'

Consider naming the artifact types more concretely in the trigger ('proposal, design, and task list') to strengthen natural keyword matching.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete outputs ('design, specs, and tasks', 'all artifacts generated in one step') rather than vague language, matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('Propose a new change with all artifacts... design, specs, and tasks') and when ('Use when the user wants to quickly describe what they want to build'), matching the 'what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	Includes some natural phrasing ('describe what they want to build', 'proposal') but lacks broader keyword coverage and common variations a user might say, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Scoped specifically to openspec change proposals with distinct triggers around building proposals, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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-propose/SKILL.md
Commit: 2945693

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