plugin-builder

Automate Claude Code plugin creation, packaging, validation, and distribution. Use when creating plugins, packaging skills, generating manifests, validating plugin structure, setting up marketplaces, or distributing skill collections.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/plugin-builder/SKILL.md

Quality

Content

63%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 is highly actionable with executable commands and strong validation workflows, but it is significantly over-long with repeated content and contains broken references to a nonexistent templates/ directory and missing reference files.

Suggestions

Create the missing templates/ files (plugin.json.minimal, plugin.json.standard, marketplace.json.minimal, marketplace.json.multi) and the missing references/component-packaging-guide.md and references/distribution-guide.md, or remove the dangling links.

Trim the duplicated content — JSON templates, common tool-set tables, and validation categories each appear 2–3 times across Operations, Best Practices, Common Mistakes, and Quick Reference; keep one canonical copy and link to it.

Cut concept explanations Claude already knows (e.g. 'Plugins are distributable packages that extend Claude Code') and move exhaustive manifest/schema detail into the existing reference files to reduce the body toward a lean overview.

Dimension	Reasoning	Score
Conciseness	At ~1430 lines the body is noticeably verbose: it re-explains what plugins are, repeats JSON templates, tool-set tables, and validation categories in multiple sections, and peppers time-sensitive '2025 schema' phrasing throughout.	2 / 5
Actionability	Provides fully executable, copy-paste-ready commands (e.g. 'python scripts/init_plugin.py my-plugin --description ...' and 'python scripts/validate_plugin.py /path/to/my-plugin --check structure') plus complete JSON/YAML templates covering the common cases.	5 / 5
Workflow Clarity	Operations 1–5 are clearly sequenced with checklists, exit codes, and a dedicated validation operation including error/FIX feedback loops; minor gaps are that the init/manifest/marketplace operations lack an inline validate-then-proceed checkpoint.	4 / 5
Progressive Disclosure	Structure with 'See Also' pointers to references/ is good, but navigation is partly broken: the entire templates/ directory (4 referenced files) does not exist and 2 of 5 referenced reference files (component-packaging-guide.md, distribution-guide.md) are missing, while large reference-style content is inlined in the main file.	3 / 5
	Total	14 / 20 Passed

Description

88%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, well-formed description that clearly states what the skill does and when to invoke it, with concrete actions and third-person voice. Minor room to add synonyms and tighten a few broad trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions — 'plugin creation, packaging, validation, and distribution' plus 'generating manifests' and 'setting up marketplaces' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (Automate ... creation, packaging, validation, and distribution) and 'when' (Use when creating plugins ... or distributing skill collections) with concrete trigger phrases in third person.	5 / 5
Trigger Term Quality	Good natural-phrase coverage ('creating plugins', 'packaging skills', 'generating manifests', 'setting up marketplaces', 'distributing skill collections'), though a few plausible terms like 'publishing' or 'installing' are absent.	4 / 5
Distinctiveness Conflict Risk	The plugin/marketplace niche is mostly distinct with minimal conflict risk, though broad terms like 'packaging skills' and 'distributing skill collections' could overlap with a generic packager.	4 / 5
	Total	18 / 20 Passed

Validation

75%

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 — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1432 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
relative_links	Relative link issues: 7 missing	Warning
referenced_paths_exist	Referenced path issues: 10 missing	Warning

	Total	12 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/plugin-builder/SKILL.md
Commit: 93ed392

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.