Document to Skill Pipeline

Use when authorized books, documentation folders, standards, research collections, or source notes should become a compact, reusable WorkBuddy Skill with progressive disclosure and provenance.

9 stars 3 forksResearch & Science

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sandbaseai/workbuddy-skill --skill document-to-skill-pipeline
Manual install
git clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/document-to-skill-pipeline ~/.claude/skills/document-to-skill-pipeline

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Document-to-Skill Pipeline

## Purpose and rights gate

Compile structured knowledge—not a document dump—into a Skill that an Agent can load on demand. Suitable inputs include licensed books, internal documentation, standards, specifications, research clusters, and public source collections whose redistribution or derivative-use rights are documented.

Before extracting anything, record the source title/owner, stable revision or retrieval date, license or permission basis, intended audience, target WorkBuddy Skill, and whether the result is for private study or redistribution. Do not scrape, reconstruct, or package a source the operator is not authorized to use. Publicly reachable does not automatically mean redistributable. Preserve attribution and provenance in `SOURCE.json` and keep the compiled result a synthesis rather than a substitute for the original.

## Choose a conversion mode

| Mode | Use | Output |
|---|---|---|
| full conversion | a bounded source set will be queried repeatedly | core Skill plus chapters/indexes |
| analyze only | structure should be reviewed before writing | extraction report; no generated Skill |
| generate from analysis | trusted analysis notes already exist | compiled structure and core |
| update/fold-in | new sources extend an existing Skill | refreshed sections and provenance diff |
| package | the result is ready for WorkBuddy distribution | validated Skill package and catalog entry |
Read the full skill on GitHub

Details

Skill name
document-to-skill-pipeline
Path
skills/document-to-skill-pipeline/SKILL.md
License
MIT
Repo updated
8 September 2026

FAQ

What does the Document to Skill Pipeline skill do?

Use when authorized books, documentation folders, standards, research collections, or source notes should become a compact, reusable WorkBuddy Skill with progressive disclosure and provenance.

How do I install the Document to Skill Pipeline skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill document-to-skill-pipeline. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Document to Skill Pipeline popular?

It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.

Related skills

Browse the most popular Claude skills, all research & science skills, or write your own with the skills generator.