name	content-pipeline
description	Use when creating content — research, outline, draft, SEO, format for platform, social promo
arguments	[{"name":"topic","description":"Content topic or title","required":true},{"name":"platform","description":"Target platform: blog, medium, dev.to, docs","required":false},{"name":"audience","description":"Target audience","required":false}]

Content Pipeline Workflow

When to use

Writing a blog post, article, or documentation page from scratch (research → outline → draft → SEO → format → social promo).
Producing platform-targeted content for blog, Medium, Dev.to, or project docs.
Creating launch content for a product or feature release.

Step 1: Research

WebSearch for existing content on the topic (top 5 results)
Identify gaps — what's NOT covered well?
Find data, statistics, examples to reference
Check if project has existing content to build on

Step 2: Outline

Structure (adapt to content type):

Hook — why should reader care? (1-2 sentences)
Context — background needed to understand
Main sections (3-5, each with a clear takeaway)
Code examples / visuals where applicable
Conclusion with actionable next steps

Present outline to user for approval before drafting.

Step 3: Draft

Write in the voice/tone matching the brand
Technical content: accurate, code-tested, no hand-waving
Marketing content: benefit-driven, concise, scannable
Include code blocks with language tags
Add internal links to other project content if available

Step 4: SEO Optimization

Target keyword in title, H1, first paragraph
Related keywords in H2s and body
Meta description: <155 chars, compelling
Internal and external links (2-3 each)
Image alt text

Step 5: Platform Formatting

Blog/Next.js: MDX with frontmatter (title, date, tags, description)
Medium: clean markdown, no custom components
dev.to: frontmatter (title, published, tags, cover_image)
Docs: follow existing docs structure and style

Step 6: Social Promotion

Generate 2-3 social snippets (for social-post skill)
Key quote or stat for sharing
Thread-worthy breakdown if content is long

Más de este repositorio

mismo repositorio

research

KeiSeiLab/KeiSeiKit

Deep research on any topic using parallel agents, web search, and cross-referencing. Use when user asks to research, investigate, or deeply analyze a topic, technology, library, or concept. Triggers on keywords like "research", "investigate", "deep dive", "find out everything about". Supports `--angle` presets for common specializations (competitors, design-refs).

2026-06-017

animate

KeiSeiLab/KeiSeiKit

Gateway router for web animation work. Picks between /scroll-animation, /motion-design, or /ai-animation via one AskUserQuestion call, then hands off. Does NOT implement animation — the downstream skills remain the source of truth for their respective domains.

2026-05-307

batch-workflow

KeiSeiLab/KeiSeiKit

Use when running multi-skill pipelines — new-feature, marketing-launch, design-to-code, web-creation, full-audit, rag-setup workflows

2026-05-307

compose-solution

KeiSeiLab/KeiSeiKit

Meta-orchestrator — converts a free-text task description into the right artefact(s) (agent, skill, hook, rule, or block) by composing existing KeiSeiKit primitives. Pure-click decision chain except the single intake field. Enriches `_blocks/` over time via Phase 6 block-augmentation — the kit gets smarter with every invocation.

2026-05-307

design-inspiration

KeiSeiLab/KeiSeiKit

Deprecated alias for /research with the design-refs angle preset. Routes to /research focused on design patterns, visual archetype references, and award-winning site teardowns.

2026-05-307

dev-guard

KeiSeiLab/KeiSeiKit

Continuous parallel quality gate during development — 3 backend agents (security/perf/structure) check every significant code change in real-time. Run after writing code, before committing.

2026-05-307

Content Pipeline Workflow

When to use

Writing a blog post, article, or documentation page from scratch (research → outline → draft → SEO → format → social promo).

Producing platform-targeted content for blog, Medium, Dev.to, or project docs.

Creating launch content for a product or feature release.

Step 1: Research

WebSearch for existing content on the topic (top 5 results)

Identify gaps — what's NOT covered well?

Find data, statistics, examples to reference

Check if project has existing content to build on

Step 2: Outline

Structure (adapt to content type):

Hook — why should reader care? (1-2 sentences)

Context — background needed to understand

Main sections (3-5, each with a clear takeaway)

Code examples / visuals where applicable

Conclusion with actionable next steps

Present outline to user for approval before drafting.

Step 3: Draft

Write in the voice/tone matching the brand

Technical content: accurate, code-tested, no hand-waving

Marketing content: benefit-driven, concise, scannable

Include code blocks with language tags

Add internal links to other project content if available

Step 4: SEO Optimization

Target keyword in title, H1, first paragraph

Related keywords in H2s and body

Meta description: <155 chars, compelling

Internal and external links (2-3 each)

Image alt text

Step 5: Platform Formatting

Blog/Next.js: MDX with frontmatter (title, date, tags, description)

Medium: clean markdown, no custom components

dev.to: frontmatter (title, published, tags, cover_image)

Docs: follow existing docs structure and style

Step 6: Social Promotion

Generate 2-3 social snippets (for social-post skill)

Key quote or stat for sharing

Thread-worthy breakdown if content is long