Menu
Conference talk builder for technical CFP submissions, speaking proposals, timed talk outlines, and slide flows. Use when the user asks for a conference talk, CFP abstract, talk proposal, or to turn a project/article into a speaking proposal.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | talk |
| description | Conference talk builder for technical CFP submissions, speaking proposals, timed talk outlines, and slide flows. Use when the user asks for a conference talk, CFP abstract, talk proposal, or to turn a project/article into a speaking proposal. |
| user-invocable | true |
| argument-hint | [conference topic or title] |
Structured for technical developer conferences. Produces three core deliverables: CFP abstract, talk outline with timing, and key slides list. Optional iA Presenter markdown is generated only when the user asks for slide markdown.
The talk structure that gets accepted and remembered:
Before drafting, confirm or explicitly mark assumptions for:
Do not invent speaker experience. If credibility is missing, ask for the story, project, production incident, research, or client work that gives the speaker standing.
Complete when those four inputs are known or a clearly labeled assumption is shown for user approval.
Format (400–500 words total):
TITLE
[Direct and specific. Concrete beats clever.]
ABSTRACT (250–300 words)
Paragraph 1: The problem — what's painful now and why it matters
Paragraph 2: The journey — what was tried, what failed, what changed
Paragraph 3: What attendees will leave able to do
WHAT ATTENDEES WILL LEARN
- [Specific skill or decision they'll be able to make]
- [Specific tool, pattern, or technique they'll use]
- [Mental model that changes how they approach this problem]
SPEAKER BIO HOOK (50 words)
One sentence about why this speaker is the right person for this topic.
Complete when the abstract names the problem, journey, takeaway, and credibility hook.
[0:00-2:00] Opening hook — failure/question/stat
[2:00-7:00] Problem setup — the painful thing everyone does
[7:00-15:00] Journey — failed attempts and turning point
[15:00-22:00] Resolution — insight, demo, or concrete example
[22:00-25:00] Takeaways + Q&A setup
Adjust for actual length. Keep demo segments to 5–7 minutes max.
Not the slides themselves — the logical flow. One line per slide/beat:
1. Opening image/question
2. The mistake everyone makes
3. Concrete wrong-way example
4. Moment of discovery
5. Key concept / architecture diagram
6. Right-way example
7. Proof: benchmark, result, or production lesson
8. Demo or backup screenshot
9. Three takeaways
10. One slide people will photograph
If the user asks for slide markdown, load references/ia-presenter-syntax.md and follow it. Do not
reconstruct the syntax from memory.
Deliverables in this order:
Present 1–3 together; they inform each other and a CFP reviewer needs the full shape.
| Priority | Load when | Reference |
|---|---|---|
| 1 | Building the narrative arc or structuring the talk story | references/story-circle.md |
| 2 | Generating iA Presenter slide markdown | references/ia-presenter-syntax.md |
Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation.
Build and modify React Hook Form forms. Use when React Hook Form is mentioned, imported, installed, or established by project conventions, including controlled widget integration, schema validation, fetched edit forms, conditional fields, multi-step wizards, field arrays, submission errors, and dirty-state handling. Use the react-hook-form-audit skill when the job is review rather than implementation.
Capture a concrete work or learning receipt in today's Obsidian note, then optionally hand it to tweet-today or blog. Use when the user says "save this for sharing", "capture this receipt", "tweet this now", or when close-day promotes an Idea Worth Sharing.
End-of-day Obsidian ritual: close the active focus loop, triage Ideas Worth Sharing, and confirm tomorrow's carry-forward. Use for "close my day", "end of day", "wrap up today", or /close-day.
Daily startup ritual for the Obsidian vault: create today's workday note, surface exact context, and require the user to choose one daily outcome and next action. Use for "start my day", "daily startup", "today's focus", or /daily.
Obsidian goals review for quarterly, monthly, or weekly goal notes. Use when the user asks to review goals, run an OKR check-in, update goals, set monthly goals, check whether goals are on track, or runs /goals.