技能工作室
- 作者仓库星标 217
- 作者仓库 claude-skills
- 领域
- 设计与多媒体
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @glebis · 未声明许可证
- 上下文用量评级
- 中等消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 需要 · Anthropic
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- Python >=3.11
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
步骤 0 —(可选)来自先前会话的种子
如果用户提供了先前的会话(Claude Code 成绩单、另一个技能工作室会话或任意成绩单路径),请为面试播种而不是从空白开始:这分两个阶段运行:确定性摄取(无 LLM)- 提取尝试的模型、成本事件、提示更改、痛点片段、子代理调用(具有描述、类型、提示片段的代理工具)、技能调用、工具序列(所有工具调用的有序列表)、工具频率和工作流程模式(重复的多工具)序列)。 50k 令牌转录本压缩为紧凑的结构化 JSON 包。
第 1 步 — 开始会话
预设:`ai-agent`(默认),`life-automation`,`knowledge-work`,`custom`。深度:`sprint`(0.60,~5–7 个问题),`standard`(0.80,~15–20 个问题,默认),`deep`(0.92,~25–35 个问题)。风格(决定问题的措辞方式):`scenario-first`(默认)—“带我经历一个特定的时间......”`socratic`—“为什么这很重要?如果……会发生什么?”
第 2 步 — 采访循环
对于每个用户的答案:提取 JSON 补丁。发出仅包含答案地址的 DesignJSON 字段的 JSON 对象。仅使用下面模式中的字段 - 切勿产生幻觉字段或值。如果没有提及任何与模式相关的内容,则发出`{}`。示例补丁:带有列表字段的示例:带有对象列表字段的示例(`scenarios`):
第 3 步 — 导出
打印路径`design.md`和`design.svg`。将两条路径呈现给用户。
# Skill Studio
## Purpose
Conduct a structured JTBD interview that captures what to build, for whom, and why — then emit a one-page `design.md` + `design.svg` spec. Sits between "should I automate this?" (automation-advisor) and "how do I package this as a skill?" (skill-creator).
## Architecture
This skill wraps an external CLI tool (`skill-studio`) installed via pip. The CLI handles session state, coverage tracking, and export. The skill orchestrates the CLI — it does not bundle scripts directly.
## When to use
Trigger on any of: "help me design...", "build a skill for...", "design an automation for...", "I want a bot/agent/workflow that...", "scope a new shortcut". Also trigger when the user describes a recurring pain and asks how to automate it.
Also trigger for session analysis: "analyze this session", "what skills could I build from this", "propose skills from session", "what workflows did I use", "what did I do in this session", "extract patterns from my work", "turn this session into a skill", "what could be automated from this". If the user references a session ID or asks about subagent activity, this skill handles it.
## Prerequisites
- `skill-studio` CLI on PATH (`pip install -e .` inside the skill directory, or `skill-studio init` for guided setup)
- Python 3.11+
- Text mode needs no API key — the interview runs natively inside Claude Code
- Voice mode (`--voice`) needs `DAILY_API_KEY`, `GROQ_API_KEY`, `DEEPGRAM_API_KEY`, and an LLM provider key (`OPENROUTER_API_KEY` by default). If any key is missing, suggest text mode instead.
To verify the CLI is available, run `skill-studio --help`. If the command is not found, install it from the skill's base directory: `pip install -e <skill-studio-base-dir>`.
## Interview protocol (text mode)
Follow these steps in order.
### Step 0 — (Optional) Seed from a prior session
If the user provides a prior session (Claude Code transcript, another skill-studio session, or arbitrary transcript path), seed the interview instead of starting blank:
```bash
# Analyze the current running session
skill-studio propose-from-session --current
# Analyze a specific session by ID (prefix match works)
skill-studio propose-from-session <session_id>
# Analyze a session from a specific project
skill-studio propose-from-session <session_id> --project <project-dir-name>
# Analyze an arbitrary transcript file
skill-studio propose-from-session --path <file>
# Inspect the raw extracted bundle without an LLM call
skill-studio propose-from-session --current --bundle-only
```
This runs in two stages:
1. **Deterministic ingest** (no LLM) — extracts models tried, cost events, prompt changes, pain snippets, **subagent calls** (Agent tool with descriptions, types, prompt snippets), **skill invocations**, **tool sequences** (ordered list of all tool calls), **tool frequency**, and **workflow patterns** (repeated multi-tool sequences). A 50k-token transcript compresses to a compact structured JSON bundle.
2. **Single LLM call** — over that compact bundle only, proposes a partial DesignJSON patch with a `rationale` map citing which signals justified each field, plus **skill proposals** — potential new skills derived from observed workflow patterns and agent orchestration.
The bundle includes these structured signals:
- `agents` — subagent calls with `description`, `subagent_type`, and `prompt_snippet`
- `skills` — skill invocations observed during the session
- `tool_sequence` — ordered list of all tool calls with descriptions
- `tool_frequency` — how often each tool was used
- `workflow_patterns` — repeated tool sequences (e.g. "Read → Edit → Bash" appearing 3× suggests a test-fix cycle)
**The proposal is NOT applied automatically.** Present it to the user (with the rationale and any skill proposals) and ask for approval. Offer: `approve as-is`, `edit inline`, `discard and start fresh`, `approve partial` (keep some fields, re-interview others).
If the proposal includes `skill_proposals`, present them separately and ask if the user wants to proceed to `/skill-creator` with any of them.
`propose-from-session` does not create a session. After approval, run `new-session` (Step 1) to create one, then pipe the approved patch to `apply-patch`, and continue the interview loop from the next uncovered target.
### Browsing Claude Code sessions
To help the user pick a session to analyze:
```bash
# List recent sessions (most recent first, all projects)
skill-studio list-sessions
# Filter to a specific project
skill-studio list-sessions --project <project-dir-name>
# Show more results
skill-studio list-sessions --limit 50
```
Output shows session ID prefix, age, size, and title.
### Step 1 — Start the session
Presets: `ai-agent` (default), `life-automation`, `knowledge-work`, `custom`.
Depth: `sprint` (0.60, ~5–7 questions), `standard` (0.80, ~15–20 questions, default), `deep` (0.92, ~25–35 questions).
Styles (shape how questions are phrased):
- `scenario-first` (default) — "Walk me through a specific time when..."
- `socratic` — "Why does that matter? What would happen if...?"
- `metaphor-first` — "If this automation were a [thing], what would it be?"
- `form` — One direct question per field, no preamble.
Run:
```bash
skill-studio new-session --preset <preset> --depth <depth> --style <style>
```
Output:
```
session_id: <uuid>
opening: <question text>
```
Store the `session_id`. Present the opening question to the user as a direct text message.
### Step 2 — Interview loop
For every user answer:
**a. Extract a JSON patch.** Emit a JSON object containing only the DesignJSON fields the answer addresses. Use only fields from the schema below — never hallucinate fields or values. If nothing schema-relevant was said, emit `{}`.
Example patch:
```json
{"jtbd.situation": "When I finish a coaching call and need to write up notes", "problem.what_hurts": "Manual note-taking takes 20 minutes and I lose details"}
```
Example with list fields:
```json
{"needs.functional": ["transcribe audio", "extract action items"], "guardrails": ["never send notes without review"]}
```
Example with object-list field (`scenarios`):
```json
{"scenarios": [{"title": "Post-coaching rush", "vignette": "Call ends at 14:00, next meeting at 14:15 — I scribble three bullet points and lose the rest by evening."}]}
```
**DesignJSON fields:**
| Field | Type | Notes |
|-------|------|-------|
| `hook` | str | One-sentence pitch of the automation |
| `problem.what_hurts` | str | Specific pain |
| `problem.cost_today` | str | What the pain costs right now |
| `needs.functional` | list[str] | What it must do |
| `needs.emotional` | list[str] | How the user wants to feel |
| `needs.social` | list[str] | Relational / status needs |
| `jtbd.situation` | str | When this happens |
| `jtbd.motivation` | str | What the user wants |
| `jtbd.outcome` | str | So they can... |
| `before_after.before_external` | str | Visible state before |
| `before_after.before_internal` | str | Felt state before |
| `before_after.after_external` | str | Visible state after |
| `before_after.after_internal` | str | Felt state after |
| `scenarios` | list[{title, vignette}] | Concrete day-in-the-life stories |
| `trigger.type` | `manual` / `scheduled` / `event` | |
| `trigger.detail` | str | e.g. "7:45am weekdays" |
| `inputs` | list[str] | Data / services consumed |
| `capabilities` | list[str] | What it does |
| `outputs` | list[str] | What it produces |
| `guardrails` | list[str] | Safety rails; negative-space rules |
| `cta` | str | Next action at end of design |
| `concept_imagery.metaphor` | str | Visual / verbal handle |
**b. Apply the patch.**
```bash
echo '<patch_json>' | skill-studio apply-patch <session_id>
```
Output:
```
coverage: 0.42
next_target: jtbd.situation
```
**c. Check stop conditions.** End the loop if either:
- `coverage >= threshold` (sprint=0.60, standard=0.80, deep=0.92)
- User says "done", "wrap up", or "stop"
**d. Ask the next question.** Target the `next_target` field, in the active style. Never re-ask a field already past 0.5 coverage. Present the question as direct text to the user.
### Step 3 — Export
```bash
skill-studio done <session_id>
```
Prints the paths to `design.md` and `design.svg`. Present both paths to the user.
## Voice mode
For voice interviews, skip the manual loop and delegate to the built-in pipeline:
```bash
skill-studio new --voice --preset <preset> --depth <depth>
```
This spins up a Daily room (auto-opens in the browser), runs Groq Whisper STT -> interview loop -> Deepgram TTS, and auto-exports on session end.
If voice mode fails due to missing API keys, fall back to text mode and inform the user. To configure keys, run `skill-studio init`.
## Other commands
- `skill-studio list` — list all skill-studio interview sessions
- `skill-studio list-sessions` — list Claude Code sessions (most recent first)
- `skill-studio list-sessions --project <name>` — filter by project
- `skill-studio export <id> md-svg` — regenerate `design.md` + `design.svg`
- `skill-studio coverage <id>` — per-field confidence JSON
- `skill-studio next-target <id>` — ask-this-next hint
- `skill-studio init` — full first-run wizard (prereq checks + keys + paths)
- `skill-studio setup` — narrower key-rotation flow (sops-only)
## Sessions
Each interview writes to `$SKILL_STUDIO_HOME/sessions/<uuid>/` (default: `~/.skill-studio/sessions/<uuid>/`):
- `design.json` — canonical schema (single source of truth)
- `transcript.md` — full Q&A log
- `design.md`, `design.svg` — exported artifacts
## Troubleshooting
- **`skill-studio: command not found`** — Run `pip install -e <skill-studio-base-dir>` and retry.
- **`apply-patch` returns an error** — Verify the JSON patch is valid (keys must match schema fields above). Run `skill-studio coverage <session_id>` to inspect current state.
- **Session not found** — Always run `new-session` before the first `apply-patch`. There is no implicit session creation. Run `skill-studio list` to check existing sessions.
- **Voice mode key errors** — Run `skill-studio init` to configure missing keys, or fall back to text mode.
## Notes
- The interview loop runs entirely inside Claude Code for text mode. No Anthropic API key is required.
- Voice mode LLM provider is swappable via `LLM_PROVIDER=anthropic` (default is `openrouter`).
章节与文件索引
按说明文件中的顺序排列。
目的
建筑
何时使用
先决条件
访谈协议(文本模式)
文件/命令 -> design.md · design.svg · skill-studio · pip install -e . · skill-studio init · --voice · DAILY_API_KEY · GROQ_API_KEY
内容校验值 -> 8370b53e8eaf
当前原文的自动摘译,尚未人工审校。
目的
进行结构化 JTBD 访谈,了解要构建什么、为谁构建以及为什么构建,然后发布一页纸
design.md+design.svg规格位于“我应该自动化这个吗?”之间(自动化顾问)和“我如何将其打包为一项技能?” (技能创造者)。建筑
该技能包含一个外部 CLI 工具(
skill-studio)通过 pip 安装。 CLI 处理会话状态、覆盖范围跟踪和导出。该技能编排 CLI — 它不直接捆绑脚本。何时使用
触发以下任何一项:“帮助我设计...”、“培养...的技能”、“为...设计自动化”、“我想要一个机器人/代理/工作流程...”、“范围新的快捷方式”。当用户描述反复出现的疼痛并询问如何自动化处理时也会触发。还触发会话分析:“分析此会话”、“我可以从中构建哪些技能”、“从会话中提出技能”、“我使用了哪些工作流程”、“我在本次会话中做了什么”、“从我的工作中提取模式”、“将此会话转变为技能”、“可以从中自动化什么”。如果用户引用会话 ID 或询问子代理活动,则此技能会处理它。
先决条件
skill-studio路径上的 CLI (pip install -e .在技能目录中,或者skill-studio init用于指导设置)Python 3.11+ 文本模式不需要 API 密钥 - 采访在 Claude Code 语音模式中本地运行(--voice)需要DAILY_API_KEY,GROQ_API_KEY,DEEPGRAM_API_KEY,以及 LLM 提供商密钥(OPENROUTER_API_KEY默认情况下)。如果缺少任何键,建议改为文本模式。要验证 CLI 是否可用,请运行skill-studio --help。如果找不到该命令,请从技能的基本目录安装它:pip install -e <skill-studio-base-dir>。访谈协议(文本模式)
按顺序执行以下步骤。