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 ./eval/local/skills/benchmarks/dependency/openspec/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 body is well-structured, lean, and highly actionable with concrete paths, commands, and copy-paste templates for an instruction-only workflow skill. Its chief weakness is the absence of explicit validation/verification checkpoints for a destructive batch operation, which caps workflow clarity.

Suggestions

Add an explicit verification checkpoint after applying changes (e.g., re-read each modified main spec to confirm the merge is coherent and the file still parses before reporting success) to lift workflow clarity above the destructive-operation cap.

De-duplicate the ADDED/MODIFIED/REMOVED/RENAMED section descriptions between step 2 and step 3, or reference step 2's list from step 3, to tighten conciseness.

Consider moving the full delta-spec format reference and the success-output template into a separate reference file (e.g., references/format.md) and linking to it, improving progressive disclosure for a body over 100 lines.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence with no concept padding, but the opening line repeats the description and the ADDED/MODIFIED/REMOVED/RENAMED sections are re-listed across steps 2 and 3, leaving minor trim opportunities that keep it just below 5.	4 / 5
Actionability	Concrete file paths, an exact command ("openspec list --json"), a named tool (AskUserQuestion), explicit per-section merge rules, and copy-paste-ready delta-format and output-template blocks fully cover the common cases for an instruction-only skill.	5 / 5
Workflow Clarity	Steps are clearly sequenced (1-4) with a summary, but this destructive/batch spec-mutation operation lacks explicit validation or verification checkpoints before/after editing main specs, so the rubric's destructive-operation cap holds workflow clarity at 3.	3 / 5
Progressive Disclosure	A single self-contained file with clear section headers and no nested references is well organized and easy to navigate, though the inline format-reference and output-template blocks could be externalized, keeping it just under 5.	4 / 5
	Total	16 / 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.

The description is concise, third-person, and clearly answers both what the skill does and when to use it with domain-specific trigger language. Its main limitation is specificity, since it describes one core sync action rather than enumerating multiple distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete action ("Sync delta specs from a change to main specs", "update main specs with changes from a delta spec") but does not list several distinct actions, so it stops at the 1-2 concrete actions anchor rather than reaching 4.	3 / 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 concrete, disambiguating trigger phrasing.	5 / 5
Trigger Term Quality	Natural domain phrases a user would say ("update main specs", "changes from a delta spec", "without archiving the change") give good keyword coverage, though synonym/extension variety is missing so it does not reach 5.	4 / 5
Distinctiveness Conflict Risk	Specialized openspec vocabulary ("delta specs", "main specs", "archiving the change") carves a clear niche with minimal overlap risk against unrelated skills.	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: rpamis/comet
Path: eval/local/skills/benchmarks/dependency/openspec/openspec-sync-specs/SKILL.md
Commit: f329b48

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