build-composition

Use once there is a confirmed composition plan, to create it. Scaffolds the plugin, authors or restructures the skills, and adds the rules, hooks, MCP servers, or commands the plan called for. Uses the CLI to scaffold the plugin, then authors the planned composition.

1.31x

Quality

75%

Does it follow best practices?

Impact

95%

1.31x

Average score across 9 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

88%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 strong, well-structured skill that provides highly actionable guidance for building plugin compositions. Its greatest strengths are the concrete CLI commands with gotcha callouts (e.g., `--workspace` not being parsed from `--name`), the thorough validation workflow with explicit file-presence assertions, and clear warnings about common pitfalls like mis-nested skills. Minor improvements could come from trimming some explanatory passages and confirming that referenced files exist in the bundle.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient and assumes Claude's competence. There's some verbosity in explanations (e.g., explaining why `tessl skill new` shouldn't be used inside a plugin with detailed rationale), but most of it earns its place by preventing real pitfalls. Minor tightening possible in a few spots.	4 / 5
Actionability	Highly actionable with copy-paste ready bash commands, exact CLI flags and their gotchas, specific file paths, and concrete validation scripts. The skill covers common cases (standalone skill, plugin, hook-only, MCP-only) with executable guidance for each.	5 / 5
Workflow Clarity	Clear 6-step sequence with explicit validation in step 5 that includes both lint AND pack checks, a feedback loop for missing files, and a concrete assertion script. The workflow also includes security review checkpoints for hooks/MCP servers and clear stop conditions. The destructive/batch concern is well-addressed with the archive inspection and per-file verification.	5 / 5
Progressive Disclosure	Good structure with clear references to `references/plugin-anatomy.md`, `references/shaping-and-decomposition.md`, and `references/hooks-and-mcp.md` for deeper content. However, no bundle files were provided to verify these references exist, and some detailed content (like the temporary seed workaround and the mis-nesting explanation) could arguably be pushed to reference files. The overall organization is logical with numbered steps serving as clear sections.	4 / 5
	Total	18 / 20 Passed

Description

62%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 reasonably clear purpose — executing a confirmed composition plan by scaffolding plugins and authoring skills — but relies on domain-specific jargon that may not match natural user language. The 'when' trigger is present but could be more explicit with concrete trigger phrases. The specificity of actions is moderate; listing concrete outputs or file types would strengthen it.

Suggestions

Add natural trigger phrases in a 'Use when...' clause, e.g., 'Use when the user says to execute, implement, or build the composition plan, or when a plan has been finalized and needs to be created.'

Include more concrete action details and expected outputs, e.g., 'Creates plugin directory structure, writes skill .md files, configures hook YAML, registers MCP server entries.'

Add synonyms and natural language variations for key terms, e.g., 'build a plugin', 'set up skills', 'implement the plan'.

Dimension	Reasoning	Score
Specificity	Names the domain (plugin/composition creation) and lists several actions (scaffolds plugin, authors/restructures skills, adds rules/hooks/MCP servers/commands), but the actions are somewhat generic within the composition domain and lack concrete detail about what each step entails.	3 / 5
Completeness	The 'what' is reasonably clear (scaffolds plugins, authors skills, adds rules/hooks/etc.). The 'when' is present ('once there is a confirmed composition plan'), though it's somewhat implicit and relies on understanding what a 'confirmed composition plan' means rather than providing explicit trigger phrases with a 'Use when...' clause.	4 / 5
Trigger Term Quality	Includes some relevant terms like 'scaffold', 'plugin', 'skills', 'rules', 'hooks', 'MCP servers', 'commands', and 'CLI', but these are fairly technical. Missing natural user phrases like 'create a plugin', 'build a composition', 'set up a new skill'. The term 'composition plan' is domain-specific and may not match how users naturally phrase requests.	3 / 5
Distinctiveness Conflict Risk	The description carves out a fairly specific niche — executing a confirmed composition plan by scaffolding plugins and authoring skills. The prerequisite of a 'confirmed composition plan' helps distinguish it from planning-phase skills. Minor overlap risk with general plugin creation or skill authoring tools.	4 / 5
	Total	14 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

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

Reviewed: 1 day 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.