od-plugin-authoring

Guided scenario for creating an Open Design plugin folder that can be installed into My plugins.

Quality

64%

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/_official/scenarios/od-plugin-authoring/SKILL.md

Quality

Content

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

The body is concise, well-structured, and appropriately scoped for a short scenario skill, with clear sequencing and a finishing checkpoint. The main gap is the absence of an explicit validation step despite referencing a schema, and a few outcome-style instructions that could be made more concrete.

Suggestions

Add an explicit validation step, e.g. 'Validate open-design.json against docs/schemas/open-design.plugin.v1.json before finishing; fix and re-validate on errors.'

Replace outcome-style instructions ('clear agent instructions', 'valid plugin metadata') with concrete requirements or a minimal inline example of the manifest fields.

Make the 'clear agent instructions' expectation explicit by listing the sections the generated SKILL.md must contain.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what a plugin is and every line is actionable guidance.	3 / 3
Actionability	Guidance names concrete files, a schema path, and id-character rules, but several items describe desired outcomes ('clear agent instructions', 'valid plugin metadata') rather than exact steps, with no executable artifact.	2 / 3
Workflow Clarity	Steps are sequenced as outcome → rules → shape → finish with a readiness/next-action checkpoint, but there is no explicit validation step despite pointing Claude at a schema file.	2 / 3
Progressive Disclosure	The short body is organized into clear sections with appropriately scoped one-level references to external spec docs, and there are no nested or broken bundle references.	3 / 3
	Total	10 / 12 Passed

Description

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

The description clearly conveys a distinct, product-specific outcome but is missing explicit 'when to use' trigger guidance and lists only one concrete action. Adding a 'Use when…' clause and a couple more natural trigger terms would raise it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to build or create their own Open Design plugin.'

Broaden trigger terms with natural variations like 'make/build a plugin', 'custom plugin', or 'plugin for Open Design'.

List one or two more concrete actions (e.g. 'scaffold the folder, write plugin metadata, validate the manifest') to improve specificity.

Dimension	Reasoning	Score
Specificity	It names a concrete deliverable ('creating an Open Design plugin folder') and outcome ('installed into My plugins'), but lists only one action rather than multiple specific concrete actions.	2 / 3
Completeness	The 'what' is clearly stated, but there is no 'Use when…' trigger clause, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	'Open Design plugin' and 'My plugins' are natural product terms, but coverage is narrow and omits common variations like 'build/make a plugin' or 'custom plugin'.	2 / 3
Distinctiveness Conflict Risk	The product-specific framing ('Open Design plugin folder', 'My plugins') defines a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: plugins/_official/scenarios/od-plugin-authoring/SKILL.md
Commit: f2760fd

Reviewed: 6 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.