菜单
Answer a reader's question about a specific part of a Lathe tutorial, in session. Use when the user invokes /lathe-ask with a slug and part like "/lathe-ask digital-synth-zig part-02.md" followed by the question on the next line (the "Ask" button in `lathe serve` pastes exactly this).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run the Lathe worker loop so the web UI's Ask / Verify / Add-a-part buttons drive work directly in this session instead of handing back a command to paste. Use when the user invokes /lathe-work (start it once per session while `lathe serve` is running). Works in any coding agent.
Generate hands-on technical tutorials for any topic on demand. Use when the user invokes /lathe with a topic like "/lathe build a digital synth in Zig" or "/lathe how to build a compiler in Rust".
Write the next part of an existing Lathe tutorial, in session. Use when the user invokes /lathe-extend with a slug like "/lathe-extend digital-synth-zig" (the "Add a new part" button in `lathe serve` hands you that command), optionally followed by guidance for where the part should go.
Author a custom writing voice for Lathe tutorials, in session, then persist it via the CLI. Use when the user invokes /lathe-voice (optionally with a name like "/lathe-voice terse") to craft a new tone/register preset that /lathe can generate in.
Pick or backfill the search tags on a stored Lathe tutorial, in session. Use when the user invokes /lathe-tag with a slug like "/lathe-tag digital-synth-zig" to choose good tags for the `lathe serve` search and tag filters, or to backfill tags on a tutorial that has none.
Verify that a stored Lathe tutorial actually works by following it end to end in a fresh scratch dir, in session. Use when the user invokes /lathe-verify with a slug like "/lathe-verify digital-synth-zig" (the "Verify this tutorial" button in `lathe serve` hands you that command).
| name | lathe-ask |
| description | Answer a reader's question about a specific part of a Lathe tutorial, in session. Use when the user invokes /lathe-ask with a slug and part like "/lathe-ask digital-synth-zig part-02.md" followed by the question on the next line (the "Ask" button in `lathe serve` pastes exactly this). |
Answer a reader's question about one part of a stored tutorial, grounded in what that tutorial actually built. Triggered by:
/lathe-ask <slug> <part-NN.md>
<the reader's question>
The web "Ask" button pastes exactly that: the slug and part on the command line, the question on the next line. Parse all three.
Read the part at ~/.lathe/tutorials/<slug>/<part-NN.md>. Read sibling parts (part-NN.md in the same dir) when the question reaches across parts or depends on earlier setup — continuity matters here too.
Answer grounded in this tutorial's concrete artifact — the same controlling example, the same numbers, the same voice the tutorial used. The reader is asking about their synth / their key-value store, not the topic in the abstract. Don't re-teach the whole topic from scratch.
Point at the tutorial, don't re-derive it. Prefer "look at the process_buffer loop in §3 — the modulo there is doing X" over a fresh ground-up explanation. You're a guide standing next to them at the page they're reading.
Be honest about gaps. If the question exposes something the tutorial got wrong, glossed over, or left under a [!UNVERIFIED] flag, say so plainly — don't paper over it. That's more useful than a confident hand-wave.
Stay engaged for follow-ups. This is a conversation, not a one-shot reply.
lathe ask command. This skill writes nothing and calls back into no CLI command — ask is deliberately conversation-only.metadata.json, verify-result.json, or the part markdown. Don't verify, don't extend, don't tag.