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

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./Plugins/plugin-factory/fixtures/budget-archive/2026-04-21/deferred-store/skills/scaffolding_templates/plugin-creator/SKILL.md

Quality

Content

50%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-structured with clear sections, concrete validation commands, and good reference signaling, but it is undermined by a duplicated line, a missing primary workflow reference, and a references/ directory that does not exist in the actual bundle. These gaps pull actionability, workflow clarity, and progressive disclosure down to the midpoint.

Suggestions

Remove the duplicated context-disposition policy line (the identical lines 45-46) and tighten the verbose OpenAI-style design-contract paragraph.

Restore or create the missing references/ files — especially references/workflow.md, which the Workflow section names as 'the detailed scaffold procedure' — so the disclosure paths resolve.

Inline a minimal concrete scaffold sequence (init plugin.json, set required policy/category fields, validate) in the body so the core procedure is actionable even before reading the external reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete sectioning, but the context-disposition policy line is duplicated verbatim (lines 45-46) and the OpenAI-style design-contract paragraph is padded with jargon ('root-visible surface', 'side-effect classes early') that could be tightened.	3 / 5
Actionability	Provides concrete validation commands, examples, and required behaviors, but the primary scaffold procedure is delegated to 'references/workflow.md' which does not exist in the bundle, leaving the core execution path inaccessible.	3 / 5
Workflow Clarity	A validation checkpoint exists ('Fail fast: stop at first failed gate and report blocker text') and Inputs/Outputs/Validation are sequenced, but the actual multi-step scaffold workflow is offloaded to a missing reference, leaving gaps in the sequence.	3 / 5
Progressive Disclosure	References are well-signaled with a 'Read when:' navigation block and the scripts/assets bundle dirs exist, but the entire references/ directory (workflow.md, factory-governance-spine.md, contract.yaml, evals.yaml, task-profile.json, plugin-json-spec.md) is absent, so the disclosure paths are broken.	3 / 5
	Total	12 / 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, third-person description that explicitly pairs a concrete capability statement with a 'Use when...' trigger, covering both what and when. It is held back only by some abstract jargon and minor overlap with adjacent scaffolding/hardening skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Scaffold Codex plugin packages with deterministic manifests, marketplace metadata, and traceability or evidence contracts' — but terms like 'traceability or evidence contracts for non-trivial adoption' are somewhat abstract, leaving minor coverage gaps versus a fully comprehensive list.	4 / 5
Completeness	Clearly answers both 'what' (scaffold plugin packages with deterministic manifests, marketplace metadata, evidence contracts) and 'when' ('Use when creating plugin roots or adopting existing skills into plugin ownership') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('plugin roots', 'existing skills', 'plugin ownership', 'marketplace') with a concrete 'Use when...' trigger, though some common variations or synonyms are missing and a few phrases lean jargon-heavy.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Codex-plugin-scaffolding niche with distinct triggers, but has minor overlap risk with the related [[skill-builder]] skill that the body itself routes hardening work to.	4 / 5
	Total	17 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 3 missing, 1 suspicious	Warning
referenced_paths_exist	Referenced path issues: 10 missing	Warning

	Total	13 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Plugins/plugin-factory/fixtures/budget-archive/2026-04-21/deferred-store/skills/scaffolding_templates/plugin-creator/SKILL.md
Commit: 2f91362

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.