菜单
Use when prepping for any work meeting (1:1, customer call, interview, review) - 60-second-readable brief
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.
Use when the user wants to capture a repeatable task as a reusable spell, or asks "how do I build a workflow / skill / framework for X"
Use when the meta-builder routes to kind=subagent. Generates a spell that dispatches one or more subagents to do work in parallel or in isolation.
Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).
Use when browsing what spells are available - bundled seeds, your personal library, or both. Filter by kind, audience, or update status.
| name | preparing-for-a-meeting |
| description | Use when prepping for any work meeting (1:1, customer call, interview, review) - 60-second-readable brief |
| kind | workflow |
| audience | knowledge-worker |
| ai-tools | any |
| complexity | simple |
| time | 5-15 min |
| version | 1.0.0 |
| source | bundled |
Generates a 60-second-readable brief you scan before the meeting starts. Three things you must know, two things to mention, three questions you could ask.
A one-screen brief with: TLDR, Key facts, Things to mention, Questions to ask.
This is a simple workflow.
Three things you'd be embarrassed not to know in this meeting. Examples: their company's recent news, their last interaction with you, the current state of the project being discussed.
For each must-know, find the answer and note the source so you could verify mid-meeting if asked.
Specific things from prior interactions or recent context that the other party would notice and appreciate. Avoids generic "great chat last time" filler.
Open-ended questions you could ask. Specific to the context, not generic ("what are your priorities?").
TLDR (1 sentence) / Key facts (3 bullets with sources) / Things to mention (2 bullets) / Questions to ask (3 bullets).
Return to Stage 1 if research reveals a must-know you missed.
Input: Hiring sync with Eng Manager Pat, 30 min, discussing two open roles.
Output:
TLDR: Pat needs help unblocking their senior backend role; their staff role is on hold.
Key facts:
- Senior backend role open since Jan; 2 candidates in pipeline (Greenhouse link)
- Staff role on hold since March (per Pat's last update)
- Pat's team shipped the new auth system last week (slack #eng)
Things to mention:
- Auth ship — congrats; ask about retro
- The new sourcing tool we trialed; results from last week
Questions to ask:
- What changed about the staff role hold?
- Of the 2 candidates in pipeline, which would you push to onsite this week?
- ...
