discovery-question-form

Turn-1 discovery question form for ambiguous briefs.

Quality

60%

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/atoms/discovery-question-form/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is actionable and well-structured with a complete code example, a precise field spec, and a clear convergence condition; it is only slightly verbose in a few clarifying asides.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and avoids explaining concepts Claude already knows, but asides like 'This is assistant text parsed by the host, not a plugin GenUI surface or a native tool call' could be tightened, matching 'mostly efficient but includes some unnecessary explanation.'	2 / 3
Actionability	It provides a concrete, copy-paste-ready <question-form> example plus an exhaustive spec of each question field and allowed types, matching 'fully executable code/commands; specific examples; copy-paste ready.'	3 / 3
Workflow Clarity	This single-action skill sequences 'When to fire' -> 'Emission shape' -> 'Convergence' with an explicit completion checkpoint (an answer for every required question, and do not re-ask), so the single action is unambiguous as the scoring notes allow.	3 / 3
Progressive Disclosure	The skill is self-contained with no bundle files and is organized into clearly signaled sections (When to fire, Emission shape, Question object shape, Convergence) with no nested references, matching 'well-organized sections' for a simple single-purpose skill.	3 / 3
	Total	11 / 12 Passed

Description

35%

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 reasonably specific and distinct but reads as internal jargon rather than user-natural language and lacks an explicit 'Use when' trigger clause, capping its completeness and trigger-term quality.

Suggestions

Reword in user-natural terms, e.g. 'Ask a short set of clarifying questions when a brief is ambiguous...' so users would naturally trigger it.

Add an explicit 'Use when...' clause listing concrete triggers (e.g. missing audience, missing target medium, brief invites questions).

List the concrete actions (e.g. render a question-form, collect answers, avoid re-asking) to raise specificity from a single action to multiple.

Dimension	Reasoning	Score
Specificity	The phrase 'discovery question form for ambiguous briefs' names the domain and a concrete action (emitting a clarifying-question form at turn 1) but does not list multiple specific actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what the skill does (a turn-1 discovery question form) but has no explicit 'Use when...' trigger clause; 'for ambiguous briefs' only implies the when, so per the guideline a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	'Turn-1 discovery question form' is internal/technical jargon; a user would not naturally say this when they need clarifying questions, so it lacks natural keywords and matches the 'no natural keywords; technical jargon' anchor.	1 / 3
Distinctiveness Conflict Risk	The GenUI question-form artifact is a fairly distinct niche, but the underlying intent (asking clarifying questions) could still overlap with general discovery or clarification skills, matching 'somewhat specific but could still overlap.'	2 / 3
	Total	7 / 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/atoms/discovery-question-form/SKILL.md
Commit: f2760fd

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