メニュー
Create a practice test for the child from their materials and progress — child-facing questions with a separate parent-only answer key, packaged as one activity.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build a designed, self-contained HTML academic map of the child's subjects, topics, and materials, plus real coaching notes for the parent on how to teach them better.
Build a designed, self-contained HTML progress report for the child — how she's actually doing, and what to work on next — surfaced in the Progress tab for both parent and child.
Create clear, child-ready study material (notes, worked examples, a revision sheet) for a topic, matched to the child's level and their own uploaded materials, packaged as one activity.
Extract genuine interest signals from the child's own conversations and keep memory/interests.md current — a Pulse-only skill, not triggered by a direct parent request.
Extract durable things the parent has said in chat and keep memory/preferences.md current — a Pulse-only skill, not triggered by a direct parent request.
A fun, off-syllabus "something new to explore" activity for the child — a light cover page plus a chat-driven discovery, tailored to grade and interests learned over time. Parent-initiated, handed off like any other activity.
| name | create-test |
| description | Create a practice test for the child from their materials and progress — child-facing questions with a separate parent-only answer key, packaged as one activity. |
Read the progress report FIRST — this is what makes the test hers.
reports/progress.html already holds the worked-out picture of her strengths and
the specific moves she's stuck on (see skills/create-progress-report/SKILL.md).
Read it before anything else and let its "Where she's stuck" bullets decide what
this test actually probes. Skipping this is how a test ends up generically correct
for her grade but not about HER — the failure worth avoiding here.
If the report is missing or clearly stale, fall back to reading recent activity
conversation.json files and attempts/ directly, and say so to the parent.
Know the child and the material. memory/child-profile.json for name, grade,
and board (ask the parent if any is missing). The relevant
materials/<subject>/<topic>/*.meta.json for what she's actually being taught —
their extracted_text already holds the full content, so her notation and method
names match what her teacher used.
Write the test as static HTML in the activity folder (see
skills/_shared/html-design.md). It should read like a real test paper: a clear
header with her name, grade/board, subject and topic, then numbered questions
easy → harder, marks shown as a .badge, and genuine space to work under each.
Cover the methods that appear in her own materials, and make most of the
questions target the specific weak moves from step 1 — a couple she can already
do (so it isn't demoralizing), the rest on the moves that actually need work,
approached from a different angle than last time rather than the same items again.
No answers, and no hints that give them away.
Write the answer key as plain Markdown at <name>-KEY.md in that SAME folder
— full worked solutions, plus a note on which questions target which weakness so
the parent knows what to watch for. Never list it in items: it stays out of the
child's activity view entirely, and what the tutor may reveal from it during her
session is governed solely by teaching_mode.
Finalize the activity with goal = "answer all N questions" (N = the real
count). A test is usually strict (hints only, no reveal) or graduated — ask
rather than assume if the parent hasn't said.
Tell the parent what you made and why those particular questions.
