Skip to content

topic-brain-pimp

Active router for ALL topic intelligence requests — classifies and routes to the correct topic skill before any response. Use when scanning trends, mapping sentiment, scoring topics, managing topic memory, or scheduling content automation.

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 topic intelligence. Not documentation — an active router. Every topic request flows through this routing table before any response.

Mandatory Announcement — FIRST OUTPUT before anything else:

┏━ 🧠 topic-brain-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
Trending topics, what’s hot, social buzz, scantrend-scanner
Polarization, sentiment, sides, debatesentiment-mapper
Score topics, ranking, leaderboard, prioritytopic-scorer
Topic history, content-topics.json, CRUDtopic-memory
Schedule, cron, autonomous, automationcontent-scheduler
Show topics, browse, listManual mode (see below)

When user says “show topics” or “content-pumper topics”:

  1. Read content-topics.json from the project root
  2. Display scored leaderboard table:
RankTopicScoreVelocityStatus
1

No skill invocation needed — direct read + display.

When triggered by content-scheduler:

  1. trend-scanner — pull fresh trending signal
  2. topic-scorer — score and rank candidates
  3. Check score threshold (default: 70+)
  4. If threshold crossed → hand off to content-pumper-pimp
ChainSequence
Full Scantrend-scanner → sentiment-mapper → topic-scorer → topic-memory
Quick Scoretrend-scanner → topic-scorer → topic-memory
Sentiment Deep-Divetrend-scanner → sentiment-mapper → topic-scorer
  • research-discipline applies to all sub-skills — cite sources, date-aware queries
  • content-integrity applies when writing or generating content
  • Never respond about topics before invoking the target skill
  • If unclear, ask ONE clarifying question, then route