community-registry-starter

A small community registry starter plugin used to verify OpenDesign marketplace install flows.

Quality

54%

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/community/registry-starter/SKILL.md

Quality

Content

55%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 maximally concise but nearly empty: it declares the plugin's purpose and nothing else. There is no actionable guidance, no usage steps, and no structure beyond a single heading, leaving Claude with nothing concrete to execute.

Suggestions

Add concrete, executable guidance — e.g. the exact commands or steps to validate registry search, install, and provenance flows using this plugin.

Include a short worked example (what a successful install/provenance check looks like) so the 'minimal community example' is actually usable.

Organize the body into at least a purpose section and a usage section so the single-purpose skill has clear, well-organized sections.

Dimension	Reasoning	Score
Conciseness	The body is two lean sentences with zero padding, no explanations of concepts Claude already knows, and every token earning its place, matching the 'lean and efficient' anchor exactly.	5 / 5
Actionability	The body only states purpose ('Use this plugin as a minimal community example when validating registry search, install, and provenance flows') with no commands, code, or steps, fitting between anchors 1 and 2: it names three specific flows (concrete-ish guidance) but gives no executable direction.	2 / 5
Workflow Clarity	No sequence, checkpoints, or defined steps exist; the single stated action is vague ('use as a minimal community example'), so the simple-skill exception (which requires an unambiguous single action) does not lift it to 5.	2 / 5
Progressive Disclosure	The skill is trivially short with no bundle files (references/, scripts/, assets/ are absent), so nothing needs external placement; however, beyond a title and one paragraph there are no organized sections, leaving minor structure gaps that keep it below 5.	4 / 5
	Total	13 / 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 and third-person with a clear, narrow niche, but it reads as a factual label rather than a trigger-oriented skill description. It lacks a 'Use when...' clause and the natural trigger phrases users would say, capping completeness and trigger-term quality at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when testing marketplace plugin installation, registry search, or provenance verification flows.'

Enumerate the concrete capabilities (search validation, install validation, provenance checks) so the 'what' is comprehensive rather than a single bundled action.

Include natural user phrases and synonyms users would actually say ('install a plugin from the registry', 'marketplace install test') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('community registry starter plugin') and one concrete action ('verify OpenDesign marketplace install flows'), matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor; it does not list several specific actions, so 4 is not warranted.	3 / 5
Completeness	The 'what' is clear (verify OpenDesign marketplace install flows) but there is no 'Use when...' clause or equivalent trigger guidance, which the judging guidelines cap at 3; not 4 because the 'when' is entirely absent rather than just imprecise.	3 / 5
Trigger Term Quality	Relevant keywords exist ('registry', 'marketplace', 'install', 'plugin') but natural user phrases and common variations/synonyms are missing, matching 'some relevant keywords but missing common variations'; not 2 because the keywords are domain-relevant rather than generic.	3 / 5
Distinctiveness Conflict Risk	The niche is specific (OpenDesign marketplace registry verification) with minimal overlap risk, fitting 'mostly distinct; minor overlap risk'; not 5 because the description provides no explicit distinct trigger phrases.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: nexu-io/open-design
Path: plugins/community/registry-starter/SKILL.md
Commit: 1b47e60

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