01-meta-chain-of-skills-150

[01] META. Сканирует доступные skills, создает план выполнения и идет шаг за шагом с подтверждением каждого этапа. Triggers on complex tasks, multi-step work, or when structured execution is needed.

6.00x

Quality

72%

Does it follow best practices?

Impact

72%

6.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/data/01-meta-chain-of-skills-150/SKILL.md

Quality

Discovery

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.

This description adequately communicates its meta-orchestration purpose and includes explicit trigger conditions, which is good. However, the trigger terms are too generic ('complex tasks', 'multi-step work') which could cause conflicts with other skills, and the specific capabilities could be more concrete. The mixed Russian/English language may also affect discoverability.

Suggestions

Add more specific natural trigger terms users would say, such as 'plan this out', 'break this down', 'coordinate multiple skills', 'orchestrate workflow'

Make the trigger conditions more distinctive by specifying what makes a task require THIS skill vs others (e.g., 'when task requires coordinating 2+ different skills' rather than generic 'complex tasks')

Dimension	Reasoning	Score
Specificity	Names the domain (meta/orchestration) and some actions ('сканирует доступные skills', 'создает план выполнения', 'идет шаг за шагом'), but the actions are somewhat abstract rather than concrete specific operations.	2 / 3
Completeness	Clearly answers both what ('Сканирует доступные skills, создает план выполнения и идет шаг за шагом с подтверждением каждого этапа') and when ('Triggers on complex tasks, multi-step work, or when structured execution is needed') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'complex tasks', 'multi-step work', 'structured execution', but these are fairly generic. Missing natural user phrases like 'plan this out', 'break this down', 'step by step', 'orchestrate', or 'coordinate'.	2 / 3
Distinctiveness Conflict Risk	The meta/orchestration role is somewhat distinct, but 'complex tasks' and 'multi-step work' are very broad triggers that could overlap with many other skills that also handle complex or multi-step operations.	2 / 3
	Total	9 / 12 Passed

Implementation

77%

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

This is a well-structured orchestration skill with excellent workflow clarity and actionability - it provides clear step-by-step execution protocols with mandatory confirmation checkpoints and concrete output formats. However, it suffers from verbosity through repeated template examples and could benefit from splitting detailed reference content (route templates, output formats) into separate files to improve token efficiency.

Suggestions

Reduce template repetition - show the execution status block format once and reference it, rather than including it 4+ times throughout the document

Move 'Common Route Templates' and detailed 'Output Format' sections to separate reference files (e.g., ROUTES.md, FORMATS.md) and link to them

Condense the 'Available Skills for Routing' table - Claude can discover these from the scan step; listing them all adds ~20 lines of redundant content

Dimension	Reasoning	Score
Conciseness	The skill is quite verbose with extensive formatting templates and repeated examples. While the content is useful, there's significant redundancy (e.g., the execution status block is shown 4+ times, route templates could be condensed). Claude doesn't need this level of template repetition.	2 / 3
Actionability	Provides concrete, executable guidance with specific bash commands for scanning skills, clear table formats for plans, exact output templates, and detailed user command mappings. The examples show copy-paste ready formats.	3 / 3
Workflow Clarity	Excellent multi-step workflow with clear sequencing (SCAN → BUILD → EXECUTE), explicit confirmation checkpoints at each step, user commands for control flow (Yes/Pause/Reroute/Stop), and a failure modes & recovery table with specific detection and recovery actions.	3 / 3
Progressive Disclosure	The skill is monolithic at ~350 lines with all content inline. While well-organized with clear sections, the route templates, output formats, and examples could be split into separate reference files. The skill references other skills but doesn't link to external documentation for its own detailed sections.	2 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: majiayu000/claude-skill-registry
Commit: 6213d1a

Reviewed: about 6 hours 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.