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.

74

Quality

92%

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%

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

A well-structured instruction skill with concrete guidance, a sequenced workflow with validation checkpoints, and clean one-level-deep reference disclosure. Its main weakness is verbosity in the selection-menu and lesson-mapping sections, which inflates tokens without adding actionability.

Suggestions

Move the AskUserQuestion lesson-selection option text and the full lesson-mapping table into a reference file, keeping only a brief pointer in SKILL.md to reduce token cost.

The 'CRITICAL — Shuffle answer options' and Acceptance Criteria both restate the shuffle-and-track rule; consolidate to a single authoritative statement to avoid redundancy.

Trim the per-question bank field listing ('question/options/correct/explanation/category') since the structure is already self-evident from the question bank file.

DimensionReasoningScore

Conciseness

Mostly efficient and instruction-oriented, but the lesson selection menu, full lesson-mapping table, and repeated AskUserQuestion option listings are verbose relative to a token-efficient overview; it could be tightened by deferring option text to a reference.

2 / 3

Actionability

Concrete, executable guidance throughout: a specific lesson-mapping table, exact file path to read (`<lesson-directory>/README.md`), 2-questions-per-round structure, shuffle-and-track-correct-position rule with a worked example, and explicit grade scale.

3 / 3

Workflow Clarity

A clear six-step sequence with explicit validation checkpoints (Acceptance Criteria verified before results, error handling for missing README / empty question bank, partial-results feedback loop on mid-quiz quit), matching the score-3 anchor.

3 / 3

Progressive Disclosure

The body is an overview pointing one level deep to real bundle files (`references/question-bank.md`, `references/results-template.md`, both present and referenced for the actual content), with no nested/deep references — well-signaled and appropriately split.

3 / 3

Total

11

/

12

Passed

Description

100%

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 precise, third-person description that states concrete capabilities, natural triggers, and an explicit use-timing clause, plus a crisp exclusion boundary. It scores at the top of every dimension with no verbosity or padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'test a learner', 'with 10 questions', 'scoring answers', 'flagging weak spots', mirroring the score-3 anchor that enumerates specific operations.

3 / 3

Completeness

Explicitly answers 'what' (test a learner with 10 questions, score, flag weak spots) and 'when' ('Use before, during, or after a lesson'), matching the anchor requiring both what AND when with explicit triggers.

3 / 3

Trigger Term Quality

Includes natural phrasings users would say ('quiz me on...', 'test my knowledge', implied by 'lesson quiz', 'test a learner') and concrete lesson tokens (01-10), giving strong coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

A clear single-lesson-quiz niche is sharpened by an explicit exclusion ('Don't use for whole-tutorial assessment or explaining a topic instead of testing it'), reducing overlap with sibling assessment/explanation skills.

3 / 3

Total

12

/

12

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.