Talk Stage 1: Extract
Transforms raw material (article, transcript, notes, or a mix) into a structured summary ready for the pipeline's downstream stages. Auto-detects source type.
When to Use This Skill
- Starting a new talk from any source material
- First step of the talk pipeline (always run before other stages)
- Auditing existing source material before committing to a talk
What This Skill Does
- Collects metadata — asks for slug, event, date, duration, audience, mode if not provided
- Reads the source — loads the source file or inline content
- Detects source type — REX (real-world proof) vs Concept (ideas/thesis) based on content signals
- Extracts the narrative arc — chronological for REX, thematic for Concept
- Extracts metrics — every measurable number with its source
- Identifies main themes — 3-7 themes
- Flags gaps — what's missing for a complete talk
- Writes
{slug}-summary.md
Input
Required:
- Source file path or inline content (article
.mdx, transcript .md, notes)
- Metadata:
slug, event, date, duration, audience, type (--rex or --concept)
If metadata is missing → AskUserQuestion before proceeding.
Output
talks/{YYYY}-{slug}-summary.md
Source Type Detection
| REX signals |
Concept signals |
| Specific dates |
Theses, arguments |
| Measured metrics |
General observations |
| Project/tool names |
Trend observations |
| Commits, releases, PRs |
Analogies, metaphors |
| "I shipped", "We built" |
"I think", "In my opinion" |
If hybrid → note both components in the summary.
Output Format
# Talk Summary — {Provisional Title}
**Slug** : {slug}
**Event** : {event}
**Date** : {date}
**Duration** : {duration} min
**Audience** : {audience description}
**Type detected** : REX | Concept | Hybrid
**Source** : {source file path}
---
## Narrative Arc
{Arc description: 3-5 sentences. Chronological if REX, thematic if Concept.}
## Main Themes
| # | Theme | Short description | Weight |
|---|-------|------------------|--------|
| 1 | {theme} | {description} | High/Medium/Low |
...
## Key Metrics Extracted
{All measurable numbers found in the source}
Format: `{value}` — {context} — Source: {section/page/git}
Examples:
- `1,200 commits` over 7 months — Source: "acceleration" section
- `-97% traffic` after SSE migration — Source: CHANGELOG v1.1.0
If none → "No verifiable metrics found (Concept mode)"
## Narrative Potential
{3-5 sentences on the strengths and possible narrative angles.
What makes this talk potentially strong. What might be missing.}
## Gaps Identified
- [ ] {gap 1} — {how to fill it}
- [ ] {gap 2} — {how to fill it}
If no obvious gaps → "No major gaps identified."
## Recommendations for next stages
- **Research**: {recommended / not applicable (Concept mode)} — {why}
- **Concepts**: {priority themes to explore}
- **Position**: {angles already visible from the source material}
---
*Generated by talk-stage1-extract — {date}*
*Source: {source path}*
Metric Extraction Rules
- Do not round without indicating it
- Always include the metric's source
- If two sources contradict → flag both, do not pick one
- No invented metrics to fill gaps
- Use
{before} → {after} format for evolutions
Anti-patterns
- Vague summary ("This text is about AI...")
- Omitting metrics — even approximate ones with their source
- Hiding gaps — naming them is better than pretending they don't exist
- Changing the detected type without justification
- Inventing a narrative arc not present in the source
Validation Checklist
Tips
- Run this before the orchestrator if you want to verify the source material is usable
- The summary is the foundation — every downstream stage reads it
- Hybrid sources (part REX, part Concept) are fine — name both components clearly
Related
1---2name: talk-stage1-extract3description: Extracts and structures source material (articles, transcripts, notes) into a talk summary with narrative arc, themes, metrics, and gaps. Auto-detects REX vs Concept type. Use when starting a new talk from any source material or auditing existing material before committing to a talk.4---56# Talk Stage 1: Extract78Transforms raw material (article, transcript, notes, or a mix) into a structured summary ready for the pipeline's downstream stages. Auto-detects source type.910## When to Use This Skill1112- Starting a new talk from any source material13- First step of the talk pipeline (always run before other stages)14- Auditing existing source material before committing to a talk1516## What This Skill Does17181. **Collects metadata** — asks for slug, event, date, duration, audience, mode if not provided192. **Reads the source** — loads the source file or inline content203. **Detects source type** — REX (real-world proof) vs Concept (ideas/thesis) based on content signals214. **Extracts the narrative arc** — chronological for REX, thematic for Concept225. **Extracts metrics** — every measurable number with its source236. **Identifies main themes** — 3-7 themes247. **Flags gaps** — what's missing for a complete talk258. **Writes `{slug}-summary.md`**2627## Input2829Required:30- Source file path or inline content (article `.mdx`, transcript `.md`, notes)31- Metadata: `slug`, `event`, `date`, `duration`, `audience`, `type` (--rex or --concept)3233If metadata is missing → `AskUserQuestion` before proceeding.3435## Output3637`talks/{YYYY}-{slug}-summary.md`3839## Source Type Detection4041| REX signals | Concept signals |42|-------------|-----------------|43| Specific dates | Theses, arguments |44| Measured metrics | General observations |45| Project/tool names | Trend observations |46| Commits, releases, PRs | Analogies, metaphors |47| "I shipped", "We built" | "I think", "In my opinion" |4849If hybrid → note both components in the summary.5051## Output Format5253```markdown54# Talk Summary — {Provisional Title}5556**Slug** : {slug}57**Event** : {event}58**Date** : {date}59**Duration** : {duration} min60**Audience** : {audience description}61**Type detected** : REX | Concept | Hybrid62**Source** : {source file path}6364---6566## Narrative Arc6768{Arc description: 3-5 sentences. Chronological if REX, thematic if Concept.}6970## Main Themes7172| # | Theme | Short description | Weight |73|---|-------|------------------|--------|74| 1 | {theme} | {description} | High/Medium/Low |75...7677## Key Metrics Extracted7879{All measurable numbers found in the source}8081Format: `{value}` — {context} — Source: {section/page/git}8283Examples:84- `1,200 commits` over 7 months — Source: "acceleration" section85- `-97% traffic` after SSE migration — Source: CHANGELOG v1.1.08687If none → "No verifiable metrics found (Concept mode)"8889## Narrative Potential9091{3-5 sentences on the strengths and possible narrative angles.92What makes this talk potentially strong. What might be missing.}9394## Gaps Identified9596- [ ] {gap 1} — {how to fill it}97- [ ] {gap 2} — {how to fill it}9899If no obvious gaps → "No major gaps identified."100101## Recommendations for next stages102103- **Research**: {recommended / not applicable (Concept mode)} — {why}104- **Concepts**: {priority themes to explore}105- **Position**: {angles already visible from the source material}106107---108109*Generated by talk-stage1-extract — {date}*110*Source: {source path}*111```112113## Metric Extraction Rules114115- Do not round without indicating it116- Always include the metric's source117- If two sources contradict → flag both, do not pick one118- No invented metrics to fill gaps119- Use `{before} → {after}` format for evolutions120121## Anti-patterns122123- Vague summary ("This text is about AI...")124- Omitting metrics — even approximate ones with their source125- Hiding gaps — naming them is better than pretending they don't exist126- Changing the detected type without justification127- Inventing a narrative arc not present in the source128129## Validation Checklist130131- [ ] Source type detected and justified132- [ ] Narrative arc in 3-5 clear sentences133- [ ] All measurable metrics extracted with their source134- [ ] Main themes listed (3-7 max)135- [ ] Gaps explicitly identified136- [ ] File saved to `talks/{YYYY}-{slug}-summary.md`137138## Tips139140- Run this before the orchestrator if you want to verify the source material is usable141- The summary is the foundation — every downstream stage reads it142- Hybrid sources (part REX, part Concept) are fine — name both components clearly143144## Related145146- [Stage 2: Research](../stage-2-research/SKILL.md) — git archaeology (REX mode)147- [Stage 3: Concepts](../stage-3-concepts/SKILL.md) — reads this summary148- [Orchestrator](../orchestrator/SKILL.md) — runs all stages in sequence