CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-orchestration

Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/design-orchestration/SKILL.md
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.

The body presents a clear, well-sequenced routing workflow with strong gating and enforcement rules, and all content is appropriately placed in a single file. Its weaknesses are modest padding (philosophy aphorisms and a filler 'When to Use' section) and a few soft spots in actionability where criteria or recovery targets are left unspecified.

Suggestions

Delete the 'Design Philosophy' section and the 'When to Use' filler line; they add no routing instruction.

Tighten the Step 5 failure path: specify which skill to return to for each failed condition instead of 'the appropriate skill'.

Give the risk classification slightly firmer criteria (e.g., which factors make a design 'high risk') so the routing decision is reproducible rather than judgment-only.

DimensionReasoningScore

Conciseness

The routing logic itself is tight, but several sections add no instruction: the 'Design Philosophy' aphorisms ('Good systems fail early. Bad systems fail in production.'), the filler 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.'), and repeated statements of purpose. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level-4 anchor.

3 / 5

Actionability

Concrete decision rules throughout: risk tiers map to required actions ('High risk → REQUIRE multi-agent-brainstorming'), explicit prohibitions ('You may NOT proceed without these artifacts'), and a named-artifact checklist. Minor gaps remain — risk classification relies on open-ended 'factors such as' and artifact formats are defined only in the external controlled skills — so it is not the fully executable level-5 anchor.

4 / 5

Workflow Clarity

A clear five-step sequence with an explicit readiness checklist (Step 5) and a feedback loop ('block execution / return to the appropriate skill'). It falls short of level 5 because recovery guidance is vague ('the appropriate skill' is unspecified) and validation of the risk classification itself is left implicit.

4 / 5

Progressive Disclosure

Well-organized sections in a single appropriately-sized file with no nested references and no content that clearly belongs in a separate file; all routing logic lives correctly in SKILL.md. Minor organization issues (redundant trailing sections, and the exit bullet at line 153 runs into the following '---' divider) keep it below the clean level-5 anchor; it also exceeds the under-50-line simple-skill exception.

4 / 5

Total

15

/

20

Passed

Description

58%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 gives a clear, third-person statement of what the skill does with several named workflow stages, but it omits any 'Use when...' trigger guidance, which both caps completeness and weakens trigger-term quality. Keyword coverage lacks the natural variations a user would actually say.

Suggestions

Append a trigger clause such as: 'Use when a user proposes a new feature or design change, when a design decision carries meaningful risk, or when designs must be validated before implementation.'

Add natural user-facing synonyms to the keyword set, e.g., 'design review', 'validate a design', 'feature proposal', 'design sign-off'.

Mention the risk-assessment and gating behavior (e.g., 'classifies design risk and blocks implementation until designs are validated') to round out capability coverage.

DimensionReasoningScore

Specificity

Lists several specific actions — 'routing work through brainstorming, multi-agent review, and execution readiness' — going beyond the 1-2 actions of the level-3 anchor, but coverage has minor gaps (e.g., risk assessment and enforcement are not mentioned), so it falls short of the comprehensive level-5 anchor.

4 / 5

Completeness

The 'what' is clear (orchestrates design workflow routing), but there is no 'Use when...' clause or equivalent trigger guidance; per the judging guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords ('design workflows', 'brainstorming', 'multi-agent review') but misses natural user phrases like 'design review', 'validate a design', or 'feature proposal', matching the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

A distinct orchestration/meta-skill niche with named stages that differ from ordinary design skills; only minor overlap risk with the brainstorming and multi-agent-brainstorming skills it routes to, so it is not the fully minimal-conflict level-5 anchor.

4 / 5

Total

14

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/design-orchestration/SKILL.md

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.