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

79%

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

Quality

Content

85%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 strong, executable skill body with a well-sequenced workflow and an explicit validate-and-fix feedback loop before summary. It respects token budget while remaining concrete, with only minor opportunities to externalize reference material.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient, leaning on concrete CLI commands and terse bullet rules rather than explaining concepts Claude already knows; a few sentences (e.g. restating the merge intent) could be trimmed but it stays close to the 4 anchor.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands (`openspec list --json`, `openspec status --change`, `openspec validate`) plus concrete path conventions (`openspec/specs/<capability>/spec.md`) and a worked delta-format reference that covers the common cases.	5 / 5
Workflow Clarity	Steps are explicitly numbered 1-5 with a clear sequence, and validation is built in as a feedback loop (`openspec validate` and 'fix any reported issues before summarizing'), satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	Well-organized into clear sections (Steps, Delta Spec Format Reference, Key Principle, Output, Guardrails) with one-level structure and no nested references; since there are no bundle files, content is appropriately self-contained, falling just short of a 5 only because a few inline blocks (e.g. the full delta-format reference) could live in a reference file.	4 / 5
	Total	18 / 20 Passed

Description

73%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 well-constructed description that clearly states both the action and trigger condition with a useful negative boundary ('without archiving'). It is held back from the top tier by jargon-leaning trigger terms rather than natural user phrasing.

Suggestions

Add a few natural user phrasings (e.g. 'apply a change's spec updates', 'merge change specs into the main specs') alongside the technical terms to improve trigger coverage.

Mirror the concrete operations (add/modify/remove/rename requirements) briefly in the description so the breadth of capability is visible without reading the body.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions in the body (add, modify, remove, rename requirements) though the description itself names the domain ('sync delta specs') plus the high-level action 'update main specs' — slightly below a 5 but above the 3 anchor.	4 / 5
Completeness	Explicitly answers 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') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Trigger phrases ('user wants to update main specs with changes from a delta spec, without archiving the change') are relevant but somewhat jargon-heavy ('delta spec', 'main specs'); missing common synonyms a casual user might say.	3 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct (delta-to-main spec sync, explicitly excluding archiving), with only minor overlap risk against other openspec skills like 'archive'.	4 / 5
	Total	16 / 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: behindthedash/worktrail
Path: skills/openspec-sync-specs/SKILL.md
Commit: ca98247

Reviewed: ~3 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.