CtrlK
BlogDocsLog inGet started
Tessl Logo

orch-pipeline

Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Advisory

Suggest reviewing before use

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.

The body is a tight, actionable orchestration reference: concrete commands and agents, a clearly gated phase sequence with validation checkpoints, and clean single-file organization with one-level references. It does not over-explain concepts Claude already knows.

DimensionReasoningScore

Conciseness

Lean tables and bullets assume Claude's competence — no padding, no explaining what TDD or conventional commits are — and every section earns its place.

3 / 3

Actionability

Concrete, executable delegation throughout: named commands ('gh search repos', '/code-review', '/gan-build "<brief>" --skip-planner'), named agents ('planner', 'security-reviewer'), and explicit phase outputs ('task_list').

3 / 3

Workflow Clarity

Phases 0–6 are clearly sequenced with two explicit human gates and a final Verification checklist (size tier, gates honored, security-reviewer iff trigger, conventional commits, coverage ≥ 80%).

3 / 3

Progressive Disclosure

Single self-contained file (no bundle dirs present) with well-organized sections and one-level-deep, clearly signaled references to 'rules/common/*.md'; no nested reference chains.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and distinct, naming concrete pipeline components and a clear niche, but it lacks an explicit 'Use when…' trigger clause and relies on technical jargon rather than natural user-language keywords. Completeness and trigger-term quality are the weak points.

Suggestions

Add an explicit trigger clause such as 'Use when adding a new orch-* operation or tuning the shared phases, gates, or agent map' to satisfy the 'when' half of completeness.

Soften jargon with natural terms a user would say (e.g. 'orch-* skills', 'orchestration pipeline') alongside the technical labels to improve trigger-term quality.

Lead with the skill's purpose in plain language before listing internal components, so the description reads as user-facing guidance rather than internal architecture.

DimensionReasoningScore

Specificity

Lists multiple concrete components — 'the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates' — rather than vague language.

3 / 3

Completeness

Clearly states what the skill is, but offers no 'Use when…' clause — 'Not usually invoked directly' is inverted guidance about when not to use it, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Names a recognizable domain ('orch-* skill family') and relevant keywords, but the phrasing is technical jargon ('orchestration engine', 'gated pipeline') with no natural 'Use when…' trigger a user would say.

2 / 3

Distinctiveness Conflict Risk

'Shared orchestration engine for the orch-* skill family' carves a clear, distinct niche unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

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.