orch-change-feature

Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.

Quality

86%

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

86%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 tight, well-structured wrapper skill that assumes competence and points clearly to the shared engine. The only soft spots are that executable and feedback-loop detail live in the referenced engine rather than in the body itself.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding; assumes Claude knows what tests, commits, and reviews are, and every line earns its place.	5 / 5
Actionability	Provides concrete operation settings, named gates, and a worked example, but delegates the executable engine detail to orch-pipeline rather than inlining it, leaving minor gaps.	4 / 5
Workflow Clarity	Clear sequence with explicit Gate 1 and Gate 2 checkpoints; the validate-fix-retry loop is delegated to the shared engine rather than spelled out inline, a minor validation gap.	4 / 5
Progressive Disclosure	Under 50 lines, no bundle files needed, well-organized sections, and a single one-level reference to orch-pipeline/SKILL.md — meets the simple-skill top anchor.	5 / 5
	Total	18 / 20 Passed

Description

87%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 and clearly states both the capability and the trigger condition, with strong distinctiveness from sibling skills. Trigger-term breadth in the description field itself is the only minor gap.

Dimension	Reasoning	Score
Specificity	Lists several concrete orchestration actions ('update its tests to the new spec', 'change the implementation to match', 'review', 'gated commit') but they are process steps rather than a comprehensive capability menu, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what (alter feature: update tests, change impl, review, gated commit) and when ('Use when behavior is not broken but should be different'), matching the top anchor.	5 / 5
Trigger Term Quality	Includes a natural trigger clause ('Use when behavior is not broken but should be different') and the body adds 'change', 'adjust', 'make it also', but the description field itself misses some common synonyms a user might say.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (change vs fix vs add) with explicit sibling disambiguation and minimal overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/orch-change-feature/SKILL.md
Commit: d8409a4

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.