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

77%

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

Quality

Content

71%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 delivers a clear, actionable, intelligent-merge workflow with sensible guardrails and good token efficiency. Its main weaknesses are the absence of a validation/verification checkpoint before success and a monolithic structure that inlines reference material instead of splitting it out.

Suggestions

Add an explicit validation step before the summary (e.g., re-read each modified main spec to confirm structure is intact and requirements are well-formed), turning the workflow into a validate-fix-retry loop.

Extract the "Delta Spec Format Reference" block and the "Output On Success" template into separate reference files (e.g., references/delta-format.md) and link to them, improving progressive disclosure and token budget.

Clarify the RENAMED step's execution detail, e.g., note how to handle a rename when the FROM requirement is not found in the main spec.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, assuming Claude's competence and avoiding concept re-explanation, but sections like the full "Delta Spec Format Reference" example and some restated guidance (e.g., repeating ADDED/MODIFIED handling in the reference) could be trimmed slightly.	4 / 5
Actionability	Concrete, executable guidance is present throughout ("Run `openspec list --json`", explicit file paths like `openspec/changes/<name>/specs/*/spec.md`, clear per-case merge rules), but it is instruction-style rather than copy-paste code, and the RENAMED FROM:/TO: handling leaves minor execution detail implicit.	4 / 5
Workflow Clarity	A clear numbered sequence (prompt selection → find deltas → apply per capability → summary) is laid out with explicit guardrails (read both specs first, preserve untouched content, ask when unclear, idempotent), but there is no validation checkpoint verifying the merged main spec is well-formed before declaring success, leaving a minor validation gap.	4 / 5
Progressive Disclosure	The content is well sectioned within a single file, but it is a monolithic ~100-line SKILL.md with no bundle files; the inlined Delta Spec Format Reference and example output block are content that could live in separate reference files, and there are no one-level-deep references to offload detail.	3 / 5
	Total	15 / 20 Passed

Description

83%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 cleanly answers both what and when in third person with concrete, domain-specific language and a useful boundary qualifier. It is strong overall, held back only by modest action enumeration and trigger synonym coverage.

Dimension	Reasoning	Score
Specificity	"Sync delta specs from a change to main specs" names the domain and the concrete action of syncing/appling delta specs, plus the qualifier "without archiving the change"; it lacks the broader enumeration of multiple sub-actions (add/modify/remove/rename) found in the body, keeping it just short of a 5.	4 / 5
Completeness	It explicitly 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"), with the additional qualifier "without archiving the change" refining the trigger.	5 / 5
Trigger Term Quality	"Use when the user wants to update main specs with changes from a delta spec" offers natural trigger phrasing around updating/applying changes, but omits common synonyms or explicit file-extension/path cues that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The openspec delta-sync niche is fairly specific and unlikely to collide with unrelated skills, but it shares "sync specs" terminology with adjacent openspec skills, leaving minor overlap risk rather than a fully unique niche.	4 / 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: fengshao1227/ccg-workflow
Path: .agents/skills/openspec-sync-specs/SKILL.md
Commit: cc8cc34

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.