eklavya-mcp 1.4.0 → 1.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/eklavya-mcp.sh +1 -1
- package/dist/assets/tutor-skill.md +1 -1
- package/package.json +1 -1
package/bin/eklavya-mcp.sh
CHANGED
|
@@ -12,7 +12,7 @@
|
|
|
12
12
|
# Keep PINNED_VERSION in step with .claude-plugin/plugin.json and
|
|
13
13
|
# mcp/package.json. A test asserts all three match.
|
|
14
14
|
|
|
15
|
-
PINNED_VERSION="1.4.
|
|
15
|
+
PINNED_VERSION="1.4.1"
|
|
16
16
|
|
|
17
17
|
MCP_DIR=$(cd "$(dirname "$0")/.." && pwd)
|
|
18
18
|
LOCAL_SERVER="$MCP_DIR/dist/server.js"
|
|
@@ -154,7 +154,7 @@ Use the **`AskUserQuestion`** tool. One question per call — the tool accepts u
|
|
|
154
154
|
|
|
155
155
|
- **Exactly four options.** One correct, three plausible.
|
|
156
156
|
- **Put the correct option where `answer_position` says.** The plan gives each question a slot from 1 to 4 — obey it. Left to your own judgement you will put the right answer first nearly every time, and a learner only needs a handful of questions to notice that and start picking A without reading. The quiz keeps looking fine and stops measuring anything. Write the four options, then place them so the correct one lands in that slot.
|
|
157
|
-
- **`header`**: set it to `
|
|
157
|
+
- **`header`**: set it to `Eklavya` (7 chars, fits). The chip is the only thing on screen that says who is asking. A question that arrives mid-task with no attribution reads as Claude going off-piste, and the developer answers a stranger. The tool still appends an "Other" choice automatically and that is the escape hatch for *"I don't know"* — name it in a `description` if a question needs it, not in the header.
|
|
158
158
|
- **`question`**: the stem, grounded per the plan's `framing`. Do not number the options in the text; the tool renders them.
|
|
159
159
|
- **`description`** on each option: one clause. This is where a near-miss gets to be genuinely tempting.
|
|
160
160
|
- **`preview`**: use it when the options are *code*. Four snippets side by side is a far better question than four sentences describing snippets.
|