Skip to content

content-pumper-pimp

Active router for ALL content generation requests — orchestrates research, writing, illustration, QA, and delivery. Use when creating any content piece, whether from topic brain or manual request.

ModelSource
sonnetpack: content-pumper
Full Reference If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill. IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT. This is not negotiable.

The orchestration layer for all content generation. Not documentation — an active router. Every content request flows through this routing table before any response.

Mandatory Announcement — FIRST OUTPUT before anything else:

┏━ ✍️ content-pumper-pimp ━━━━━━━━━━━━━━━━━━━━━━━┓
┃ [one-line description of request/routing] ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

No exceptions. Box frame first, then route.

Classify the request. Invoke the matching skill. No response before invocation.

Request PatternSkill
Research a topic for contentcontent-researcher
Write / create / draft contentcontent-writer
Generate illustrations / visuals / hero imagecontent-illustrator
Quality check, content QA, assesscontent-qa
Full pipeline, generate content, content-pumperFull pipeline (see below)
Trending topics, social buzz, trend scantrend-scanner
Topic sentiment, polarization map, debate sidessentiment-mapper
Score topics, topic ranking, topic leaderboardtopic-scorer
Content scheduling presets, content croncontent-scheduler

Detect mode before invoking the pipeline:

ConditionMode
DefaultBlog
topic.category contains "news" or "sports"News
topic.targetMode === "location"Location
topic.targetMode === "dual-angle" OR (topic.sentiment.polarized === true AND polarizationHeat > 0.5)Dual-angle
content-researcher → content-writer → content-illustrator → content-qa → delivery

Delivery routing by mode:

  • Blog / News → add-blog-post
  • Location → add-location-page
SourceTrigger
Topic from topic-memoryAutonomous (scheduler hand-off)
Topic title from userManual override
Existing draftQA-only pass (skip researcher + writer)

If content-qa rejects:

  1. Re-invoke content-writer with QA feedback attached
  2. Re-run content-qa
  3. Max 2 iterations — escalate to user if still failing after 2
  • content-integrity enforced on every generation pass
  • research-discipline applies to content-researcher — cite sources, date-aware queries
  • Never respond about content before invoking the target skill
  • If unclear, ask ONE clarifying question, then route