CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

63%

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 ./Plugins/plugin-factory/fixtures/budget-archive/2026-04-21/deferred-store/skills/scaffolding_templates/plugin-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 a well-organized policy overview with real validation gates and failure-mode handling, but its progressive-disclosure design is unfulfilled: all referenced detail files are absent from the bundle, so the actual workflow and governance detail cannot be reached. Combined with a duplicated line and environment-specific validation paths, the skill reads as a stub whose details were lost.

Suggestions

Restore or create the references/ files (workflow.md, factory-governance-spine.md, contract.yaml, evals.yaml, task-profile.json, plugin-json-spec.md) so the signaled navigation actually resolves.

Remove the duplicated "Apply the context-disposition policy" line and the motivational "Remember" filler to tighten the body.

Replace the environment-specific validation commands (python3 Skills/skill-builder/Infrastructure/scripts/...) with paths relative to the skill bundle so they are copy-paste runnable.

DimensionReasoningScore

Conciseness

The body is mostly lean and well-sectioned, but contains a verbatim duplicated line ("Apply the context-disposition policy..." appears twice), motivational filler ("The agent is capable of extraordinary plugin work..."), and a "Read when" list that partially repeats the Workflow section. These are unnecessary tokens, fitting anchor 3 rather than the clean anchor 4.

3 / 5

Actionability

There are concrete elements (validation commands, deterministic rules like "folder name must equal manifest name", request examples), but the core scaffold procedure is delegated to "references/workflow.md" which does not exist in the bundle, and the validation commands use environment-specific absolute paths that are not runnable as-is. Key executable detail is missing, matching anchor 3 rather than 4.

3 / 5

Workflow Clarity

A validation checkpoint is explicitly present (quick_validate.py plus the lint script with "Fail fast: stop at first failed gate and report blocker text"), which avoids a lower score. However, the actual step sequence lives only in the missing references/workflow.md, so the multi-step process (including the semi-destructive skill-adoption move) cannot be followed from the skill as bundled; checkpoints exist but the sequence is unreachable, fitting anchor 3.

3 / 5

Progressive Disclosure

Scored against the actual bundle: the body's reference signaling is well designed (a "Read when" list plus a References section), but every referenced detail file is missing — references/workflow.md, factory-governance-spine.md, contract.yaml, evals.yaml, task-profile.json, plugin-json-spec.md, and the out-of-bundle ../../../../../Infrastructure path all do not exist. Navigation collapses in practice because the signaled references are dangling, placing it below anchor 3 where references at least resolve.

2 / 5

Total

11

/

20

Passed

Description

67%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.

The description answers both what and when with an explicit Use-when clause and names concrete artifacts, but leans on internal jargon ("plugin roots", "traceability or evidence contracts for non-trivial adoption") that weakens natural trigger matching. Overall solid but with room to make trigger phrasing user-facing.

Suggestions

Replace internal jargon such as "plugin roots" and "traceability or evidence contracts" with natural user phrasing like "create a plugin package" or "move an existing skill into a plugin".

Broaden trigger coverage with common variations users would actually say (e.g., "make a plugin", "add my skill to the marketplace", "plugin.json manifest").

DimensionReasoningScore

Specificity

"Scaffold Codex plugin packages with deterministic manifests, marketplace metadata, and traceability or evidence contracts" names the domain plus several concrete artifacts (manifests, marketplace metadata, evidence contracts). It falls short of 5 because coverage of the actual actions (scaffolding steps, adoption/move handling) is incomplete, and is above 3 because it lists more than 1-2 specific deliverables.

4 / 5

Completeness

Both parts are present: a clear "what" ("Scaffold Codex plugin packages with deterministic manifests, marketplace metadata...") and an explicit "Use when creating plugin roots or adopting existing skills into plugin ownership" clause, so it clears the 3-cap for missing trigger guidance. It is not 5 because the when-clause triggers are jargon phrases rather than concrete wording a user would actually say.

4 / 5

Trigger Term Quality

"plugin", "marketplace", and "adopting existing skills" are terms a user might say, but "plugin roots", "deterministic manifests", and "traceability or evidence contracts" are internal jargon users would not naturally use. Some relevant keywords exist, but common natural variations ("create a plugin", "turn my skill into a plugin") are missing, matching anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

"Codex plugin packages" plus marketplace/adoption framing carves a fairly distinct niche with low confusion risk against unrelated skills. Minor overlap remains with generic plugin-creation or marketplace tooling (the word "plugin" alone is broad), so it fits anchor 4 rather than the fully-distinct anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

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.