CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-ref-jev-question-design

Question-design reference for the gated TypeSafe System One judgment capability. How to author typed questions that return useful, honest answers: compute the question in code, always admit a no-match answer, keep the supplied state small, phrase noul questions so both polarities are expressible. Carries the question-design rules ONLY — never the call path; where and how to reach the capability is the MCP catalogue's concern.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/moai-ref-jev-question-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a lean, well-structured, self-contained reference whose rules are concrete and clearly scoped, with strong failure-mode framing. Its main gap is the absence of even one worked example — a composed question with its minimal state and typed answer — which would move the guidance from principled to directly imitable.

Suggestions

Add one short worked example: a question composed in code from named inputs, the minimal denatured state it ships, and the typed answer (including a no-match case) — this directly addresses the lowest-scoring dimension.

Tighten the intro paragraph's exception sentence about the `todo --auto` auto-scoped ranking exception, and merge the Rule 2 noul guidance into Rule 4 to remove overlap.

Consider a brief authoring/review checklist that sequences the four rules, so a reader applying them to a draft question has an explicit order of checks.

DimensionReasoningScore

Conciseness

The body is dense with no filler and explains nothing Claude already knows; each rule states its do/don't in a few tight sentences ("the same inputs always compose the same question, and a change in phrasing shows up as a diff"). It is not a 5 because the intro's stuffed exception sentence ("A narrow exception is the `todo --auto` cycle's own candidate ranking, the auto-scoped ranking exception...") could be trimmed, and Rule 2's noul guidance overlaps Rule 4. Not a 3, since nothing is padding or unnecessary explanation.

4 / 5

Actionability

There is concrete directive guidance — "Compose question text with the project's language's string formatting from named inputs — never hand-type a question into a prompt-shaped literal", example option strings ("none of these fit", "no listed option"), and "record it next to the question id in the caller's own output" — but the skill never shows a worked example of a composed question, a minimal state payload, or a typed answer, leaving key details of what good output actually looks like missing. Per the instruction-only scoring note the absence of code is not itself penalized, but the incompleteness matches anchor 3 rather than anchor 4's mostly-complete guidance.

3 / 5

Workflow Clarity

The four rules are clearly organized, each with explicit do/don't framing and failure-mode reasoning, and the closing section names the failure mode ("Silent defaulting — treating an absent answer as either polarity... is the failure mode these rules exist to prevent"). This is a single-purpose reference skill with no destructive or batch operations, so no validation loop is required, and the simple-skill exception could apply; it falls short of 5 only because there is no authoring/review sequence or checklist that ties the rules into an applicable order.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent) and none are needed: the body is a self-contained ~60-line set of rules with clean, well-navigable section headers ("## Rule 1 — ..." through "## What an absence means") and no content that clearly belongs in a separate file. This matches the rubric's simple-skill guidance that a self-contained, well-organized skill with no need for external references scores 5 on progressive disclosure.

5 / 5

Total

16

/

20

Passed

Description

62%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 communicates a tightly scoped niche with an explicit boundary against a companion skill, and lists four concrete design rules. Its main weaknesses are the absence of a use-when trigger clause within the description field itself (it sits in the separate when_to_use frontmatter) and heavy internal jargon that suppresses natural trigger terms.

Suggestions

Add an explicit "Use when..." clause to the description itself (e.g., "Use when authoring or reviewing typed questions for the judgment capability") so the description field alone answers both what and when.

Include natural trigger phrases users would actually say — such as "question phrasing", "forced answer", "uninformative answer" — and gloss or replace internal jargon like "noul" and "TypeSafe System One" with a plain-language apposition.

DimensionReasoningScore

Specificity

The description lists four concrete directives — "compute the question in code", "always admit a no-match answer", "keep the supplied state small", "phrase noul questions so both polarities are expressible" — which goes well beyond naming 1-2 actions, but internal jargon ("noul", "gated TypeSafe System One judgment capability") leaves the actions only partially concrete to a reader outside the system, matching anchor 4 rather than anchor 5's fully comprehensive and accessible coverage.

4 / 5

Completeness

The "what" is clear and specific ("How to author typed questions that return useful, honest answers" plus the four rules), but the description field itself contains no "Use when..." clause or equivalent trigger guidance — that lives in the separate when_to_use field — and the rubric guideline caps completeness at 3 in that case. The scope hint "for the gated TypeSafe System One judgment capability" only weakly implies "when", matching anchor 3 exactly.

3 / 5

Trigger Term Quality

Some relevant natural keywords appear ("author typed questions", "question-design", "no-match answer"), but invented jargon such as "noul" and "TypeSafe System One" are phrases no user would naturally say, and common variations/synonyms (e.g., "question phrasing", "write questions for the judgment API") are missing from the description itself. This fits anchor 3: relevant keywords present but missing common variations.

3 / 5

Distinctiveness Conflict Risk

The description carves out an unambiguous niche ("Question-design reference for the gated TypeSafe System One judgment capability") and explicitly fences its scope against the sibling skill ("Carries the question-design rules ONLY — never the call path; where and how to reach the capability is the MCP catalogue's concern"), giving it distinct triggers and minimal conflict risk, matching anchor 5.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

modu-ai/moai-adk

Path

.claude/skills/moai-ref-jev-question-design/SKILL.md

Reviewed

Table of Contents

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.