Drop in any call with an expert, a peer, or a thought leader. Get back their systems, their terminology, their workflows, and their thinking, mapped into steps you can build this week.
← All Claude SkillsYou talk to smart people. Their best ideas fade within a day. Intelligence Extract reads any conversation and pulls out the systems, terms, workflows, and principles the other person shared, then hands you a step-by-step path to build each one into your own world. Copy the two blocks below and give them to your Claude.
Step 1. Copy the skill block below.
Step 2. Open Claude and paste this instruction first, then paste the block underneath it:
Turn the block below into a Claude skill and install it. Create the skill file exactly as written. Then personalize it with smart defaults from what you know about me: my business, the tools and systems I already run, my current priorities, and where I keep my notes. Confirm when it is installed and tell me 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.
Claude reads the block, builds the skill file, and installs it. From then on, you just run the skill in any conversation. No folders to find, no code to write.
Every week you see what's working, build it live, and put it to work in your business.
Here's the shape of what this skill hands you when it runs. Copy it, use it, keep moving.
You don't need to hold any of this in your head. That's the skill's job. If you're curious what it's doing for you, here's the idea underneath it.
Most expert conversations get consumed once and then evaporate. The knowledge was right there. It just had nowhere to go. Intelligence Extract gives it somewhere to go. It reads what one person shared, sorts it into four kinds of usable material, and hands you a build path for each piece. Talking to experts becomes building like one.
The skill reads the transcript four times, once for architecture, once for terminology, once for workflows, once for strategic insights. Every pass has its own lens, so nothing usable slips past.
Each system the skill finds arrives with numbered steps that name your tools and files. You get a system you can start building today.
Every term the expert used gets a Your Version column that maps it onto your context, so new language becomes an application you can act on.
The operating patterns come back adapted to your schedule and tools, framed as something you set up now rather than someday.
The extraction ends with a ranked action list split across this week, the next two weeks, and this month, so you know exactly where to start.
The skill reads your transcript four times, each pass with a different lens. Pass one captures architecture and systems. Pass two builds a terminology glossary. Pass three pulls the workflows and operating patterns. Pass four collects the strategic insights and principles. Four passes means nothing usable slips by.
Every architecture pattern the skill finds comes with an implementation path: specific numbered steps that name the tools, files, and systems you already run. It maps their system onto your world so you can start building it today.
The glossary captures every term, framework name, and tool the expert used. The Your Version column translates each one into your context, so a new word becomes an application you can act on rather than a definition you forget.