CtrlK
BlogDocsLog inGet started
Tessl Logo

lesson-quiz

Test a learner on a single Claude Code tutorial lesson (01-10) with 10 questions, scoring answers and flagging weak spots. Use before, during, or after a lesson. Don't use for whole-tutorial assessment or explaining a topic instead of testing it.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A well-structured, actionable interactive-skill body with clear sequencing, validation via acceptance criteria, and appropriately externalized bulk content. The main improvement is trimming repeated emphasis and the redundant closing example.

Suggestions

Collapse the repeated 'IMPORTANT'/'CRITICAL' shuffle reminders into a single guardrail statement to reduce token cost.

Remove or shorten the trailing 'Example: for a 7/10 after run on Hooks' block since the Acceptance Criteria already specify the expected output.

Provide a concrete AskUserQuestion invocation skeleton once so each round can reuse it instead of re-describing headers and options inline.

DimensionReasoningScore

Conciseness

The body is lean for a multi-step interactive skill and avoids explaining concepts Claude already knows, but repeats emphasis ('IMPORTANT', 'CRITICAL') and includes a trailing illustrative example that could be trimmed.

4 / 5

Actionability

Provides concrete executable guidance — an exact lesson mapping table, literal AskUserQuestion option strings, and a shuffle example — with only minor gaps such as the full AskUserQuestion invocation payload not being templated.

4 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced, an Acceptance Criteria checklist acts as explicit validation before final output, and the Edge Cases section supplies error-recovery feedback loops (invalid arg, quit mid-quiz, missing README, empty bank).

5 / 5

Progressive Disclosure

The body is an overview that cleanly externalizes bulk material to one-level-deep, clearly signaled references — references/question-bank.md (~51KB) and references/results-template.md — both confirmed to exist, with no nested reference chains.

5 / 5

Total

18

/

20

Passed

Description

92%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.

A strong, specific description that concretely states capabilities, trigger timing, and boundaries in third person. Its only gap is omitting the natural keyword 'quiz' that users would most likely say.

Suggestions

Include the word 'quiz' (and a synonym like 'practice') in the description so the most common user phrasing matches the trigger.

Consider adding 'score' or 'grade' as an explicit trigger term to reinforce the assessment framing.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Test a learner... with 10 questions, scoring answers and flagging weak spots' — with specific parameters (single lesson 01-10, 10 questions), giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what ('Test a learner on a single... lesson... scoring answers and flagging weak spots') and when ('Use before, during, or after a lesson'), plus a concrete negative-trigger clause ('Don't use for whole-tutorial assessment or explaining a topic instead of testing it').

5 / 5

Trigger Term Quality

Natural terms 'test', 'lesson', and 'questions' appear, but the most common user phrasing 'quiz' (and synonyms like 'practice' or 'knowledge check') are absent from the description, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (single lesson 01-10 quiz) with an explicit boundary statement ruling out whole-tutorial assessment and topic explanation, giving minimal conflict risk with sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
luongnv89/claude-howto
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.