菜单
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).
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/devenjarvis/lathe --skill lathe-ask命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| 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.