CtrlK
BlogDocsLog inGet started
Tessl Logo

orchestrator

Skill do Tech Lead/Orquestrador do pipeline de desenvolvimento. Deve ser usada no inicio de toda task e entre etapas relevantes do pipeline. Coordena qual skill executar, em que ordem, adapta o fluxo ao contexto, garante que nenhuma etapa critica seja pulada e mantem visao geral do progresso. Trigger em: "nova task", "iniciar", "pipeline de desenvolvimento", "orquestrar", "coordenar", "planejar execucao", "proximo step do pipeline", "workflow".

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 thorough, actionable orchestrator playbook with concrete code, decision tables, and explicit validation gates. Its main weaknesses are a verbatim-duplicated section inflating length and heavy inlining that limits progressive disclosure.

Suggestions

Remove the duplicate 'Constituicao (se existir)' block (lines 41-46) — it is identical to lines 34-39 and wastes context tokens.

Move the long 'Pipeline Base' skill list and 'Adaptacao de Pipeline' case table into a referenced file (e.g. docs/skill-guides/pipeline-catalog.md), keeping only the decision rule inline in SKILL.md.

Tighten prose throughout by dropping restatements of kit-global rules already defined in GLOBAL.md and policies/ (the 'Quando Nao Usar' section already flags this anti-pattern but the body still repeats some).

DimensionReasoningScore

Conciseness

Mostly dense and useful, but the 'Constituicao (se existir)' subsection is duplicated verbatim (lines 34-39 and 41-46), which is pure padding that should be tightened.

3 / 5

Actionability

Provides executable guidance — a concrete Agent({subagent_type, isolation, model, ...}) dispatch example, commands like `node scripts/route-task.mjs --json`, and a model-routing table — with only minor gaps in surrounding context.

4 / 5

Workflow Clarity

Multi-step pipelines are clearly sequenced with explicit validation (pre-execution ambiguity gate, Readiness Gate PASS/CONCERNS/FAIL, rejection feedback loops), but the duplicated section signals minor disorganization.

4 / 5

Progressive Disclosure

References are well-signaled and one level deep (policies/, programs/, templates/, docs/skill-guides/), but a large amount of routing detail is inlined in a ~430-line body rather than split out, keeping it just below the top anchor.

4 / 5

Total

15

/

20

Passed

Description

96%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.

A strong, third-person description that explicitly states capabilities and trigger phrases with comprehensive synonym coverage. The only soft spot is a modest overlap risk with sibling meta-routing skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Coordena qual skill executar, em que ordem, adapta o fluxo ao contexto, garante que nenhuma etapa critica seja pulada e mantem visao geral do progresso' — giving comprehensive coverage of the orchestrator's capabilities.

5 / 5

Completeness

Clearly answers both 'what' (coordinate skills/order/flow, ensure critical steps, maintain progress) and 'when' ('Deve ser usada no inicio de toda task e entre etapas relevantes' plus the trigger list), satisfying the top anchor.

5 / 5

Trigger Term Quality

The explicit 'Trigger em:' clause enumerates natural user phrases including synonyms ('nova task', 'iniciar', 'orquestrar', 'coordenar', 'planejar execucao', 'proximo step do pipeline', 'workflow'), matching the comprehensive-synonym anchor.

5 / 5

Distinctiveness Conflict Risk

It carves a clear orchestration niche, but the broad coordination framing risks minor overlap with closely related meta-skills in the same kit (e.g. the program-router), so it sits just below the minimal-conflict anchor.

4 / 5

Total

19

/

20

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

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
felvieira/claude-skills-fv
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.