skill from notebook

Documentation Community

Skill notes

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

Step 0: Identify Input Type

Critical first step - Determine which processing path to use: Path A indicators (Methodology Document): Contains words like "how to", "steps", "method", "guide" Has numbered lists or step sequences Written with teaching intent

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

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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Documentation
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@GBSOSS · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview skill-from-notebook.preview
# Path B: Reverse Engineer from Example

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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.