CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is plugin-builder in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

41%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 well-scaffolded with concrete commands, clear sequences, and strong validation culture, but it is massively over-padded and ships references to files that do not exist — most critically the generate_marketplace.py script that Operation 3 and the entire distribution workflow depend on. The skill would be dramatically more reliable and cheaper to load after aggressive trimming and fixing the bundle to match its documentation.

Suggestions

Cut the 'Common Mistakes' catalog and 'Quick Reference' section (~400 lines): JSON trailing commas, semver, README value, and kebab-case are knowledge Claude already has, and the per-operation sections already contain every command shown there; move genuine error catalogs into references/validation-rules.md.

Fix the bundle/doc mismatch: either add scripts/generate_marketplace.py, the templates/ files, and references/distribution-guide.md + component-packaging-guide.md, or remove Operations 3 and all links to them — currently the marketplace/distribution workflow, a core advertised capability, is unexecutable.

Normalize and verify paths: commands mix '/path/to/plugin-builder/scripts/init_plugin.py' with 'scripts/init_plugin.py' relative forms, and every See Also link should resolve to a real file; move the full plugin.json/marketplace.json examples into the existing schema reference files to shrink SKILL.md.

DimensionReasoningScore

Conciseness

At ~1430 lines / 35KB the body is severely verbose: it explains concepts Claude already knows ("JSON doesn't allow trailing commas", semver MAJOR/MINOR/PATCH breakdown, why a README matters, what kebab-case is), prints full mock interactive transcripts, and the Quick Reference section restates every command and JSON example already shown per-operation. This matches the anchor-1 'heavily padded, extensively explains known concepts' profile, well beyond the 'several unnecessary explanations' of anchor 2.

1 / 5

Actionability

Commands are concrete and flag-complete for four real scripts (init_plugin.py, generate_manifest.py, validate_plugin.py, package_skills.py), but Operation 3 is built entirely on scripts/generate_marketplace.py which does not exist in the bundle, five links point to a nonexistent templates/ directory, and references/distribution-guide.md and references/component-packaging-guide.md are missing — following the doc for marketplace setup fails immediately. Not 4: these are missing key details, not minor gaps; not 2: the majority of operations are genuinely executable.

3 / 5

Workflow Clarity

Operations are clearly sequenced with explicit validation checkpoints, exit codes, error/FIX pairs, pre-publish checklists, and fix-then-revalidate loops ("Fix errors above before distributing plugin", "Only proceed when validation passes" behavior in the workflow). Not 5: the end-to-end distribution workflow breaks at step 3 because the marketplace-generation step depends on the missing script, so the full pipeline cannot be followed as written.

4 / 5

Progressive Disclosure

Structure exists (per-operation sections, See Also blocks, a References section, three real reference files), but ~600 lines that belong in separate files are inlined (the 8-entry Common Mistakes catalog, the duplicated Quick Reference, full manifest/marketplace JSON examples), and 7 of the referenced bundle paths are broken (templates/ x5, distribution-guide.md, component-packaging-guide.md), undermining navigation. Not 4: broken links and heavy inlining exceed 'minor organization gaps'; not 2: references are clearly signaled, not buried.

3 / 5

Total

11

/

20

Passed

Description

83%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 description: third-person voice, concrete action list, and an explicit 'Use when' clause with natural trigger phrases covering creation, packaging, validation, and distribution. Only minor improvements possible — adding synonyms (publish, share) and literal artifact names (plugin.json, marketplace.json).

DimensionReasoningScore

Specificity

"Automate Claude Code plugin creation, packaging, validation, and distribution" plus "generating manifests, setting up marketplaces" lists several specific actions with minor gaps. Not 5: the actions stay at the verb/domain level rather than fully concrete file-level operations (e.g., generating plugin.json/marketplace.json appears only as 'generating manifests'); not 3: coverage clearly exceeds 1-2 actions.

4 / 5

Completeness

Explicitly answers both: "Automate Claude Code plugin creation, packaging, validation, and distribution" (what) and "Use when creating plugins... or distributing skill collections" (when) with concrete trigger phrases, matching the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Triggers like "creating plugins, packaging skills, generating manifests, validating plugin structure, setting up marketplaces" are natural phrases users would say. Not 5: missing common synonyms such as "publish", "share", or literal artifact names (plugin.json, marketplace.json) that a user might type verbatim.

4 / 5

Distinctiveness Conflict Risk

"Claude Code plugin" is a clear niche with distinct triggers (manifests, marketplaces, plugin validation). Not 5: "packaging skills" and "distributing skill collections" carry minor overlap risk with skill-creation/authoring skills a user might invoke instead.

4 / 5

Total

17

/

20

Passed

Validation

75%

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

CriteriaDescriptionResult

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

.claude/skills/plugin-builder/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.