blog-drafts

Manage internal blog drafts and revision history before publication.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/b0ase/path401-com --skill blog-drafts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog-drafts
Source: https://github.com/b0ase/path401-com/tree/main/.claude/skills/blog-drafts
Command: npx skills add https://github.com/b0ase/path401-com --skill blog-drafts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internal blogging requires careful review and version tracking to prevent premature publication and to maintain quality and regulatory compliance.

Core Features & Use Cases

  • Sequential revisions: store edits as numbered files per slug (e.g., content/drafts/[slug]/1.md, 2.md, ...), providing a clear audit trail.
  • Draft lifecycle: supports internal knowledge base, sensitive topics, regulatory considerations, and review workflows before publishing.
  • Publish-ready workflow: promote the final revision to the public blog with optional formatting and review integrations.

Quick Start

Create content/drafts/[slug]/1.md with frontmatter and initial content, then add revisions as content/drafts/[slug]/2.md, content/drafts/[slug]/3.md, and so on.

Frequently Asked Questions about blog-drafts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage internal blog drafts to prevent premature publication?

Internal blog drafts are managed by storing sequential revisions as numbered files per slug within a content/drafts/[slug]/ directory. Each draft requires frontmatter, creating a clear audit trail before any final version is promoted to publication.

What's the best way to track revision history for sensitive blog content?

Tracking revision history for sensitive blog content involves saving iterative edits as numbered markdown files (e.g., 1.md, 2.md) under a shared slug directory. This sequential file structure supports review workflows and regulatory compliance considerations before publishing.

How do I set up the file structure for blog draft revisions?

You set up the file structure by creating a content/drafts/[slug]/ directory and adding your initial content as 1.md with frontmatter. Subsequent edits are then added sequentially as 2.md, 3.md, and so on within the same slug folder.

Can I integrate a draft review workflow with my existing blog tooling?

Yes, you can integrate this draft review workflow with existing blog tooling. The process supports promoting the final revision to your public blog with optional formatting and review integrations to ensure publish-ready compliance.

When do I need a dedicated internal drafts workflow for blog posts?

You need a dedicated internal drafts workflow when handling sensitive topics, legal or regulatory content, and iterative messaging. It guards internal drafts before publication by enforcing sequential version tracking and structured reviews.