Tessl • The package manager for agent skills

Blog Docs Log inGet started

SkillPublic

od-plugin-authoring

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

Quality

75%

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

86%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 an exemplary lean instruction-only skill: concrete required outcomes, precise rules, a clear folder shape, and a closing validation-oriented readiness summary with a next-action prompt. Its only weaknesses are the absence of an explicit numbered step sequence and of a small example of the required SKILL.md/open-design.json contents.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence: three tight sections, no explanation of known concepts, and every line adds constraint or outcome information. Even the caveat "Do not create empty directories just to match the sketch" earns its place by preventing a real failure mode.	5 / 5
Actionability	Concrete, executable guidance: exact required files (SKILL.md, open-design.json with named metadata fields), a plugin-id naming rule ("lowercase letters, numbers, dashes, underscores, or dots"), spec/schema paths to follow, and a defined ready-to-install readiness summary. Minor gap: no example frontmatter or open-design.json snippet, keeping it below the fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	The flow is coherent (required outcome -> authoring rules -> folder shape -> readiness summary) and the readiness summary explicitly requires reporting "Any validation or follow-up needed before install", which acts as a final checkpoint. However, the steps are not explicitly ordered and there is no validate-fix-retry feedback loop, so it does not reach anchor 5.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files provided (references/, scripts/, assets/ are absent) and no need for external references; the referenced docs/plugins-spec.md and schema are external project documents, not nested bundle references. Sections are well organized, so per the simple-skill guidance it scores 5.	5 / 5
	Total	18 / 20 Passed

Description

53%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 is concise, specific to its niche, and clearly states what the skill does, but it completely lacks a 'when to use' trigger clause and offers limited natural trigger phrasing. Adding an explicit use-when clause with common user phrasings would raise both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to build, create, or scaffold their own OpenDesign plugin, or asks to add a custom plugin to My plugins."

Expand the 'what' with 2-3 more concrete actions, e.g. generating the plugin folder, writing SKILL.md instructions and open-design.json metadata, and validating against the plugin schema.

Include natural synonyms users would say ("make my own plugin", "plugin development", "scaffold a plugin") so the description surfaces on varied phrasings.

Dimension	Reasoning	Score
Specificity	The description names the domain ("OpenDesign plugin folder") and 1-2 concrete actions ("creating", "can be installed into My plugins"), but does not list the several specific actions needed for anchor 4. It is well above the generic-minimal anchor 2 because the actions are domain-specific, not generic.	3 / 5
Completeness	The 'what' is clearly stated ("Guided scenario for creating an OpenDesign plugin folder that can be installed into My plugins") but there is no 'Use when...' clause or equivalent trigger guidance, which the judging guidelines explicitly cap at 3. It is not a 2 because the 'what' is concrete and unambiguous.	3 / 5
Trigger Term Quality	Natural keywords like "OpenDesign plugin", "My plugins", and "creating" are present, but common variations and synonyms users would say ("build/make my own plugin", "plugin development", "write a plugin") are missing, matching the 'some relevant keywords but missing variations' anchor rather than the near-complete coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	The OpenDesign plugin-authoring niche is distinct and unlikely to trigger for unrelated skills, but triggers are only implicit in the 'what' statement and there is minor overlap risk with generic plugin-install or scaffolding skills, placing it between anchors 4 and 5.	4 / 5
	Total	13 / 20 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
Revision: 78d5637

Reviewed: 17 days ago

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.

od-plugin-authoring

Table of Contents

Is this your skill?