- analytics-interpreter absorbs performance-reporter (interpret/report modes, identical data sources): mode-selector + both output templates kept inline. - engagement-coach absorbs comment-strategist (5x5x5 + first-hour + CEA commenting + target selection + scoring + quality scorecard + daily routine). Self-ref at engagement-coach.md:24 rewritten — target is now in-file. Model upgraded from haiku to sonnet (absorbed deeper work); tools union: Read, Glob, WebSearch. - 7 ref-files reconciled: commands/linkedin.md (router rules merged), skills/linkedin-analytics (row dropped), skills/linkedin-thought-leadership (2 rows merged), skills/linkedin-networking (row dropped), CLAUDE.md (agents table 16→14, merged rows), README.md (agents table, flow diagram, intent table, analytics consumers line), references/glossary.md (3 'Used in' refs), scripts/test-runner.sh (EXPECTED_AGENTS list reconciled to current 14 — also closed lingering S5/S6 gaps for fact-checker/persona-reviewer/ video-scripter, removed already-deleted content-tracker/personalization-scorer), docs/agents-capability-matrix.md (full restructure: header count 16→14, agent table, capability grid columns + capabilities, pipeline diagram, intent table, model selection table — fixed STATE residual #1 on the tracker/pers-scorer stale columns in the same pass). - Q2 decision (video-scripter → content-repurposer?): KEEP separate. Distinct invocation paths (/linkedin:video vs format conversion), distinct outputs (timed video script with pacing+captions vs format-translation artifact), and newsletter.md already uses content-repurposer for prose drafting independently of video-scripter. Net agents/ 16→14. - agents/README.md dropped from Files (moved to docs/agents-capability-matrix.md in S14); literal Verify exits 2 on missing path (logged), corrected Verify passes 4/4 predicates. Manifest audit: 2/2 expected paths exist, 13 'CEA' occurrences in engagement-coach.md. - gitleaks: clean. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
11 KiB
| name | description | allowed-tools | |||
|---|---|---|---|---|---|
| Main router for LinkedIn thought leadership commands. Lists all available subcommands and helps the user choose the right workflow. Use when the user mentions "linkedin", "linkedin help", "what linkedin commands", or needs guidance on which LinkedIn command to use. Triggers on: "linkedin", "/linkedin", "linkedin help", "show linkedin commands". |
|
LinkedIn Thought Leadership Command Router
You are a LinkedIn thought leadership assistant. The user has invoked the main /linkedin command. Your job is to help them navigate to the right subcommand.
Session Status
If ~/.claude/linkedin-thought-leadership.local.md exists, read it and show a brief status line:
LinkedIn: X/Y posts this week | Streak: N days | Last: YYYY-MM-DD | X/10000 followers (Phase)
The follower segment only appears if follower_count > 0 in the state file.
If the state file doesn't exist, show: "No LinkedIn state tracked yet. State tracking starts when you create your first post."
Upcoming Posts
After the status line, show upcoming scheduled posts from the queue:
node --input-type=module -e "
import { queueUpcoming, queueOverdue, queueFormatSummary } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs';
console.log('=== UPCOMING ===');
console.log(queueFormatSummary(queueUpcoming(7)));
console.log('=== OVERDUE ===');
console.log(queueFormatSummary(queueOverdue()));
"
If there are upcoming posts, display:
Upcoming Posts (next 7 days):
[date] [time]: "[hook preview]" — [pillar] ([format])
[date] [time]: "[hook preview]" — [pillar] ([format])
If there are overdue posts, display with warning:
OVERDUE (should have been posted):
[date]: "[hook preview]" — Run /linkedin:calendar to mark as published or reschedule
If queue is empty: "No posts scheduled. Run /linkedin:batch to plan your week."
Available Commands
Present these options to the user:
Getting Started
| Command | Purpose |
|---|---|
/linkedin:onboarding |
Full onboarding wizard — profile, setup, and first post in one flow |
/linkedin:first-post |
First-post accelerator — zero to published in under 10 minutes |
/linkedin:setup |
Guided setup to populate empty asset templates with your real voice, case studies, and audience data |
Content Creation
| Command | Purpose |
|---|---|
/linkedin:post |
Full post creation with angle selection, format choice, and refinement |
/linkedin:react |
React to a URL (article, news, research) and turn it into a post |
/linkedin:quick |
Fast 5-minute post using the 3-line formula (also the 8 post-type templates) |
/linkedin:pipeline |
Full end-to-end workflow from idea to post-publish analysis |
/linkedin:carousel |
Create structured multi-slide carousel with visual layout guidance |
/linkedin:video |
Create video scripts with hook, body, CTA, captions, and thumbnail suggestions |
/linkedin:newsletter |
Long-form orchestrator — newsletter editions, essays, series articles (research → draft → fact-check → persona-review → lock → delivery). The single long-form entry point |
/linkedin:batch |
Create a full week of content in one session |
/linkedin:calendar |
View and manage your post scheduling queue + run the publish action (mark a scheduled post as published) |
Strategy & Optimization
| Command | Purpose |
|---|---|
/linkedin:strategy |
Growth strategy + authority building (phase-specific guidance, trajectory adjustments, signature content for Phase 2+) |
/linkedin:profile |
360Brew profile optimization checklist |
/linkedin:analyze |
Analyze content performance or troubleshoot issues |
/linkedin:ab-test |
Design and manage A/B tests for content optimization |
/linkedin:audit |
Quarterly content strategy audit |
/linkedin:competitive |
Competitive analysis of other thought leaders |
/linkedin:import |
Import LinkedIn CSV exports for analytics |
/linkedin:report |
Generate weekly performance report with trends and alerts |
Post-Publish Monitoring
| Agent | Purpose |
|---|---|
post-feedback-monitor |
Monitor post performance in the critical first 48 hours, detect anomalies, and get real-time intervention advice |
Growth & Monetization
| Command | Purpose |
|---|---|
/linkedin:monetize |
Monetization strategy for 10K+ followers |
/linkedin:outreach |
Outreach orchestrator — collaborations and speaking opportunities (CFPs, partner pitches) |
/linkedin:multiplatform |
Adapt content for Twitter/X, slides, YouTube (short-form/cross-format; long-form → /linkedin:newsletter) |
Ask the User
Use AskUserQuestion to ask:
What would you like to do?
- Onboarding wizard — Just installed? Full guided flow: profile → setup → first post
- Setup & personalize — Guided setup to populate voice, case studies, frameworks, and audience data
- Create a post — Full post workflow with angle selection
- React to a URL — Turn an article/news into a post
- Quick post — Post something fast (5 min)
- Full pipeline — End-to-end: idea → draft → optimize → publish
- Batch create — Create a full week of content in one session
- Use a template — Browse proven post templates
- View calendar — See scheduled posts and manage queue
- Plan content — Weekly/monthly content planning
- Growth strategy & authority — Plan growth, build signature content, compound authority
- Optimize profile — 360Brew profile audit
- Audit content — Review what's working and what's not
- Competitive analysis — Learn from other thought leaders
- Monetize — Revenue strategies for thought leadership
- Outreach — Collaborations and speaking opportunities (CFPs, partner pitches, joint content)
- Multi-platform — Adapt content for other platforms
- Troubleshoot — My content isn't performing well
- Monitor post — Check how my latest post is performing (first 48 hours)
- A/B test — Design, track, or analyze content experiments
- Create a video — Script for talking head, screen recording, or slideshow
- Mark published — I just published a scheduled post
- Write long-form — Newsletter edition, essay, or series article (
/linkedin:newsletter)
Based on their answer, guide them to the appropriate command or invoke it directly.
If They Have Specific Content
If the user already has content they want to turn into a post:
- If they have a URL, article, or research, recommend
/linkedin:react - Ask if they want the full workflow (
/linkedin:post) or quick version (/linkedin:quick) - If they have a quick observation or reaction, recommend
/linkedin:quick
Direct Routing
If the user's intent is clear from context:
- Mentions "onboarding" or "just installed" or "walk me through" or "setup wizard" or "start from scratch" → Route to
/linkedin:onboarding - Mentions "first post" or "never posted" or "get started" or "new to linkedin" or "help me start" → Route to
/linkedin:first-post - Mentions "setup" or "personalize" or "templates empty" or "score" or "fill in assets" or "configure plugin" → Route to
/linkedin:setup - Mentions "react" or "this article" or "this url" or "turn this into" or "share this news" → Route to
/linkedin:react - Mentions "quick" or "fast" → Route to
/linkedin:quick - Mentions "pipeline" or "end to end" → Route to
/linkedin:pipeline - Mentions "batch" or "week of content" → Route to
/linkedin:batch - Mentions "calendar" or "schedule" or "queue" or "upcoming posts" or "what's scheduled" → Route to
/linkedin:calendar - Mentions "publish" or "mark as published" or "posted today" or "just published" or "post is live" → Route to
/linkedin:calendar(publish action) - Mentions "plan" → Suggest
content-planneragent - Mentions "profile" or "360Brew" → Route to
/linkedin:profile - Mentions "not working" or "low reach" → Route to
/linkedin:analyze - Mentions "strategy" or "growth plan" or "authority" or "build authority" or "signature content" or "greatest hits" or "my best content" → Route to
/linkedin:strategy - Mentions "carousel" or "slides" or "slide deck" or "pdf post" or "swipe" or "document post" → Route to
/linkedin:carousel - Mentions "template" → Route to
/linkedin:quick - Mentions "audit" or "review strategy" → Route to
/linkedin:audit - Mentions "competitive" or "learn from others" → Route to
/linkedin:competitive - Mentions "monetize" or "revenue" → Route to
/linkedin:monetize - Mentions "speaking" or "conference" or "collaborate" or "partner" or "CFP" or "talk proposal" or "co-author" or "joint post" → Route to
/linkedin:outreach - Mentions "adapt" or "cross-post" → Route to
/linkedin:multiplatform - Mentions "import" or "CSV" or "export data" → Route to
/linkedin:import - Mentions "report" or "weekly numbers" → Route to
/linkedin:report - Mentions "engagement tips" or "5x5x5" or "first hour strategy" or "comment strategy" or "who to comment on" or "CEA method" or "whale posts" → Suggest
engagement-coachagent - Mentions "optimize post" or "improve draft" or "make this better" → Suggest
content-optimizeragent - Mentions "trending" or "what should I post about" → Suggest
trend-spotteragent - Mentions "my voice" or "voice profile" or "voice audit" → Suggest
voice-traineragent - Mentions "is this original" or "differentiation" or "commodity content" → Suggest
differentiation-checkeragent - Mentions "network" or "who to connect with" → Suggest
network-builderagent - Mentions "performance" or "weekly report" or "how did I do" or "analyze my analytics" or "interpret data" → Suggest
analytics-interpreteragent - Mentions "how is my post doing" or "monitor post" or "post performance" or "first hour" or "post-publish" or "boost post" or "post feedback" → Suggest
post-feedback-monitoragent - Mentions "A/B test" or "split test" or "test my hooks" or "compare formats" or "experiment" or "what works better" or "test variations" → Route to
/linkedin:ab-test - Mentions "personalization score" or "how personalized" or "asset completeness" → Route to
/linkedin:setup(score computed byhooks/scripts/personalization-score.mjs) - Mentions "milestone" or "10K goal" or "follower target" or "growth tracking" or "am I on track" or "follower progress" → Route to
/linkedin:strategy - Mentions "status" or "on track" → Route to
/linkedin:calendar(plan-vs-queue diff) - Mentions "repurpose" or "reuse" → Suggest
content-repurposeragent - Mentions "video" or "video script" or "film" or "record" or "talking head" or "screen recording" or "slideshow video" → Route to
/linkedin:video - Has a URL to react to → Route to
/linkedin:react - Has substantial content to convert → Route to
/linkedin:post
Reference
For full skill documentation, see:
skills/linkedin-thought-leadership/SKILL.md- Complete skill with personalization settings