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

78%

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/skills/scaffolding_templates/plugin-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, terse skill body with concrete commands, validation gates, failure-mode handling, and a genuinely one-level-deep reference bundle. The main defect is navigational: five of the declared reference paths (the external Infrastructure links, plus a bare `assets/` entry) do not resolve, which undermines the otherwise good progressive-disclosure layout.

Suggestions

Fix or inline the three external `../../../../../Infrastructure/references/...` links — they do not resolve from this skill's location; either copy the needed guidance into `references/` or correct the relative paths, since two "Read when" bullets currently dead-end.

Replace the bare `assets/` entry in the References list with the actual files (`assets/plugin-creator.png`, `assets/plugin-creator-small.svg`) and a note on when each is needed.

Deduplicate the reference routing: the Workflow section and the "Read when" bullets both enumerate the same files — keep one purpose-labeled routing list to save tokens.

DimensionReasoningScore

Conciseness

The body is directive and mostly lean — constraint bullets like "folder name must equal manifest `name`" and "redact secrets and tokens in generated examples" assume competence and explain nothing Claude already knows. Minor trimmable redundancy remains: the Workflow section and the "Read when" bullets repeat the same reference targets, and dense policy phrasing ("context-disposition policy", "budget posture") costs re-reading.

4 / 5

Actionability

The Validation section gives two copy-paste commands plus a fail-fast rule, and the body points to references/workflow.md which carries the executable scaffold commands (create_basic_plugin.pyw with --with-marketplace/--with-hooks/--path/--force). The primary creation command is one reference away rather than in the body, and Inputs/Outputs are specified concretely, leaving only minor gaps.

4 / 5

Workflow Clarity

The sequence (normalize name → classify posture → create root/manifest → optional surfaces → marketplace update → move-not-copy adoption) lives in references/workflow.md with a validation gate in the body ("stop at first failed gate and report blocker text") and error-recovery guidance ("Report the exact blocker and the smallest safe next action"). The full step sequence is delegated rather than inline and there is no explicit re-validate loop, which keeps it just below anchor 5.

4 / 5

Progressive Disclosure

The overview-to-references split is real and well signaled for bundled files (workflow.md, factory-governance-spine.md, contract.yaml, evals.yaml, task-profile.json, plugin-json-spec.md all exist, with purpose-labeled "Read when" bullets). However, the ../../../../../Infrastructure/... paths referenced in the "Read when" section and three References entries do not resolve to any actual file in or above this bundle, so navigation to those targets fails; the bare `assets/` entry is also underspecified.

3 / 5

Total

15

/

20

Passed

Description

78%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, concrete deliverables, and an explicit "Use when" trigger clause covering both creation and adoption flows. Its weaknesses are mild jargon density ("traceability or evidence contracts for non-trivial adoption") and a few missing natural trigger synonyms.

DimensionReasoningScore

Specificity

"Scaffold Codex plugin packages with deterministic manifests, marketplace metadata, and traceability or evidence contracts" names the domain plus several concrete deliverables (manifests, marketplace metadata, traceability contracts), but coverage stops short of comprehensive — the acting verbs are essentially just "scaffold", and "traceability or evidence contracts for non-trivial adoption" is partly abstract.

4 / 5

Completeness

Both parts are explicit: the "what" (scaffold plugin packages with manifests/marketplace/traceability contracts) and a literal "Use when creating plugin roots or adopting existing skills into plugin ownership" clause. The "what" leans jargon-heavy ("deterministic manifests", "traceability or evidence contracts"), so it is clear but not maximally concrete — above anchor 4's midpoint but not fully matching anchor 5's crisp concrete-phrase standard.

4 / 5

Trigger Term Quality

Natural trigger phrases are present — "creating plugin roots", "adopting existing skills into plugin ownership", "marketplace metadata" — which map well to how a user would phrase a scaffolding request. A few natural variants are missing (e.g. "new plugin", "plugin manifest", `.codex-plugin`), keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Codex plugin scaffolding and skill-adoption moves) with distinct triggers that a general skill-authoring or plugin-usage skill would not claim, so conflict risk is minimal.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

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.