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

85%

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

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.

Excellent action-oriented skill content: concrete commands, explicit file paths, a full delta-format example, and a workflow with a real validation feedback loop and guardrails. The only refinements are minor — trimming the duplicated validation caveat between step 4d and Guardrails, and potentially moving the delta-format reference block into a separate reference file.

Dimension	Reasoning	Score
Conciseness	The body is dense and procedural with no explanations of concepts Claude already knows; nearly every line is task-specific instruction. Minor over-explanation remains — the title-line/validation caveat is stated both in step 4d and again in Guardrails, and the store-selection paragraph is a long inline block that could be tightened — so anchor 4 rather than the every-token-earns-its-place anchor 5.	4 / 5
Actionability	Fully executable guidance throughout: copy-paste commands (`openspec list --json`, `openspec status --change "<name>" --json`, `openspec validate <capability> --json`), exact file paths (`openspec/specs/<capability>/spec.md`), concrete per-section merge rules (ADDED/MODIFIED/REMOVED/RENAMED), a complete delta-format reference example, and a concrete output template. Matches anchor 5.	5 / 5
Workflow Clarity	Five clearly sequenced steps with an explicit validate-then-fix feedback loop ("run `openspec validate` ... and fix any reported issues before summarizing"), a guardrails checklist, an idempotency requirement, and forced user selection of the change. This is a batch/spec-modifying operation and validation is explicitly present with error-recovery instructions, matching anchor 5.	5 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-sectioned (Steps, Format Reference, Key Principle, Output, Guardrails) with no nested references. However, the ~25-line inline delta-spec format reference block is content that could live in a separate references file, and the skill exceeds the simple under-50-lines case, so it sits at anchor 4 rather than 5.	4 / 5
	Total	18 / 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 strong description: it clearly and explicitly states both what the skill does and when to use it, in third person, with niche-specific terminology that minimizes conflict risk with other skills. The only gap is specificity of capabilities — it names the single 'sync' action without enumerating the underlying operations (adding, modifying, removing, renaming requirements).

Dimension	Reasoning	Score
Specificity	The description names the domain ("delta specs from a change to main specs") and one concrete action ("sync"), but does not enumerate the several specific operations it performs (add/modify/remove/rename requirements). It matches anchor 3 (domain plus 1-2 concrete actions) rather than anchor 4, which requires a list of several specific actions.	3 / 5
Completeness	It 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. The 'when' clause is explicit and specific, including a scope qualifier distinguishing it from archiving, matching anchor 5 rather than the could-be-more-explicit anchor 4.	5 / 5
Trigger Term Quality	Natural domain terms users would say are present: "update main specs", "changes from a delta spec", "without archiving". Common synonyms like "apply", "merge", or "promote" delta specs are missing, so it falls at anchor 4 rather than the comprehensive synonym coverage of anchor 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche with distinct OpenSpec vocabulary (delta specs, changes, main specs, archiving) and an explicit differentiator ("without archiving the change") that separates it from the archive operation. Minimal conflict risk with other skills, matching anchor 5.	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: behindthedash/worktrail
Path: skills/openspec-sync-specs/SKILL.md
Commit: 9e05b5c

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