skill-from-notebook

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 0144be4307b8 · 23 Oct 2026Report an issue or request a re-scan

• Publishergbsoss GitHub organizationOwner of the repository this skill is read from
• Source foldergbsoss/skill-from-masters/skills/skill-from-notebookThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict0144be4307b8A new audit runs when the source changes
• Repository statusNot archivedLast push 249 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Extract methodologies from documents or examples to create executable skills

---
name: skill-from-notebook
description: Extract methodologies from documents or examples to create executable skills
model: sonnet
---

# Skill from Notebook

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 to Use

When users want to turn knowledge into executable skills:

- "I just read this article about code review, help me create a skill from it"
- "Here's a great technical blog post, extract the writing methodology"
- "Turn this PDF guide into a skill I can reuse"
- "Learn from this example and create a skill to produce similar output"

## Supported Input Types

| 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 |

## Step 0: Identify Input Type

**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):
- Contains words like "how to", "steps", "method", "guide"
- Has numbered lists or step sequences
- Written with teaching intent
- Describes "what to do"

**Path B indicators** (Example/Output):
- Is a complete work/artifact
- No teaching intent
- Is "the thing itself" rather than "how to make the thing"
- Examples: a well-written blog post, a polished proposal, a code project

---

## Path A: Extract from Methodology Document

### A1: Validate Document Suitability

Check if the document is suitable for skill generation (must meet at least 2):

- [ ] Has clear goal/outcome
- [ ] Has repeatable steps/process
- [ ] Has quality criteria
- [ ] Has context/scenario description

**If not suitable**: Tell user honestly and explain why.

### A2: Identify Skill Type

| 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 |

### A3: Extract Structure by Type

**For How-to:**
- Prerequisites
- Step sequence (with expected output per step)
- Final expected result
- Common errors

**For Decision:**
- Decision factors
- Options with pros/cons
- Decision tree/flowchart
- Recommended default

**For Framework:**
- Core concepts
- Analysis dimensions
- Application method
- Limitations

**For Checklist:**
- Check items with criteria
- Priority levels
- Commonly missed items

### A4: Generate Skill

Use this template:

```markdown
## 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]
```

---

## Path B: Reverse Engineer from Example

When input is a finished work (not a tutorial), reverse engineer the methodology.

### B1: Identify Output Type

What kind of artifact is this?
- Technical blog post
- Product proposal/PRD
- Academic paper
- Code architecture
- Design document
- Other: [specify]

### B2: Analyze Structure

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:
- How many parts does it have?
- What's the function of each part?
- What's the order and proportion?

### B3: Extract Quality Characteristics

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? |

### B4: Reverse Engineer the Process

Deduce: To create this output, what steps are needed?

```markdown
## 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]
```

### B5: Generate Skill

Use this template for reverse-engineered skills:

```markdown
## 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]
```

---

## Example: Path A (Methodology Document)

**User**: "Extract a skill from this article about writing good commit messages"

**Process**:
1. Read the article
2. Identify: This is a **How-to** type (has steps, teaching intent)
3. Extract:
   - Goal: Write clear, useful commit messa

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/gbsoss/skill-from-masters
git -C skill-from-masters checkout 0144be4307b8

Works in

1. 2026-10-23
   ✓SAFE B 89 / 100

   first audit · source 0144be4307b8

Questions about skill-from-notebook

• github.com/gbsoss/skill-from-masters/tree/main/skills/skill-from — the audited source at commit 0144be4307b8 and every finding aboveObserved · 23 Oct 2026

Spotted something wrong? Report a correction · Methodology