CtrlK
BlogDocsLog inGet started
Tessl Logo

orch-fix-defect

Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An efficient, well-structured orchestration wrapper: concise, concrete in its delegations, with a clear gated workflow and one-level-deep reference to the shared engine. It earns top marks across all content dimensions for a skill of this scope.

DimensionReasoningScore

Conciseness

Lean throughout with no concept-explanation padding; every section (settings, How It Works, Example) carries actionable content and assumes Claude's competence, including the one aphoristic line which still clarifies intent.

3 / 3

Actionability

Provides concrete, specific guidance — named agents (code-explorer, build-error-resolver, security-reviewer), explicit phase mask, Gate 1/Gate 2, the 'fix:' commit prefix, and a worked example flow — rather than vague direction; phase numbers are intentionally defined in the delegated orch-pipeline engine, so their absence here is progressive disclosure, not vagueness.

3 / 3

Workflow Clarity

A clearly numbered sequence (1–4) with explicit validation checkpoints (Gate 1 only-if-plan, Gate 2 pre-commit 'confirm') and a built-in red-test→green verification loop before the commit.

3 / 3

Progressive Disclosure

Under 50 lines with well-organized sections and a single one-level-deep, clearly signaled reference to ../orch-pipeline/SKILL.md; no bundle files exist to verify, and none are needed.

3 / 3

Total

12

/

12

Passed

Description

92%

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 tight, action-oriented description that states concrete steps and an explicit 'Use when' trigger. Its only weakness is distinctiveness: the trigger could be sharpened to separate defect-fixing from behavior-change intents directly in the description.

Suggestions

Add a brief disambiguation clause to the description (e.g., 'not for desired-but-absent behavior') so the trigger alone separates it from orch-change-feature and orch-add-feature.

Consider including a couple more natural user phrasings (e.g., 'crash', 'error', 'regression') to broaden trigger-term coverage beyond 'bug/broken/wrong'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'reproduce it as a failing regression test, fix to green, review, and gated commit' and 'delegating each phase to the matching ECC agent' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (the reproduce→fix→review→commit orchestration pipeline) and when ('Use when existing behavior is broken or wrong'), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say — 'bug', 'broken', 'wrong' — alongside 'regression test', giving good coverage rather than jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

The 'broken or wrong' trigger is defect-focused but could still overlap with feature-change siblings; the disambiguation from orch-change-feature/orch-add-feature lives only in the body, not the description itself.

2 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository
affaan-m/ECC
Reviewed

Table of Contents

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.