mcpField
P
probe

probe

github.com/vasanthsreeramProductivity165447 installsUpdated 10w ago
Repository

About probe

probe is a quiz-based skill for assessing a learner's prerequisite knowledge and recording dependency strands in a map. It assigns statuses based on answer evidence and identifies where teaching should begin.

Key features

  1. 01Ask questions through the quiz UI
  2. 02Present 1–3 multiple-choice questions per turn
  3. 03Include an “I don't know” option
  4. 04Label dependency status using evidence
  5. 05Update and show the knowledge map

Use cases

  1. 01Assess foundations before a lesson
  2. 02Identify unclear knowledge strands
  3. 03Help teachers choose a starting point

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/vasanthsreeram/alvarmethod --skill probe

After installing, type/probein Claude Code to confirm it loaded.

Details

From the project README

Probe

Measure first. Do not teach during a probe except a one-line correction after they answer.

Quiz UI is mandatory. Read ../teach/references/quiz-ui.md and call that tool. Never print A/B/C/D in the chat.

Goal

Produce .alvar/maps/<slug>.md that labels every dependency strand:

known | edge | unknown | blocked

blocked = they said they don't know, or the question needs a tool you don't have.

How to ask

  • 1–3 multiple-choice questions per turn. Wait.
  • Always include D. I don't know (or an extra "I don't know" option).
  • Start wide (what kind of object is this? what does this operator measure?). Then split the strand that the answer leaves ambiguous.
  • If they already listed solid ground, skip those strands.
  • Invite a talk-through: a wrong reason + right letter is edge, not known.

One right answer. No trick options that hinge on wording. Put I don't know as an option. Do not mark the correct choice recommended.

Scoring

resultstatus move
correct + sound reasonknown
correct, thin reasonedge
wrong, near-missedge
wrong, foundation missingunknown
I don't knowblocked or unknown

After each batch, update the map. Stop when the upcoming lesson's dependencies are all labeled — not when you have asked "enough questions."

Map file

# Map — <goal>

Updated: <ISO date>
Goal: <one sentence>

## Strands
| strand | status | evidence |
|--------|--------|----------|
| … | known | Q2 + reason |

## Quiz log
- Q1 [strand] <letter> — correct|wrong|idk — <five words>

End

Show the table. Say which strands a teacher should start from. Do not start the lesson unless they ask.

Comments

Markdown supported