build-composition

Use once there is a confirmed composition plan, to create it. Scaffolds the plugin, authors or restructures the skill(s), decomposes anything too big, and adds any rules or MCP servers the plan called for. Uses the CLI to scaffold the plugin, then adds further skills by hand.

1.42x

Quality

72%

Does it follow best practices?

Impact

94%

1.42x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

Quality

Content

77%

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

This is a strong, actionable skill with a clear multi-step workflow and excellent validation steps including a bash script to verify pack completeness. The content is mostly concise but has some areas of over-explanation (particularly around the `tessl skill new` anti-pattern and security review details). Progressive disclosure is reasonable with two referenced files, though the absence of bundle files makes it hard to fully validate the reference structure.

Suggestions

Consider moving the detailed explanation of why `tessl skill new` nests incorrectly inside plugins into a reference file, keeping only the directive 'create the file directly' in the main body.

The security review paragraph in step 5 could be tightened—the parenthetical about `--workspace` on `tessl review run` repeats a pattern already established earlier.

Dimension	Reasoning	Score
Conciseness	Generally efficient and assumes Claude's competence, but some sections could be tightened. The lint vs pack explanation and the security review paragraph are somewhat verbose. The warning about `tessl skill new` nesting is valuable but slightly over-explained.	2 / 3
Actionability	Provides concrete, executable CLI commands, specific bash validation scripts, exact file paths, and clear do/don't instructions. The pack-and-verify bash snippet is copy-paste ready and the CLI flags are explicitly documented with gotchas.	3 / 3
Workflow Clarity	Clear numbered sequence (scaffold → add skills → author → add primitives → validate → hand off) with explicit validation checkpoints in step 5 including a feedback loop (lint AND pack, then assert each file). The 'When to stop' section provides a clear completion criterion.	3 / 3
Progressive Disclosure	References to `references/plugin-anatomy.md` and `references/shaping-and-decomposition.md` are well-signaled and one-level deep. However, no bundle files were provided to confirm these exist, and some inline content (like the detailed explanation of why `tessl skill new` fails inside plugins) could potentially be pushed to a reference file to keep the main skill leaner.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 does well at specifying when to use the skill ('once there is a confirmed composition plan') and lists several actions, giving it good completeness. However, the actions described use somewhat jargon-heavy language that may not match natural user phrasing, and some terms like 'decomposes anything too big' are vague. The description could be more distinctive by clarifying its unique scope relative to planning or editing skills.

Suggestions

Add more natural trigger terms a user might say, such as 'build plugin', 'create skills', 'implement composition', 'set up MCP server'.

Make the specific actions more concrete—e.g., instead of 'decomposes anything too big', say 'splits skills exceeding size limits into smaller focused skills'.

Dimension	Reasoning	Score
Specificity	The description names several actions—scaffolding the plugin, authoring/restructuring skills, decomposing large items, adding rules or MCP servers—but these are somewhat domain-specific and not fully concrete (e.g., 'decomposes anything too big' is vague). It sits between vague and fully specific.	2 / 3
Completeness	The description explicitly answers both 'what' (scaffolds plugin, authors/restructures skills, decomposes large items, adds rules/MCP servers) and 'when' ('once there is a confirmed composition plan'). The trigger condition is clearly stated upfront.	3 / 3
Trigger Term Quality	It includes some relevant terms like 'composition plan', 'scaffold', 'plugin', 'skill', 'rules', 'MCP servers', and 'CLI', but these are fairly technical/jargon-heavy. A user might say 'create the plugin' or 'build the composition' but many natural variations are missing.	2 / 3
Distinctiveness Conflict Risk	The description carves out a niche around executing a confirmed composition plan, which helps distinguish it. However, terms like 'skill', 'plugin', 'rules', and 'MCP servers' could overlap with other skills related to plugin management, skill editing, or configuration tasks.	2 / 3
	Total	9 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: tesslio/product-plugins
Path: plugin-creator/skills/build-composition/SKILL.md
Commit: 320f749

Reviewed: 2 days 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.