// Extract methodologies from documents or examples to create executable skills
Search and recommend Claude Code skills from trusted marketplaces
通过真实案例创建高质量skill。先找黄金案例和失败案例，归纳什么有效什么无效，再用理论解释为什么。skill是干活的，要从实践中学习，不是从书本中学习。触发词："帮我创建一个skill"、"我想做一个skill来..."
Create skills by learning from high-quality GitHub projects
| name | skill-from-notebook |
| description | Extract methodologies from documents or examples to create executable skills |
| model | sonnet |
Extract actionable methodologies from learning materials (documents, articles, videos) or quality examples (blog posts, designs, code) to generate reusable Skills.
Core Philosophy: NotebookLM helps you understand. This skill helps you do.
When users want to turn knowledge into executable skills:
| Type | How to Process |
|---|---|
| Local files | PDF, Word, Markdown - Read directly |
| Web URL | WebFetch to extract content |
| YouTube | Use yt-dlp for subtitles, Whisper if unavailable |
| NotebookLM link | Browser automation to extract notes/summaries |
| Example/Output | Reverse engineer the methodology |
Critical first step - Determine which processing path to use:
User Input
│
├─ Has teaching intent? ("how to", "steps", "guide")
│ └─ YES → Path A: Methodology Document
│
├─ Is a finished work? (article, design, code, proposal)
│ └─ YES → Path B: Example (Reverse Engineering)
│
└─ Neither? → Tell user this content is not suitable
Path A indicators (Methodology Document):
Path B indicators (Example/Output):
Check if the document is suitable for skill generation (must meet at least 2):
If not suitable: Tell user honestly and explain why.
| Type | Characteristics | Examples |
|---|---|---|
| How-to | Clear step sequence, input→output | Deploy Docker, Configure CI/CD |
| Decision | Conditions, trade-offs, choices | Choose database, Select framework |
| Framework | Mental model, analysis dimensions | SWOT, 5W1H, First Principles |
| Checklist | Verification list, pass/fail criteria | Code review checklist, Launch checklist |
For How-to:
For Decision:
For Framework:
For Checklist:
Use this template:
## Applicable Scenarios
[When to use this skill]
## Prerequisites
- [What's needed before starting]
## Steps
1. [Step 1] - [Expected outcome]
2. [Step 2] - [Expected outcome]
...
## Quality Checkpoints
- [ ] [Checkpoint 1]
- [ ] [Checkpoint 2]
## Common Pitfalls
- [Pitfall 1]: [How to avoid]
## Source
- Document: [name/URL]
- Extracted: [timestamp]
When input is a finished work (not a tutorial), reverse engineer the methodology.
What kind of artifact is this?
Break down the example:
Structure Analysis:
├── [Part 1]: [Function] - [Proportion %]
├── [Part 2]: [Function] - [Proportion %]
├── [Part 3]: [Function] - [Proportion %]
└── [Part N]: [Function] - [Proportion %]
Questions to answer:
What makes this example good?
| Dimension | Questions |
|---|---|
| Structure | How is content organized? |
| Style | Tone, word choice, expression? |
| Technique | What methods make it effective? |
| Logic | How does information flow? |
| Details | Small but important touches? |
Deduce: To create this output, what steps are needed?
## Deduced Production Steps
1. [Step 1]: [What to do] - [Key point]
2. [Step 2]: [What to do] - [Key point]
...
## Key Decisions
- [Decision 1]: [Options] - [This example chose X because...]
## Reusable Techniques
- [Technique 1]: [How to apply]
- [Technique 2]: [How to apply]
Use this template for reverse-engineered skills:
## Output Type
[What kind of artifact this produces]
## Applicable Scenarios
[When to create this type of output]
## Structure Template
1. [Part 1]: [Function] - [~X%]
2. [Part 2]: [Function] - [~X%]
...
## Quality Characteristics (Learned from Example)
- [Characteristic 1]: [How it manifests]
- [Characteristic 2]: [How it manifests]
## Production Steps
1. [Step 1]: [What to do] - [Tips]
2. [Step 2]: [What to do] - [Tips]
...
## Checklist
- [ ] [Check item 1]
- [ ] [Check item 2]
## Reference Example
- Source: [name/URL]
- Analyzed: [timestamp]
User: "Extract a skill from this article about writing good commit messages"
Process:
User: "Here's a great technical blog post. Learn from it and create a skill for writing similar posts."
Process:
├── Hook: Real pain point (2-3 sentences)
├── Problem: 3 sentences on the core issue
├── Solution: Conclusion first, then details
├── Code: Each snippet < 20 lines, with comments
├── Pitfalls: 3 common errors
└── Summary: One-line takeaway
When user provides multiple examples of the same type:
Example A ──┐
Example B ──┼──> Extract commonalities ──> Core methodology
Example C ──┘ │
▼
Analyze differences ──> Style variants / Optional techniques
This produces more robust, generalizable skills.