Open Knowledge Pack Writing Pipeline Agent Skill

How to work in a Writing Pipeline project (the `writing-pipeline` starter pack): a three-stage drafting flow, ideas → drafts → published. Read when the project has these folders, OR when asked to capture an idea, start or revise a draft, review a piece before it ships, or publish it. Carries the stage flow and review behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.

605 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

3271

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/inkeep/open-knowledge --skill open-knowledge-pack-writing-pipeline

The instruction itself

3 sections, as written by the author

Writing Pipeline pack — how to work here

A lean three-stage flow for short-to-medium-form writing (essays, newsletters, blog posts).

> This skill is pack guidance. The platform open-knowledge skill (read/write/preview/linking/grounding rules) still governs every markdown operation — this layers the drafting flow on top.

ideas/      one-line premises, captured before they fade
   ↓ commit to writing it
drafts/     active prose; CRDT history covers revisions (no named-revision folders)
   ↓ ship
published/  shipped work; treat as immutable

Per-folder rules + agent behaviors

ideas/ — premises, headlines, fragments. Kept short on purpose; not a draft folder. Promote into drafts/ when you commit to the piece. *Agent: review ideas idle more than 30 days and surface them to park or promote.*
drafts/ — active prose. Frontmatter tracks status: drafting/review, word count, parent idea. *Agent: review drafts idle more than 14 days; for drafts in review, suggest publication targets based on target_form. If a piece needs research notes, create drafts/<slug>/research/ on demand rather than a top-level folder.*
published/ — shipped work; carries published_at, canonical_url, channel. Treat as immutable; to revise, copy to a new draft. *Agent: on publish, auto-fill canonical_url when a Substack / Ghost / Mirror URL is pasted into the file.*

Templates

Create with write({ document: { path, template: "<name>" } }). Templates carry only structure; section meaning lives here, not in the document body.

Other skills for the same job

different authors, same section of the catalogue

Doc Coauthoring

by anthropics

vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Test Driven Development

by w95

×7

Use when implementing any feature or bugfix, before writing implementation code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

Crafting Effective Readmes

by softaworks

×3

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

6k tokens

Opentrons Integration

by christophacham

×3

Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.

9k tokens scripts

How to use it

Copy the folder

Take inkeep/open-knowledge-pack-writing-pipeline from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.