openspec-sync-specs

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/openspec-sync-specs/SKILL.md

Quality

Content

88%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 content is highly actionable with concrete commands, a well-sequenced validated workflow, and strong guardrails for a destructive merge operation; its only real weakness is mild redundancy between the steps and the Guardrails section.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence without explaining concepts, but the Guardrails section repeats guidance already stated in the steps and the 6-condition retirement checklist could be tightened, fitting 'efficient with minor over-explanation that could be trimmed'.	4 / 5
Actionability	It provides copy-paste-ready CLI commands (e.g. 'openspec status --change "<name>" --json', 'openspec validate --specs'), concrete file paths, and full delta/main spec format examples covering the common merge cases.	5 / 5
Workflow Clarity	A clear 6-step sequence includes an explicit validation checkpoint (step 5), stop-before-write guards on invalid instruction JSON, and a 6-item retirement checklist with feedback loops, satisfying the top anchor for a destructive/batch operation.	5 / 5
Progressive Disclosure	The skill is single-file with no bundle references and is well-organized into clearly signaled sections, but at 250+ lines the Delta/Main Spec Format Reference blocks are inlined where a separate reference file could reduce top-level weight.	4 / 5
	Total	18 / 20 Passed

Description

71%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 cleanly answers both what and when with an explicit trigger and a clear niche, though it is jargon-heavy and names only a single concrete action.

Suggestions

Add one or two more concrete actions (e.g., 'merge, add, modify, remove, or rename requirements') to lift specificity above a single sync verb.

Soften jargon in the trigger with a natural synonym (e.g., 'update specs', 'apply spec changes') so users not fluent in openspec terms still match it.

Dimension	Reasoning	Score
Specificity	The phrase 'Sync delta specs from a change to main specs' names the domain and one concrete action (sync), but lists no secondary actions, matching the anchor for naming a domain with 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It explicitly states the what ('Sync delta specs from a change to main specs') and the when ('Use when the user wants to update main specs with changes from a delta spec, without archiving the change') with a concrete trigger phrase, matching the top anchor.	5 / 5
Trigger Term Quality	Triggers like 'update main specs with changes from a delta spec' are relevant but rely on openspec jargon ('delta spec', 'main spec') and omit natural synonyms a user might say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The skill occupies a clear niche (spec syncing) and explicitly carves itself out from archiving ('without archiving the change'), leaving only minor overlap risk with a related archive skill rather than full distinctiveness.	4 / 5
	Total	15 / 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: Fission-AI/OpenSpec
Path: skills/openspec-sync-specs/SKILL.md
Commit: 6926ccb

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