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

75%

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-sync-specs/SKILL.md

Quality

Content

68%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 well-structured, actionable agent-workflow skill with exact paths, commands, format examples, and a defined output template. The main gap is the absence of a validation/verification step for what is a batch edit across multiple spec files, which the rubric caps at workflow clarity 3; there is also mild redundancy in how the delta-spec sections are documented three times.

Suggestions

Add an explicit validation checkpoint before the summary step (e.g., re-read each modified main spec to confirm the delta applied cleanly, or run an openspec validation command), turning the batch edit into a validate-and-recover loop.

Consolidate the delta-spec section documentation: the ADDED/MODIFIED/REMOVED/RENAMED sections are described in Step 2, re-explained in Step 3, and shown in the format reference — the Step 2 listing could be dropped in favor of the format example.

Include a short example of a main spec requirement block so the agent knows the target format it is merging into, not just the delta format it is reading.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes competence ('agent-driven operation', 'use your judgment to merge changes sensibly'), with concrete paths and commands instead of background explanation. Minor redundancy — the ADDED/MODIFIED/REMOVED/RENAMED sections are described in Step 2, re-explained in Step 3, and shown again in the format reference — keeps it below the 'every token earns its place' anchor.	4 / 5
Actionability	Concrete, executable guidance throughout: `openspec list --json`, exact paths (`openspec/changes/<name>/specs/<capability>/spec.md`, `openspec/specs/<capability>/spec.md`), a complete delta-spec format example, and an explicit output template. Minor gaps (no example of the main-spec requirement block format, RENAMED handling is thin) keep it below fully copy-paste-ready coverage.	4 / 5
Workflow Clarity	Steps 1-4 are clearly sequenced with guardrails, but this batch operation (editing multiple main spec files across capabilities) has no validation or verification step — no check of the merged result before the summary, and no error-recovery loop. Per the rubric, missing validation in batch operations caps workflow clarity at 3 even though the sequence itself is well-defined.	3 / 5
Progressive Disclosure	The body is well-organized with clearly labeled sections (Steps, Delta Spec Format Reference, Key Principle, Output On Success, Guardrails) and needs no external references at this size. At ~130 lines with the format reference inlined rather than split out, it has minor organization gaps that keep it below the 'clear overview with well-signaled references' top anchor.	4 / 5
	Total	15 / 20 Passed

Description

82%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, third-person description that clearly and explicitly states both what the skill does and when to use it, with strong domain-specific trigger terms. Its only weakness is that it summarizes the operation as a single 'sync' action rather than naming the specific merge operations it performs.

Dimension	Reasoning	Score
Specificity	The description names the domain ('delta specs', 'main specs') and one concrete action ('Sync delta specs from a change to main specs'), but does not enumerate the underlying operations (add/modify/remove/rename requirements), so coverage is not comprehensive. It sits above score 2 (which requires only generic actions) but below score 4 (which requires several specific actions listed).	3 / 5
Completeness	It explicitly answers both questions: 'Sync delta specs from a change to main specs' (what) and 'Use when the user wants to update main specs with changes from a delta spec, without archiving the change' (when, with concrete trigger phrasing). Both are stated clearly and explicitly, matching the top anchor rather than score 4 where the 'when' would be less specific.	5 / 5
Trigger Term Quality	Phrases like 'delta spec', 'main specs', 'update main specs', 'sync', and 'without archiving the change' map well to what an openspec user would naturally say. A few natural variations ('apply changes', 'merge specs', 'promote changes') are missing, keeping it just below the comprehensive synonym coverage of score 5.	4 / 5
Distinctiveness Conflict Risk	The openspec-specific vocabulary ('delta spec', 'change', 'main specs', 'archiving') carves out a clear niche with minimal overlap risk against generic file- or document-editing skills. It is not merely 'somewhat specific' (score 3) — the triggers are domain-unique.	5 / 5
	Total	17 / 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-sync-specs/SKILL.md
Commit: ccea788

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