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

—

Does it follow best practices?

Impact

72%

6.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

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

A thorough, well-sequenced orchestration protocol with strong workflow clarity and actionable templates, but it is verbose and monolithic. Redundant restatements of the same steps and an inlined 380-line body limit token efficiency and progressive disclosure.

Suggestions

Deduplicate the SCAN/BUILD/EXECUTE flow: keep one canonical 'Execution Protocol' section and have 'What This Skill Does' and 'Three Steps' reference it instead of restating the status block and step formats.

Move Common Route Templates and the detailed Output Format specs into reference files (e.g., ROUTES.md, FORMATS.md) so SKILL.md stays a lean overview.

Consolidate the repeated status-block template into a single defined block referenced by all sections that use it.

Dimension	Reasoning	Score
Conciseness	Content is relevant and assumes Claude's intelligence (no basic-concept padding), but it is heavily redundant — SCAN/BUILD/EXECUTE is restated across 'What This Skill Does', 'Three Steps', and 'Execution Protocol', and the status block template is repeated in several sections. It could be tightened well below the score-3 'lean' bar without losing clarity.	2 / 3
Actionability	Provides concrete executable scan commands (ls -la of the specific skill dirs), specific named route templates, exact output-format templates, and a precise user-command table. For an instruction-only orchestration skill the guidance is concrete and actionable, so the absence of large code blocks is not penalized.	3 / 3
Workflow Clarity	Clear SCAN→BUILD→EXECUTE→COMPLETE/REBUILD sequence with explicit confirmation gates at every step ('Continue? Yes/Pause/Reroute/Stop'), plus a failure-modes table and a reroute recovery feedback loop — matching the score-3 anchor of explicit checkpoints and error-recovery loops.	3 / 3
Progressive Disclosure	The file is well-sectioned, but at ~380 lines it is a monolithic body with route templates and detailed format specs inlined that a leaner SKILL.md overview could push to reference files; no bundle files exist, and the under-50-line simple-skill exception does not apply.	2 / 3
	Total	10 / 12 Passed

Description

77%

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 solid meta-skill description that names concrete orchestration actions and includes an explicit trigger clause answering both 'what' and 'when'. The weaker points are trigger phrasing and distinctiveness — 'structured execution' is jargon and the generic terms overlap with sibling planning skills.

Suggestions

Replace jargon like 'structured execution' with natural user phrasings (e.g., 'break this into steps', 'multi-step task') to improve trigger term quality.

Sharpen distinctiveness by contrasting with chain-flow-150 / action-plan-150 in the description itself (e.g., 'Use when a task needs an explicit step-by-step plan with per-step confirmation — not for single-skill work').

Drop the '[01] META.' prefix label to reduce noise and over-claim.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Сканирует', 'создает план выполнения', 'идет шаг за шагом', 'с подтверждением каждого этапа' — naming scan, plan, execute, and per-stage confirm. The '[01] META.' prefix is mild noise, but the action set is concrete and multiple, matching the score-3 anchor rather than the single-domain score-2 anchor.	3 / 3
Completeness	Explicitly answers what (scan skills, create plan, execute step by step, confirm each stage) and when via 'Triggers on complex tasks, multi-step work, or when structured execution is needed.' The explicit 'Triggers on...' clause satisfies the trigger-guidance requirement that would otherwise cap completeness at 2.	3 / 3
Trigger Term Quality	Trigger phrases 'complex tasks' and 'multi-step work' are reasonably natural, but 'structured execution' is jargon and common user variations are limited, so it stops short of the broad natural-term coverage expected at score 3.	2 / 3
Distinctiveness Conflict Risk	The orchestration niche is somewhat distinct, but generic triggers like 'complex tasks' and 'multi-step work' overlap with related planning skills the body itself cites (action-plan-150, chain-flow-150), so it could trigger for the wrong skill.	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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: majiayu000/claude-skill-registry
Commit: 8271354

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