CtrlK
BlogDocsLog inGet started
Tessl Logo

plan-composition

Use once the problem and artifacts are understood, to decide the right shape for the context. Produces a short composition plan - a single skill for simple cases, or a plugin with the right mix of skills, rules, hooks, MCP servers, and commands - and confirms it with the user before anything is built.

89

1.31x
Quality

61%

Does it follow best practices?

Impact

95%

1.31x

Average score across 9 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugin-creator/skills/plan-composition/SKILL.md

The canonical home for this skill is tessl/plugin-creator

SKILL.md
Quality
Evals
Security

Quality

Content

67%Scale 1-5

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 planning skill that clearly defines decision criteria for choosing between different composition primitives (skills, rules, hooks, MCP servers). Its main strengths are clear workflow sequencing and efficient use of tokens. Its primary weakness is the lack of a concrete example plan output, which would make the 'Write the plan' step more actionable and reduce ambiguity about what the deliverable should look like.

Suggestions

Add a brief example of what a completed composition plan looks like (e.g., a 5-line sample plan showing problem, artifacts, proposed shape, and primitive assignments) to make the 'Write the plan' section more actionable.

Add explicit guidance for what happens when the user rejects or modifies the plan (e.g., 'If the user disagrees, revise the plan and re-confirm') to close the feedback loop.

DimensionReasoningScore

Conciseness

The content is efficient and well-structured. There's minor verbosity in some explanations (e.g., 'In Tessl a skill is already a minimal plugin (it gets a plugin.json), so this is not a lesser option' could be trimmed), but overall it respects Claude's intelligence and avoids over-explaining concepts.

4 / 5

Actionability

The skill provides clear decision criteria and a structured process, but it's inherently an instruction-only planning skill with no code or commands. The guidance is moderately concrete—it tells Claude what to decide and what to output—but the 'Write the plan' section is somewhat vague about the exact format or structure of the plan output. An example plan would significantly improve actionability.

3 / 5

Workflow Clarity

The workflow is clearly sequenced: choose primitive → decide shape → write plan → confirm → hand off. The 'When to stop' section provides a clear exit condition, and confirmation with the user serves as a validation checkpoint. Minor gap: no explicit guidance on what to do if the user rejects the plan (feedback loop for iteration).

4 / 5

Progressive Disclosure

The skill references [references/choosing-the-shape.md] for deeper detail on primitive selection, which is appropriate progressive disclosure. The content is well-organized with clear section headers. However, since no bundle files were provided, we can't verify the referenced file exists. The skill is appropriately sized for a single file with one reference.

4 / 5

Total

15

/

20

Passed

Description

55%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 communicates a clear role in a workflow (planning before building) and specifies the output (composition plan), but relies heavily on internal terminology rather than natural user language. The 'when' clause is process-oriented rather than trigger-oriented, and the description could benefit from more concrete trigger terms that match how users would naturally request this capability.

Suggestions

Replace internal jargon with natural trigger terms users would say, e.g., 'plan a skill', 'design a plugin', 'architect a solution', 'what skills do I need'.

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g., 'Use when the user asks to plan, design, or scope a new skill, plugin, or extension before building it.'

Clarify the concrete actions more specifically — e.g., 'Analyzes requirements, recommends skill vs. plugin structure, lists needed components (rules, hooks, MCP servers, commands), and outputs a composition plan for user approval.'

DimensionReasoningScore

Specificity

Names the domain (composition planning for skills/plugins) and describes a couple of concrete actions (produces a composition plan, confirms with user), but uses somewhat abstract language like 'right shape for the context' and 'right mix' without fully specifying what concrete steps are taken.

3 / 5

Completeness

The 'what' is reasonably clear (produces a composition plan for skills/plugins). The 'when' is present ('once the problem and artifacts are understood') but is implicit and process-oriented rather than using explicit trigger phrases a user might say. It describes a workflow stage rather than user-facing triggers.

4 / 5

Trigger Term Quality

Includes some relevant terms like 'skill', 'plugin', 'rules', 'hooks', 'MCP servers', 'commands', and 'composition plan', but these are internal/technical jargon rather than natural phrases a user would say. Missing natural trigger terms like 'design', 'plan', 'architecture', 'scaffold', or 'structure'.

2 / 5

Distinctiveness Conflict Risk

The description carves out a fairly specific niche — planning the composition of skills, plugins, hooks, etc. before building — which is distinct from actual building/coding skills. Minor overlap risk with skills related to project planning or architecture more broadly.

4 / 5

Total

13

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
tesslio/product-plugins
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.