メニュー
Gives direct, concise answers to factual and structural questions. Use when the user needs a fast answer rather than a teaching interaction — lookups, syntax reminders, "how do I do X," or "what does Y do." Flags the bigger picture in one sentence when a narrow question hints at a structural gap, but never cascades into teaching.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Returns the file path of the current session's JSONL log. With --stamp, adds provenance (session path + timestamp) to a file as YAML frontmatter (default) or HTML comment (--back). Use when a skill or agent needs to reference or annotate the current conversation's log file.
Onboarding interview for the personal development harness. Scans background/ for pre-loaded materials (code, resumes, writing, transcripts), runs a conversational interview to discover background, goals, current skills, and learning preferences, then generates a personalized CLAUDE.md and initial current-state.md. Use when setting up a new learner, onboarding, or bootstrapping the harness.
Cross-session learning pattern analysis. Reads multiple session logs and learning state to detect stalls, regressions, goal drift, and arc readiness that no single session review can see. Proposes updates to learning state files. Use when the user asks "how am I doing", "review my progress", "am I improving", or "progress review". Also dispatched automatically by startwork when enough sessions have accumulated.
Returns a structured learning-state diff from session evidence without quizzing or writing files. Callers (session-review, startwork, or the user's main context) handle presentation, approval, and writes. Use when learning state is stale, before startwork, or when the user wants to update scores without a full session review.
Discovers Claude Code conversation sessions on the local machine within a date range. Returns a structured manifest of sessions with metadata. Use when a skill or agent needs to find prior conversations — e.g., session-review gathering evidence, progress-review windowing, or startwork checking recent activity. Not user-facing; designed as infrastructure for other skills.
Audits Claude Code security configuration against the Safer YOLO guide. Checks sandbox, deny rules, hooks, DCG, and gitleaks. Surfaces findings in plain language with customized recommendations. Use when the user mentions YOLO mode, bypass permissions, skipping permissions, "dangerously-skip-permissions", security setup, or wants to harden their configuration.
| name | quick-ref |
| description | Gives direct, concise answers to factual and structural questions. Use when the user needs a fast answer rather than a teaching interaction — lookups, syntax reminders, "how do I do X," or "what does Y do." Flags the bigger picture in one sentence when a narrow question hints at a structural gap, but never cascades into teaching. |
Answer the question. Be done.
Every question gets classified on arrival. The response shape follows.
Fact question — has a single correct answer.
"What does .bind() do?" / "How do I center a div?" / "What's the difference between let and const?"
Structural question — the answer is correct but incomplete without context.
"Why is my array empty after .map()?" / "Why does this change inside my callback?"
The test: if giving only the narrow answer would leave the user solving the same class of problem again next week, it's structural. Flag the pattern; don't teach it.
When a narrow question reveals a structural gap, after giving the direct answer, add one sentence that:
Example:
setTimeout callback have the wrong value of i?"
A: [direct fix with let or closure] + "This is the closure-over-loop-variable problem — var shares one binding across iterations, let creates a new one each time."If the question is purely factual, skip the flag.