community-import-smoke-test

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

Quality

68%

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

82%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 concise, well-structured, and gives concrete actionable guidance for a simple instruction-only skill. Its only notable gap is an unreferenced bundle file and the absence of explicit validation checkpoints.

Dimension	Reasoning	Score
Conciseness	The ~15-line body is lean, assumes Claude's competence, and never explains concepts Claude already knows; every line carries guidance or a constraint.	5 / 5
Actionability	Concrete, actionable guidance is given (enumerated path types and explicit receipt fields), and as an instruction-only skill absent code is not penalized; held at 4 because no exact output format is specified.	4 / 5
Workflow Clarity	A clear numbered sequence (identify path, produce receipt, keep output small) is present; it is a non-destructive smoke test so the destructive-cap does not apply, but no explicit validation checkpoint keeps it below 5.	4 / 5
Progressive Disclosure	The short body is well-organized for a simple skill, but the bundled assets/import-checklist.md exists and is never referenced from the body, a minor navigation gap below the 5 anchor.	4 / 5
	Total	17 / 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 states a clear, distinct purpose but omits any 'Use when...' trigger guidance and relies on terse domain jargon without natural synonyms or file extensions. It is competent but capped by the missing trigger clause.

Suggestions

Append an explicit 'Use when...' clause with natural user phrases, e.g. 'Use when testing that Open Design can import a community plugin from a local folder, zip archive, GitHub subpath, or marketplace entry.'

Add natural synonyms and concrete terms users would say ('import', 'install', 'load', '.zip', 'marketplace plugin') to broaden trigger term coverage.

Name more than one concrete action (e.g. 'detect, import, and report on community plugins') to move specificity beyond a single verb.

Dimension	Reasoning	Score
Specificity	Names the domain ('Open Design plugin import flows') plus one concrete action ('validating'), matching the 1-2 concrete actions anchor; not a 4 because only a single action is named.	3 / 5
Completeness	Provides a clear 'what' (validating import flows) but no 'Use when...' trigger clause, which the guidelines cap at 3; the anchor example matches this pattern exactly.	3 / 5
Trigger Term Quality	Relevant keywords ('Open Design', 'plugin', 'import') are present but terse and jargon-leaning, with no synonyms or file extensions; matches 'some relevant keywords, missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Carves a distinct niche (Open Design community plugin import validation) with only minor overlap risk against other plugin-handling skills; not 5 because the triggers are not maximally distinct.	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/import-smoke-test/SKILL.md
Commit: 1a7a23d

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