CHRISTINE Turn One Expert Call Into Your Build Plan
Intelligence Extract mines any conversation with someone ahead of you — their systems, their terminology, their workflows, their principles — and hands it all back as one structured document with specific steps to implement it in your own business.
← Back to the Skills LibraryInstalled in under a minute. No tech skills required.
You don't need to know how to code, and you don't need to set anything up. There are two blocks below. If you can copy and paste, you can install this.
Paste the instruction
Copy the first block and paste it into a brand-new Claude conversation. Don't hit send yet — it's the note that tells Claude what to do.
Paste the skill underneath, then send
Copy the full skill block and paste it right below the instruction. Send it. Claude builds the skill, personalizes it to your business, and confirms when it's ready.
Install the skill below for me. Keep the skill text exactly as written, then personalize its defaults from what you already know about me — my business, my voice, my priorities, and the places I keep my notes and files. Confirm when it's installed and show me exactly how to run it.
---
name: intelligence-extract
description: Mine any conversation transcript with an expert, colleague, or thought leader to extract their unique knowledge, terminology, architecture patterns, workflows, and operational intelligence that you can implement into your own infrastructure. Use this skill whenever you say "extract intelligence," "intelligence extract," "what did they teach me," "mine this for what I can use," "extract what they know," "what can I steal from this person," or drop a transcript and want to capture what the OTHER person shared that is valuable for your own build. Also trigger when you want to process a call with a technical expert, architect, operator, or thought leader into implementable knowledge for your own systems. This skill captures another person's expertise and turns it into infrastructure you can build on.
---
# Intelligence Extract: Knowledge Mining Engine
You take a conversation where someone shared expertise, architecture, workflows, or operational knowledge and you mine it for everything you can implement into your own world.
Intelligence Extract mines what ONE specific person shared so you can absorb their knowledge and build on it.
Think of it this way. You just had a call with someone who is 6 months ahead of you in a specific area. They showed you their system, dropped terminology you had never heard, described workflows that blew your mind. This skill captures ALL of it in a structured format so nothing gets lost and everything becomes implementable.
## Trigger Phrases
- "extract intelligence"
- "intelligence extract"
- "mine this for what I can use"
- "what did they teach me"
- "extract what they know"
- "what can I steal from this person"
- "run intelligence extract"
- Any transcript drop where you want to capture what another person shared for your own implementation
## Input
Any conversation transcript where one or more participants shared expertise, systems, architecture, tools, terminology, or operational patterns worth capturing. Common sources:
- Call with a technical expert or architect
- Mastermind session with a peer who is ahead in a specific area
- Coaching call where the client revealed valuable process knowledge
- Podcast interview with a thought leader
- Strategy call with a potential partner
- Workshop or training session notes
- Any conversation where someone showed you how they do something
## The Engine: Four Extraction Passes
### Pass 1: Architecture and Systems
Read the entire transcript looking for how this person builds and operates their systems.
For each architecture pattern or system found, extract:
| Field | What to capture |
|---|---|
| **Pattern name** | A clear, memorable name for this architecture pattern or system (use their term if they named it, or create one) |
| **What they built** | Plain description of the system, structure, or architecture. Written so someone who was not on the call understands it completely. |
| **Why this matters for you** | Direct connection to your goals, current build, or infrastructure. How does this fit into what you are already doing? |
| **Implementation path** | Specific numbered steps to implement this in your own world. Name the tools, the files, the systems. Be concrete enough to start today. |
Requirements:
- Capture EVERY system, architecture, or structural pattern mentioned. Do not filter prematurely. If they described how something is organized, how agents collaborate, how data flows, how teams are structured, how tools connect, capture it.
- The implementation path must reference your actual tools and systems when known.
### Pass 2: Terminology and Language
Read the transcript again looking for specific words, terms, and phrases this person uses that represent concepts you need to know.
Create a glossary table:
| Term | What they mean by it | Your version (how to think about this in your own context) |
|---|---|---|
Requirements:
- Capture every technical term, framework name, tool name, or concept that would be valuable for you to have in your vocabulary.
- "Your version" must translate the term into your world. Not just a definition. An application.
- Include tools and platforms mentioned with brief descriptions of what they do and why they matter.
### Pass 3: Workflows and Operational Patterns
Read the transcript looking for how this person actually operates day to day. Their habits, their sequences, their automations, their decision patterns.
For each workflow or operational pattern, extract:
| Field | What to capture |
|---|---|
| **Pattern name** | Clear name for this workflow or operational habit |
| **What they do** | Step-by-step description of the workflow or pattern as they described it |
| **What makes this valuable** | Why this pattern produces results. What is the leverage point? |
| **How to adopt this** | Specific steps to implement this pattern in your own workflow. Adapted to your tools, schedule, and operating style. |
Requirements:
- Capture both explicit workflows (they walked you through it step by step) and implicit patterns (things they do that they might not even realize are a system).
- "How to adopt this" must be practical and immediate. More like "set this up tomorrow morning during your first focused block."
### Pass 4: Strategic Insights and Principles
Read the transcript one final time looking for the higher-level thinking. The mental models. The principles. The beliefs that drive their decisions. The things they said that made you stop and think.
For each strategic insight, extract:
| Field | What to capture |
|---|---|
| **The insight** | One clear statement of the principle or mental model |
| **Context** | When and why they said it. What prompted this insight in the conversation? |
| **Why this hits** | What makes this insight valuable for your situation specifically? |
| **How to apply this** | One concrete way to put this principle into practice this week |
Requirements:
- These should be the "quotable moments" and "mindset shifts" from the conversation.
- Only include insights that are genuinely valuable. Not generic motivation. Specific, applicable principles.
## Output Format
The output is a clean, structured markdown document. Not an interactive artifact. This is a reference document that goes into your notes, wherever you keep them.
```
# Intelligence Extract: [Person's Name]
**Source:** [Call description, date, duration]
**Extraction date:** [YYYY-MM-DD]
**Context:** [One sentence on who this person is and why their expertise matters]
---
## Architecture and Systems
### [Pattern Name]
**What they built:** [Description]
**Why this matters for you:** [Connection to your world]
**Implementation:**
1. [Step]
2. [Step]
3. [Step]
---
[Repeat for each pattern]
---
## Terminology Glossary
| Term | What They Mean | Your Version |
|---|---|---|
| [Term] | [Their definition] | [Applied to your context] |
---
## Workflows and Operational Patterns
### [Pattern Name]
**What they do:** [Description]
**What makes this valuable:** [The leverage point]
**How to adopt this:**
1. [Step]
2. [Step]
3. [Step]
---
[Repeat for each pattern]
---
## Strategic Insights
### "[The insight in their words or paraphrased clearly]"
**Context:** [When and why they said it]
**Why this hits:** [Why it matters for your situation]
**How to apply this:** [One concrete action this week]
---
[Repeat for each insight]
---
## Implementation Priorities
**This week:**
1. [Item]
2. [Item]
3. [Item]
**Next 2 weeks:**
4. [Item]
5. [Item]
6. [Item]
**This month:**
7. [Item]
8. [Item]
9. [Item]
---
## Routing
| What | Suggested home in your notes |
|---|---|
| [Architecture patterns] | [Where systems and builds live] |
| [Terminology] | [Where your glossary lives] |
| [Workflows] | [Where your operating patterns live] |
| [Strategic insights] | [Where your principles live] |
```
## Quality Standards
**Every architecture pattern must have an implementation path.** If you cannot write specific steps to implement it, it is not actionable and should be moved to a "future reference" note, not the main extraction.
**Every term in the glossary must have a "Your Version."** The glossary is a translation layer between their world and yours.
**Every workflow must be adoptable.** Adoptable. If you cannot start doing it this week, reframe it as something you can.
**The implementation priorities section is the most important part of the document.** This is what you look at tomorrow morning to know exactly what to do. Bias heavily toward action now.
**Capture the person's actual words when they said something that hits.** Quotable moments in the Strategic Insights section should use their real language when possible. This preserves the original signal.
## Voice and Tone
Write in your own voice. Direct, clear, action-oriented.
**Do this:**
- Conversational and specific
- "You" throughout the implementation sections
- Name the actual tools, files, databases, and systems
- Short paragraphs, clear structure
- Speak like you are handing a field guide to a friend
**Never do this:**
- Never use: delve, unlock, craft, foster, tapestry, embarking, unleash, unveil, realm, boasts, revolutionize, tenets
- Never use semicolons
- Never use contrastive framing ("Not X, but Y")
- Never be vague when you can be specific
- Never pad with items that do not have clear implementation value
- Never write it like an academic paper or blog post
## After Delivery
After presenting the extraction, offer:
1. **"Want me to save this to your notes?"** Route the full extraction or specific sections to wherever you keep your reference material.
2. **"Want me to turn this into a one-page reference card?"** If the session produced a big enough insight, capture it as a standalone card.
3. **"Want me to pull the action list into your task manager?"** Take the implementation priorities and drop them where you actually work.
4. **"Any of these patterns worth turning into a skill?"** If a workflow or architecture pattern is repeatable enough, it could become its own Claude skill.
From then on, just drop in a transcript and say "Extract intelligence."
Want to go further than skills?
Skills like this are how Christine runs her own business every day. In the Heart-Led AI Signature Group Coaching, she teaches you the whole system — live, in plain English, at your pace.
Explore Signature CoachingOne reference document. Everything they taught you.
Run Intelligence Extract on any expert conversation and you get back a clean, structured reference document — not a pile of scattered notes. These are the labeled sections of the real output, every time:
1 · Architecture & Systems
Every system and structural pattern they described — what they built, why it matters for your world, and numbered steps to implement it with your actual tools.
2 · Terminology Glossary
Every term, framework, and tool worth having in your vocabulary — what they mean by it, plus a "your version" that translates it into your own context.
3 · Workflows & Operational Patterns
How they actually operate day to day — their habits, sequences, and automations, each with practical steps to adopt it in your own week.
4 · Strategic Insights
The principles and mental models behind their decisions — captured in their own words when they said it best, with one concrete way to apply each this week.
5 · Implementation Priorities — plus the Routing Table
The most important section of the document: exactly what to do this week, the next two weeks, and this month — plus a routing table showing where each piece belongs in your notes. This is what you look at tomorrow morning to know exactly what to do.
And if something isn't buildable yet?
Intelligence Extract holds a firm line: every pattern in the main document must come with a real implementation path. If it can't be written as specific steps you could start on, it moves to a future-reference note instead of padding the extraction. What's left is only what you can actually build.
Keep stacking: pairs beautifully with Knowledge Library
Intelligence Extract mines one conversation with one expert — Knowledge Library processes your whole collection of notes, surfacing the through-lines that run across everything you've captured.
Get Knowledge Library →Because the person ahead of you already solved it.
You just talked with someone six months ahead of you in one specific area. They showed you their system, dropped terms you'd never heard, described workflows that changed how you think. By next week, most of that is gone — unless you capture it in a form you can build from.
Four passes catch what one read misses
The skill reads the transcript four separate times — once for systems, once for terminology, once for workflows, once for principles. Each pass hunts for one kind of knowledge, so nothing valuable slips through because you were looking for something else.
Every pattern comes with an implementation path
It's never just "here's what they built." Each system arrives with numbered steps that name real tools — concrete enough to start today. Knowledge you can't act on is just trivia.
The glossary translates their world into yours
Every term gets a "your version" column — not just a definition, an application. That's the difference between knowing what an expert means and knowing what to do with it.
It tells you what to do tomorrow morning
The Implementation Priorities section splits everything into this week, the next two weeks, and this month — and the skill treats it as the most important part of the document. You end with a plan, not a pile.
It keeps their words when they said it best
When something hit hard on the call, the extraction quotes it in their real language instead of paraphrasing it flat. That preserves the original signal you'll want to come back to.