Social
coreyhaines31/marketingskills
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
Extract methodologies from documents or examples to create executable skills
Install Skill From Notebook
$ npx skills add GBSOSS/skill-from-masters --skill skill-from-notebook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GBSOSS/skill-from-masters skill-from-notebook --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-from-notebook .claude/skills/skill-from-notebook && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "skill-from-notebook" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-notebook into .claude/skills/skill-from-notebook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-notebook", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-notebookType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add GBSOSS/skill-from-masters --skill skill-from-notebook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GBSOSS/skill-from-masters skill-from-notebook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-from-notebook .agents/skills/skill-from-notebook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-from-notebook" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-notebook into .agents/skills/skill-from-notebook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-notebook", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GBSOSS/skill-from-masters --skill skill-from-notebook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GBSOSS/skill-from-masters skill-from-notebook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-from-notebook .cursor/skills/skill-from-notebook && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-from-notebook" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-notebook into .cursor/skills/skill-from-notebook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-notebook", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/GBSOSS/skill-from-masters.git --path skills/skill-from-notebook--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add GBSOSS/skill-from-masters --skill skill-from-notebook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GBSOSS/skill-from-masters skill-from-notebook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-from-notebook .gemini/skills/skill-from-notebook && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "skill-from-notebook" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-notebook into .gemini/skills/skill-from-notebook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-notebook", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install GBSOSS/skill-from-masters skill-from-notebookInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add GBSOSS/skill-from-masters --skill skill-from-notebook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-from-notebook .github/skills/skill-from-notebook && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "skill-from-notebook" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-notebook into .github/skills/skill-from-notebook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-notebook", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GBSOSS/skill-from-masters --skill skill-from-notebook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GBSOSS/skill-from-masters skill-from-notebook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GBSOSS/skill-from-masters.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-from-notebook .opencode/skills/skill-from-notebook && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-from-notebook" agent skill from https://github.com/GBSOSS/skill-from-masters/tree/main/skills/skill-from-notebook into .opencode/skills/skill-from-notebook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-notebook", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
skill-from-notebook- GitHub stars
- 1.6k
- Token cost
- ~2k tokens
- SKILL.md length
- 750 words
- Files
- 2
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Extract methodologies from documents or examples to create executable skills
- Works in 4 steps: Read the article → Identify: This is a How-to type (has… → Extract → …
- Writing & Content work in your project
- SKILL.md covers When to Use, Supported Input Types, Step 0: Identify Input Type and Path A: Extract from…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Skill From Notebook is an agent skill from GBSOSS/skill-from-masters. Extract methodologies from documents or examples to create executable skills
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `TEST-CASES.md`).
It sits in Writing & Content. The repository describes itself as: Stand on the shoulders of giants — Create AI skills built on proven methodologies from domain experts. The licence is MIT.
When your agent uses it
- Writing & Content work in your project
Example prompts
- “/skill-from-notebook”
Requirements
- Docker
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read the article
- Identify: This is a How-to type (has steps, teaching intent)
- Extract
- Generate skill with steps and checklist
What it can do on your machine
Read from SKILL.md and the folder at commit c4d27d2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Skill From Notebook loads about 2k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 750 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from GBSOSS/skill-from-masters at commit c4d27d2, republished under its MIT licence (© GBSOSS). 750 words, ~2,039 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-from-notebook/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- 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 suitablePath 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:
## 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?
## 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]Show full SKILL.md (310 more words)Show less
B5: Generate Skill
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]Example: Path A (Methodology Document)
User: "Extract a skill from this article about writing good commit messages"
Process:
- Read the article
- Identify: This is a How-to type (has steps, teaching intent)
- Extract:
- Goal: Write clear, useful commit messages
- Steps: Use conventional format, separate subject/body, etc.
- Quality criteria: Subject < 50 chars, imperative mood, etc.
- Generate skill with steps and checklist
Example: Path B (Reverse Engineering)
User: "Here's a great technical blog post. Learn from it and create a skill for writing similar posts."
Process:
- Identify: This is an example (finished work, no teaching intent)
- Analyze structure:
├── 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 - Extract quality characteristics:
- Title = specific tech + problem solved
- One idea per paragraph
- Code:text ratio ~40:60
- Personal anecdotes for credibility
- Reverse engineer steps:
- Start with a real problem you solved
- Write the solution first, then the setup
- Add code samples progressively
- etc.
- Generate skill: "How to Write a Technical Blog Post"
Advanced: Multi-Example Learning
When user provides multiple examples of the same type:
Example A ──┐
Example B ──┼──> Extract commonalities ──> Core methodology
Example C ──┘ │
▼
Analyze differences ──> Style variants / Optional techniquesThis produces more robust, generalizable skills.
Important Notes
- Always validate first - Not all content is suitable for skill extraction
- Identify the path early - Methodology doc vs Example require different approaches
- Be specific - Vague skills are useless; include concrete steps and criteria
- Preserve the source - Always credit where the knowledge came from
- Ask for clarification - If unsure about user intent, ask before proceeding
- Quality over speed - Take time to truly understand the content
What This Skill is NOT
- NOT a summarizer (that's NotebookLM's job)
- NOT a document converter
- It's about extracting actionable methodology that can be repeatedly executed
© GBSOSS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/skill-from-notebook of GBSOSS/skill-from-masters.
- SKILL.md
- TEST-CASES.md
Open the folder on GitHubat commit c4d27d2
Compare with similar skills
Skill From Notebook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill From Notebook this skillGBSOSS/skill-from-masters | 1.6k | — | ~2k | Automated safety check: Pass | MIT | |
| Socialcoreyhaines31/marketingskills | 54k | 4 repos | ~4.5k | Automated safety check: Pass | MIT | |
| HumanizerAzure-Samples/interview-coach-agent-framework | 173 | 38 repos | ~5.8k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| User-Facing Text Cleanupguillaumemeyer/watermarks-remover | 24k | — | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
Humanizer
Azure-Samples/interview-coach-agent-framework
Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.
Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
User-Facing Text Cleanup
guillaumemeyer/watermarks-remover
Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.
Install Anti Slop
trycompai/crm
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.
More from GBSOSS/skill-from-masters
Skill From Masters
GBSOSS/skill-from-masters
通过真实案例创建高质量skill。先找黄金案例和失败案例，归纳什么有效什么无效，再用理论解释为什么。skill是干活的，要从实践中学习，不是从书本中学习。触发词："帮我创建一个skill"、"我想做一个skill来..."
Skill From GitHub
GBSOSS/skill-from-masters
Create skills by learning from high-quality GitHub projects. An agent skill from GBSOSS/skill-from-masters.
Search Skill
GBSOSS/skill-from-masters
Search and recommend Claude Code skills from trusted marketplaces
Related
Categories
Questions about Skill From Notebook
What does Skill From Notebook do?
Extract methodologies from documents or examples to create executable skills. Skill From Notebook is an agent skill from GBSOSS/skill-from-masters.
When should I use Skill From Notebook?
Skill From Notebook fits situations like: writing & Content work in your project.
How do I install Skill From Notebook in Claude Code?
Run `npx skills add GBSOSS/skill-from-masters --skill skill-from-notebook -a claude-code`. Or copy the skill folder (skills/skill-from-notebook in GBSOSS/skill-from-masters) into .claude/skills/skill-from-notebook in your project. Claude Code loads it when a task matches its description.
How do I install Skill From Notebook in Codex?
Run `npx skills add GBSOSS/skill-from-masters --skill skill-from-notebook -a codex`. Or copy the skill folder (skills/skill-from-notebook in GBSOSS/skill-from-masters) into .agents/skills/skill-from-notebook in your project. Codex loads it when a task matches its description.
Can I use Skill From Notebook in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GBSOSS/skill-from-masters --skill skill-from-notebook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-from-notebook, .gemini/skills/skill-from-notebook, .github/skills/skill-from-notebook and .opencode/skills/skill-from-notebook in your project.
What does Skill From Notebook need to run?
SKILL.md names no scripts, command-line tools or credentials: Skill From Notebook is instructions for the agent only. Our summary lists: Docker.
Does Skill From Notebook access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Skill From Notebook safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Skill From Notebook use?
Skill From Notebook is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skill From Notebook use?
About 2k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Skill From Notebook?
Skills that share tags, products or a category with Skill From Notebook: Social (coreyhaines31/marketingskills, 54k stars), Humanizer (Azure-Samples/interview-coach-agent-framework, 173 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars) and JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill From Notebook?
GBSOSS (a GitHub organization) maintains it in GBSOSS/skill-from-masters, which has 1,588 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on February 16, 2026.
Source: GBSOSS/skill-from-masters on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.