writing-workflow — Claude Code skill: what it does, how to install
writing-workflow — a skill for Claude Code and Codex that structures writing into ideas, drafts, and published stages. Triggers when capturing a note, revising prose, or shipping a piece.
MIT 102 installs ★ 17 updated 2026-10-21
npx skills add inkeep/open-knowledge-skills --skill writing-workflow -a claude-codeWhat writing-workflow does
The skill structures short and medium-form writing across three dedicated folders: ideas/, drafts/, and published/. Notes in ideas/ stay short, and the agent flags items idle past 30 days to promote or park them. Once drafted, files live in drafts/ with frontmatter tracking word count and status, prompting updates if a draft sits unchanged for 14 days.
The published/ folder remains immutable; revising an article requires cloning it into a new draft. Pasting a Substack, Ghost, or Mirror link prompts the agent to populate canonical_url automatically.
Operation depends on a configured OpenKnowledge MCP server alongside the platform /open-knowledge skill. Local project setups seed via ok seed --pack writing-pipeline.
What it helps with
- structure essays and articles across ideas, drafts, and archive stages
- track stale ideas inactive for 30 days and untouched drafts past 14 days
- archive immutable published articles with canonical platform links
- recommend publishing channels based on draft metadata
Example prompts for the agent
- Capture a quick idea for a technical blog post in ideas/
- Surface any drafts that have been idle for over two weeks
- Publish this post to published/ and attach the Ghost link
How to install writing-workflow
1Skills CLI (Vercel)
npx skills add inkeep/open-knowledge-skills --skill writing-workflow -a claude-code2Manually: put the files in place
~/.claude/skills/writing-workflow/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/writing-workflow/
1Skills CLI (Vercel)
npx skills add inkeep/open-knowledge-skills --skill writing-workflow -a codex2Manually: put the files in place
.agents/skills/writing-workflow/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add inkeep/open-knowledge-skills --skill writing-workflow -a cursor2Manually: put the files in place
.cursor/skills/writing-workflow/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install inkeep/open-knowledge-skills skills/starter-packs/writing-workflow/writing-workflow2Manually: put the files in place
.github/skills/writing-workflow/SKILL.md1Skills CLI (Vercel)
npx skills add inkeep/open-knowledge-skills --skill writing-workflow -a gemini-cli2Platform CLI
gemini skills install https://github.com/inkeep/open-knowledge-skills --path skills/starter-packs/writing-workflow/writing-workflowManually: put the files in place
.devin/skills/writing-workflow/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add inkeep/open-knowledge-skills --skill writing-workflow -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about writing-workflow
How to install writing-workflow in Claude Code?
Run npx skills add inkeep/open-knowledge-skills --skill writing-workflow -a claude-code. The file will be placed in ~/.claude/skills/writing-workflow/SKILL.md.
What does writing-workflow do?
It manages a three-phase publishing pipeline from raw concepts to immutable published posts. The agent monitors stale files and suggests publication channels based on frontmatter.
What is required to run writing-workflow?
It requires the OpenKnowledge MCP server configured on the agent host and the platform /open-knowledge skill. Projects initialize the pack using ok seed --pack writing-pipeline.
Source text
SKILL.md · MIT
---
name: writing-workflow
description: "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."
compatibility: "Any agent host with the OpenKnowledge MCP server configured. Installed project-local by `ok seed --pack writing-pipeline` (`ok-beta` for Beta)."
metadata:
pack: "writing-pipeline"
author: "Inkeep"
repository: "https://github.com/inkeep/open-knowledge-skills"
---
# 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.
© Inkeep · MIT · inkeep/open-knowledge-skills