CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quiz

Create strict JSON single-answer multiple-choice quizzes.

Quality

80%

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 ./docker/sandbox/skills/quiz/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

96%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 an exemplary single-purpose skill: lean, fully concrete, with an explicit verify-fix-reverify loop and a well-defined save gate plus revision path. The only structural nit is that the revision workflow lacks its own heading and the content slightly exceeds the simple-skill size band.

Suggestions

Give the revision workflow its own heading (e.g. '## Revisions') so it reads as a distinct path rather than trailing the save step.

Consider splitting the field-length and formatting rules into a short reference block if the contract grows, keeping the inline overview lean.

DimensionReasoningScore

Conciseness

The body is pure instruction with zero padding — rules like 'Write three plausible distractors', 'Escape each backslash as `\\` in JSON', and 'Write UTF-8 JSON without comments or a byte-order mark' assume Claude's competence and never explain concepts it already knows. Nothing can be trimmed without losing a real constraint, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

The guidance is fully executable: an exact JSON shape with example values, exact tool calls ('verify_artifact(path="/workspace/<slug>.json", format="quiz")', 'save_artifact(...)'), and specific numeric limits (5–30 questions, title 1–200 chars, correct_option_index 0–3). The revision path is also concrete (edit restored JSON from primary_path, verify expected_output_path, save with artifact_id), matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

The sequence create → verify → fix all blockers together → rewrite once → reverify → save includes an explicit validation checkpoint and a bounded error-recovery loop ('If a blocker remains, stop and explain it instead of looping') that prevents infinite retry. The gating condition ('After verification returns status="verified"') makes the checkpoint explicit, matching the top anchor; the batch-JSON write operation is fully validated, so no cap applies.

5 / 5

Progressive Disclosure

The two-section structure (Contract / Verify and save) is well organized with nothing that clearly belongs in a separate file, but the body runs ~70 lines — beyond the rubric's under-50-line simple-skill exception — and the revision workflow is an unheaded paragraph tucked at the end of 'Verify and save' rather than its own section. That minor organization gap fits the 4-anchor ('good structure; minor organization gaps') better than the 5-anchor.

4 / 5

Total

19

/

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 gives a clear, specific 'what' with good format qualifiers and low conflict risk, but it completely lacks a 'when' clause and misses common trigger synonyms (test, exam, MCQ, practice questions). It is a solid one-liner that needs trigger guidance to be complete.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a quiz, test, exam, practice questions, or multiple-choice questions.'

Include natural synonyms such as 'MCQ', 'test', 'exam', or 'practice questions' so the description matches phrases users actually say.

Reflect the revision capability the body supports, e.g. 'Create or revise strict JSON single-answer multiple-choice quizzes.'

DimensionReasoningScore

Specificity

The phrase 'Create strict JSON single-answer multiple-choice quizzes' names the domain plus one concrete action with useful format qualifiers ('strict JSON', 'single-answer'), matching the anchor for 1-2 concrete actions without comprehensive coverage. It falls short of 4 because only one action verb is listed, and is above 2 because the actions are not generic.

3 / 5

Completeness

The 'what' is clear ('Create strict JSON single-answer multiple-choice quizzes'), but there is no 'when' at all — no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not 2 because the 'what' is concrete; not 4 because the 'when' is not even weakly implied.

3 / 5

Trigger Term Quality

Natural keywords like 'quiz' and 'multiple-choice' are present, but common variations users would say — 'test', 'exam', 'MCQ', 'practice questions' — are absent, matching the 'some relevant keywords but missing common variations or synonyms' anchor. It is below 4 because keyword coverage is thin (roughly three terms) and above 2 because the terms present are natural, not jargon.

3 / 5

Distinctiveness Conflict Risk

The qualifiers 'strict JSON', 'single-answer', 'multiple-choice' carve a specific niche (machine-readable quiz generation) with only minor overlap risk against other assessment or JSON-generation skills, matching the 'mostly distinct; minor overlap risk' anchor. Not 5 because there are no distinct trigger phrases to disambiguate at invocation time.

4 / 5

Total

13

/

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

MODSetter/SurfSense

Path

docker/sandbox/skills/quiz/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.