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

Quality

Content

72%

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 instruction-only workflow with concrete paths and commands. Its main weaknesses are a missing verification feedback loop for destructive spec edits and mild redundancy between the steps and the format-reference block.

Suggestions

Add an explicit validation/verification step before declaring success — e.g., re-read the resulting main spec to confirm the merge applied correctly and is internally consistent — to support a workflow_clarity score of 3.

Trim redundancy between the numbered steps (which already describe ADDED/MODIFIED/REMOVED/RENAMED) and the "Delta Spec Format Reference" block by making the reference a compact single worked example rather than re-explaining each section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the full "Delta Spec Format Reference" block and "Output On Success" template partially duplicate guidance already covered in the numbered steps, leaving room to tighten.	2 / 3
Actionability	It provides concrete commands (`openspec list --json`), exact file paths (`openspec/changes/<name>/specs/<capability>/spec.md`), and per-requirement-type (ADDED/MODIFIED/REMOVED/RENAMED) handling — actionable and specific for an instruction-only skill.	3 / 3
Workflow Clarity	Steps are clearly sequenced with a "stop if no delta specs found" checkpoint, but a spec-merging operation that modifies main specs (destructive/batch) lacks an explicit validate-then-proceed feedback loop, which caps this at 2 per the rubric.	2 / 3
Progressive Disclosure	The skill is a single well-organized file with clearly labeled sections (Input, Steps, Format Reference, Key Principle, Output, Guardrails), no nested references, and no content that needs splitting out — easy to navigate.	3 / 3
	Total	10 / 12 Passed

Description

75%

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 cleanly answers both what and when and occupies a distinct niche. It is held back only by a single-action specificity and somewhat jargon-bound trigger terms.

Suggestions

Expand the action list in the first sentence to surface the concrete sub-operations (add, modify, remove, and rename requirements) for stronger specificity.

Broaden the "Use when" clause with more natural user phrasings (e.g. "apply a change's specs to the main specs") alongside the openspec jargon.

Dimension	Reasoning	Score
Specificity	The description names a concrete action — "Sync delta specs from a change to main specs" — and the domain, but offers a single primary action rather than the multiple specific concrete actions that anchor a 3 (e.g. "extract, fill, merge").	2 / 3
Completeness	It explicitly states what the skill does (sync delta specs to main specs) and gives an explicit "Use when..." trigger clause, matching the 3 anchor that answers both what and when.	3 / 3
Trigger Term Quality	The "Use when the user wants to update main specs with changes from a delta spec" clause provides a relevant trigger, but relies on openspec jargon ("delta spec", "archiving the change") and misses common natural-language variations.	2 / 3
Distinctiveness Conflict Risk	The niche is very specific — syncing openspec delta specs to main specs without archiving — with triggers unlikely to fire for unrelated skills, matching the clear-niche 3 anchor.	3 / 3
	Total	10 / 12 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: rpamis/comet
Path: eval/local/skills/benchmarks/dependency/openspec/openspec-sync-specs/SKILL.md
Commit: 2945693

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