CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

01-meta-chain-of-skills-150

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

72

6.00x
Quality

72%

Does it follow best practices?

Impact

72%

6.00x

Average score across 3 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

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

The canonical home for this skill is 01-meta-chain-of-skills-150 in majiayu000/claude-skill-registry

SKILL.md
Quality
Evals
Security

Quality

Content

62%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 clearly sequenced, well-gated workflow with strong feedback loops and concrete commands, tables, and templates. However, it is noticeably redundant — the same status-block and plan templates repeat across multiple sections — and it inlines substantial material (route templates, examples, routing table) that belongs in separate reference files.

Suggestions

Define the EXECUTION STATUS block template once and reference it from the other sections instead of repeating it four to five times

Move the Common Route Templates, the worked dark-mode example, and the Available Skills routing table into reference files (e.g. references/routes.md, references/skills-table.md) to cut the main file roughly in half

Merge the overlapping Three Steps, Execution Protocol, and Output Format sections into a single coherent flow to eliminate restated scan/plan/execute content

DimensionReasoningScore

Conciseness

The EXECUTION STATUS block template is repeated roughly five times (in Three Steps, Output Format, Step Completion Format, and Examples), and the Execution Protocol / Output Format / Examples sections all restate the same scan→plan→execute flow with decorative box-drawing art — several padded, redundant sections.

2 / 5

Actionability

Provides executable bash commands for skill discovery ("ls -la ./.codex/skills/ ..."), a concrete user-command table, four ready-to-use route templates, and exact output formats; minor gap in that much of the guidance is presentation mockups rather than executable instruction.

4 / 5

Workflow Clarity

SCAN→BUILD→EXECUTE→REROUTE is clearly sequenced with confirmation gates at every step, and the Failure Modes & Recovery table provides explicit detection→recovery feedback loops (retry or skip on step failure, rebuild on wrong plan, simplify when >8 steps).

5 / 5

Progressive Disclosure

No bundle files exist and everything is inlined in one ~380-line file: the 18-skill routing table, four route templates, and a full worked example would fit naturally in reference files. Section headers are clear, but there is no reference structure at all.

3 / 5

Total

14

/

20

Passed

Description

67%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 clearly states its capabilities in third person with an explicit trigger clause, covering both what and when. Its main weaknesses are generic, overly broad trigger terms that create conflict risk with many sibling orchestration skills, and a missing mention of the reroute/rebuild capability.

Suggestions

Narrow the trigger terms to distinguish this meta-orchestration skill from siblings, e.g. "Use when a task needs chaining multiple existing skills into a confirmed step-by-step plan, rather than a single skill"

Mention the reroute/rebuild capability ("может перестроить план") so the capability list is comprehensive

Add natural user phrasings such as "multi-step workflow", "orchestrate skills", or "step-by-step plan with confirmation" to improve trigger recall

DimensionReasoningScore

Specificity

"Сканирует доступные skills, создает план выполнения и идет шаг за шагом с подтверждением каждого этапа" lists several concrete actions (scan skills, build plan, step-by-step execution with per-stage confirmation), but omits the reroute/rebuild capability, leaving a minor coverage gap.

4 / 5

Completeness

Both what ("Сканирует... создает план... идет шаг за шагом с подтверждением") and when ("Triggers on complex tasks, multi-step work, or when structured execution is needed") are explicitly present, but the when clause is generic and could be more specific about concrete user situations.

4 / 5

Trigger Term Quality

"Triggers on complex tasks, multi-step work, or when structured execution is needed" uses natural user phrasing, but misses common synonyms and variations such as "workflow", "orchestrate", or "break this down into steps".

4 / 5

Distinctiveness Conflict Risk

"complex tasks, multi-step work, structured execution" is very broad — almost any non-trivial request would match, creating high overlap risk with the sibling skills the body itself lists (action-plan-150, gated-exec-150, chain-flow-150).

2 / 5

Total

14

/

20

Passed

Validation

100%

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/01-meta-chain-of-skills-150/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.