Name: 00-meta-chain-flow-150
Rating: 77 (1 reviews)
Author: majiayu000

00-meta-chain-flow-150

[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.

1.56x

Quality

67%

Does it follow best practices?

Impact

89%

1.56x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/00-meta-chain-flow-150/SKILL.md

The canonical home for this skill is 00-meta-chain-flow-150 in majiayu000/claude-skill-registry

Quality

Content

42%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 skill body is well-structured and easy to follow but significantly over-padded with redundant ASCII diagrams and restated templates, and its orchestration guidance leans on placeholders rather than executable instruction. Validation checkpoints for batch skill execution are absent, capping workflow clarity.

Suggestions

Collapse the three restatements of the 6-step model (ASCII diagram, Chain Building Process, Output Format) into one canonical sequence to cut substantial redundancy.

Replace placeholder templates ([Execute skill...], [skill-name] → WHY: ...) with a concrete worked example showing real skill names and real output, or move templates to a reference file.

Add an explicit validation/verification checkpoint after each skill executes (e.g., confirm the skill's stated success criteria were met before proceeding) to support the batch workflow.

Move the chain-pattern catalog and output-format templates into a separate reference file and reference it one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose: the same 6-step model is restated as an ASCII diagram, a prose "Chain Building Process", and again as output/execution templates, plus motivational filler like the "150% Orchestration Rule" and "Most real problems need chains of skills".	2 / 5
Actionability	Gives concrete executable discovery commands (ls/cat of skill dirs), but the core chain-building and execution guidance is templated placeholders ("[Execute skill...]", "[skill-name] → WHY: [justification]") rather than real instructions.	3 / 5
Workflow Clarity	The 6-step sequence and confirmation gates are clear, but orchestrating a batch of skills has no validation that each step's output is correct — only yes/no confirmation — so the batch-operation validation cap applies.	3 / 5
Progressive Disclosure	It is a single 360+ line file with no bundle references, inlining chain patterns and output templates that would fit better in separate reference files; section headers provide structure but nothing is split out.	3 / 5
	Total	11 / 20 Passed

Description

92%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: it names concrete actions, gives explicit trigger phrases with synonyms, and covers both what and when clearly. The only weakness is its near-universal scope, which raises conflict risk with other planning skills.

Suggestions

Narrow the trigger scope (e.g., "when no single skill covers the task and sequencing multiple skills is required") to reduce overlap with general planning/analysis skills.

Drop the "[00] META." prefix token from the description; it adds noise without aiding user-side triggering.

Consider noting when NOT to use it (e.g., single-step or single-skill tasks) to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step"), giving comprehensive coverage of the orchestration domain.	5 / 5
Completeness	Explicitly answers both what ("Orchestrate skills into dynamic chains...") and when ("Use for any complex task... Triggers on...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases with synonyms ("plan this", "how to approach", "what's the strategy", "build a plan"), matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	The orchestration framing is a distinct niche, but the universal scope ("any complex task", "any multi-step problem") creates real overlap risk with many planning/analysis skills.	3 / 5
	Total	18 / 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-data
Path: data/00-meta-chain-flow-150/SKILL.md
Commit: a1e9f44

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