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

73%

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

76%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 and well-structured with exact paths, commands, and templates, making it an exemplar instruction-only skill. Its main weakness is the absence of an explicit validation/verification checkpoint for a destructive merge operation, which caps workflow clarity.

Suggestions

Add an explicit validation step after applying changes, e.g. re-read each modified main spec to confirm well-formedness and that ADDED/MODIFIED/REMOVED/RENAMED sections resolved as intended before showing the summary.

Introduce a verify-then-finalize feedback loop ('if a referenced requirement is missing or a merge is ambiguous, surface it and re-prompt') to satisfy the destructive-operation checkpoint requirement.

Consider moving the Delta Spec Format Reference and Output On Success templates into a references file so the SKILL.md body stays a concise overview pointing one level deep.

Dimension	Reasoning	Score
Conciseness	The body is dense and purposeful with exact paths and commands, assuming Claude's competence; minor redundancy between the step 2 section list and the Delta Spec Format Reference example keeps it just short of fully lean.	4 / 5
Actionability	For an instruction-only skill it is copy-paste-ready: exact CLI command, exact file globs, named tool (AskUserQuestion), explicit per-section merge rules for all four delta types, and a complete output template cover the common cases exhaustively.	5 / 5
Workflow Clarity	The 4-step sequence and guardrails are clear, but this is a destructive/batch operation that mutates and removes main specs with no explicit validation checkpoint confirming the merged result, so the destructive-cap rule holds workflow_clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the skill is self-contained with clear section headers and one-level-deep navigation, though the inlined format-reference and output-template blocks could be externalized for a cleaner overview.	4 / 5
	Total	16 / 20 Passed

Description

70%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 is strong and well-formed, answering both what and when with a concrete trigger and a clear niche. It is held back from the top band by a narrow single-action specificity and limited trigger-term variety.

Suggestions

Broaden specificity by naming the concrete merge actions the skill performs (e.g., add, modify, remove, rename requirements) rather than the single verb 'Sync'.

Expand trigger terms with natural synonyms and the tool name, e.g. 'Use when applying an openspec delta to main specs, updating requirements, or merging change deltas into specs.'

Add file/extension-style anchors users might say (e.g. mentions of 'openspec changes/', 'delta spec', 'spec.md') to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('delta specs', 'main specs') and one concrete action ('Sync'), but the action set is narrow and not comprehensive — it is essentially a single sync/merge operation rather than several specific actions.	3 / 5
Completeness	Clearly states both what ('Sync delta specs from a change to main specs') and when ('Use when the user wants to update main specs with changes from a delta spec, without archiving the change'), matching the anchor for both present with an explicit but single-phrased trigger.	4 / 5
Trigger Term Quality	Includes a reasonably natural trigger phrase ('Use when the user wants to update main specs with changes from a delta spec'), but lacks synonyms, common variations, and the openspec tool name as an explicit trigger.	4 / 5
Distinctiveness Conflict Risk	The openspec sync niche is clear and the 'without archiving' qualifier distinguishes it from adjacent openspec skills, though minor overlap risk remains with related change-management skills.	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: Draculabo/AntigravityManager
Path: .agent/skills/openspec-sync-specs/SKILL.md
Commit: e29cfdc

Reviewed: 1 day 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.