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

71%

Does it follow best practices?

Impact

72%

6.00x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/data/01-meta-chain-of-skills-150/SKILL.md

Quality

Content

63%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 well-structured, actionable orchestration protocol with clear sequencing and confirmation gates, but it is noticeably redundant and monolithic. Consolidating the repeated workflow/status-block descriptions and splitting the route templates and skill catalog into reference files would materially improve it.

Suggestions

Consolidate the three parallel descriptions of the SCAN/BUILD/EXECUTE workflow ("What This Skill Does", "Three Steps", "Execution Protocol") into a single canonical sequence, and define the EXECUTION STATUS block template once then reference it.

Move the route templates and the "Available Skills for Routing" catalog into separate reference files (e.g. ROUTES.md, SKILL-CATALOG.md) linked from the body, so the overview stays lean and supports progressive disclosure.

Add a concrete validation step after each skill executes (e.g. check expected artifact/output before marking the step complete) instead of the generic 'retry or skip' recovery, since executing code changes can be destructive.

Dimension	Reasoning	Score
Conciseness	The body is operational rather than padded with concepts Claude already knows, but the SCAN/BUILD/EXECUTE workflow is restated three times ("What This Skill Does", "Three Steps", "Execution Protocol") and the EXECUTION STATUS block template is repeated four-plus times, so it could be tightened considerably; not a 2 because the content is actionable rather than filler.	3 / 5
Actionability	Provides executable bash scan commands, a named skill catalog, copy-paste route templates, and a full worked dark-mode example; held at 4 rather than 5 because actual skill execution is abstracted away as "[... skill execution output ...]" and the action is heavily about output formatting.	4 / 5
Workflow Clarity	The process is clearly sequenced (SCAN → ANALYZE → BUILD → SHOW → EXECUTE → COMPLETE/REBUILD) with explicit per-step confirmation gates and a Failure Modes & Recovery table; held at 4 rather than 5 because verifying that a skill produced a correct result is shallow (generic retry/skip) rather than a real validation step.	4 / 5
Progressive Disclosure	Section headers are well organized, but this is a monolithic ~380-line file with route templates, the skill catalog, and multiple format examples all inlined and no external reference files; the under-50-line simple-skill exception does not apply, and content that could be split (routes, catalog) is inline.	3 / 5
	Total	14 / 20 Passed

Description

80%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 description that clearly states both what the skill does and when to trigger it, with concrete actions and natural trigger phrases. Its main weakness is overlap risk: the trigger conditions are broad enough to compete with sibling planning skills.

Dimension	Reasoning	Score
Specificity	Names the meta-orchestration domain and several concrete actions ("Сканирует доступные skills", "создает план выполнения", "идет шаг за шагом с подтверждением каждого этапа"), matching the 'lists several specific actions; minor gaps' anchor rather than 5 because the actions are high-level and not comprehensive.	4 / 5
Completeness	It explicitly answers both what (scan skills → build plan → execute step-by-step with confirmation) and when (an explicit "Triggers on…" clause with concrete trigger phrases), matching the anchor for clearly answering both with concrete triggers.	5 / 5
Trigger Term Quality	"Triggers on complex tasks, multi-step work" are phrases a user would naturally say, giving good keyword coverage; held at 4 rather than 5 because "structured execution" is technical and common synonyms (orchestration, workflow, plan) are missing.	4 / 5
Distinctiveness Conflict Risk	The meta-orchestration niche is somewhat distinct, but broad triggers like "complex tasks" and "multi-step work" overlap with related planning/orchestration skills (chain-flow-150, chain-of-skills noted in the body), so it could still trigger for the wrong skill.	3 / 5
	Total	16 / 20 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
Path: skills/data/01-meta-chain-of-skills-150/SKILL.md
Commit: 04324c6

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