plugin-creator

Scaffold Codex plugin packages with deterministic manifests, marketplace metadata, and traceability or evidence contracts for non-trivial adoption. Use when creating plugin roots or adopting existing skills into plugin ownership.

Quality

71%

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 ./Plugins/plugin-factory/skills/scaffolding_templates/plugin-creator/SKILL.md

Quality

Content

57%Weight 40%Scale 1-3

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

Well-organized with strong progressive disclosure and real, one-level-deep references, but the body is somewhat padded and delegates the core executable workflow and sequence to referenced files, leaving the inline body more policy than procedure.

Suggestions

Trim padding — remove or tighten the 'Core Philosophy' bullets and the motivational 'Remember' line so every token earns its place.

Fold the redundant 'Read when' reference list into the existing Workflow/References sections to avoid restating the same paths twice.

Inline a brief numbered scaffold sequence (or at least the key steps) before pointing to workflow.md, so the body carries the workflow rather than only the validation tail.

Dimension	Reasoning	Score
Conciseness	Mostly efficient policy prose with no generic concept explanations, but it carries padding — self-evident 'Core Philosophy' bullets, a motivational 'Remember' line, and a 'Read when' block that repeats references already listed under Workflow and References.	2 / 3
Actionability	It offers concrete validation commands and concrete examples, but the primary scaffold action is delegated ('Use the detailed scaffold procedure in references/workflow.md') rather than given as inline executable guidance.	2 / 3
Workflow Clarity	Validation checkpoints are explicit ('Fail fast: stop at first failed gate', a Validation section), but the multi-step scaffold sequence itself is not laid out in the body — it lives in the referenced workflow.md.	2 / 3
Progressive Disclosure	Clear sectioned overview with well-signaled one-level-deep references (verified real files in references/, scripts/, assets/) and a 'Read when' navigation map; no deep reference chaining.	3 / 3
	Total	9 / 12 Passed

Description

85%Weight 40%Scale 1-3

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, specific description with an explicit trigger clause and a clear niche. Its main weakness is trigger phrasing that uses internal terminology ('plugin roots', 'plugin ownership') over the natural terms a user would actually say.

Suggestions

Add plain-language trigger terms a user would naturally say, e.g. 'create a plugin', 'turn a skill into a plugin', or 'package a skill as a Codex plugin'.

Consider replacing jargon like 'plugin roots' and 'non-trivial adoption' in the trigger clause with user-facing phrasing while keeping the precise terms in the body.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Scaffold Codex plugin packages with deterministic manifests, marketplace metadata, and traceability or evidence contracts' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what it does and when to use it, with an explicit 'Use when…' clause covering plugin creation and skill adoption.	3 / 3
Trigger Term Quality	The trigger 'Use when creating plugin roots or adopting existing skills into plugin ownership' is relevant but leans technical ('plugin roots', 'plugin ownership', 'non-trivial adoption') and omits common natural phrasings such as 'create a plugin'.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Codex plugin package scaffolding) with distinct triggers, making conflict with unrelated skills unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Plugins/plugin-factory/skills/scaffolding_templates/plugin-creator/SKILL.md
Commit: 46e4be2

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.