community-import-smoke-test

A portable community plugin for validating Open Design plugin import flows.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/community/import-smoke-test/SKILL.md

Quality

Content

65%

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 and well-structured, but it is an instruction-only skill whose guidance stops short of a concrete receipt template, lacks an explicit verification checkpoint despite being about inspecting states, and leaves its bundle checklist unreferenced.

Suggestions

Add a concrete receipt template or example output so the guidance is copy-paste ready (e.g. a fenced block showing name, source kind, files detected, note).

Insert an explicit verification step, e.g. 'Confirm install, apply, and provenance states render correctly in the UI before reporting success,' to add a feedback checkpoint.

Link the bundle file from the body, e.g. 'See [import-checklist.md](assets/import-checklist.md) for the required-file checklist,' so progressive disclosure is signaled.

Dimension	Reasoning	Score
Conciseness	The body is lean (~20 lines), does not explain concepts Claude already knows, and every line earns its place ('Use this plugin when...', a 3-step list, and a short constraint block), matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Step 2 says to 'Produce a compact import receipt that includes the plugin name, source kind, files detected, and any user note' — concrete fields, but no template or example receipt is given, so guidance is actionable yet incomplete ('missing key details'). Not a 3 because nothing is copy-paste ready.	2 / 3
Workflow Clarity	Steps 1–3 are clearly sequenced, but for a skill whose purpose is inspecting install/apply/provenance states there is no explicit verification checkpoint — 'Keep the output intentionally small so...states are easy to inspect' is implicit, fitting 'sequence present but checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	The body is well-organized into sections, but the provided assets/import-checklist.md is never referenced or signaled from the body, matching 'references present but not clearly signaled'. Not a 3 because the one bundle file is orphaned rather than linked at one level deep.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 identifies a clear niche but is thin: it gives only one abstract action and omits any explicit 'Use when...' trigger guidance. Distinctiveness is strong, while trigger quality and completeness are capped by the missing trigger clause.

Suggestions

Append a 'Use when...' clause with natural trigger terms, e.g. 'Use when testing whether Open Design can install and apply community plugins from a local folder, zip, GitHub subpath, or marketplace entry.'

Replace the single abstract action with concrete ones the user would name, e.g. 'produce a compact import receipt and inspect install, apply, and provenance states' to raise specificity.

Add common keyword variations (e.g. 'plugin import', 'install/apply smoke test', 'marketplace entry') so the description matches language users actually say.

Dimension	Reasoning	Score
Specificity	Quotes "validating Open Design plugin import flows" name a domain and one action, but only a single abstract action is given rather than multiple concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what the plugin does but never states when Claude should use it; per the guideline a missing 'Use when...' clause caps completeness at 2 ('has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	Terms like "Open Design plugin import flows" are recognizable but lean technical and omit a natural 'Use when...' trigger and common variations, fitting 'some relevant keywords but missing common variations'. Not a 3 because no user-natural trigger phrase is present.	2 / 3
Distinctiveness Conflict Risk	The phrase "Open Design plugin import flows" carves a clear, platform-specific niche that is unlikely to conflict with other skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 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/import-smoke-test/SKILL.md
Commit: f2760fd

Reviewed: about 17 hours 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.