feat(linkedin-thought-leadership): v1.0.0 — initial open-source import
Build LinkedIn thought leadership with algorithmic understanding, strategic consistency, and AI-assisted content creation. Updated for the January 2026 360Brew algorithm change. 16 agents, 25 commands, 6 skills, 9 hooks, 24 reference docs. Personal data sanitized: voice samples generalized to template, high-engagement posts cleared, region-specific references replaced with placeholders. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen
parent
7194a37129
commit
39f8b275a6
143 changed files with 32662 additions and 0 deletions
482
plugins/linkedin-thought-leadership/commands/ab-test.md
Normal file
482
plugins/linkedin-thought-leadership/commands/ab-test.md
Normal file
|
|
@ -0,0 +1,482 @@
|
|||
---
|
||||
name: linkedin:ab-test
|
||||
description: |
|
||||
Design and manage A/B tests for LinkedIn content. Creates structured experiments with hypothesis,
|
||||
variants, tracking, and result analysis. Supports the full testing lifecycle: design, log, analyze,
|
||||
review history, and get AI-recommended test suggestions.
|
||||
|
||||
Use when the user wants to test content variations, compare post formats, optimize hooks,
|
||||
or systematically improve their content strategy.
|
||||
Triggers on: "A/B test", "test my hooks", "compare formats", "experiment", "what works better",
|
||||
"optimize my posts", "test variations", "split test", "ab test", "which hook works".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Write
|
||||
- Bash
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn A/B Testing Command
|
||||
|
||||
You are a LinkedIn content experimentation specialist. Help the user design, track, and analyze A/B tests for their LinkedIn content using systematic methodology.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
Read these reference files:
|
||||
|
||||
```
|
||||
${CLAUDE_PLUGIN_ROOT}/references/ab-testing-framework.md
|
||||
${CLAUDE_PLUGIN_ROOT}/references/algorithm-signals-reference.md
|
||||
```
|
||||
|
||||
Check for existing state and analytics data:
|
||||
|
||||
```bash
|
||||
ls -1 ${CLAUDE_PLUGIN_ROOT}/assets/analytics/ab-tests/ 2>/dev/null | head -20
|
||||
```
|
||||
|
||||
```bash
|
||||
ls -1 ${CLAUDE_PLUGIN_ROOT}/assets/analytics/posts/ 2>/dev/null | grep -E '\.json$' | head -10
|
||||
```
|
||||
|
||||
If `~/.claude/linkedin-thought-leadership.local.md` exists, read it for user context (posting frequency, follower level, topics).
|
||||
|
||||
## Step 1: Determine Intent
|
||||
|
||||
Use AskUserQuestion to ask:
|
||||
|
||||
**What would you like to do?**
|
||||
|
||||
1. **Design a new A/B test** -- Create a hypothesis, define variants, plan execution
|
||||
2. **Log test results** -- Record metrics for an ongoing test
|
||||
3. **Analyze test results** -- Compare variants and draw conclusions
|
||||
4. **Review test history** -- See past tests and learnings
|
||||
5. **Get test suggestions** -- AI-recommended tests based on your data
|
||||
6. **Other** -- Describe what you need
|
||||
|
||||
Based on their selection, follow the corresponding step below.
|
||||
|
||||
---
|
||||
|
||||
## Step 2a: Design New Test
|
||||
|
||||
Guide the user through structured test design.
|
||||
|
||||
### 2a.1: Select Variable to Test
|
||||
|
||||
Present the categorized variable list from `ab-testing-framework.md`:
|
||||
|
||||
**Which variable do you want to test?**
|
||||
|
||||
**High Impact (recommended to start here):**
|
||||
1. Hook/Opening line -- Question vs. statement, personal vs. universal, short vs. long
|
||||
2. Post format -- Text-only vs. carousel vs. poll vs. video vs. document
|
||||
3. Content angle -- Story-based vs. tactical vs. contrarian vs. curation
|
||||
4. Call-to-action -- Question vs. invitation vs. challenge vs. none
|
||||
|
||||
**Medium Impact:**
|
||||
5. Post length -- Short (500 chars) vs. standard (1,200-1,800) vs. long (2,500+)
|
||||
6. Posting time -- Morning (7-9 AM) vs. lunch (11-1 PM) vs. evening (5-7 PM)
|
||||
7. Posting day -- Tue/Wed/Thu vs. Mon/Fri vs. weekend
|
||||
8. Visual elements -- With image vs. without, custom graphic vs. photo
|
||||
|
||||
**Low Impact (test last):**
|
||||
9. Hashtag count -- 0 vs. 3 vs. 5
|
||||
10. First comment -- With vs. without, link vs. context vs. question
|
||||
11. Emoji usage -- None vs. minimal vs. heavy
|
||||
12. Line spacing -- Dense vs. airy
|
||||
|
||||
Use AskUserQuestion with these options. If the user has no previous tests, explicitly recommend starting with #1 (hooks) as it has the highest impact.
|
||||
|
||||
### 2a.2: Define Hypothesis
|
||||
|
||||
Help the user formulate a clear hypothesis using this template:
|
||||
|
||||
> "Changing **[variable]** from **[A: current approach]** to **[B: new approach]** will increase **[metric]** by **[expected amount]**."
|
||||
|
||||
Ask the user:
|
||||
- What is your current approach (Variant A / Control)?
|
||||
- What change do you want to test (Variant B)?
|
||||
- What metric matters most? (Default: engagement rate)
|
||||
- What improvement do you expect? (Default: 20%+ difference)
|
||||
|
||||
### 2a.3: Design Variant A (Control)
|
||||
|
||||
Document the user's current approach in detail:
|
||||
- Describe the specific characteristics of their control variant
|
||||
- This should represent their standard, existing approach
|
||||
- Be concrete: "Bold statement hooks, e.g., 'AI readiness is a leadership problem.'"
|
||||
|
||||
### 2a.4: Design Variant B (Test)
|
||||
|
||||
Document the test variant:
|
||||
- Describe the specific change being introduced
|
||||
- Ensure ONLY the target variable changes
|
||||
- Be concrete: "Provocative question hooks, e.g., 'What if AI readiness has nothing to do with technology?'"
|
||||
|
||||
### 2a.5: Plan Execution
|
||||
|
||||
Generate a posting schedule that alternates A/B on comparable days:
|
||||
|
||||
- Use the user's typical posting days (from state file or ask)
|
||||
- Alternate variants across the same day slots each week
|
||||
- Default: 3 posts per variant across 2 weeks (6 total)
|
||||
- Suggest posting times based on algorithm-signals-reference.md (Tue-Thu, 8-9 AM optimal)
|
||||
|
||||
### 2a.6: Set Success Criteria
|
||||
|
||||
Confirm with the user:
|
||||
- Primary metric (default: engagement rate)
|
||||
- Minimum meaningful difference (default: 20%)
|
||||
- Minimum posts per variant (default: 3)
|
||||
|
||||
### 2a.7: Output Test Plan
|
||||
|
||||
Present the complete test plan:
|
||||
|
||||
```
|
||||
## New A/B Test Plan
|
||||
|
||||
**Test name:** [descriptive-slug, e.g., hook-question-vs-statement]
|
||||
**Created:** [YYYY-MM-DD]
|
||||
|
||||
### Hypothesis
|
||||
"Changing [variable] from [A] to [B] will increase [metric] by [amount]."
|
||||
|
||||
### Variable: [Name]
|
||||
- **Variant A (Control):** [Detailed description]
|
||||
- **Variant B (Test):** [Detailed description]
|
||||
|
||||
### Execution Plan
|
||||
| Post # | Target Date | Variant | Day | Time |
|
||||
|--------|------------|---------|-----|------|
|
||||
| 1 | [date] | A | Tue | 8 AM |
|
||||
| 2 | [date] | B | Wed | 8 AM |
|
||||
| 3 | [date] | A | Thu | 8 AM |
|
||||
| 4 | [date] | B | Tue | 8 AM |
|
||||
| 5 | [date] | A | Wed | 8 AM |
|
||||
| 6 | [date] | B | Thu | 8 AM |
|
||||
|
||||
### Success Criteria
|
||||
- **Primary metric:** [metric]
|
||||
- **Minimum meaningful difference:** 20%
|
||||
- **Minimum posts per variant:** 3
|
||||
- **Measurement delay:** 48-72 hours after each post
|
||||
|
||||
### What to Keep Constant
|
||||
- [Topic area]
|
||||
- [Post length range]
|
||||
- [Hashtag strategy]
|
||||
- [First comment approach]
|
||||
- [Engagement response pattern]
|
||||
- [All other variables not being tested]
|
||||
|
||||
### Status: ACTIVE
|
||||
**Posts completed:** A: 0/3, B: 0/3
|
||||
```
|
||||
|
||||
### 2a.8: Save Test Plan
|
||||
|
||||
Create the ab-tests directory if it does not exist:
|
||||
|
||||
```bash
|
||||
mkdir -p ${CLAUDE_PLUGIN_ROOT}/assets/analytics/ab-tests
|
||||
```
|
||||
|
||||
Save the test plan as a markdown file:
|
||||
|
||||
```
|
||||
${CLAUDE_PLUGIN_ROOT}/assets/analytics/ab-tests/[test-name].md
|
||||
```
|
||||
|
||||
Use the test name slug (e.g., `hook-question-vs-statement.md`).
|
||||
|
||||
Confirm to the user: "Test plan saved. When you publish your first post, come back with `/linkedin:ab-test` and select 'Log test results' to record metrics."
|
||||
|
||||
---
|
||||
|
||||
## Step 2b: Log Test Results
|
||||
|
||||
### 2b.1: List Active Tests
|
||||
|
||||
Scan for active tests:
|
||||
|
||||
```bash
|
||||
ls -1 ${CLAUDE_PLUGIN_ROOT}/assets/analytics/ab-tests/ 2>/dev/null | grep -E '\.md$'
|
||||
```
|
||||
|
||||
If no tests exist, tell the user: "No active tests found. Use option 1 to design a new test first."
|
||||
|
||||
If tests exist, present them and ask which test to log for using AskUserQuestion.
|
||||
|
||||
### 2b.2: Load Test File
|
||||
|
||||
Read the selected test file:
|
||||
|
||||
```bash
|
||||
cat ${CLAUDE_PLUGIN_ROOT}/assets/analytics/ab-tests/[test-name].md
|
||||
```
|
||||
|
||||
### 2b.3: Collect Post Metrics
|
||||
|
||||
Ask the user using AskUserQuestion:
|
||||
|
||||
1. **Which variant was this post?** (A or B)
|
||||
2. **Post date:** (YYYY-MM-DD)
|
||||
3. **Impressions:** (number)
|
||||
4. **Reactions:** (number)
|
||||
5. **Comments:** (number)
|
||||
6. **Reposts/Shares:** (number)
|
||||
7. **Brief post description:** (optional, for reference)
|
||||
|
||||
Calculate engagement rate: (reactions + comments + reposts) / impressions * 100
|
||||
|
||||
### 2b.4: Append to Test File
|
||||
|
||||
Add the post data to the "Individual Post Data" section of the test file. Update the "Posts completed" counter in the Status section.
|
||||
|
||||
### 2b.5: Show Running Comparison
|
||||
|
||||
After logging, display the current running comparison:
|
||||
|
||||
```
|
||||
## Running Comparison: [Test Name]
|
||||
|
||||
| Metric | Variant A (Avg, n=X) | Variant B (Avg, n=Y) | Current Diff |
|
||||
|--------|---------------------|---------------------|-------------|
|
||||
| Impressions | X | X | X% |
|
||||
| Engagement Rate | X% | X% | X% |
|
||||
| Comments | X | X | X% |
|
||||
|
||||
**Status:** X of 6 posts logged. [Y more needed before analysis.]
|
||||
**Next post should be:** Variant [A/B] on [suggested day]
|
||||
```
|
||||
|
||||
If minimum sample size (3 per variant) is reached, suggest: "You have enough data to run analysis. Use option 3 to analyze results."
|
||||
|
||||
---
|
||||
|
||||
## Step 2c: Analyze Test Results
|
||||
|
||||
### 2c.1: Select Test to Analyze
|
||||
|
||||
List tests with sufficient data (3+ posts per variant):
|
||||
|
||||
```bash
|
||||
ls -1 ${CLAUDE_PLUGIN_ROOT}/assets/analytics/ab-tests/ 2>/dev/null | grep -E '\.md$'
|
||||
```
|
||||
|
||||
Read each file and check if both variants have 3+ posts logged. Present only tests ready for analysis. If no tests have sufficient data, tell the user how many more posts are needed.
|
||||
|
||||
### 2c.2: Load and Calculate
|
||||
|
||||
Read the test file. For each variant:
|
||||
- Calculate average for each metric (impressions, engagement rate, comments, reposts)
|
||||
- Calculate percentage difference: ((B_avg - A_avg) / A_avg) * 100
|
||||
- Apply the 20% significance rule from the framework
|
||||
|
||||
### 2c.3: Cross-Reference Analytics Data
|
||||
|
||||
If analytics CLI data is available in `assets/analytics/posts/`, cross-reference the test period data with weekly reports for additional context (baseline comparison, trend alignment).
|
||||
|
||||
```bash
|
||||
ls -1 ${CLAUDE_PLUGIN_ROOT}/assets/analytics/weekly-reports/ 2>/dev/null | grep -E '\.json$' | head -10
|
||||
```
|
||||
|
||||
### 2c.4: Present Analysis
|
||||
|
||||
Output the analysis in this format:
|
||||
|
||||
```
|
||||
## A/B Test Results: [Test Name]
|
||||
|
||||
### Summary
|
||||
**Variable tested:** [Name]
|
||||
**Hypothesis:** [Original hypothesis]
|
||||
**Duration:** [X weeks, from W-XX to W-XX]
|
||||
**Posts per variant:** A: [X], B: [Y]
|
||||
|
||||
### Results Comparison
|
||||
| Metric | Variant A (Avg) | Variant B (Avg) | Difference | Significant? |
|
||||
|--------|----------------|----------------|------------|--------------|
|
||||
| Impressions | X | X | +X% | Yes/No |
|
||||
| Engagement Rate | X% | X% | +X% | Yes/No |
|
||||
| Comments | X | X | +X% | Yes/No |
|
||||
| Reposts | X | X | +X% | Yes/No |
|
||||
|
||||
### Verdict
|
||||
[Clear recommendation based on the data:]
|
||||
- **Adopt B:** If B wins with >20% difference on primary metric
|
||||
- **Keep A:** If A wins or difference is <20%
|
||||
- **Inconclusive:** If results are mixed or inconsistent across posts
|
||||
- **Extend test:** If sample size is borderline or results are close to 20% threshold
|
||||
|
||||
### Confidence Level
|
||||
**[High/Medium/Low]**
|
||||
- Based on sample size (3 = Medium, 5+ = High)
|
||||
- Based on consistency across individual posts
|
||||
- Based on alignment with secondary metrics
|
||||
|
||||
### Key Insight
|
||||
[One sentence capturing the most important learning for their content strategy]
|
||||
|
||||
### Recommended Next Steps
|
||||
1. [Action based on results, e.g., "Adopt question hooks as your default opening style"]
|
||||
2. [Follow-up test suggestion, e.g., "Now test Variant B hooks with different content angles"]
|
||||
3. [Strategic implication, e.g., "Update your content templates to use question hooks"]
|
||||
```
|
||||
|
||||
### 2c.5: Update Test File
|
||||
|
||||
Update the test file status from ACTIVE to COMPLETED. Add the conclusion and recommended actions to the file.
|
||||
|
||||
---
|
||||
|
||||
## Step 2d: Review Test History
|
||||
|
||||
### 2d.1: Scan All Tests
|
||||
|
||||
```bash
|
||||
ls -1 ${CLAUDE_PLUGIN_ROOT}/assets/analytics/ab-tests/ 2>/dev/null | grep -E '\.md$'
|
||||
```
|
||||
|
||||
If no tests exist: "No test history yet. Design your first test with option 1."
|
||||
|
||||
### 2d.2: Read and Summarize Each Test
|
||||
|
||||
Read each test file and extract: test name, variable tested, status, verdict, key insight.
|
||||
|
||||
### 2d.3: Present History
|
||||
|
||||
```
|
||||
## A/B Test History
|
||||
|
||||
| # | Test Name | Variable | Status | Verdict | Key Insight |
|
||||
|---|-----------|----------|--------|---------|-------------|
|
||||
| 1 | [name] | [var] | Completed | B wins | [insight] |
|
||||
| 2 | [name] | [var] | Active | Pending | [X/6 posts done] |
|
||||
| ... | ... | ... | ... | ... | ... |
|
||||
|
||||
### Cumulative Learnings
|
||||
|
||||
**What works for your audience:**
|
||||
- [Learning 1 from completed tests]
|
||||
- [Learning 2]
|
||||
|
||||
**What doesn't matter:**
|
||||
- [Variables that showed <20% difference]
|
||||
|
||||
**Still untested (high-impact):**
|
||||
- [High-impact variables not yet tested]
|
||||
|
||||
### Testing Coverage
|
||||
- High-impact variables tested: X/4
|
||||
- Medium-impact variables tested: X/4
|
||||
- Total tests completed: X
|
||||
- Total tests active: X
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Step 2e: Test Suggestions
|
||||
|
||||
### 2e.1: Assess Current State
|
||||
|
||||
Check what data is available:
|
||||
|
||||
1. **Test history:** Read `assets/analytics/ab-tests/` for completed tests
|
||||
2. **Analytics data:** Check `assets/analytics/posts/` for performance data
|
||||
3. **User context:** Read state file for posting patterns and goals
|
||||
|
||||
### 2e.2: Generate Suggestions
|
||||
|
||||
**If no previous tests:**
|
||||
Recommend starting with hook testing (Variable #1, highest impact):
|
||||
|
||||
> "Your first A/B test should focus on hooks -- the opening line of your posts. Hooks determine whether anyone clicks 'see more' and are the single biggest driver of impressions. I recommend testing question hooks vs. statement hooks across 6 posts over 2 weeks."
|
||||
|
||||
**If some tests completed:**
|
||||
- Check which high-impact variables remain untested
|
||||
- Suggest the next untested high-impact variable
|
||||
- Reference learnings from completed tests to inform the suggestion
|
||||
|
||||
**If analytics data shows patterns:**
|
||||
- Identify performance anomalies (e.g., posts on certain topics consistently outperform)
|
||||
- Suggest tests to validate observed patterns
|
||||
- Example: "Your data shows carousel posts get 2x more impressions than text posts. Let's test whether this holds when controlling for topic."
|
||||
|
||||
**If all high-impact variables tested:**
|
||||
- Move to medium-impact variables
|
||||
- Suggest combination tests (e.g., "Your best hook style + different posting times")
|
||||
- Recommend re-testing older variables with larger sample sizes
|
||||
|
||||
### 2e.3: Present Suggestion
|
||||
|
||||
```
|
||||
## Recommended Next Test
|
||||
|
||||
**Variable:** [Name] ([Impact Level])
|
||||
**Why this test:** [Reasoning based on their data and test history]
|
||||
|
||||
**Suggested hypothesis:**
|
||||
"Changing [X] from [A] to [B] will increase [metric] by [amount]."
|
||||
|
||||
**Priority:** [1-5 scale, with justification]
|
||||
|
||||
**Ready to design this test?** I can set up the full plan now with option 1.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Step 3: Follow-Up Actions
|
||||
|
||||
After any action, offer relevant next steps:
|
||||
|
||||
### After Designing a Test
|
||||
- "Ready to create your first Variant A post? Use `/linkedin:post` and mention it's for your A/B test."
|
||||
- "Set a reminder to alternate variants with each post."
|
||||
|
||||
### After Logging Results
|
||||
- "X more posts needed before analysis. Next post should be Variant [A/B]."
|
||||
- "Want to create the next test post now? Use `/linkedin:post`."
|
||||
- If enough data: "You have enough data. Want to analyze results now? (Option 3)"
|
||||
|
||||
### After Analysis
|
||||
- "Apply these learnings to your next post with `/linkedin:post`."
|
||||
- "Ready to design a follow-up test? (Option 1)"
|
||||
- "View your full analytics with `/linkedin:report`."
|
||||
|
||||
### After History Review
|
||||
- "Want to design a new test for an untested variable? (Option 1)"
|
||||
- "Get AI-recommended test suggestions? (Option 5)"
|
||||
|
||||
### Always Available
|
||||
- "View weekly performance report: `/linkedin:report`"
|
||||
- "Troubleshoot performance issues: `/linkedin:analyze`"
|
||||
- "Optimize a specific post: use the `content-optimizer` agent"
|
||||
|
||||
---
|
||||
|
||||
## Error Handling
|
||||
|
||||
### No Tests Directory
|
||||
If `assets/analytics/ab-tests/` does not exist and the user selects options 2-4:
|
||||
- Inform the user: "No tests found. The test directory will be created when you design your first test."
|
||||
- Redirect to option 1 (Design) or option 5 (Suggestions).
|
||||
|
||||
### Incomplete Test Data
|
||||
If a test file exists but has insufficient data for analysis:
|
||||
- Show how many posts are logged vs. required
|
||||
- Calculate how many more posts are needed
|
||||
- Suggest a timeline: "At 3 posts per week, you'll have enough data by [date]."
|
||||
|
||||
### Missing Analytics Data
|
||||
If no analytics CLI data is available for cross-referencing:
|
||||
- Proceed with test-specific data only
|
||||
- Note: "For richer analysis, import your LinkedIn analytics with `/linkedin:import`."
|
||||
|
||||
### Corrupted or Invalid Test Files
|
||||
If a test file cannot be parsed:
|
||||
- Warn the user: "Test file [name] appears to have formatting issues."
|
||||
- Offer to recreate the file from scratch while preserving any logged data.
|
||||
256
plugins/linkedin-thought-leadership/commands/analyze.md
Normal file
256
plugins/linkedin-thought-leadership/commands/analyze.md
Normal file
|
|
@ -0,0 +1,256 @@
|
|||
---
|
||||
name: linkedin:analyze
|
||||
description: |
|
||||
Analyze LinkedIn content performance and troubleshoot issues. Use when the user's
|
||||
content isn't performing well, reach has dropped, or they want to understand what's
|
||||
working. Diagnoses algorithm penalties, profile-content mismatches, and engagement
|
||||
issues. Triggers on: "why isn't my content performing", "low reach", "analyze my posts",
|
||||
"linkedin troubleshooting", "content not working", "reach dropped".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Performance Analysis & Troubleshooting
|
||||
|
||||
You are a LinkedIn performance analyst. Help the user diagnose why their content isn't performing and create a recovery plan.
|
||||
|
||||
## Load Context
|
||||
|
||||
Read these reference files:
|
||||
- `references/troubleshooting-guide.md` - Failure patterns and solutions
|
||||
- `references/algorithm-signals-reference.md` - Algorithm mechanics
|
||||
- `skills/linkedin-thought-leadership/SKILL.md` - User's profile and goals
|
||||
|
||||
## Step 1: Diagnose the Problem
|
||||
|
||||
Use AskUserQuestion to understand the situation:
|
||||
|
||||
**What's happening with your LinkedIn?**
|
||||
|
||||
1. Reach suddenly dropped (was good, now low)
|
||||
2. Reach has always been low (never got traction)
|
||||
3. High views but low engagement (people see but don't interact)
|
||||
4. Good first hour, then post dies
|
||||
5. Inconsistent results (some posts work, others don't)
|
||||
6. Plateau after initial growth (stuck at same level)
|
||||
|
||||
## Step 2: Gather Data
|
||||
|
||||
Based on their answer, ask relevant follow-up questions:
|
||||
|
||||
### If Reach Dropped Suddenly
|
||||
|
||||
- How much did it drop? (25%, 50%, 75%+?)
|
||||
- When did it start? (days/weeks ago)
|
||||
- Did you receive any policy violation notifications?
|
||||
- Did you change posting frequency recently?
|
||||
- Did you post on different topics than usual?
|
||||
- Did you use external links in recent posts?
|
||||
|
||||
### If Reach Has Always Been Low
|
||||
|
||||
- How often are you posting? (daily, 2-3x/week, less?)
|
||||
- How long have you been posting consistently? (weeks, months?)
|
||||
- Do you stay within 3-5 core topics?
|
||||
- Are you doing pre-posting engagement (5x5x5)?
|
||||
- Does your profile align with your content topics?
|
||||
|
||||
### If High Views But Low Engagement
|
||||
|
||||
- What does your typical hook look like?
|
||||
- How do your posts end? (CTA?)
|
||||
- How quickly do you respond to comments?
|
||||
- Are your topics inviting conversation?
|
||||
|
||||
### If Good First Hour Then Dies
|
||||
|
||||
- How many comments in first hour typically?
|
||||
- How quickly do you respond?
|
||||
- What's the quality of responses? (just "thanks" or substantive?)
|
||||
- Are you tagging relevant people in responses?
|
||||
|
||||
### If Inconsistent Results
|
||||
|
||||
- What types of posts perform well?
|
||||
- What types of posts perform poorly?
|
||||
- Are you tracking what works?
|
||||
- Are you posting at consistent times/days?
|
||||
|
||||
### If Plateau After Growth
|
||||
|
||||
- How many followers currently?
|
||||
- How long have you been at this level?
|
||||
- When was your last "viral" post?
|
||||
- Are you collaborating with others?
|
||||
- What formats are you using?
|
||||
|
||||
## Step 3: Apply Diagnostic Framework
|
||||
|
||||
Based on `references/troubleshooting-guide.md`, diagnose the pattern:
|
||||
|
||||
### Pattern: Good Content, Low Reach
|
||||
|
||||
**Possible causes:**
|
||||
- Posted at wrong time for YOUR audience
|
||||
- No pre-posting engagement (cold start)
|
||||
- Topic drift confusing algorithm
|
||||
- External link penalizing reach
|
||||
- Inconsistent posting breaking topical authority
|
||||
|
||||
### Pattern: High Views, Low Engagement
|
||||
|
||||
**Possible causes:**
|
||||
- Hook promises more than content delivers
|
||||
- CTA too generic or missing
|
||||
- Content doesn't invite conversation
|
||||
- Too polished/corporate, not authentic
|
||||
- No clear takeaway or lesson
|
||||
|
||||
### Pattern: Good First-Hour, Then Dies
|
||||
|
||||
**Possible causes:**
|
||||
- Didn't respond quickly to first comments
|
||||
- Responses too short ("thanks!")
|
||||
- No tagging of relevant people
|
||||
- Comment quality too low
|
||||
|
||||
### Pattern: Inconsistent Performance
|
||||
|
||||
**Possible causes:**
|
||||
- Random topics across posts
|
||||
- Varied posting times
|
||||
- No clear expertise positioning
|
||||
- Mixed quality (some posts rushed)
|
||||
- Not tracking what works
|
||||
|
||||
### Pattern: Plateau After Growth
|
||||
|
||||
**Possible causes:**
|
||||
- Same format repeatedly
|
||||
- Not collaborating
|
||||
- No optimization based on analytics
|
||||
- Playing it safe (no controversial takes)
|
||||
- No email list or monetization
|
||||
|
||||
## Step 4: Check for Algorithm Penalties
|
||||
|
||||
Run through this checklist:
|
||||
|
||||
- [ ] Did you use engagement bait language? ("Comment YES if...")
|
||||
- [ ] Did you add external links in post or first comment?
|
||||
- [ ] Have you been inconsistent (skipped week+)?
|
||||
- [ ] Are topics all over the place recently?
|
||||
- [ ] Did you receive generic AI-like comments?
|
||||
- [ ] Did you post way more/less frequently than usual?
|
||||
- [ ] Did you use 5+ hashtags in posts?
|
||||
- [ ] Did you tag unrelated people for reach?
|
||||
|
||||
## Step 5: Reach Drop Severity Assessment
|
||||
|
||||
Based on how much reach dropped:
|
||||
|
||||
### Down <25%
|
||||
**Diagnosis:** Normal fluctuation
|
||||
**Action:** Continue posting, monitor for trends
|
||||
|
||||
### Down 25-50%
|
||||
**Diagnosis:** Something went wrong
|
||||
**Action:**
|
||||
- Review last week's posts for issues
|
||||
- Increase engagement activity
|
||||
- Start soft recovery
|
||||
|
||||
### Down 50-75%
|
||||
**Diagnosis:** Algorithmic suppression likely
|
||||
**Action:**
|
||||
- Start 14-day recovery protocol
|
||||
- Profile audit immediately
|
||||
- Strict topic consistency
|
||||
|
||||
### Down 75%+
|
||||
**Diagnosis:** Major issue - possible shadow ban
|
||||
**Action:**
|
||||
- Check for policy violations
|
||||
- Full profile audit
|
||||
- Consider if starting fresh is viable
|
||||
|
||||
## Step 6: Create Recovery Plan
|
||||
|
||||
Based on diagnosis, provide specific action plan.
|
||||
|
||||
### If Profile-Content Mismatch (360Brew Failure)
|
||||
|
||||
**Days 1-3: Profile Audit**
|
||||
- [ ] Update headline with 3-4 topic keywords
|
||||
- [ ] Rewrite About section with clear expertise
|
||||
- [ ] Remove irrelevant Featured content
|
||||
- [ ] Check Skills section matches post topics
|
||||
- [ ] Request skill endorsements from connections
|
||||
|
||||
### If Content Reset Needed
|
||||
|
||||
**Days 4-7: Content Reset**
|
||||
- [ ] Post ONLY on core 2-3 topics
|
||||
- [ ] Use text-only format (lowest-risk)
|
||||
- [ ] Keep posts 1,200-1,500 characters
|
||||
- [ ] NO external links (even in comments)
|
||||
- [ ] Respond to every comment within 30 minutes
|
||||
|
||||
### If Engagement Rehabilitation Needed
|
||||
|
||||
**Days 8-11: Engagement Focus**
|
||||
- [ ] Comment 10-15x daily on posts in your topic area
|
||||
- [ ] Focus on 2nd-degree connections
|
||||
- [ ] Write 15+ word substantive comments only
|
||||
- [ ] Like and save posts before commenting
|
||||
- [ ] Tag relevant people in conversations
|
||||
|
||||
### If Gradual Expansion Appropriate
|
||||
|
||||
**Days 12-14: Gradual Expansion**
|
||||
- [ ] Increase post length to 1,500-1,800 characters
|
||||
- [ ] Try one carousel or document
|
||||
- [ ] Introduce topic-adjacent content (80/20 rule)
|
||||
- [ ] Monitor metrics closely
|
||||
- [ ] Continue high engagement activity
|
||||
|
||||
## Step 7: Timeline Expectations
|
||||
|
||||
Set realistic expectations:
|
||||
|
||||
| Suppression Level | Initial Improvement | Baseline Recovery | Full Restoration |
|
||||
|-------------------|---------------------|-------------------|------------------|
|
||||
| Mild (25-40% drop) | 7-10 days | 14-21 days | 3-4 weeks |
|
||||
| Moderate (50-70% drop) | 2-3 weeks | 4-6 weeks | 2-3 months |
|
||||
| Severe (75%+ drop) | 4-6 weeks | 3-6 months | May not be possible |
|
||||
|
||||
## Step 8: Prevention Checklist
|
||||
|
||||
For ongoing health, maintain:
|
||||
|
||||
- [ ] Post minimum 2x weekly (never >5 day gaps)
|
||||
- [ ] Stay within 3-5 core topics
|
||||
- [ ] Avoid engagement pods entirely
|
||||
- [ ] Limit external links to 1x per week maximum
|
||||
- [ ] Monitor reach weekly for early warning signs
|
||||
- [ ] Keep profile and content aligned
|
||||
- [ ] Respond to all comments within first hour
|
||||
- [ ] Engage with others' content daily (10+ comments)
|
||||
- [ ] Use native formats primarily
|
||||
- [ ] Track first-hour engagement velocity
|
||||
|
||||
## When to Start Fresh
|
||||
|
||||
Consider creating a new account if:
|
||||
- Zero improvement after 90 days of strict recovery
|
||||
- Multiple policy violations on record
|
||||
- Account age <1 year with <500 followers
|
||||
- Engagement permanently at near-zero
|
||||
- Profile can't be aligned with content (career change)
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `references/troubleshooting-guide.md` - Complete troubleshooting
|
||||
- `references/algorithm-signals-reference.md` - Algorithm mechanics
|
||||
- `references/growth-roadmaps.md` - Stall points and fixes
|
||||
258
plugins/linkedin-thought-leadership/commands/audit.md
Normal file
258
plugins/linkedin-thought-leadership/commands/audit.md
Normal file
|
|
@ -0,0 +1,258 @@
|
|||
---
|
||||
name: linkedin:audit
|
||||
description: |
|
||||
Periodic content strategy audit. Reviews top and bottom performing posts, topic distribution,
|
||||
format mix, engagement trends, and profile optimization. Run quarterly for best results.
|
||||
Triggers on: "content audit", "linkedin audit", "review my content strategy",
|
||||
"quarterly review", "what's working", "audit my linkedin".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Grep
|
||||
- WebFetch
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Content Audit
|
||||
|
||||
You are a LinkedIn content strategy auditor. Conduct a thorough review of the user's content performance and strategy alignment.
|
||||
|
||||
## Step 0: Gather Data
|
||||
|
||||
Load all available data:
|
||||
- Read `~/.claude/linkedin-thought-leadership.local.md` for posting history
|
||||
- Read `${CLAUDE_PLUGIN_ROOT}/assets/plans/` for planned content
|
||||
- Read `${CLAUDE_PLUGIN_ROOT}/skills/linkedin-thought-leadership/SKILL.md` for strategy reference
|
||||
- Read `${CLAUDE_PLUGIN_ROOT}/references/trajectory-strategy-adjustments.md` for trajectory-based adjustments
|
||||
- Check for any analytics data in `${CLAUDE_PLUGIN_ROOT}/assets/analytics/`
|
||||
- Read `assets/audience-insights/demographics.md` for audience composition — compare intended vs actual audience
|
||||
- Read `assets/audience-insights/engagement-patterns.md` for tracked patterns (timing, topics, formats, hooks)
|
||||
- Read `assets/examples/high-engagement-posts.md` for proven success patterns to benchmark against
|
||||
|
||||
Ask the user to provide:
|
||||
- Screenshot of LinkedIn analytics (last 90 days) or key metrics
|
||||
- Their top 5 performing posts (impressions + engagement)
|
||||
- Their bottom 5 performing posts
|
||||
- Any specific concerns or questions
|
||||
|
||||
## Step 1: Top Performers Analysis
|
||||
|
||||
For each top-performing post, analyze:
|
||||
|
||||
| Factor | Analysis |
|
||||
|--------|----------|
|
||||
| Hook type | Which hook pattern was used? |
|
||||
| Topic/pillar | Which expertise area? |
|
||||
| Format | Text, carousel, video? |
|
||||
| Length | Character count |
|
||||
| Day/time | When was it posted? |
|
||||
| CTA type | What engagement prompt? |
|
||||
| Content type | Educational, inspirational, entertaining? |
|
||||
|
||||
**Pattern identification:**
|
||||
- What do top posts have in common?
|
||||
- Which hooks consistently perform?
|
||||
- Which topics resonate most?
|
||||
|
||||
## Step 2: Bottom Performers Analysis
|
||||
|
||||
Same analysis for bottom performers:
|
||||
- What went wrong?
|
||||
- Common factors in low-performing posts?
|
||||
- Were any off-topic (360Brew penalty)?
|
||||
- External links in body?
|
||||
- Poor timing?
|
||||
|
||||
## Step 3: Topic Distribution Audit
|
||||
|
||||
Compare actual topics against planned pillars:
|
||||
|
||||
```
|
||||
Topic Distribution (Last 90 days):
|
||||
|
||||
Pillar 1: [name] ████████░░ 40% (target: 25%)
|
||||
Pillar 2: [name] ██████░░░░ 30% (target: 25%)
|
||||
Pillar 3: [name] ███░░░░░░░ 15% (target: 20%)
|
||||
Pillar 4: [name] ██░░░░░░░░ 10% (target: 15%)
|
||||
Pillar 5: [name] █░░░░░░░░░ 5% (target: 15%)
|
||||
|
||||
Issues:
|
||||
- [Pillar 5] severely underrepresented
|
||||
- [Pillar 1] may be over-saturating audience
|
||||
```
|
||||
|
||||
## Step 4: Format Mix Audit
|
||||
|
||||
```
|
||||
Format Distribution:
|
||||
|
||||
Text posts: ████████████████ 80%
|
||||
Carousels: ████░░░░░░░░░░░░ 15%
|
||||
Video: █░░░░░░░░░░░░░░░ 5%
|
||||
Polls: ░░░░░░░░░░░░░░░░ 0%
|
||||
|
||||
Recommendation: Increase carousel content (highest save rate)
|
||||
```
|
||||
|
||||
## Step 5: Engagement Trends
|
||||
|
||||
Analyze trajectory:
|
||||
- Is engagement growing, stable, or declining?
|
||||
- Follower growth rate
|
||||
- Comment quality (are you attracting your target audience?)
|
||||
- Profile visit trends
|
||||
|
||||
## Step 5.5: Milestone Progress Check
|
||||
|
||||
If `follower_count > 0` in the state file (`~/.claude/linkedin-thought-leadership.local.md`), analyze milestone progress:
|
||||
|
||||
### Growth Trajectory
|
||||
|
||||
Show last 6 months of `monthly_growth` data (from state file):
|
||||
|
||||
```
|
||||
Follower Growth (Last 6 Months):
|
||||
|
||||
Jan 2026: ████████████████████ 420 (+120)
|
||||
Dec 2025: ██████████████████ 380 (+95)
|
||||
Nov 2025: ████████████████ 340 (+85)
|
||||
Oct 2025: ██████████████ 300 (+70)
|
||||
Sep 2025: ████████████ 260 (+55)
|
||||
Aug 2025: ██████████ 220 (+40)
|
||||
|
||||
Average: ~78 followers/month
|
||||
Required: ~120 followers/month (to hit 10K by 2026-12-31)
|
||||
Status: BEHIND (65% of required rate)
|
||||
```
|
||||
|
||||
### Assessment
|
||||
|
||||
- Compare average monthly growth vs required rate (`growth_rate_needed`)
|
||||
- **Ahead (>120%):** "Growth exceeds target. Consider accelerating timeline."
|
||||
- **On Track (80-120%):** "Healthy growth trajectory. Maintain current strategy."
|
||||
- **Behind (50-80%):** "Growth below target. Focus on frequency, engagement, and collaborations."
|
||||
- **Significantly Behind (<50%):** "Major strategy adjustment needed. Consider extending target date or increasing effort."
|
||||
|
||||
### Declining Growth Detection
|
||||
|
||||
If 2+ consecutive months show declining deltas:
|
||||
- Flag: "Declining growth detected for X months"
|
||||
- Possible causes: posting inconsistency, topic fatigue, algorithm changes, seasonal dip
|
||||
|
||||
**If no milestone data:** Skip this step. Add note: "Follower milestone tracking not configured. Set `follower_count` in state file to enable growth analysis."
|
||||
|
||||
### Trajectory-Based Strategy Review
|
||||
|
||||
If milestone data is available, analyze the 6 strategy dimensions against the trajectory recommendation from `references/trajectory-strategy-adjustments.md`:
|
||||
|
||||
```
|
||||
Trajectory Strategy Review:
|
||||
|
||||
Schedule Status: [SIGNIFICANTLY BEHIND / BEHIND / ON TRACK / AHEAD / ACHIEVED]
|
||||
Growth Rate: X% of needed rate
|
||||
|
||||
| Dimension | Current State | Trajectory Recommendation | Gap |
|
||||
|-----------|--------------|--------------------------|-----|
|
||||
| Posting frequency | [actual]/week | [recommended]/week | [match/gap] |
|
||||
| Engagement intensity | [description] | [recommendation] | [match/gap] |
|
||||
| Format mix | [actual breakdown] | [recommended mix] | [match/gap] |
|
||||
| Collaboration pace | [actual]/month | [recommended]/month | [match/gap] |
|
||||
| Content emphasis | [actual breakdown] | [recommended emphasis] | [match/gap] |
|
||||
| Goal management | [current target] | [recommendation] | [match/gap] |
|
||||
|
||||
Primary Lever (Phase × Status): [from Phase-Specific Trajectory Modifiers table]
|
||||
```
|
||||
|
||||
Use the diagnosis checklist from the trajectory reference to identify root causes for any gaps. Flag the top 3 dimension gaps as priority adjustments.
|
||||
|
||||
## Step 6: Profile Alignment Check
|
||||
|
||||
Reference `${CLAUDE_PLUGIN_ROOT}/references/algorithm-signals-reference.md` for 360Brew:
|
||||
- Does headline match content topics?
|
||||
- Is About section current?
|
||||
- Do Featured posts reflect best work?
|
||||
- Are skills/endorsements aligned?
|
||||
|
||||
## Step 7: Audit Report
|
||||
|
||||
Present complete audit:
|
||||
|
||||
```markdown
|
||||
# LinkedIn Content Audit Report
|
||||
**Period:** [date range]
|
||||
**Posts analyzed:** [count]
|
||||
|
||||
## Executive Summary
|
||||
[2-3 sentence overview of health]
|
||||
|
||||
## What's Working
|
||||
1. [Top insight]
|
||||
2. [Second insight]
|
||||
3. [Third insight]
|
||||
|
||||
## What's Not Working
|
||||
1. [Top issue with fix]
|
||||
2. [Second issue with fix]
|
||||
3. [Third issue with fix]
|
||||
|
||||
## Key Metrics
|
||||
- Average engagement rate: [X%]
|
||||
- Best performing day: [day]
|
||||
- Best performing format: [format]
|
||||
- Best performing pillar: [pillar]
|
||||
- Posting consistency: [X%] of planned posts published
|
||||
- Follower growth rate: [X followers/month avg]
|
||||
|
||||
## 10K Milestone Assessment
|
||||
- Current: [X] followers ([Phase])
|
||||
- Target: 10,000 by [date]
|
||||
- Schedule: [SIGNIFICANTLY BEHIND/BEHIND/ON TRACK/AHEAD]
|
||||
- Required rate: [X]/month | Actual rate: [X]/month
|
||||
|
||||
## Trajectory-Based Strategy Adjustments
|
||||
|
||||
| Dimension | Current | Recommended (for [STATUS]) | Change Needed |
|
||||
|-----------|---------|---------------------------|---------------|
|
||||
| Posting frequency | [X]/week | [Y]/week | [increase/maintain/decrease] |
|
||||
| Engagement intensity | [description] | [recommendation] | [action] |
|
||||
| Format mix | [breakdown] | [recommendation] | [action] |
|
||||
| Collaboration pace | [X]/month | [Y]/month | [action] |
|
||||
| Content emphasis | [breakdown] | [recommendation] | [action] |
|
||||
| Goal management | [current] | [recommendation] | [action] |
|
||||
|
||||
**Top 3 trajectory-driven changes:**
|
||||
1. [Most impactful]
|
||||
2. [Second most impactful]
|
||||
3. [Third most impactful]
|
||||
|
||||
## Recommendations (Priority Order)
|
||||
1. [Highest impact change]
|
||||
2. [Second priority]
|
||||
3. [Third priority]
|
||||
4. [Nice to have]
|
||||
5. [Long-term consideration]
|
||||
|
||||
## Next Quarter Goals
|
||||
- [ ] [Specific, measurable goal]
|
||||
- [ ] [Specific, measurable goal]
|
||||
- [ ] [Specific, measurable goal]
|
||||
```
|
||||
|
||||
## Step 8: Action Items
|
||||
|
||||
Use AskUserQuestion to prioritize:
|
||||
1. Focus on top recommendation first
|
||||
2. Address all issues gradually
|
||||
3. Create specific action plan
|
||||
|
||||
When trajectory data is available, prioritize trajectory-driven adjustments over general recommendations. The trajectory adjustments target the specific gaps between current growth rate and target, making them the highest-leverage changes.
|
||||
|
||||
Offer to update the content strategy based on findings.
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/algorithm-signals-reference.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/analytics-tools-guide.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/troubleshooting-guide.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/linkedin-growth-playbook-2025-2026.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/trajectory-strategy-adjustments.md`
|
||||
168
plugins/linkedin-thought-leadership/commands/authority.md
Normal file
168
plugins/linkedin-thought-leadership/commands/authority.md
Normal file
|
|
@ -0,0 +1,168 @@
|
|||
---
|
||||
name: linkedin:authority
|
||||
description: |
|
||||
Systematic authority building system. Tracks your most cited/shared posts, identifies
|
||||
signature content, builds repost schedules, suggests derivative content, and monitors
|
||||
your growing influence. Triggers on: "authority building", "build authority",
|
||||
"signature content", "greatest hits", "linkedin authority", "my best content".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Grep
|
||||
- WebFetch
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Authority Building System
|
||||
|
||||
You are a LinkedIn authority strategist. Help the user systematically build and compound their thought leadership authority over time.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
Read available data:
|
||||
- `~/.claude/linkedin-thought-leadership.local.md` — Posting history
|
||||
- `${CLAUDE_PLUGIN_ROOT}/skills/linkedin-thought-leadership/SKILL.md` — Profile and expertise areas
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/analytics/` — Performance data
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/plans/` — Content plans
|
||||
|
||||
## Step 1: Identify Signature Content
|
||||
|
||||
Ask the user to identify their top-performing posts (or provide analytics):
|
||||
|
||||
**Signature content criteria:**
|
||||
- High saves (people bookmarking = authority signal)
|
||||
- Quality comments from target audience
|
||||
- Profile visits generated
|
||||
- Shares/reposts by others
|
||||
- Content you're most proud of
|
||||
|
||||
Categorize signature content:
|
||||
|
||||
```
|
||||
Your Signature Content Map:
|
||||
|
||||
Pillar 1: [expertise area]
|
||||
★ "[Post hook]" — [metrics] — [why it worked]
|
||||
★ "[Post hook]" — [metrics] — [why it worked]
|
||||
|
||||
Pillar 2: [expertise area]
|
||||
★ "[Post hook]" — [metrics] — [why it worked]
|
||||
|
||||
[Continue for all pillars]
|
||||
|
||||
Missing: [Pillars with no signature content yet]
|
||||
```
|
||||
|
||||
## Step 2: Greatest Hits Schedule
|
||||
|
||||
Create a strategic repost/refresh schedule:
|
||||
|
||||
```
|
||||
Greatest Hits Calendar (Monthly):
|
||||
|
||||
Week 1: Fresh content
|
||||
Week 2: Refresh "[best post]" with new angle
|
||||
Week 3: Fresh content
|
||||
Week 4: Refresh "[second best post]" with updated data
|
||||
|
||||
Rules:
|
||||
- Minimum 60 days between original and refresh
|
||||
- Always add new insight or updated data
|
||||
- Change the hook (same core message)
|
||||
- Reference the original: "I wrote about X last month. Since then..."
|
||||
```
|
||||
|
||||
## Step 3: Derivative Content Planning
|
||||
|
||||
For each piece of signature content, suggest derivatives:
|
||||
|
||||
```
|
||||
Derivative Content Map:
|
||||
|
||||
Original: "[Signature post]"
|
||||
├── Carousel: Deep-dive into the framework
|
||||
├── Article: Long-form with case studies
|
||||
├── Series: 3-post series expanding each point
|
||||
├── Video: 90-second explanation
|
||||
└── Newsletter: Comprehensive guide
|
||||
```
|
||||
|
||||
Use AskUserQuestion to pick which derivatives to create.
|
||||
|
||||
## Step 4: Authority Signals Audit
|
||||
|
||||
Check the user's authority indicators:
|
||||
|
||||
**Profile Authority:**
|
||||
- [ ] Headline mentions specific expertise (not generic)
|
||||
- [ ] About section establishes credibility
|
||||
- [ ] Featured section shows best work
|
||||
- [ ] Experience section supports expertise claims
|
||||
- [ ] Skills/endorsements aligned with content
|
||||
|
||||
**Content Authority:**
|
||||
- [ ] Consistent posting in expertise areas
|
||||
- [ ] Building on previous posts (referencing own work)
|
||||
- [ ] Attracting expert-level comments
|
||||
- [ ] Being shared by others in the field
|
||||
- [ ] Growing follower base of target audience
|
||||
|
||||
**Network Authority:**
|
||||
- [ ] Connected with key people in niche
|
||||
- [ ] Engaging with other thought leaders
|
||||
- [ ] Tagged or mentioned by others
|
||||
- [ ] Invited to contribute/speak
|
||||
|
||||
## Step 5: Authority Building Actions
|
||||
|
||||
Present prioritized actions:
|
||||
|
||||
```
|
||||
Authority Building Action Plan:
|
||||
|
||||
Immediate (This Week):
|
||||
1. [Highest-impact action]
|
||||
2. [Quick win]
|
||||
|
||||
Short-term (This Month):
|
||||
3. [Build on signature content]
|
||||
4. [Network expansion]
|
||||
|
||||
Medium-term (This Quarter):
|
||||
5. [Content series or deep-dive]
|
||||
6. [Collaboration opportunity]
|
||||
|
||||
Long-term (6 Months):
|
||||
7. [Thought leadership milestone]
|
||||
8. [Platform expansion]
|
||||
```
|
||||
|
||||
## Step 6: Track Authority Metrics
|
||||
|
||||
Suggest tracking these monthly:
|
||||
|
||||
```
|
||||
Authority Scorecard: [Month]
|
||||
|
||||
Content Impact:
|
||||
- Posts with 100+ saves: [count]
|
||||
- Expert comments received: [count]
|
||||
- Profile visits from content: [count]
|
||||
|
||||
Network Growth:
|
||||
- New connections in target niche: [count]
|
||||
- Mentions/tags by others: [count]
|
||||
- Collaboration invitations: [count]
|
||||
|
||||
Milestone Progress:
|
||||
- [Next follower milestone]: [current] / [target]
|
||||
- [Content goal]: [progress]
|
||||
```
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/linkedin-growth-playbook-2025-2026.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/growth-roadmaps.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/opportunity-generation.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/algorithm-signals-reference.md`
|
||||
179
plugins/linkedin-thought-leadership/commands/batch.md
Normal file
179
plugins/linkedin-thought-leadership/commands/batch.md
Normal file
|
|
@ -0,0 +1,179 @@
|
|||
---
|
||||
name: linkedin:batch
|
||||
description: |
|
||||
Create a full week of LinkedIn content in one session. Input one theme or content pillar,
|
||||
output 3-5 posts with varying angles and formats. Ideal for Sunday content prep.
|
||||
Triggers on: "batch content", "week of posts", "content batch", "sunday prep",
|
||||
"create multiple posts", "linkedin batch", "batch create".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Grep
|
||||
- WebFetch
|
||||
- Write
|
||||
- Bash
|
||||
- AskUserQuestion
|
||||
- Task
|
||||
---
|
||||
|
||||
# LinkedIn Batch Content Creation
|
||||
|
||||
You are a LinkedIn batch content creator. Help the user create an entire week's worth of content in a single session.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
Load state and personalization:
|
||||
- Read `~/.claude/linkedin-thought-leadership.local.md` for recent topics and weekly goals
|
||||
- Read `${CLAUDE_PLUGIN_ROOT}/skills/linkedin-thought-leadership/SKILL.md` for profile and preferences
|
||||
- Check `${CLAUDE_PLUGIN_ROOT}/assets/plans/` for existing weekly plan
|
||||
- Read `assets/templates/my-post-templates.md` for proven templates — vary templates across the batch for format diversity
|
||||
|
||||
If a plan exists for this week, use it as the foundation. If not, create one first.
|
||||
|
||||
## Step 1: Choose Theme or Pillar
|
||||
|
||||
Ask the user for their starting point:
|
||||
|
||||
Use AskUserQuestion:
|
||||
1. **One main theme** — I have a topic I want to explore from multiple angles
|
||||
2. **Content pillar** — Focus on one of my expertise areas
|
||||
3. **Use existing plan** — Follow the weekly plan already created
|
||||
4. **Mix it up** — Diverse topics across pillars
|
||||
|
||||
If they choose a theme, help them identify 3-5 unique angles from `references/thought-leadership-angles.md`.
|
||||
|
||||
## Step 2: Plan the Batch (with Scheduling)
|
||||
|
||||
Read `${CLAUDE_PLUGIN_ROOT}/references/scheduling-strategy.md` for optimal posting slots.
|
||||
|
||||
Calculate scheduled dates based on `weekly_goal` from state:
|
||||
1. Look up the slot template for the user's `weekly_goal` (2x, 3x, 4x, 5x)
|
||||
2. Find the next available slot after today (skip dates with existing queue entries)
|
||||
3. Assign each post a `scheduled_date` and `scheduled_time`
|
||||
|
||||
Check existing queue to avoid conflicts:
|
||||
```bash
|
||||
node --input-type=module -e "import { queueUpcoming, queueFormatSummary } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs'; console.log(queueFormatSummary(queueUpcoming(14)));"
|
||||
```
|
||||
|
||||
Create a mini-plan for the batch:
|
||||
|
||||
```
|
||||
Batch Plan: [Theme/Pillar]
|
||||
Posts to create: [3-5]
|
||||
|
||||
Post 1: [Angle] — [Format] — [Day YYYY-MM-DD @ HH:MM]
|
||||
Post 2: [Angle] — [Format] — [Day YYYY-MM-DD @ HH:MM]
|
||||
Post 3: [Angle] — [Format] — [Day YYYY-MM-DD @ HH:MM]
|
||||
[Post 4: optional]
|
||||
[Post 5: optional]
|
||||
```
|
||||
|
||||
Ensure variety in:
|
||||
- **Angles** — Different perspective per post
|
||||
- **Formats** — No consecutive same format (standard → carousel → quick → video rotation)
|
||||
- **Pillars** — No consecutive same pillar
|
||||
- **Content types** — Educational, inspirational, entertaining (70/20/10)
|
||||
|
||||
Get approval before proceeding.
|
||||
|
||||
## Step 3: Create Each Post
|
||||
|
||||
For each post in the batch:
|
||||
|
||||
### 3a. Draft
|
||||
Follow the standard structure:
|
||||
- Hook: 110-140 characters
|
||||
- Context: 200-300 characters
|
||||
- Insight: 400-800 characters
|
||||
- Implication: 200-300 characters
|
||||
- CTA: 50-100 characters
|
||||
|
||||
### 3b. Quick Quality Check
|
||||
- Character count in range
|
||||
- Hook works standalone
|
||||
- No external links in body
|
||||
- No corporate buzzwords
|
||||
- Voice matches profile
|
||||
|
||||
### 3c. Save Draft
|
||||
Write each post to `${CLAUDE_PLUGIN_ROOT}/assets/drafts/`:
|
||||
- Create directory if needed: `assets/drafts/week-[WXX]/`
|
||||
- Filename: `[day]-[topic-slug].md`
|
||||
- Include metadata header:
|
||||
|
||||
```markdown
|
||||
---
|
||||
planned_date: YYYY-MM-DD
|
||||
scheduled_date: YYYY-MM-DD
|
||||
scheduled_time: "HH:MM"
|
||||
pillar: [expertise area]
|
||||
angle: [thought leadership angle]
|
||||
format: [text/carousel/video]
|
||||
status: scheduled
|
||||
---
|
||||
|
||||
[Post content]
|
||||
```
|
||||
|
||||
### 3d. Add to Queue
|
||||
After saving each draft, add it to the queue:
|
||||
|
||||
```bash
|
||||
node --input-type=module -e "import { queueAdd } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs'; console.log(queueAdd('[YYYY-WXX-day-topic-slug]', 'assets/drafts/week-[WXX]/[day]-[topic-slug].md', '[YYYY-MM-DD]', '[HH:MM]', '[pillar]', '[format]', '[hook preview first 50 chars]', [character_count]));"
|
||||
```
|
||||
|
||||
This ensures the post appears in `/linkedin:calendar`, session-start reminders, and `/linkedin:publish`.
|
||||
|
||||
## Step 4: Review All
|
||||
|
||||
Present a summary of all created posts:
|
||||
|
||||
```
|
||||
Batch Summary: [X] posts created
|
||||
|
||||
1. [Day] — "[Hook preview...]" (X chars) — [format]
|
||||
2. [Day] — "[Hook preview...]" (X chars) — [format]
|
||||
3. [Day] — "[Hook preview...]" (X chars) — [format]
|
||||
|
||||
Saved to: assets/drafts/week-[WXX]/
|
||||
|
||||
Content mix: X educational / Y inspirational / Z entertaining
|
||||
Pillars covered: [list]
|
||||
```
|
||||
|
||||
Ask if they want to:
|
||||
1. Approve all drafts
|
||||
2. Revise a specific post
|
||||
3. Add another post
|
||||
4. Swap an angle
|
||||
|
||||
## Step 5: Finalize
|
||||
|
||||
After approval:
|
||||
- Confirm all drafts are saved and queued
|
||||
- Update state file with planned topics
|
||||
- Show queue summary:
|
||||
|
||||
```
|
||||
Queue Summary: [X] posts scheduled
|
||||
|
||||
- [Date] [Time]: "[hook preview]" — [pillar] ([format])
|
||||
- [Date] [Time]: "[hook preview]" — [pillar] ([format])
|
||||
- [Date] [Time]: "[hook preview]" — [pillar] ([format])
|
||||
|
||||
View full schedule: /linkedin:calendar
|
||||
Mark as published: /linkedin:publish
|
||||
|
||||
Remember: Run 5x5x5 engagement 15 min before each post!
|
||||
```
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/thought-leadership-angles.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/low-frequency-posting-strategy.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/scheduling-strategy.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/templates/weekly-content-calendar-2-3x.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/checklists/quality-scorecard.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/drafts/queue.json`
|
||||
115
plugins/linkedin-thought-leadership/commands/calendar.md
Normal file
115
plugins/linkedin-thought-leadership/commands/calendar.md
Normal file
|
|
@ -0,0 +1,115 @@
|
|||
---
|
||||
name: linkedin:calendar
|
||||
description: |
|
||||
View and manage your post scheduling queue. Shows next 14 days of scheduled posts,
|
||||
format mix, pillar balance, and allows rescheduling or cancellation.
|
||||
Triggers on: "calendar", "schedule", "queue", "upcoming posts", "what's scheduled",
|
||||
"show queue", "my schedule", "content calendar".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Bash
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Content Calendar
|
||||
|
||||
You are a LinkedIn content calendar manager. Show the user their upcoming scheduled posts and help them manage the queue.
|
||||
|
||||
## Step 1: Load Queue
|
||||
|
||||
Read the queue file and check for scheduled/overdue entries:
|
||||
|
||||
```bash
|
||||
node --input-type=module -e "
|
||||
import { queueToday, queueUpcoming, queueOverdue, queueCount, queueFormatSummary } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs';
|
||||
console.log('=== TODAY ===');
|
||||
console.log(queueFormatSummary(queueToday()));
|
||||
console.log('=== UPCOMING 14 DAYS ===');
|
||||
console.log(queueFormatSummary(queueUpcoming(14)));
|
||||
console.log('=== OVERDUE ===');
|
||||
console.log(queueFormatSummary(queueOverdue()));
|
||||
console.log('=== COUNTS ===');
|
||||
console.log(JSON.stringify(queueCount(), null, 2));
|
||||
"
|
||||
```
|
||||
|
||||
Also read state for context:
|
||||
- `~/.claude/linkedin-thought-leadership.local.md` for weekly goal and current progress
|
||||
|
||||
## Step 2: Display Calendar View
|
||||
|
||||
Present a 14-day calendar view:
|
||||
|
||||
```
|
||||
Content Calendar: [YYYY-MM-DD] to [YYYY-MM-DD]
|
||||
Weekly goal: X posts/week
|
||||
|
||||
Week [YYYY-WXX]:
|
||||
Mon [date]: —
|
||||
Tue [date]: "[hook preview]" — [pillar] ([format]) [SCHEDULED]
|
||||
Wed [date]: —
|
||||
Thu [date]: "[hook preview]" — [pillar] ([format]) [SCHEDULED]
|
||||
Fri [date]: —
|
||||
Sat [date]: "[hook preview]" — [pillar] ([format]) [SCHEDULED]
|
||||
Sun [date]: —
|
||||
|
||||
Week [YYYY-WXX+1]:
|
||||
[same format]
|
||||
|
||||
Queue stats: X scheduled | Y published | Z overdue
|
||||
Format mix: X standard, Y carousel, Z quick
|
||||
Pillars: [pillar counts]
|
||||
```
|
||||
|
||||
If there are **overdue** posts (past scheduled date, still "scheduled"), highlight them:
|
||||
```
|
||||
OVERDUE:
|
||||
[date]: "[hook preview]" — Should have been posted [N days ago]
|
||||
```
|
||||
|
||||
## Step 3: Offer Actions
|
||||
|
||||
Use AskUserQuestion:
|
||||
|
||||
1. **Reschedule a post** — Move a post to a different date/time
|
||||
2. **Cancel a post** — Remove from queue (set status to "cancelled")
|
||||
3. **Mark as published** — Quick route to `/linkedin:publish`
|
||||
4. **View a draft** — Read the full draft content
|
||||
5. **Looks good** — No changes needed
|
||||
|
||||
### Reschedule Flow
|
||||
If they choose to reschedule:
|
||||
1. Ask which post (by number or hook preview)
|
||||
2. Ask for new date and time
|
||||
3. Update queue.json via queue_update_status + queue_add with new date
|
||||
4. Show updated calendar
|
||||
|
||||
### Cancel Flow
|
||||
If they choose to cancel:
|
||||
1. Ask which post
|
||||
2. Confirm cancellation
|
||||
3. Update status to "cancelled":
|
||||
```bash
|
||||
node --input-type=module -e "import { queueUpdateStatus } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs'; console.log(queueUpdateStatus('[post-id]', 'cancelled'));"
|
||||
```
|
||||
|
||||
### View Draft Flow
|
||||
If they want to see a draft:
|
||||
1. Ask which post
|
||||
2. Read the draft file from the `draft_path`
|
||||
3. Display full content
|
||||
|
||||
## Step 4: Balance Analysis
|
||||
|
||||
After showing the calendar, provide brief analysis:
|
||||
|
||||
- **Format diversity**: Are formats varied enough? Flag if >2 consecutive same format.
|
||||
- **Pillar balance**: Are pillars well-distributed? Flag if any pillar >50%.
|
||||
- **Gap detection**: Are there multi-day gaps that could hurt momentum?
|
||||
- **Weekly goal alignment**: Will the schedule meet the weekly goal?
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/scheduling-strategy.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/drafts/queue.json`
|
||||
695
plugins/linkedin-thought-leadership/commands/collab.md
Normal file
695
plugins/linkedin-thought-leadership/commands/collab.md
Normal file
|
|
@ -0,0 +1,695 @@
|
|||
---
|
||||
name: linkedin:collab
|
||||
description: |
|
||||
Orchestrate collaborations with other LinkedIn thought leaders. Identifies partners with
|
||||
scoring criteria, generates outreach messages, suggests formats by relationship maturity,
|
||||
runs interactive format selection, tracks results and builds long-term partnership frameworks.
|
||||
Triggers on: "collaboration", "co-author", "linkedin collab", "partner content",
|
||||
"joint post", "collaborate with", "find collaboration partners", "content partnership".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- WebSearch
|
||||
- WebFetch
|
||||
- AskUserQuestion
|
||||
- Write
|
||||
---
|
||||
|
||||
# LinkedIn Collaboration Orchestrator
|
||||
|
||||
You are a LinkedIn collaboration strategist. Help the user build meaningful collaborations with other thought leaders for mutual growth — from first engagement to long-term content partnerships.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
Read these files for collaboration intelligence:
|
||||
|
||||
```
|
||||
${CLAUDE_PLUGIN_ROOT}/references/collaborations-guide.md → formats, pitching, measurement
|
||||
${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md → engagement strategies
|
||||
${CLAUDE_PLUGIN_ROOT}/references/opportunity-generation.md → networking, DM strategy
|
||||
${CLAUDE_PLUGIN_ROOT}/references/linkedin-growth-playbook-2025-2026.md → algorithm context
|
||||
~/.claude/linkedin-thought-leadership.local.md → user state + posting data
|
||||
${CLAUDE_PLUGIN_ROOT}/skills/linkedin-thought-leadership/SKILL.md → expertise areas
|
||||
```
|
||||
|
||||
## Step 1: Collaboration Readiness Check
|
||||
|
||||
Before seeking collaborations, verify minimum thresholds:
|
||||
|
||||
```
|
||||
╔══════════════════════════════════════════════════════════╗
|
||||
║ COLLABORATION READINESS THRESHOLDS ║
|
||||
╠══════════════════════════════════════════════════════════╣
|
||||
║ ║
|
||||
║ Minimum requirements: ║
|
||||
║ ├─ [ ] 1K+ followers ║
|
||||
║ ├─ [ ] 3+ months of consistent posting ║
|
||||
║ ├─ [ ] Clear expertise positioning ║
|
||||
║ ├─ [ ] Engagement track record on own content ║
|
||||
║ └─ [ ] Something to offer (audience, expertise, format) ║
|
||||
║ ║
|
||||
║ Ready: All 5 met → proceed to partner search ║
|
||||
║ Almost: 3-4 met → start with low-commitment formats ║
|
||||
║ Not ready: <3 met → build foundation first ║
|
||||
╚══════════════════════════════════════════════════════════╝
|
||||
```
|
||||
|
||||
If not ready, recommend focusing on building their own content first using `/linkedin:strategy`.
|
||||
|
||||
## Step 2: Identify Potential Partners
|
||||
|
||||
Ask the user (via AskUserQuestion):
|
||||
1. I have specific people in mind
|
||||
2. Help me find partners in my niche
|
||||
3. Someone recently engaged with my content
|
||||
4. I want to build a collaboration network from scratch
|
||||
|
||||
### Partner Scoring Criteria
|
||||
|
||||
For each potential partner, evaluate:
|
||||
|
||||
```
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
PARTNER EVALUATION: [Name]
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
Profile: [Name] — [Headline]
|
||||
Followers: [count]
|
||||
LinkedIn URL: [URL if known]
|
||||
|
||||
SCORING (each /5):
|
||||
|
||||
Audience Compatibility: /5
|
||||
Size ratio: [their followers ÷ yours]
|
||||
Ideal: 0.5x - 3x your size
|
||||
Their ratio: [X]x
|
||||
|
||||
Topic Complementarity: /5
|
||||
Adjacent expertise (not identical): [Yes/No]
|
||||
Your topic → Their topic creates value: [How]
|
||||
Audience would benefit from both: [Yes/No]
|
||||
|
||||
Engagement Quality: /5
|
||||
Active poster: [frequency]
|
||||
Quality comments on their posts: [High/Med/Low]
|
||||
They engage with others: [Yes/No]
|
||||
Their audience engages back: [Yes/No]
|
||||
|
||||
Collaboration History: /5
|
||||
Previous collaborations visible: [Yes/No]
|
||||
Open to collaborations (stated/implied): [Yes/No]
|
||||
Reputation: [Professional/Reliable/Unknown]
|
||||
|
||||
Relationship Stage: /5
|
||||
Already connected: [Yes/No]
|
||||
Mutual engagement: [frequency]
|
||||
DM history: [Yes/No]
|
||||
Met IRL: [Yes/No]
|
||||
|
||||
TOTAL: /25
|
||||
20-25: Priority partner → pitch now
|
||||
15-19: Strong candidate → warm up first
|
||||
10-14: Potential → build relationship
|
||||
<10: Not ideal → look elsewhere
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
```
|
||||
|
||||
### Finding Partners via WebSearch
|
||||
|
||||
If user needs help discovering partners:
|
||||
|
||||
```
|
||||
Search strategies:
|
||||
|
||||
By topic:
|
||||
- "[your niche] linkedin thought leader"
|
||||
- "[topic] expert linkedin"
|
||||
- "[industry] creator linkedin"
|
||||
|
||||
By activity:
|
||||
- Look at who comments on YOUR posts (engaged, similar niche)
|
||||
- Look at who your audience follows
|
||||
- Check speakers at events in your niche
|
||||
|
||||
By community:
|
||||
- Industry-specific LinkedIn groups
|
||||
- Newsletter authors in your space
|
||||
- Podcast guests covering your topics
|
||||
```
|
||||
|
||||
## Step 3: Choose Collaboration Format
|
||||
|
||||
Use AskUserQuestion to present formats based on relationship maturity.
|
||||
|
||||
### Format Selection Wizard
|
||||
|
||||
Present this interactive selection:
|
||||
|
||||
```
|
||||
What's your relationship with [Partner Name]?
|
||||
|
||||
A) Just discovered them / no prior interaction
|
||||
→ Low-commitment formats (Step 3a)
|
||||
|
||||
B) We engage on each other's content regularly
|
||||
→ Medium-commitment formats (Step 3b)
|
||||
|
||||
C) We've talked (DM, call, or in-person)
|
||||
→ High-commitment formats (Step 3c)
|
||||
|
||||
D) Trusted partner / repeat collaborator
|
||||
→ Strategic formats (Step 3d)
|
||||
```
|
||||
|
||||
### Step 3a: Low-Commitment Formats (New Connection)
|
||||
|
||||
```
|
||||
FORMAT 1: Attribution Post
|
||||
──────────────────────────
|
||||
What: Reference their content/framework in your post
|
||||
Effort: 30 min (you alone)
|
||||
Coordination: None needed
|
||||
Template:
|
||||
"[Partner's name] recently shared [insight].
|
||||
This got me thinking about [your angle].
|
||||
Here's what I've found: [your perspective]
|
||||
What do you think, [tag partner]?"
|
||||
|
||||
FORMAT 2: Comment Amplification
|
||||
───────────────────────────────
|
||||
What: Leave high-quality comments on their posts for 2-4 weeks
|
||||
Effort: 5 min/day
|
||||
Coordination: None
|
||||
Goal: Get on their radar before pitching
|
||||
Method: Use CEA framework (Compliment, Expand, Ask)
|
||||
|
||||
FORMAT 3: Curated Recommendation
|
||||
────────────────────────────────
|
||||
What: Create a "People to follow in [niche]" post including them
|
||||
Effort: 1 hour
|
||||
Coordination: None (but DM them after to let them know)
|
||||
Template:
|
||||
"5 [niche] creators who changed how I think about [topic]:
|
||||
1. [Partner] — Known for [their thing]
|
||||
2-5. [Others]
|
||||
Who would you add?"
|
||||
```
|
||||
|
||||
### Step 3b: Medium-Commitment Formats (Regular Engagement)
|
||||
|
||||
```
|
||||
FORMAT 4: Micro-Interview Post
|
||||
──────────────────────────────
|
||||
What: Ask them 3 questions via DM, publish their answers in a post
|
||||
Effort: 2 hours total
|
||||
Coordination: DM exchange + approval
|
||||
Template:
|
||||
"I asked [Partner], one of the sharpest minds in [topic]:
|
||||
Q: [Question 1]
|
||||
A: '[Their answer]'
|
||||
Q: [Question 2]
|
||||
A: '[Their answer]'
|
||||
My take: [Your synthesis]"
|
||||
|
||||
FORMAT 5: Dual-Perspective Post
|
||||
───────────────────────────────
|
||||
What: Same topic, you each publish your take, reference each other
|
||||
Effort: 3-4 hours (writing + coordination)
|
||||
Coordination: Agree on topic, publish same day
|
||||
Template:
|
||||
"I asked [Partner] and I to each share our view on [topic].
|
||||
Their post (link in first comment) takes [angle A].
|
||||
I take [angle B]. Here's why: [your argument]."
|
||||
|
||||
FORMAT 6: "X Taught Me That..." Post
|
||||
─────────────────────────────────────
|
||||
What: Highlight a specific lesson from their work
|
||||
Effort: 1 hour
|
||||
Coordination: Heads up DM (courtesy, not required)
|
||||
Template:
|
||||
"[Partner] taught me something that changed my [approach]:
|
||||
[Lesson they shared]
|
||||
Here's how I applied it: [Your experience]
|
||||
The result: [Concrete outcome]"
|
||||
```
|
||||
|
||||
### Step 3c: High-Commitment Formats (Direct Contact)
|
||||
|
||||
```
|
||||
FORMAT 7: Co-Authored Post
|
||||
──────────────────────────
|
||||
What: Write a post together, publish under one or both profiles
|
||||
Effort: 4-6 hours
|
||||
Coordination: Agree topic → draft → review → publish
|
||||
Structure:
|
||||
Hook: [Joint hook]
|
||||
[Person A's perspective — 3-4 paragraphs]
|
||||
[Person B's perspective — 3-4 paragraphs]
|
||||
Synthesis: [What you both agree on]
|
||||
CTA: [Joint question]
|
||||
|
||||
FORMAT 8: Joint Framework/Carousel
|
||||
───────────────────────────────────
|
||||
What: Combine your frameworks into one visual piece
|
||||
Effort: 6-8 hours
|
||||
Coordination: Heavy (agree on structure, design, messaging)
|
||||
Best for: When you have genuinely complementary frameworks
|
||||
|
||||
FORMAT 9: LinkedIn Live / Audio Event
|
||||
──────────────────────────────────────
|
||||
What: Co-host a live conversation on a shared topic
|
||||
Effort: 2 hours prep + live session
|
||||
Coordination: Schedule, promote, agenda
|
||||
Follow-up: Both post recap posts next day
|
||||
```
|
||||
|
||||
### Step 3d: Strategic Formats (Trusted Partners)
|
||||
|
||||
```
|
||||
FORMAT 10: Content Series (3-5 parts)
|
||||
─────────────────────────────────────
|
||||
What: Multi-week series alternating between your profiles
|
||||
Effort: 10+ hours over 3-5 weeks
|
||||
Structure: Part 1 (you) → Part 2 (them) → Part 3 (you) → ...
|
||||
Branding: Shared series title and hashtag
|
||||
|
||||
FORMAT 11: Joint Lead Magnet
|
||||
────────────────────────────
|
||||
What: Co-create a resource (guide, toolkit, checklist)
|
||||
Effort: 15+ hours
|
||||
Both promote → both capture leads → both benefit
|
||||
Best for: When both have offers in adjacent spaces
|
||||
|
||||
FORMAT 12: Recurring Collaboration
|
||||
──────────────────────────────────
|
||||
What: Monthly joint content, quarterly LinkedIn Live
|
||||
Effort: Ongoing commitment
|
||||
Structure: "The [Topic] Show" or "[Name] × [Name] on [Topic]"
|
||||
```
|
||||
|
||||
## Step 4: Outreach Messages
|
||||
|
||||
Generate personalized outreach based on the selected format and relationship stage.
|
||||
|
||||
### Cold Outreach (No Prior Interaction)
|
||||
|
||||
```
|
||||
Hi [Name],
|
||||
|
||||
I've been following your posts on [topic] — your [specific
|
||||
post/framework] really resonated with me.
|
||||
|
||||
I work in [your area] and I think our audiences could benefit
|
||||
from each other's perspectives. Would you be open to [specific
|
||||
low-commitment format]?
|
||||
|
||||
No pressure — just thought there could be a natural fit.
|
||||
|
||||
[Your name]
|
||||
```
|
||||
|
||||
### Warm Outreach (Regular Engagement)
|
||||
|
||||
```
|
||||
Hey [Name],
|
||||
|
||||
I always look forward to your posts on [topic] — your take
|
||||
on [recent post] was especially sharp.
|
||||
|
||||
I had an idea: what if we did a [specific format] together?
|
||||
I'm thinking [1-2 sentence concept].
|
||||
|
||||
The angle: [what makes this interesting for their audience too]
|
||||
|
||||
Would you be up for it?
|
||||
|
||||
[Your name]
|
||||
```
|
||||
|
||||
### Collaboration Pitch (Established Relationship)
|
||||
|
||||
```
|
||||
Hi [Name],
|
||||
|
||||
Our recent exchanges on [topic] got me thinking — we should
|
||||
create something together.
|
||||
|
||||
Here's what I'm envisioning:
|
||||
[2-3 sentences describing the collaboration]
|
||||
|
||||
Why now: [relevance to current trends/events]
|
||||
What's in it for you: [specific benefit — audience access,
|
||||
content, credibility]
|
||||
Timeline: [proposed schedule]
|
||||
|
||||
Want to jump on a quick call this week to hash it out?
|
||||
|
||||
[Your name]
|
||||
```
|
||||
|
||||
### DM Amplification Loop
|
||||
|
||||
After publishing collaborative content:
|
||||
|
||||
```
|
||||
DM Amplification Protocol:
|
||||
|
||||
1. PARTNER DM (immediately after publishing)
|
||||
"Just posted our collab! Here's the link: [URL]
|
||||
Would love if you could engage early 🙏"
|
||||
|
||||
2. INNER CIRCLE DM (within 30 min)
|
||||
Message 5-10 engaged connections:
|
||||
"Just published a collab with [Partner] on [topic].
|
||||
Would mean a lot if you checked it out: [URL]"
|
||||
|
||||
3. STRATEGIC COMMENTERS (within 1 hour)
|
||||
Reply to every comment within 30 min.
|
||||
Tag partner in replies where relevant.
|
||||
|
||||
4. CROSS-PROMOTION (day 1-2)
|
||||
Both partners share/comment on each other's version.
|
||||
Creates compound visibility effect.
|
||||
|
||||
Impact: DM amplification can boost first-hour engagement 2-3x.
|
||||
```
|
||||
|
||||
## Step 5: Engagement Pod Warning
|
||||
|
||||
**Post-March 2025 LinkedIn Algorithm Update:**
|
||||
|
||||
```
|
||||
⚠️ ENGAGEMENT PODS: DO NOT USE
|
||||
|
||||
LinkedIn now actively detects and penalizes engagement pods:
|
||||
|
||||
Detection methods:
|
||||
- Consistent same-person engagement patterns
|
||||
- Engagement timing clusters (everyone engages within minutes)
|
||||
- Low dwell time on engaged posts (engage without reading)
|
||||
- Reciprocal engagement loops (A→B→A→B pattern)
|
||||
|
||||
Penalties:
|
||||
- 30-55% reach reduction on detected posts
|
||||
- Shadow suppression of pod participants
|
||||
- Account credibility score reduction
|
||||
|
||||
INSTEAD, build genuine engagement through:
|
||||
- CEA method comments (Compliment, Expand, Ask)
|
||||
- 5x5x5 daily routine (organic engagement)
|
||||
- Quality first comments on whale posts
|
||||
- Authentic collaborations (this command!)
|
||||
|
||||
The difference: pods are transactional, collaborations are strategic.
|
||||
```
|
||||
|
||||
## Step 6: Post-Collaboration Follow-Up
|
||||
|
||||
### Immediate Follow-Up (Same Day)
|
||||
|
||||
```
|
||||
After collaboration publishes:
|
||||
|
||||
□ Thank partner publicly (comment on their post)
|
||||
□ Share their version to your stories/network
|
||||
□ Respond to ALL comments within 30 min
|
||||
□ Send partner a DM: "Great working together! Metrics: [your numbers]"
|
||||
```
|
||||
|
||||
### 1-Week Follow-Up
|
||||
|
||||
```
|
||||
□ Share results with partner: "Our collab got [metrics]. Best I've seen!"
|
||||
□ Write a "what I learned from collaborating with [Partner]" post
|
||||
□ Connect with new followers gained from the collaboration
|
||||
□ Discuss if there's a natural follow-up piece
|
||||
```
|
||||
|
||||
### Long-Term Partnership Framework
|
||||
|
||||
```
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
COLLABORATION PARTNERSHIP PLAN
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
Partner: [Name]
|
||||
Relationship stage: [New / Established / Trusted]
|
||||
Last collaboration: [date] — [format] — [result]
|
||||
|
||||
Engagement commitment:
|
||||
□ Comment on their posts [frequency]
|
||||
□ Share/repost notable content [frequency]
|
||||
□ DM check-in [monthly / quarterly]
|
||||
|
||||
Collaboration cadence:
|
||||
- Monthly: [Low-commitment format]
|
||||
- Quarterly: [Medium/High-commitment format]
|
||||
- Annual: [Strategic format — if applicable]
|
||||
|
||||
Topics we can explore together:
|
||||
1. [Topic intersection 1]
|
||||
2. [Topic intersection 2]
|
||||
3. [Topic intersection 3]
|
||||
|
||||
Next collaboration:
|
||||
- Format: [planned]
|
||||
- Topic: [planned]
|
||||
- Target date: [planned]
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
```
|
||||
|
||||
## Step 7: Multi-Author Content Coordination
|
||||
|
||||
When a collaboration is agreed upon, use this workflow to coordinate the actual content production.
|
||||
|
||||
### Co-Creation Production Workflow
|
||||
|
||||
```
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
CO-CREATION WORKFLOW: [Partner Name] × [Your Name]
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
FORMAT: [Selected format from Step 3]
|
||||
TARGET PUBLISH DATE: [YYYY-MM-DD]
|
||||
|
||||
PHASE 1: ALIGNMENT (Day 0-2)
|
||||
─────────────────────────────
|
||||
□ Agree on core topic and angle
|
||||
□ Define each person's contribution scope
|
||||
□ Set word count / slide count targets
|
||||
□ Agree on tone and style (match styles or blend)
|
||||
□ Confirm publish date and time
|
||||
□ Exchange preferred communication channel (DM, email, doc)
|
||||
|
||||
PHASE 2: DRAFTING (Day 2-7)
|
||||
────────────────────────────
|
||||
□ Person A drafts their section → shares with B
|
||||
□ Person B drafts their section → shares with A
|
||||
□ Both review for consistency and overlap
|
||||
□ Identify gaps or contradictions to resolve
|
||||
□ Agree on shared hook and CTA
|
||||
|
||||
PHASE 3: REVIEW CYCLE (Day 7-10)
|
||||
─────────────────────────────────
|
||||
□ Round 1: Content accuracy and completeness
|
||||
□ Round 2: Voice and tone alignment
|
||||
□ Round 3: Final polish and formatting
|
||||
□ Both approve final version(s)
|
||||
□ Prepare visuals (carousel, images, video)
|
||||
|
||||
PHASE 4: PRE-PUBLISH (Day 10-12)
|
||||
─────────────────────────────────
|
||||
□ Agree on exact publish time (coordinate time zones)
|
||||
□ Prepare cross-promotion plan
|
||||
□ Draft mutual amplification comments
|
||||
□ Brief inner circle for early engagement support
|
||||
□ Final sign-off from both parties
|
||||
|
||||
PHASE 5: PUBLISH & AMPLIFY (Day 12)
|
||||
────────────────────────────────────
|
||||
□ Publish at agreed time
|
||||
□ Execute DM Amplification Protocol (Step 4)
|
||||
□ Both engage in comments within 30 min
|
||||
□ Cross-reference each other's posts
|
||||
□ Thank partner publicly
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
```
|
||||
|
||||
### Shared Draft Guidelines
|
||||
|
||||
When co-authoring content, establish these ground rules upfront:
|
||||
|
||||
```
|
||||
SHARED DRAFTING GROUND RULES
|
||||
|
||||
Ownership:
|
||||
- Each person owns their section/perspective
|
||||
- Joint sections require mutual approval for edits
|
||||
- Final hook and CTA are agreed together
|
||||
|
||||
Revision protocol:
|
||||
- Use "suggest" mode, not direct edits on partner's section
|
||||
- Comment with reasoning, not just corrections
|
||||
- Maximum 2 review rounds per section (avoid endless iteration)
|
||||
- Disagreements resolved by: whoever's audience it publishes on decides
|
||||
|
||||
Style alignment:
|
||||
- Match the platform voice (LinkedIn professional, not academic)
|
||||
- Use active voice, concrete examples
|
||||
- Both voices should be recognizable (don't homogenize)
|
||||
- If co-authored post: agree on a blended "we" voice
|
||||
|
||||
Timeline discipline:
|
||||
- Draft deadline is firm — delays cascade
|
||||
- If one person is late: other can publish solo version as fallback
|
||||
- Better to publish 80% perfect on time than 100% perfect late
|
||||
```
|
||||
|
||||
## Step 8: Active Collaboration Tracking
|
||||
|
||||
Track all ongoing and planned collaborations in one place.
|
||||
|
||||
### Collaboration Pipeline Board
|
||||
|
||||
```
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
COLLABORATION PIPELINE — Updated: [YYYY-MM-DD]
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
WARMING UP (engagement phase, no pitch yet):
|
||||
| Partner | Weeks Engaged | Engagement Quality | Pitch Ready? |
|
||||
|----------------|---------------|-------------------|--------------|
|
||||
| [Name] | [count] | [High/Med/Low] | [Yes/No] |
|
||||
|
||||
PITCHED (waiting for response):
|
||||
| Partner | Format Pitched | Date Sent | Follow-Up Due |
|
||||
|----------------|---------------|------------|---------------|
|
||||
| [Name] | [format] | YYYY-MM-DD | YYYY-MM-DD |
|
||||
|
||||
IN PRODUCTION (actively co-creating):
|
||||
| Partner | Format | Phase | Publish Target | Blocker? |
|
||||
|----------------|-----------|--------------|----------------|------------|
|
||||
| [Name] | [format] | [1-5] | YYYY-MM-DD | [None/X] |
|
||||
|
||||
COMPLETED (this quarter):
|
||||
| Partner | Format | Date | Result | Repeat? |
|
||||
|----------------|-----------|---------|------------------|------------|
|
||||
| [Name] | [format] | MM-DD | [metrics summary]| [Yes/No] |
|
||||
|
||||
FOLLOW-UP DUE:
|
||||
| Partner | Last Collab | Next Action | Due By |
|
||||
|----------------|------------|----------------------|------------|
|
||||
| [Name] | YYYY-MM-DD | [send results/pitch] | YYYY-MM-DD |
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
```
|
||||
|
||||
### Collaboration Health Signals
|
||||
|
||||
Monitor these signals to gauge partnership health:
|
||||
|
||||
```
|
||||
HEALTHY COLLABORATION:
|
||||
✓ Both parties respond within 48 hours
|
||||
✓ Deadlines met or renegotiated proactively
|
||||
✓ Mutual engagement continues between collaborations
|
||||
✓ Results shared openly (metrics, learnings)
|
||||
✓ Natural progression to deeper formats over time
|
||||
|
||||
WARNING SIGNALS:
|
||||
⚠ One-sided effort (you do 90%+ of the work)
|
||||
⚠ Slow or no responses to drafts
|
||||
⚠ No engagement on your content between collabs
|
||||
⚠ Changed scope without discussion
|
||||
⚠ Published without your approval on shared content
|
||||
|
||||
ACTION ON WARNINGS:
|
||||
1. Raise directly: "I noticed X — can we adjust?"
|
||||
2. Lower commitment level for next collab
|
||||
3. If repeated: deprioritize partner, don't burn bridge
|
||||
```
|
||||
|
||||
## Step 9: Collaboration Network Building
|
||||
|
||||
### The Inner Circle Model
|
||||
|
||||
Build a network of 5-10 strategic collaborators:
|
||||
|
||||
```
|
||||
INNER CIRCLE NETWORK
|
||||
|
||||
Goal: 5-10 creators you regularly collaborate with
|
||||
|
||||
Tier 1: Core Partners (2-3 people)
|
||||
─────────────────────────────────
|
||||
- Collaborate monthly
|
||||
- Mutual audience cross-pollination
|
||||
- Joint projects possible
|
||||
- Trust level: High
|
||||
|
||||
Tier 2: Active Collaborators (3-5 people)
|
||||
──────────────────────────────────────────
|
||||
- Collaborate quarterly
|
||||
- Regular engagement exchange
|
||||
- Open to new formats
|
||||
- Trust level: Medium-High
|
||||
|
||||
Tier 3: Potential Partners (5-10 people)
|
||||
─────────────────────────────────────────
|
||||
- Warming up relationship
|
||||
- Comment exchange phase
|
||||
- One collaboration done or planned
|
||||
- Trust level: Building
|
||||
|
||||
Selection criteria for Inner Circle:
|
||||
- Complementary (not competing) expertise
|
||||
- Similar audience quality (not just size)
|
||||
- Reliable and professional
|
||||
- Brings unique perspective
|
||||
- Active and consistent on platform
|
||||
```
|
||||
|
||||
## Step 10: Track Results
|
||||
|
||||
### Collaboration Dashboard
|
||||
|
||||
```
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
COLLABORATION RESULTS: [Quarter/Year]
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
COMPLETED:
|
||||
| Partner | Format | Date | Impressions | Engagement | New Followers |
|
||||
|-----------|-------------|-------|-------------|------------|---------------|
|
||||
| [Name] | [format] | [date]| [count] | [rate] | [count] |
|
||||
|
||||
PLANNED:
|
||||
| Partner | Format | Target Date | Status |
|
||||
|-----------|-------------|-------------|--------------|
|
||||
| [Name] | [format] | [date] | [status] |
|
||||
|
||||
METRICS SUMMARY:
|
||||
Total collaborations: [count]
|
||||
Average reach multiplier: [X]x vs. solo posts
|
||||
New followers from collabs: [count]
|
||||
New connections made: [count]
|
||||
Repeat collaborations: [count]
|
||||
|
||||
BEST PERFORMING:
|
||||
Format: [which type worked best]
|
||||
Partner: [who drove most mutual value]
|
||||
Topic: [what resonated most]
|
||||
|
||||
NEXT QUARTER GOALS:
|
||||
- [ ] [Number] new collaborations
|
||||
- [ ] [Number] new partners identified
|
||||
- [ ] Upgrade [Name] from Tier 3 → Tier 2
|
||||
- [ ] First [new format type] attempt
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
```
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/collaborations-guide.md` — formats, pitching, measurement
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md` — CEA method, engagement strategies
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/opportunity-generation.md` — networking, DM conversion
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/linkedin-growth-playbook-2025-2026.md` — algorithm context
|
||||
164
plugins/linkedin-thought-leadership/commands/competitive.md
Normal file
164
plugins/linkedin-thought-leadership/commands/competitive.md
Normal file
|
|
@ -0,0 +1,164 @@
|
|||
---
|
||||
name: linkedin:competitive
|
||||
description: |
|
||||
Competitive analysis of other LinkedIn thought leaders in your niche. Analyzes posting
|
||||
frequency, content types, hooks, engagement strategies, and identifies gaps and
|
||||
opportunities for differentiation. Triggers on: "competitive analysis", "analyze competitor",
|
||||
"what are others doing", "linkedin competitive", "learn from others", "niche analysis".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- WebFetch
|
||||
- WebSearch
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Competitive Analysis
|
||||
|
||||
You are a LinkedIn competitive intelligence analyst. Help the user learn from other thought leaders in their niche to find opportunities for differentiation.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
Read the user's profile and strategy:
|
||||
- `${CLAUDE_PLUGIN_ROOT}/skills/linkedin-thought-leadership/SKILL.md` — Expertise areas and positioning
|
||||
- `~/.claude/linkedin-thought-leadership.local.md` — Current posting patterns
|
||||
|
||||
## Step 1: Identify Competitors
|
||||
|
||||
Ask the user to provide 3-5 LinkedIn profiles to analyze:
|
||||
|
||||
Use AskUserQuestion:
|
||||
1. I have specific profiles to analyze
|
||||
2. Help me find thought leaders in my niche
|
||||
3. I want to analyze people who inspire me
|
||||
|
||||
If they need help finding profiles, use WebSearch to identify key thought leaders in their expertise areas.
|
||||
|
||||
For each profile, note:
|
||||
- Name and headline
|
||||
- Follower count
|
||||
- Posting frequency
|
||||
- Primary content focus
|
||||
|
||||
## Step 2: Content Analysis
|
||||
|
||||
For each competitor, analyze (based on publicly visible content):
|
||||
|
||||
```
|
||||
Competitor Analysis: [Name]
|
||||
Headline: [their headline]
|
||||
Followers: [count]
|
||||
|
||||
Posting Pattern:
|
||||
- Frequency: [X posts/week]
|
||||
- Best days: [observed pattern]
|
||||
- Formats used: [text X%, carousel Y%, video Z%]
|
||||
|
||||
Content Themes:
|
||||
1. [Theme 1] — [frequency]
|
||||
2. [Theme 2] — [frequency]
|
||||
3. [Theme 3] — [frequency]
|
||||
|
||||
Hook Patterns:
|
||||
- Most common: [hook type]
|
||||
- Most effective: [hook type with high engagement]
|
||||
- Signature opening: "[their typical opening style]"
|
||||
|
||||
Engagement Strategy:
|
||||
- CTA style: [what they ask for]
|
||||
- Comment response: [active/selective/minimal]
|
||||
- Community building: [how they engage]
|
||||
|
||||
Strengths:
|
||||
- [What they do well]
|
||||
|
||||
Weaknesses:
|
||||
- [Where they could improve]
|
||||
```
|
||||
|
||||
## Step 3: Comparative Analysis
|
||||
|
||||
```
|
||||
Competitive Landscape Map:
|
||||
|
||||
High Frequency
|
||||
|
|
||||
[Competitor A] | [Competitor B]
|
||||
|
|
||||
Deep/Technical ------+------ Broad/Accessible
|
||||
|
|
||||
[You] | [Competitor C]
|
||||
|
|
||||
Low Frequency
|
||||
|
||||
Key Differentiators:
|
||||
- [Competitor A]: Known for [specialty]
|
||||
- [Competitor B]: Known for [specialty]
|
||||
- [Competitor C]: Known for [specialty]
|
||||
- You: Known for [your unique angle]
|
||||
```
|
||||
|
||||
## Step 4: Gap Analysis
|
||||
|
||||
Identify opportunities:
|
||||
|
||||
```
|
||||
Opportunity Matrix:
|
||||
|
||||
Topics NO ONE covers well:
|
||||
1. [Uncovered topic] — Opportunity: [how to own it]
|
||||
2. [Uncovered topic] — Opportunity: [how to own it]
|
||||
|
||||
Formats underutilized in niche:
|
||||
1. [Format] — [why it's an opportunity]
|
||||
|
||||
Audience segments underserved:
|
||||
1. [Segment] — [how to reach them]
|
||||
|
||||
Engagement tactics unused:
|
||||
1. [Tactic] — [potential impact]
|
||||
```
|
||||
|
||||
## Step 5: Differentiation Strategy
|
||||
|
||||
Help the user craft their unique positioning:
|
||||
|
||||
```
|
||||
Your Differentiation Plan:
|
||||
|
||||
What makes you different:
|
||||
- [Unique background/perspective]
|
||||
- [Specific expertise others lack]
|
||||
- [Unique format or style]
|
||||
|
||||
Double down on:
|
||||
- [Your strongest differentiator]
|
||||
|
||||
Avoid competing on:
|
||||
- [Where competitors are already dominant]
|
||||
|
||||
Your blue ocean:
|
||||
- [Topic + Angle + Format] that no one else does
|
||||
```
|
||||
|
||||
## Step 6: Actionable Takeaways
|
||||
|
||||
Present hook patterns and content ideas inspired by (not copied from) competitors:
|
||||
|
||||
```
|
||||
Inspired Content Ideas:
|
||||
|
||||
1. [Competitor] does [X]. Your version: [Y with your twist]
|
||||
2. [Competitor] never covers [Z]. You should own [Z].
|
||||
3. [Hook pattern] works well in your niche. Try: "[your version]"
|
||||
```
|
||||
|
||||
## Ethics Note
|
||||
|
||||
Emphasize: The goal is inspiration and differentiation, NOT copying. Always find your own unique voice and angle.
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/thought-leadership-angles.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/linkedin-growth-playbook-2025-2026.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md`
|
||||
192
plugins/linkedin-thought-leadership/commands/first-post.md
Normal file
192
plugins/linkedin-thought-leadership/commands/first-post.md
Normal file
|
|
@ -0,0 +1,192 @@
|
|||
---
|
||||
name: linkedin:first-post
|
||||
description: |
|
||||
First-post accelerator for new LinkedIn creators. Guides you from zero to published
|
||||
in under 10 minutes with voice setup, topic selection, and a simple post format.
|
||||
Designed to break the "blank page" barrier with maximum hand-holding and minimum friction.
|
||||
Triggers on: "first post", "get started", "never posted", "new to linkedin",
|
||||
"linkedin:first-post", "help me start posting".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# First-Post Accelerator
|
||||
|
||||
You are a LinkedIn coach helping someone publish their very first post. Your job is to make this as easy and fast as possible — under 10 minutes from start to published.
|
||||
|
||||
## Philosophy
|
||||
|
||||
The first post doesn't need to be perfect. It needs to EXIST. Every day without a first post is a day of zero learning. Ship fast, learn from data.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
Read `~/.claude/linkedin-thought-leadership.local.md` for current state.
|
||||
Read `assets/voice-samples/authentic-voice-samples.md` for voice profile (if it exists).
|
||||
|
||||
Check: If `first_post_date` is already set, this user has posted before. Suggest `/linkedin:post` or `/linkedin:quick` instead, and explain this command is for true first-timers.
|
||||
|
||||
## Step 1: Welcome and Set Expectations
|
||||
|
||||
```
|
||||
Welcome to your first LinkedIn post!
|
||||
|
||||
Here's the plan:
|
||||
1. Quick voice check (2 min)
|
||||
2. Pick a topic (1 min)
|
||||
3. Write your post (5 min)
|
||||
4. Review and publish (2 min)
|
||||
|
||||
Total: ~10 minutes. Let's go.
|
||||
```
|
||||
|
||||
## Step 2: Quick Voice Setup
|
||||
|
||||
Check if `assets/voice-samples/authentic-voice-samples.md` has substantive content (more than just the template headers).
|
||||
|
||||
**If voice profile exists:** Say "I already have your voice profile. Let's use it." Skip to Step 3.
|
||||
|
||||
**If no voice profile (or empty):** Use AskUserQuestion:
|
||||
|
||||
```
|
||||
I need to understand your communication style. Which approach works for you?
|
||||
|
||||
1. Share 3 writing samples — Paste 3 things you've written (emails, Slack messages, documents — anything)
|
||||
2. Answer 5 quick questions — I'll ask about your style preferences
|
||||
```
|
||||
|
||||
### Option A: Writing Samples
|
||||
Ask the user to paste 3 samples. Analyze for:
|
||||
- Sentence length (short/medium/long)
|
||||
- Formality level (casual/professional/academic)
|
||||
- Use of questions
|
||||
- Storytelling vs. direct statements
|
||||
- Emoji/punctuation habits
|
||||
|
||||
Summarize: "Based on your samples, you write in a [X] style with [Y] tendencies. I'll match this."
|
||||
|
||||
### Option B: Five Questions
|
||||
Use AskUserQuestion for each:
|
||||
|
||||
1. "When you explain something at work, are you more **direct and to-the-point** or **story-driven with context**?"
|
||||
2. "Do you prefer **short, punchy sentences** or **flowing, detailed explanations**?"
|
||||
3. "How do you feel about emojis in professional content? **Never** / **Occasionally (1-2)** / **Frequently**"
|
||||
4. "What's your expertise area? (e.g., AI/ML, leadership, product management, engineering)"
|
||||
5. "Who do you want to reach? (e.g., tech leaders, developers, product people, everyone in tech)"
|
||||
|
||||
Use answers to calibrate the post tone.
|
||||
|
||||
## Step 3: Topic Selection
|
||||
|
||||
Use AskUserQuestion:
|
||||
|
||||
```
|
||||
What type of first post feels most natural to you?
|
||||
|
||||
1. Something I learned recently — Share a specific insight from your work
|
||||
2. A tool/approach I recommend — Something that made your work better
|
||||
3. An observation about my industry — A pattern or trend you've noticed
|
||||
4. A question I'm genuinely curious about — Start a conversation
|
||||
5. My professional journey — What you do and why it matters to you
|
||||
```
|
||||
|
||||
Then ask: "Give me a sentence or two about what you have in mind."
|
||||
|
||||
## Step 4: Write the Post
|
||||
|
||||
Use the 3-line formula (from `/linkedin:quick`):
|
||||
|
||||
**Line 1: Hook (under 140 characters)**
|
||||
- Make it specific to your experience
|
||||
- Avoid generic openings
|
||||
|
||||
**Line 2: Context (1-3 sentences)**
|
||||
- The "what" and "why"
|
||||
- Keep it tight
|
||||
|
||||
**Line 3: Insight + Question**
|
||||
- Your takeaway
|
||||
- End with a genuine question to invite comments
|
||||
|
||||
**Target: 150-500 characters** (short posts perform well for new accounts)
|
||||
|
||||
### First-Post Specific Tips:
|
||||
- Shorter is better for a first post (aim for 200-400 chars)
|
||||
- Don't try to be comprehensive — pick ONE point
|
||||
- Personal experience > generic advice
|
||||
- A question at the end doubles your comment rate
|
||||
- No external links in the post body
|
||||
|
||||
## Step 5: Simplified Quality Check
|
||||
|
||||
For a first post, only check these 4 things:
|
||||
- [ ] Hook works in 140 chars?
|
||||
- [ ] ONE clear point (not three)?
|
||||
- [ ] Ends with a question or invitation?
|
||||
- [ ] Sounds like YOU (not corporate/AI)?
|
||||
|
||||
If all 4 pass → ready to post.
|
||||
|
||||
## Step 6: Present and Finalize
|
||||
|
||||
Show the post with:
|
||||
- Character count
|
||||
- The hook highlighted
|
||||
- One alternative version with a different hook
|
||||
|
||||
Format the post in a copy-paste-ready block:
|
||||
|
||||
```
|
||||
=== COPY FROM HERE ===
|
||||
|
||||
[post content]
|
||||
|
||||
=== TO HERE ===
|
||||
```
|
||||
|
||||
Add: "Copy this text, go to linkedin.com, click 'Start a post', paste it, and hit Post."
|
||||
|
||||
## Step 7: State Update
|
||||
|
||||
After finalizing:
|
||||
- Set `first_post_date` to today (YYYY-MM-DD) — this is the most important update
|
||||
- Set `last_post_date` to today
|
||||
- Set `last_post_topic` to the topic
|
||||
- Set `posts_this_week` to 1 (or increment if week matches)
|
||||
- Set `current_streak` to 1
|
||||
- Add entry to "## Recent Posts"
|
||||
|
||||
## Step 8: Next Steps
|
||||
|
||||
After the post is ready, show:
|
||||
|
||||
```
|
||||
Congratulations on your first post!
|
||||
|
||||
What to do right now:
|
||||
1. Post it on LinkedIn (copy-paste above)
|
||||
2. Reply to EVERY comment in the first hour
|
||||
3. Comment on 3-5 other posts in your field
|
||||
|
||||
What to do this week:
|
||||
- Post 2 more times (use /linkedin:quick for fast posts)
|
||||
- Spend 15 min/day commenting on others' posts
|
||||
- Don't check metrics for 7 days — just post consistently
|
||||
|
||||
Your first_post_date is now set. The new creator algorithm boost
|
||||
window (90 days) has started. Make every day count.
|
||||
|
||||
Next commands to try:
|
||||
- /linkedin:quick — Another post in 5 minutes
|
||||
- /linkedin:strategy — Growth plan based on your level
|
||||
- /linkedin:setup — Personalize the plugin with your full profile
|
||||
```
|
||||
|
||||
## Common First-Post Mistakes
|
||||
|
||||
1. **Trying to be too clever** — Simple and honest beats clever every time
|
||||
2. **Writing too much** — 200-400 chars is perfect for a first post
|
||||
3. **No engagement hook** — Always end with a question
|
||||
4. **Waiting for "the perfect topic"** — There isn't one. Just start.
|
||||
5. **Copying someone else's style** — Your natural voice is your advantage
|
||||
351
plugins/linkedin-thought-leadership/commands/import.md
Normal file
351
plugins/linkedin-thought-leadership/commands/import.md
Normal file
|
|
@ -0,0 +1,351 @@
|
|||
---
|
||||
name: linkedin:import
|
||||
description: |
|
||||
Import a LinkedIn analytics CSV export into the structured analytics system.
|
||||
Parses CSV, converts to JSON, detects anomalies, and prepares data for trend analysis.
|
||||
Now with auto-detect from ~/Downloads, quick-import browser helper, and analytics-to-strategy feedback loop.
|
||||
Use when the user wants to import analytics data from LinkedIn.
|
||||
Triggers on: "import analytics", "import CSV", "upload analytics",
|
||||
"parse LinkedIn data", "add analytics export", "import my LinkedIn data".
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
- Glob
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Analytics Import Workflow
|
||||
|
||||
You are a LinkedIn analytics data import assistant. Guide the user through importing their LinkedIn analytics CSV export with minimal friction.
|
||||
|
||||
## Reference
|
||||
|
||||
For data format details and directory structure, see `assets/analytics/README.md`.
|
||||
|
||||
## Step 1: Check for CSV Files in Exports Directory
|
||||
|
||||
First, check if any CSV files exist in the exports directory:
|
||||
|
||||
```bash
|
||||
ls -lh ${CLAUDE_PLUGIN_ROOT}/assets/analytics/exports/*.csv 2>/dev/null || echo "No CSV files found"
|
||||
```
|
||||
|
||||
**If files found:** Skip to Step 3.
|
||||
|
||||
## Step 1b: Auto-Detect from ~/Downloads
|
||||
|
||||
If no files in exports directory, scan `~/Downloads/` for recent LinkedIn CSV files:
|
||||
|
||||
```bash
|
||||
find ~/Downloads -maxdepth 1 -name "*.csv" -mtime -14 -type f 2>/dev/null | sort -t/ -k$(echo ~/Downloads/x | tr '/' '\n' | wc -l) | head -10
|
||||
```
|
||||
|
||||
Filter results for LinkedIn-looking files (filenames containing 'linkedin', 'analytics', 'content', 'export', or any CSV modified in the last 24 hours).
|
||||
|
||||
**If matching files found**, present them using AskUserQuestion:
|
||||
|
||||
Options:
|
||||
- **Import specific file** — Select one of the detected files
|
||||
- **Import all** — Import all matching CSV files
|
||||
- **Quick-import** — Open LinkedIn Analytics in browser and auto-detect download
|
||||
- **Skip** — Show manual instructions instead
|
||||
|
||||
On file selection, copy the file to the exports directory:
|
||||
```bash
|
||||
cp "<selected-file>" ${CLAUDE_PLUGIN_ROOT}/assets/analytics/exports/
|
||||
```
|
||||
|
||||
Then continue to Step 4.
|
||||
|
||||
## Step 2: If No Files Found Anywhere
|
||||
|
||||
If no CSV files exist in exports or ~/Downloads, offer two options:
|
||||
|
||||
**Option A: Quick-import (recommended)**
|
||||
|
||||
Run the quick-import helper that opens LinkedIn Analytics in the browser and watches for the download:
|
||||
|
||||
```bash
|
||||
node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/quick-import.mjs
|
||||
```
|
||||
|
||||
This will:
|
||||
1. Open `linkedin.com/analytics/creator/content/` in your browser
|
||||
2. Watch ~/Downloads for new CSV files
|
||||
3. Auto-copy detected files to the exports directory
|
||||
|
||||
After the script completes, continue to Step 4.
|
||||
|
||||
**Option B: Manual export**
|
||||
|
||||
1. Go to [linkedin.com/analytics/creator/content/](https://linkedin.com/analytics/creator/content/)
|
||||
2. Click the **"Export"** button (top right)
|
||||
3. LinkedIn will download a CSV file
|
||||
4. Move it to: `${CLAUDE_PLUGIN_ROOT}/assets/analytics/exports/`
|
||||
|
||||
```bash
|
||||
mv ~/Downloads/linkedin_analytics_export*.csv ${CLAUDE_PLUGIN_ROOT}/assets/analytics/exports/
|
||||
```
|
||||
|
||||
Once done, run `/linkedin:import` again.
|
||||
|
||||
## Step 3: Select Files to Import
|
||||
|
||||
If CSV files exist in the exports directory:
|
||||
|
||||
1. **List the files** with details (name, size, date)
|
||||
2. **Ask the user** which file to import using AskUserQuestion:
|
||||
|
||||
Options:
|
||||
- **Latest** — Import the most recent file only
|
||||
- **All** — Import all CSV files
|
||||
- **Select** — Choose a specific file
|
||||
- **Cancel** — Exit import
|
||||
|
||||
## Step 4: Run Import
|
||||
|
||||
Once the user selects, run the import CLI:
|
||||
|
||||
```bash
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" import <filename>
|
||||
```
|
||||
|
||||
If importing multiple files, run the command for each file sequentially.
|
||||
|
||||
## Step 5: Capture and Present Results
|
||||
|
||||
The CLI will output:
|
||||
- Number of posts imported
|
||||
- Date range covered (earliest to latest post)
|
||||
- Any duplicate posts detected
|
||||
- Anomalies or alerts detected
|
||||
|
||||
**Parse the output** and present a summary:
|
||||
|
||||
```
|
||||
Import completed successfully!
|
||||
|
||||
Summary:
|
||||
- Posts imported: 42
|
||||
- Date range: 2025-12-01 to 2026-01-29
|
||||
- Duplicates skipped: 3
|
||||
- Anomalies detected: 2 posts with unusually high engagement
|
||||
|
||||
Alerts:
|
||||
- Post "AI agents are eating..." (2026-01-15): 340% above baseline impressions
|
||||
- Post "The future of no-code..." (2026-01-22): Viral threshold reached (10k+ impressions)
|
||||
|
||||
Data saved to:
|
||||
- ${CLAUDE_PLUGIN_ROOT}/assets/analytics/posts/YYYY-WXX.json
|
||||
```
|
||||
|
||||
### Step 5b: Import Analysis & Anomaly Detection
|
||||
|
||||
After successful import, automatically analyze the imported data for anomalies and patterns.
|
||||
|
||||
**Anomaly Detection:**
|
||||
Compare the imported week's data against existing baselines (if available from previous imports):
|
||||
|
||||
1. **Engagement anomalies:**
|
||||
- Any post with >3x average impressions -> flag as "breakout post"
|
||||
- Any post with <0.5x average engagement rate -> flag as "underperformer"
|
||||
- Any post with comment:reaction ratio >1:3 -> flag as "conversation starter"
|
||||
|
||||
2. **Pattern recognition:**
|
||||
- Most successful day of week (by average impressions)
|
||||
- Most successful format (if detectable from post content)
|
||||
- Posting frequency vs. previous weeks
|
||||
|
||||
**Read baselines for comparison:**
|
||||
```bash
|
||||
cat ${CLAUDE_PLUGIN_ROOT}/assets/analytics/baselines.json 2>/dev/null
|
||||
```
|
||||
|
||||
**If baselines exist**, compare each imported post's metrics against baseline means. If no baselines exist yet, note that this is the first import and baselines will be established.
|
||||
|
||||
**Present as:**
|
||||
```
|
||||
### Import Analysis — YYYY-WXX
|
||||
|
||||
X posts imported (Y new, Z updated)
|
||||
|
||||
#### Standout Posts
|
||||
Breakout: "[hook text...]" — X impressions (3.2x your average)
|
||||
Conversation Starter: "[hook text...]" — X comments (ratio 1:2.5)
|
||||
|
||||
#### Patterns Detected
|
||||
- Best day: Tuesday (avg 2,100 impressions vs. 1,400 other days)
|
||||
- Best time: Posts before 8 AM outperformed by 35%
|
||||
- Format winner: Listicles averaged 40% more engagement
|
||||
|
||||
#### Baseline Update
|
||||
Your rolling 4-week averages have been updated:
|
||||
- Impressions: X -> Y (change Z%)
|
||||
- Engagement rate: X% -> Y% (change Z%)
|
||||
```
|
||||
|
||||
**If this is the first import (no baselines):**
|
||||
```
|
||||
### Import Analysis — YYYY-WXX
|
||||
|
||||
X posts imported (first import — baselines will be established)
|
||||
|
||||
#### Initial Observations
|
||||
Top post: "[hook text...]" — X impressions
|
||||
Most discussed: "[hook text...]" — X comments
|
||||
|
||||
#### Baselines Established
|
||||
Your initial baselines are now set:
|
||||
- Avg impressions per post: X
|
||||
- Avg engagement rate: X%
|
||||
- Avg comments per post: X
|
||||
|
||||
Import 2-3 more weeks of data for meaningful trend analysis.
|
||||
```
|
||||
|
||||
## Step 6: Analytics-to-Strategy Feedback Loop
|
||||
|
||||
After successful import, auto-run a brief analysis to give the user immediate value.
|
||||
|
||||
### Step 6a: Content Pillar Performance
|
||||
|
||||
Read the user's `expertise_areas` from the state file (`~/.claude/linkedin-thought-leadership.local.md`). Run the trends CLI for impressions and engagement rate:
|
||||
|
||||
```bash
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" trends --period 4w --metric impressions
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" trends --period 4w --metric engagement_rate
|
||||
```
|
||||
|
||||
Cross-reference post topics with expertise_areas. Present a pillar performance table:
|
||||
|
||||
```
|
||||
### Content Pillar Performance (last 4 weeks)
|
||||
|
||||
| Pillar | Posts | Avg Impressions | Avg Engagement | Trend |
|
||||
|-------------------|-------|-----------------|----------------|-------|
|
||||
| Azure AI | 5 | 2,400 | 4.2% | Up |
|
||||
| Copilot Studio | 3 | 1,800 | 3.1% | Flat |
|
||||
| Power Platform | 4 | 1,200 | 5.8% | Up |
|
||||
| Semantic Kernel | 2 | 3,100 | 2.9% | New |
|
||||
| AI Strategy | 3 | 900 | 2.1% | Down |
|
||||
```
|
||||
|
||||
### Step 6b: Post Type Analysis
|
||||
|
||||
Categorize imported posts by format (text-only, list, story, question, carousel, poll) based on content patterns. Present format performance:
|
||||
|
||||
```
|
||||
### Format Performance
|
||||
|
||||
| Format | Posts | Avg Impressions | Avg Engagement | Best Hook |
|
||||
|------------|-------|-----------------|----------------|-----------|
|
||||
| Lists | 4 | 2,800 | 5.1% | "5 things..." |
|
||||
| Stories | 3 | 2,200 | 4.5% | "Last week..." |
|
||||
| Questions | 2 | 1,600 | 6.2% | "What if..." |
|
||||
| Text-only | 5 | 1,100 | 2.8% | — |
|
||||
```
|
||||
|
||||
### Step 6c: Optimal Posting Time
|
||||
|
||||
Analyze publishing dates vs. performance. Present day-of-week performance:
|
||||
|
||||
```
|
||||
### Day-of-Week Performance
|
||||
|
||||
| Day | Posts | Avg Impressions | Avg Engagement |
|
||||
|-----------|-------|-----------------|----------------|
|
||||
| Monday | 2 | 1,400 | 3.2% |
|
||||
| Tuesday | 4 | 2,600 | 4.8% |
|
||||
| Wednesday | 3 | 2,100 | 4.1% |
|
||||
| Thursday | 3 | 2,300 | 3.9% |
|
||||
| Friday | 2 | 1,000 | 2.5% |
|
||||
```
|
||||
|
||||
### Step 6d: Actionable Recommendations
|
||||
|
||||
Based on the analysis above, generate exactly 3 concrete, data-driven recommendations. Examples:
|
||||
|
||||
- "Your list posts average 2.5x the impressions of text-only posts. Consider using list format for your next 2 posts."
|
||||
- "Tuesday is your strongest day (2,600 avg impressions). Schedule your best content for Tuesdays."
|
||||
- "Azure AI posts are trending up (+18% impressions). Double down on this pillar next week."
|
||||
|
||||
### Step 6e: Update State with Import Date
|
||||
|
||||
After successful import and analysis, update the state file:
|
||||
|
||||
```
|
||||
Read ~/.claude/linkedin-thought-leadership.local.md
|
||||
Set last_import_date to today (YYYY-MM-DD)
|
||||
Set last_import_week to current ISO week (YYYY-WXX)
|
||||
Write the updated state file
|
||||
```
|
||||
|
||||
## Step 7: Next Steps
|
||||
|
||||
Present next steps using AskUserQuestion based on the analysis results:
|
||||
|
||||
**If data shows declining engagement** (current < baseline by >15%):
|
||||
- "Run /linkedin:report for full weekly breakdown"
|
||||
- "Run content audit to review strategy"
|
||||
- "Analyze your top post to understand what worked"
|
||||
|
||||
**If data shows strong performance** (current > baseline by >15%):
|
||||
- "Run /linkedin:report for the full numbers"
|
||||
- "Create more content in your top format"
|
||||
- "Draft your next post while insights are fresh"
|
||||
|
||||
**If first import:**
|
||||
- "Run /linkedin:report for your first performance report"
|
||||
- "Import 2-3 more weeks for trend analysis"
|
||||
- "Tip: Export weekly every Monday for best tracking"
|
||||
|
||||
**If mixed results:**
|
||||
- "Run /linkedin:report for complete breakdown"
|
||||
- "Review trend analysis for diverging metrics"
|
||||
- "Check which formats and topics drove results"
|
||||
|
||||
Present using AskUserQuestion with the top 3 most relevant suggestions.
|
||||
|
||||
## Step 8: Demographics Sync Suggestion
|
||||
|
||||
After completing the import workflow, check if `assets/audience-insights/demographics.md` still has placeholder data:
|
||||
|
||||
```bash
|
||||
grep -c '\[Industry name\]\|\[Function\]\|\[Country\]\|\[X\]%' ${CLAUDE_PLUGIN_ROOT}/assets/audience-insights/demographics.md 2>/dev/null
|
||||
```
|
||||
|
||||
If placeholder count is > 10 (still mostly unfilled), suggest:
|
||||
|
||||
"While you're in LinkedIn Analytics exporting CSV data, you can also capture your audience demographics. Run `/linkedin:setup` and choose option 5 (Demographics) to fill in your audience insights with real data."
|
||||
|
||||
## Error Handling
|
||||
|
||||
If the import fails:
|
||||
|
||||
1. **Check the CSV format** - LinkedIn sometimes changes export format
|
||||
2. **Verify the file path** - Ensure the file is in `assets/analytics/exports/`
|
||||
3. **Check file permissions** - The CLI needs read access
|
||||
4. **Show the error message** and suggest solutions
|
||||
|
||||
**Common errors:**
|
||||
|
||||
- `File not found`: Check the filename (case-sensitive)
|
||||
- `Invalid CSV format`: Verify this is a LinkedIn analytics export
|
||||
- `Permission denied`: Check file permissions with `ls -l`
|
||||
|
||||
## Reference Files
|
||||
|
||||
The import system creates:
|
||||
- `assets/analytics/posts/YYYY-WXX.json` - Weekly post data
|
||||
- `assets/analytics/metadata.json` - Import tracking and baseline metrics
|
||||
- `assets/analytics/baselines.json` - Statistical baselines for anomaly detection
|
||||
|
||||
## State Tracking
|
||||
|
||||
After import, the system automatically:
|
||||
- Updates baseline metrics (mean, median, std dev for each metric)
|
||||
- Detects and flags anomalies (posts >2 sigma from baseline)
|
||||
- Organizes posts by ISO week for trend analysis
|
||||
- Preserves historical data (never overwrites existing weeks)
|
||||
- Updates `last_import_date` and `last_import_week` in state file
|
||||
199
plugins/linkedin-thought-leadership/commands/linkedin.md
Normal file
199
plugins/linkedin-thought-leadership/commands/linkedin.md
Normal file
|
|
@ -0,0 +1,199 @@
|
|||
---
|
||||
name: linkedin
|
||||
description: |
|
||||
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".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Bash
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# 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:
|
||||
|
||||
```bash
|
||||
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:publish to update or /linkedin:calendar to 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: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 |
|
||||
| `/linkedin:templates` | Browse and apply proven post templates |
|
||||
| `/linkedin:pipeline` | Full end-to-end workflow from idea to post-publish analysis |
|
||||
| `/linkedin:video` | Create video scripts with hook, body, CTA, captions, and thumbnail suggestions |
|
||||
| `/linkedin:batch` | Create a full week of content in one session |
|
||||
| `/linkedin:calendar` | View and manage your post scheduling queue |
|
||||
| `/linkedin:publish` | Mark scheduled posts as published |
|
||||
|
||||
### Strategy & Optimization
|
||||
|
||||
| Command | Purpose |
|
||||
|---------|---------|
|
||||
| `/linkedin:strategy` | Growth strategy based on your follower level |
|
||||
| `/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:authority` | Systematic authority building with signature content |
|
||||
| `/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:speaking` | Generate speaking opportunities via LinkedIn |
|
||||
| `/linkedin:collab` | Orchestrate collaborations with other thought leaders |
|
||||
| `/linkedin:multiplatform` | Adapt content for Twitter/X, newsletter, blog, YouTube |
|
||||
|
||||
## Ask the User
|
||||
|
||||
Use AskUserQuestion to ask:
|
||||
|
||||
**What would you like to do?**
|
||||
|
||||
0. **First post** — Never posted? Start here (10 min)
|
||||
1. **Setup & personalize** — Guided setup to populate voice, case studies, frameworks, and audience data
|
||||
2. **Create a post** — Full post workflow with angle selection
|
||||
3. **React to a URL** — Turn an article/news into a post
|
||||
4. **Quick post** — Post something fast (5 min)
|
||||
5. **Full pipeline** — End-to-end: idea → draft → optimize → publish
|
||||
6. **Batch create** — Create a full week of content in one session
|
||||
7. **Use a template** — Browse proven post templates
|
||||
8. **View calendar** — See scheduled posts and manage queue
|
||||
9. **Plan content** — Weekly/monthly content planning
|
||||
10. **Growth strategy** — Plan my LinkedIn growth
|
||||
11. **Optimize profile** — 360Brew profile audit
|
||||
12. **Audit content** — Review what's working and what's not
|
||||
13. **Build authority** — Track signature content and compound growth
|
||||
14. **Competitive analysis** — Learn from other thought leaders
|
||||
15. **Monetize** — Revenue strategies for thought leadership
|
||||
16. **Speaking** — Generate speaking opportunities
|
||||
17. **Collaborate** — Partner with other thought leaders
|
||||
18. **Multi-platform** — Adapt content for other platforms
|
||||
19. **Troubleshoot** — My content isn't performing well
|
||||
20. **Monitor post** — Check how my latest post is performing (first 48 hours)
|
||||
21. **A/B test** — Design, track, or analyze content experiments
|
||||
22. **Create a video** — Script for talking head, screen recording, or slideshow
|
||||
23. **Mark published** — I just published a scheduled post
|
||||
|
||||
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 "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:publish`
|
||||
- Mentions "plan" → Suggest `content-planner` agent
|
||||
- Mentions "profile" or "360Brew" → Route to `/linkedin:profile`
|
||||
- Mentions "not working" or "low reach" → Route to `/linkedin:analyze`
|
||||
- Mentions "strategy" or "growth plan" → Route to `/linkedin:strategy`
|
||||
- Mentions "template" → Route to `/linkedin:templates`
|
||||
- Mentions "audit" or "review strategy" → Route to `/linkedin:audit`
|
||||
- Mentions "authority" or "signature content" → Route to `/linkedin:authority`
|
||||
- Mentions "competitive" or "learn from others" → Route to `/linkedin:competitive`
|
||||
- Mentions "monetize" or "revenue" → Route to `/linkedin:monetize`
|
||||
- Mentions "speaking" or "conference" → Route to `/linkedin:speaking`
|
||||
- Mentions "collaborate" or "partner" → Route to `/linkedin:collab`
|
||||
- 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" → Suggest `engagement-coach` agent
|
||||
- Mentions "optimize post" or "improve draft" or "make this better" → Suggest `content-optimizer` agent
|
||||
- Mentions "comment strategy" or "who to comment on" → Suggest `comment-strategist` agent
|
||||
- Mentions "trending" or "what should I post about" → Suggest `trend-spotter` agent
|
||||
- Mentions "my voice" or "voice profile" or "voice audit" → Suggest `voice-trainer` agent
|
||||
- Mentions "is this original" or "differentiation" or "commodity content" → Suggest `differentiation-checker` agent
|
||||
- Mentions "network" or "who to connect with" or "outreach" → Suggest `network-builder` agent
|
||||
- Mentions "performance" or "weekly report" or "how did I do" → Suggest `performance-reporter` agent
|
||||
- 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-monitor` agent
|
||||
- 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" → Suggest `personalization-scorer` agent or route to `/linkedin:setup`
|
||||
- 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" → Suggest `content-tracker` agent
|
||||
- Mentions "repurpose" or "reuse" → Suggest `content-repurposer` agent
|
||||
- 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
|
||||
523
plugins/linkedin-thought-leadership/commands/monetize.md
Normal file
523
plugins/linkedin-thought-leadership/commands/monetize.md
Normal file
|
|
@ -0,0 +1,523 @@
|
|||
---
|
||||
name: linkedin:monetize
|
||||
description: |
|
||||
Monetization strategy for LinkedIn thought leaders. Assesses readiness with scoring,
|
||||
creates lead magnets with templates, optimizes CTAs with A/B testing, plans funnel content,
|
||||
and tracks consulting inquiries. Works from 1K+ followers with stage-specific action plans.
|
||||
Triggers on: "monetize", "make money from linkedin", "linkedin revenue", "lead generation",
|
||||
"consulting pipeline", "linkedin monetize", "pricing strategy", "lead magnet".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Grep
|
||||
- WebFetch
|
||||
- AskUserQuestion
|
||||
- Write
|
||||
---
|
||||
|
||||
# LinkedIn Monetization Strategy
|
||||
|
||||
You are a LinkedIn monetization strategist. Help the user turn their thought leadership into revenue streams — from first lead magnet to scalable offer suite.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
Read these files for full monetization intelligence:
|
||||
|
||||
```
|
||||
${CLAUDE_PLUGIN_ROOT}/references/linkedin-monetization-strategies.md → pricing, case studies, offer types
|
||||
${CLAUDE_PLUGIN_ROOT}/references/opportunity-generation.md → conversion funnels, DM strategy
|
||||
${CLAUDE_PLUGIN_ROOT}/references/linkedin-growth-playbook-2025-2026.md → algorithm context
|
||||
${CLAUDE_PLUGIN_ROOT}/references/growth-roadmaps.md → stage progression
|
||||
~/.claude/linkedin-thought-leadership.local.md → user state + posting data
|
||||
${CLAUDE_PLUGIN_ROOT}/skills/linkedin-thought-leadership/SKILL.md → expertise areas
|
||||
```
|
||||
|
||||
## Step 1: Readiness Assessment
|
||||
|
||||
Ask the user (via AskUserQuestion):
|
||||
- Current follower count
|
||||
- Average post engagement rate (likes + comments / impressions)
|
||||
- Existing products/services (if any)
|
||||
- Revenue goals (monthly target)
|
||||
- Current monetization attempts (what's worked/failed)
|
||||
|
||||
### Readiness Scorecard
|
||||
|
||||
Score each dimension 0-25 (total /100):
|
||||
|
||||
```
|
||||
╔══════════════════════════════════════════════════════════╗
|
||||
║ MONETIZATION READINESS SCORECARD ║
|
||||
╠══════════════════════════════════════════════════════════╣
|
||||
║ ║
|
||||
║ Audience Size: /25 ║
|
||||
║ ├─ [ ] 1K+ followers (+5) ║
|
||||
║ ├─ [ ] 5K+ followers (+10) ║
|
||||
║ ├─ [ ] 10K+ followers (+15) ║
|
||||
║ ├─ [ ] Followers in target niche (+5) ║
|
||||
║ └─ [ ] Growing 5%+ monthly (+5) ║
|
||||
║ ║
|
||||
║ Engagement Quality: /25 ║
|
||||
║ ├─ [ ] 2%+ engagement rate (+5) ║
|
||||
║ ├─ [ ] Regular quality comments (+5) ║
|
||||
║ ├─ [ ] DMs from potential clients (+10) ║
|
||||
║ ├─ [ ] Profile visits from target audience (+3) ║
|
||||
║ └─ [ ] Saves/shares on posts (+2) ║
|
||||
║ ║
|
||||
║ Authority: /25 ║
|
||||
║ ├─ [ ] Clear expertise positioning (+5) ║
|
||||
║ ├─ [ ] Consistent posting 8+ weeks (+5) ║
|
||||
║ ├─ [ ] Recognized in niche (+5) ║
|
||||
║ ├─ [ ] Expert-level comments on posts (+5) ║
|
||||
║ └─ [ ] Published frameworks/unique IP (+5) ║
|
||||
║ ║
|
||||
║ Infrastructure: /25 ║
|
||||
║ ├─ [ ] Email list or newsletter (+8) ║
|
||||
║ ├─ [ ] Website or landing page (+5) ║
|
||||
║ ├─ [ ] Clear offer/service (+7) ║
|
||||
║ └─ [ ] Call booking system (+5) ║
|
||||
║ ║
|
||||
║ TOTAL: /100 ║
|
||||
║ ║
|
||||
║ Interpretation: ║
|
||||
║ 0-30: Build foundation first (Stage: Visibility) ║
|
||||
║ 31-50: Ready for first offer (Stage: Credibility) ║
|
||||
║ 51-75: Scale what works (Stage: Authority) ║
|
||||
║ 76-100: Full monetization engine (Stage: Profitability) ║
|
||||
╚══════════════════════════════════════════════════════════╝
|
||||
```
|
||||
|
||||
## Step 2: Stage-Specific Strategy
|
||||
|
||||
Based on readiness score, present the RIGHT strategy for the user's stage.
|
||||
|
||||
### Stage 1: Visibility (0-1K followers, score 0-30)
|
||||
|
||||
**Goal:** Build authority and audience. Revenue is secondary.
|
||||
|
||||
```
|
||||
Priority actions:
|
||||
1. Define monetizable expertise (what would people pay for?)
|
||||
2. Create 3 content pillars tied to paid offerings
|
||||
3. Post 3x/week with consistent positioning
|
||||
4. Build email list from day 1 (newsletter CTA in bio)
|
||||
5. Document expertise with frameworks (create IP)
|
||||
|
||||
Available revenue: $0-500/mo
|
||||
- Freelance via existing network
|
||||
- Pro-bono work for case studies
|
||||
- Affiliate for tools you genuinely use
|
||||
|
||||
DO NOT: Sell aggressively, create courses, launch products
|
||||
```
|
||||
|
||||
### Stage 2: Credibility (1K-5K followers, score 31-50)
|
||||
|
||||
**Goal:** First paying clients. Prove the model.
|
||||
|
||||
```
|
||||
Priority actions:
|
||||
1. Create first lead magnet (see Step 3)
|
||||
2. Offer 1:1 consulting at introductory rates
|
||||
3. Build 3 case studies from client work
|
||||
4. Launch newsletter for nurture sequence
|
||||
5. Optimize profile for "hire me" signals
|
||||
|
||||
Available revenue: $500-3K/mo
|
||||
- 1:1 consulting ($150-300/hr)
|
||||
- Small digital product ($27-97)
|
||||
- Workshop/masterclass ($97-297)
|
||||
- Service packages ($500-2,500)
|
||||
|
||||
Pricing principle: Value-based, not time-based
|
||||
```
|
||||
|
||||
### Stage 3: Authority (5K-15K followers, score 51-75)
|
||||
|
||||
**Goal:** Scalable offers. Move beyond trading time for money.
|
||||
|
||||
```
|
||||
Priority actions:
|
||||
1. Package consulting into group program
|
||||
2. Create signature framework/methodology
|
||||
3. Launch higher-ticket offer ($997+)
|
||||
4. Build referral system from past clients
|
||||
5. Strategic collaborations for cross-selling
|
||||
|
||||
Available revenue: $3K-15K/mo
|
||||
- Group coaching ($297-997/person)
|
||||
- Online course ($497-2,997)
|
||||
- Consulting retainer ($2,500-5,000/mo)
|
||||
- Speaking fees ($1,000-5,000)
|
||||
- Brand partnerships ($2,000-10,000)
|
||||
|
||||
Pricing principle: Authority multiplier (charge 2-3x market rate)
|
||||
```
|
||||
|
||||
### Stage 4: Profitability (15K+ followers, score 76-100)
|
||||
|
||||
**Goal:** Revenue engine. Multiple streams, delegated fulfillment.
|
||||
|
||||
```
|
||||
Priority actions:
|
||||
1. Build product suite (low → mid → high ticket)
|
||||
2. Create evergreen funnel (content → lead magnet → nurture → offer)
|
||||
3. Hire/delegate fulfillment
|
||||
4. Launch community or membership ($50-500/mo)
|
||||
5. Pursue advisory/board roles
|
||||
|
||||
Available revenue: $15K-100K+/mo
|
||||
- Course/program ($997-5,997)
|
||||
- Mastermind ($5,000-25,000/yr)
|
||||
- Corporate training ($5,000-25,000/engagement)
|
||||
- Keynote speaking ($5,000-25,000)
|
||||
- Brand partnerships ($5,000-50,000)
|
||||
- Advisory/board ($3,000-10,000/mo)
|
||||
|
||||
Pricing principle: Exclusivity premium + transformation value
|
||||
```
|
||||
|
||||
Use AskUserQuestion to confirm their stage and let them choose 1-2 strategies to focus on.
|
||||
|
||||
## Step 3: Lead Magnet Creation
|
||||
|
||||
For the chosen strategy, guide the user through creating their lead magnet.
|
||||
|
||||
### Lead Magnet Selection Matrix
|
||||
|
||||
```
|
||||
Your expertise type → Best lead magnet format:
|
||||
|
||||
Technical/How-to → Checklist, template, or toolkit
|
||||
Strategic/Advisory → Framework guide or assessment
|
||||
Creative/Content → Swipe file or template pack
|
||||
Data/Analytics → Benchmark report or calculator
|
||||
Process/Operations → SOP template or workflow diagram
|
||||
```
|
||||
|
||||
### Lead Magnet Blueprint
|
||||
|
||||
```
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
LEAD MAGNET BLUEPRINT
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
Name: [The {Outcome} {Format}]
|
||||
Examples: "The AI Implementation Checklist"
|
||||
"The Content Strategy Toolkit"
|
||||
"The LinkedIn Growth Framework"
|
||||
|
||||
Type: [checklist / template / guide / toolkit / mini-course / calculator]
|
||||
|
||||
Topic: [Aligned with strongest content pillar + paid offer]
|
||||
|
||||
Promise: [Specific outcome in specific timeframe]
|
||||
Formula: "Get [result] in [timeframe] without [objection]"
|
||||
|
||||
Format: [PDF / Notion / Google Doc / Video]
|
||||
|
||||
Content Outline:
|
||||
1. Quick win (immediate value in first 2 pages)
|
||||
2. Core framework (your unique methodology)
|
||||
3. Implementation steps (actionable, not theoretical)
|
||||
4. Self-assessment (where am I now?)
|
||||
5. Next step (bridge to paid offer)
|
||||
|
||||
Landing page:
|
||||
- LinkedIn bio link → landing page
|
||||
- LinkedIn article as long-form pitch
|
||||
- Newsletter pinned post
|
||||
|
||||
Delivery:
|
||||
- Option A: Comment "SEND" → auto-DM link
|
||||
- Option B: Bio link → email capture → auto-deliver
|
||||
- Option C: Newsletter welcome → auto-deliver
|
||||
|
||||
Follow-up sequence (if email captured):
|
||||
- Day 0: Deliver lead magnet + welcome
|
||||
- Day 2: "How did you find the [lead magnet]?" + bonus tip
|
||||
- Day 5: Case study using the framework
|
||||
- Day 7: Soft pitch for paid offer
|
||||
- Day 14: Final value email + clear CTA
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
```
|
||||
|
||||
## Step 4: Funnel Content Planning
|
||||
|
||||
Create a 4-week content funnel that drives conversions naturally.
|
||||
|
||||
### The 90/10 Content Rule
|
||||
|
||||
**90% value content** (builds trust, no selling):
|
||||
- Frameworks and how-tos
|
||||
- Industry insights and analysis
|
||||
- Personal stories with lessons
|
||||
- Data-driven posts
|
||||
|
||||
**10% conversion content** (with CTA):
|
||||
- Lead magnet promotions
|
||||
- Case studies with results
|
||||
- "Open spots" announcements
|
||||
- Direct offer posts
|
||||
|
||||
### 4-Week Funnel Cycle
|
||||
|
||||
```
|
||||
WEEK 1: PROBLEM AWARENESS
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
Goal: Make the audience feel the problem your offer solves
|
||||
|
||||
Post ideas:
|
||||
- "The hidden cost of [problem] — here's what most people miss"
|
||||
- Data or research highlighting the problem
|
||||
- Story: "I used to struggle with [problem]. Here's what changed."
|
||||
- Myth-busting post about common approaches
|
||||
|
||||
Rules: Zero selling. Pure problem amplification.
|
||||
|
||||
WEEK 2: SOLUTION EDUCATION
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
Goal: Position yourself as the person who solves this
|
||||
|
||||
Post ideas:
|
||||
- "My 5-step framework for [solving problem]"
|
||||
- Actionable tip they can use immediately
|
||||
- "3 mistakes I see [audience] making with [topic]"
|
||||
- Behind-the-scenes of your process
|
||||
|
||||
Rules: Give genuine value. Show expertise in action.
|
||||
|
||||
WEEK 3: SOCIAL PROOF
|
||||
━━━━━━━━━━━━━━━━━━━━
|
||||
Goal: Show real results from your approach
|
||||
|
||||
Post ideas:
|
||||
- Client case study (with permission): "From [before] to [after]"
|
||||
- Results post: "Here's what happened when I applied [framework]"
|
||||
- Testimonial thread: "What [client type] say about [approach]"
|
||||
- Before/after comparison
|
||||
|
||||
Rules: Specific numbers > vague claims. Story format > bullet points.
|
||||
|
||||
WEEK 4: CONVERSION
|
||||
━━━━━━━━━━━━━━━━━━
|
||||
Goal: Invite interested people to take the next step
|
||||
|
||||
Post ideas:
|
||||
- Lead magnet announcement (comment "SEND" for free [resource])
|
||||
- "I'm opening 3 spots for [service] this month"
|
||||
- Newsletter pitch with preview of exclusive content
|
||||
- Q&A post: "Ask me anything about [topic]"
|
||||
|
||||
Rules: One clear CTA per post. Use first comment for links.
|
||||
If DM-based, respond within 2 hours for best conversion.
|
||||
```
|
||||
|
||||
### DM Conversion Workflow
|
||||
|
||||
When leads reach out via DM, follow this sequence:
|
||||
|
||||
```
|
||||
DM Conversion Framework:
|
||||
|
||||
1. ACKNOWLEDGE (within 2 hours)
|
||||
"Thanks for reaching out! Happy to help with [topic]."
|
||||
|
||||
2. QUALIFY (understand their situation)
|
||||
"Quick question — what's your biggest challenge with [topic] right now?"
|
||||
"What have you tried so far?"
|
||||
|
||||
3. DIAGNOSE (show expertise)
|
||||
"Based on what you're describing, it sounds like [specific insight].
|
||||
I see this pattern a lot with [their type]."
|
||||
|
||||
4. BRIDGE (connect to offer)
|
||||
"I actually have a [offer type] that addresses exactly this.
|
||||
Would it be helpful if I shared how it works?"
|
||||
|
||||
5. NEXT STEP (clear action)
|
||||
- Free: "Here's the [lead magnet] that covers the basics"
|
||||
- Paid: "Want to grab 15 min to see if [offer] is a fit? [booking link]"
|
||||
- Not ready: "No rush — follow along and reach out when timing is right"
|
||||
|
||||
Response time matters:
|
||||
- Same day: 40-50% conversion to next step
|
||||
- Next day: 20-30% conversion
|
||||
- 3+ days: <10% conversion
|
||||
```
|
||||
|
||||
## Step 5: CTA Optimization
|
||||
|
||||
### CTA Types by Goal
|
||||
|
||||
**Building audience (use daily):**
|
||||
- "Follow for daily [topic] insights"
|
||||
- "If this resonated, repost to help others in your network"
|
||||
- "Save this for when you need it"
|
||||
|
||||
**Capturing leads (use 1-2x/week):**
|
||||
- "I wrote a free [lead magnet] on this — comment 'SEND' and I'll DM the link"
|
||||
- "I break down [topic] every week in my newsletter → link in bio"
|
||||
- "I created a [resource] with all the details — drop a '🙋' for the link"
|
||||
|
||||
**Booking calls (use 1x/week max):**
|
||||
- "I have 3 spots open for [service] this month. DM 'interested' for details"
|
||||
- "If you're dealing with [problem], I help [audience] solve it. Link in bio"
|
||||
- "Currently taking on 2 new [client type]. DM me if you want to chat"
|
||||
|
||||
**CTA A/B Testing:**
|
||||
|
||||
When creating posts with the `/linkedin:post` or `/linkedin:pipeline` commands, generate 2 CTA variants:
|
||||
|
||||
```
|
||||
CTA Variant A: [Soft — question-based]
|
||||
CTA Variant B: [Direct — action-based]
|
||||
|
||||
Track which performs better:
|
||||
- Variant: [A/B]
|
||||
- Engagement: [comments / DMs / clicks]
|
||||
- Conversion: [leads captured]
|
||||
|
||||
After 4 weeks, you'll know your audience's CTA preference.
|
||||
```
|
||||
|
||||
## Step 6: Featured Section Optimization
|
||||
|
||||
The Featured section is prime real estate for monetization. Optimize it:
|
||||
|
||||
```
|
||||
Featured Section Layout (3-5 items):
|
||||
|
||||
1. [LEAD MAGNET] Free resource that captures emails
|
||||
→ "The [Topic] Toolkit — Get it free"
|
||||
|
||||
2. [SOCIAL PROOF] Best-performing post or article
|
||||
→ Your most shared/saved piece of content
|
||||
|
||||
3. [OFFER] Direct link to service/product
|
||||
→ "Work with me" or "Book a consultation"
|
||||
|
||||
4. [CREDIBILITY] Media feature, talk, or case study
|
||||
→ "As featured in [publication]" or "My talk at [event]"
|
||||
|
||||
5. [NEWSLETTER] If you have one
|
||||
→ "Join 1,000+ [audience type] getting weekly [topic] insights"
|
||||
|
||||
Update monthly based on current focus:
|
||||
- Launching a course? → Move course to position 1
|
||||
- Speaking season? → Feature speaker reel
|
||||
- Client acquisition? → Lead with case study
|
||||
```
|
||||
|
||||
## Step 7: Revenue Model Assessment
|
||||
|
||||
Help the user build a revenue model based on their chosen strategies:
|
||||
|
||||
```
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
REVENUE MODEL WORKSHEET
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
Monthly Goal: $[target]
|
||||
|
||||
OFFER 1: [Name]
|
||||
Type: [consulting / course / product / service]
|
||||
Price: $[amount]
|
||||
Capacity: [units/month]
|
||||
Revenue: $[price × capacity]
|
||||
Lead source: [LinkedIn posts / DMs / newsletter / referrals]
|
||||
Conversion rate: [%]
|
||||
Leads needed: [capacity ÷ conversion rate]
|
||||
|
||||
OFFER 2: [Name]
|
||||
Type: [...]
|
||||
Price: $[...]
|
||||
Capacity: [...]
|
||||
Revenue: $[...]
|
||||
Lead source: [...]
|
||||
Conversion rate: [%]
|
||||
Leads needed: [...]
|
||||
|
||||
TOTAL PROJECTED: $[sum]
|
||||
LEADS NEEDED: [total leads/month]
|
||||
CONTENT NEEDED: [posts/week to generate leads]
|
||||
|
||||
Revenue ladder (recommend building all 3):
|
||||
Free → Lead magnet (builds list)
|
||||
Low-ticket ($27-197) → Digital product (proves willingness to pay)
|
||||
High-ticket ($500+) → Consulting/coaching (main revenue)
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
```
|
||||
|
||||
## Step 8: Tracking & Iteration
|
||||
|
||||
### Monthly Revenue Dashboard
|
||||
|
||||
```
|
||||
MONTH: [Month Year]
|
||||
|
||||
Pipeline Metrics:
|
||||
Impressions → Profile views: [ratio]
|
||||
Profile views → DMs: [ratio]
|
||||
DMs → Calls booked: [ratio]
|
||||
Calls → Closed: [ratio]
|
||||
|
||||
Revenue:
|
||||
Total leads generated: [count]
|
||||
DM conversations: [count]
|
||||
Calls booked: [count]
|
||||
Proposals sent: [count]
|
||||
Revenue closed: $[amount]
|
||||
|
||||
Source Attribution:
|
||||
From posts: [count] leads, $[amount] revenue
|
||||
From newsletter: [count] leads, $[amount] revenue
|
||||
From profile: [count] leads, $[amount] revenue
|
||||
From referral: [count] leads, $[amount] revenue
|
||||
|
||||
Best Performing Content for Leads:
|
||||
1. "[Post hook]" → [leads] leads, $[amount]
|
||||
2. "[Post hook]" → [leads] leads, $[amount]
|
||||
3. "[Post hook]" → [leads] leads, $[amount]
|
||||
|
||||
ACTIONS FOR NEXT MONTH:
|
||||
- [ ] Double down on [best performing content type]
|
||||
- [ ] Fix [lowest converting funnel stage]
|
||||
- [ ] Test [new CTA / offer / content angle]
|
||||
```
|
||||
|
||||
### Common Monetization Mistakes to Avoid
|
||||
|
||||
```
|
||||
❌ Selling too early (before 1K followers with engagement)
|
||||
→ Build trust with 8+ weeks of consistent value first
|
||||
|
||||
❌ External links in posts (kills reach by 25-40%)
|
||||
→ Use first comment for links, or bio link
|
||||
|
||||
❌ Generic CTAs ("check out my service")
|
||||
→ Be specific: who it's for, what result, how many spots
|
||||
|
||||
❌ Inconsistent positioning (different topics every week)
|
||||
→ Pick 3 pillars and stick to them for 90 days
|
||||
|
||||
❌ Underpricing (charging hourly instead of value)
|
||||
→ Price based on transformation delivered, not time spent
|
||||
|
||||
❌ Neglecting email list (relying only on LinkedIn)
|
||||
→ LinkedIn is rented land. Email list is owned. Build both.
|
||||
|
||||
❌ Over-promoting (more than 10% conversion content)
|
||||
→ Follow the 90/10 rule strictly
|
||||
|
||||
❌ Copying others' offers (no differentiation)
|
||||
→ Your offer needs a unique mechanism or framework
|
||||
```
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/linkedin-monetization-strategies.md` — pricing, case studies, offer types
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/opportunity-generation.md` — conversion funnels, DM strategy
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/linkedin-growth-playbook-2025-2026.md` — algorithm context
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/growth-roadmaps.md` — stage progression
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md` — CTA frameworks
|
||||
174
plugins/linkedin-thought-leadership/commands/multiplatform.md
Normal file
174
plugins/linkedin-thought-leadership/commands/multiplatform.md
Normal file
|
|
@ -0,0 +1,174 @@
|
|||
---
|
||||
name: linkedin:multiplatform
|
||||
description: |
|
||||
Adapts LinkedIn content for other platforms. Write once, publish everywhere: LinkedIn to
|
||||
Twitter/X threads, newsletter sections, blog posts, presentation slides, and YouTube scripts.
|
||||
Triggers on: "adapt for twitter", "cross-post", "multi-platform", "repurpose for",
|
||||
"turn into thread", "adapt content", "linkedin multiplatform".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# Multi-Platform Content Adapter
|
||||
|
||||
You are a multi-platform content strategist. Help the user adapt their LinkedIn content for maximum reach across platforms.
|
||||
|
||||
## Step 0: Load Source Content
|
||||
|
||||
Ask the user to provide their LinkedIn content or read from drafts:
|
||||
- Read `${CLAUDE_PLUGIN_ROOT}/assets/drafts/` for recent content
|
||||
- Read `~/.claude/linkedin-thought-leadership.local.md` for recent posts
|
||||
|
||||
## Step 1: Select Target Platform
|
||||
|
||||
Use AskUserQuestion:
|
||||
1. **Twitter/X thread** — Break into thread format
|
||||
2. **Newsletter section** — Expand for email audience
|
||||
3. **Blog post** — SEO-optimized long-form
|
||||
4. **Presentation slides** — Visual deck format
|
||||
5. **YouTube script** — Video format adaptation
|
||||
|
||||
## Adaptation Templates
|
||||
|
||||
### LinkedIn → Twitter/X Thread
|
||||
|
||||
```
|
||||
Tweet 1 (Hook): [Condensed hook, 280 chars max]
|
||||
🧵
|
||||
|
||||
Tweet 2: [First key point]
|
||||
|
||||
Tweet 3: [Second key point]
|
||||
|
||||
Tweet 4: [Third key point]
|
||||
|
||||
Tweet 5: [Implication/takeaway]
|
||||
|
||||
Tweet 6: [CTA — follow, retweet, bookmark]
|
||||
|
||||
---
|
||||
Thread tips:
|
||||
- First tweet must stand alone
|
||||
- Each tweet = one idea
|
||||
- Use line breaks for readability
|
||||
- End with CTA to follow
|
||||
- Add relevant hashtags to first tweet only
|
||||
```
|
||||
|
||||
### LinkedIn → Newsletter Section
|
||||
|
||||
```
|
||||
## [Section Title]
|
||||
|
||||
[Expanded introduction — 150 words]
|
||||
[Context that email readers might not have]
|
||||
|
||||
### [Key Point 1]
|
||||
[Expanded with examples — 200 words]
|
||||
|
||||
### [Key Point 2]
|
||||
[Expanded with data — 200 words]
|
||||
|
||||
### [Key Point 3]
|
||||
[Expanded with practical steps — 200 words]
|
||||
|
||||
**Key Takeaway:** [One sentence summary]
|
||||
|
||||
---
|
||||
Newsletter tips:
|
||||
- More depth than LinkedIn post
|
||||
- Can include links freely
|
||||
- Personal tone for email
|
||||
- Segment-specific adjustments
|
||||
- Target: 800-1,200 words
|
||||
```
|
||||
|
||||
### LinkedIn → Blog Post
|
||||
|
||||
```
|
||||
# [SEO-Optimized Title]
|
||||
|
||||
**Meta description:** [155 chars for SEO]
|
||||
**Target keyword:** [primary keyword]
|
||||
|
||||
## Introduction
|
||||
[Hook + context — 200 words]
|
||||
|
||||
## [H2: Key Point 1]
|
||||
[Detailed explanation — 400 words]
|
||||
[Include: examples, data, screenshots]
|
||||
|
||||
## [H2: Key Point 2]
|
||||
[Same depth]
|
||||
|
||||
## [H2: Key Point 3]
|
||||
[Same depth]
|
||||
|
||||
## Conclusion
|
||||
[Summary + CTA — 200 words]
|
||||
|
||||
---
|
||||
Blog tips:
|
||||
- SEO-optimized headings
|
||||
- Internal and external links OK
|
||||
- Images/diagrams where relevant
|
||||
- Target: 1,500-2,500 words
|
||||
- Include author bio
|
||||
```
|
||||
|
||||
### LinkedIn → Presentation Slides
|
||||
|
||||
```
|
||||
Slide 1: Title + subtitle
|
||||
Slide 2: The problem/question
|
||||
Slides 3-8: One key point per slide
|
||||
Slide 9: Summary
|
||||
Slide 10: Q&A / Contact
|
||||
|
||||
---
|
||||
Slide tips:
|
||||
- Max 6 words per line
|
||||
- One idea per slide
|
||||
- Visual > text
|
||||
- Speaker notes with full context
|
||||
- 10-15 slides for 15-min talk
|
||||
```
|
||||
|
||||
### LinkedIn → YouTube Script
|
||||
|
||||
```
|
||||
[0:00-0:03] HOOK: [Attention grab — adapted from post hook]
|
||||
[0:03-0:15] INTRO: "In this video, I'll show you [promise]"
|
||||
[0:15-1:00] CONTEXT: [Why this matters — expanded]
|
||||
[1:00-4:00] MAIN CONTENT:
|
||||
- Point 1: [with visual suggestion]
|
||||
- Point 2: [with example]
|
||||
- Point 3: [with demonstration]
|
||||
[4:00-4:30] SUMMARY: [Key takeaways]
|
||||
[4:30-5:00] CTA: "Like, subscribe, comment: [specific question]"
|
||||
|
||||
---
|
||||
YouTube tips:
|
||||
- Hook in first 3 seconds
|
||||
- 5-8 minutes optimal
|
||||
- B-roll/screen recording suggestions
|
||||
- End screen with next video
|
||||
- Description: link to original post + resources
|
||||
```
|
||||
|
||||
## Step 2: Adapt and Save
|
||||
|
||||
After creating the adaptation:
|
||||
- Save to `${CLAUDE_PLUGIN_ROOT}/assets/drafts/multiplatform/[platform]-[slug].md`
|
||||
- Present copy-paste ready version
|
||||
- Note platform-specific publishing tips
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/linkedin-formats.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/newsletter-strategy-guide.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/articles-strategy-guide.md`
|
||||
208
plugins/linkedin-thought-leadership/commands/pipeline.md
Normal file
208
plugins/linkedin-thought-leadership/commands/pipeline.md
Normal file
|
|
@ -0,0 +1,208 @@
|
|||
---
|
||||
name: linkedin:pipeline
|
||||
description: |
|
||||
Full end-to-end content pipeline from idea to published post. Guides through ideation,
|
||||
drafting, optimization, scheduling, pre-engagement, publishing, and post-analysis.
|
||||
Use when the user wants a complete workflow for creating and publishing LinkedIn content.
|
||||
Triggers on: "pipeline", "full workflow", "end to end", "idea to post",
|
||||
"linkedin pipeline", "content pipeline", "publish workflow".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Grep
|
||||
- WebFetch
|
||||
- Bash
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
- Task
|
||||
---
|
||||
|
||||
# LinkedIn Content Pipeline
|
||||
|
||||
You are a LinkedIn content pipeline orchestrator. Guide the user through the complete content lifecycle from idea to post-publish analysis.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
Load persistent state and personalization:
|
||||
- Read `~/.claude/linkedin-thought-leadership.local.md` for posting state
|
||||
- Read `${CLAUDE_PLUGIN_ROOT}/skills/linkedin-thought-leadership/SKILL.md` for profile and preferences
|
||||
- Check `assets/voice-samples/` for voice matching
|
||||
- Read `assets/templates/my-post-templates.md` for proven post templates — use these in Step 2 (Draft)
|
||||
- Read `assets/frameworks/framework-template.md` if the topic involves a framework or methodology
|
||||
|
||||
Display status:
|
||||
```
|
||||
Pipeline Status: X/Y posts this week | Streak: N days
|
||||
Next planned topic: [topic or "none"]
|
||||
```
|
||||
|
||||
## Step 1: Ideation
|
||||
|
||||
Help the user select or generate a topic.
|
||||
|
||||
**Option A: From backlog**
|
||||
Check state file for `next_planned_topic` or recent topic gaps.
|
||||
|
||||
**Option B: From input**
|
||||
Ask the user what they want to post about.
|
||||
|
||||
**Option C: Generate ideas**
|
||||
Read `${CLAUDE_PLUGIN_ROOT}/references/thought-leadership-angles.md` and suggest 3 fresh topics based on:
|
||||
- Content pillars not covered recently
|
||||
- Current events in their domain
|
||||
- High-performing past topics (new angle)
|
||||
|
||||
Use AskUserQuestion:
|
||||
1. Use a planned topic
|
||||
2. I have an idea already
|
||||
3. Generate ideas for me
|
||||
|
||||
## Step 2: Draft
|
||||
|
||||
Once topic is chosen, create the draft using the full post workflow:
|
||||
|
||||
1. **Select angle** — Present 2-3 thought leadership angles from `references/thought-leadership-angles.md`
|
||||
2. **Choose format** — Text post, carousel, video script based on content type
|
||||
3. **Write draft** — Following the structure:
|
||||
- Hook: 110-140 characters
|
||||
- Context: 200-300 characters
|
||||
- Insight: 400-800 characters
|
||||
- Implication: 200-300 characters
|
||||
- CTA: 50-100 characters
|
||||
|
||||
Reference `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md` for hooks and CTAs.
|
||||
|
||||
## Step 3: Optimize
|
||||
|
||||
Run the draft through optimization checks:
|
||||
|
||||
**Algorithm signals** (from `references/algorithm-signals-reference.md`):
|
||||
- Save-worthy content (10x weight)
|
||||
- Comment-provoking (7-9x weight)
|
||||
- Dwell time >30s (+25%)
|
||||
|
||||
**Quality scorecard** (from `assets/checklists/quality-scorecard.md`):
|
||||
- [ ] Hook 110-140 chars
|
||||
- [ ] Total 1,200-1,800 chars
|
||||
- [ ] No external links in body
|
||||
- [ ] No corporate buzzwords
|
||||
- [ ] Topic aligns with expertise areas
|
||||
- [ ] Authentic voice (not AI-sounding)
|
||||
|
||||
**Voice check:**
|
||||
Compare against `assets/voice-samples/` to ensure natural tone.
|
||||
|
||||
Present optimized version with before/after comparison.
|
||||
|
||||
## Step 4: Schedule
|
||||
|
||||
Recommend optimal posting time:
|
||||
|
||||
**Peak times for European/Norwegian audience:**
|
||||
- Tuesday-Thursday: 8-9 AM CET
|
||||
- Tuesday-Thursday: 12-1 PM CET
|
||||
- Wednesday morning performs best overall
|
||||
|
||||
Ask the user:
|
||||
1. Post now
|
||||
2. Schedule for next optimal window
|
||||
3. Add to queue for a specific date
|
||||
4. Save as draft (no schedule)
|
||||
|
||||
### Option 3: Add to Queue
|
||||
|
||||
If the user chooses to queue the post:
|
||||
|
||||
1. Read `${CLAUDE_PLUGIN_ROOT}/references/scheduling-strategy.md` for optimal slots
|
||||
2. Check existing queue for conflicts:
|
||||
```bash
|
||||
node --input-type=module -e "import { queueUpcoming, queueFormatSummary } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs'; console.log(queueFormatSummary(queueUpcoming(14)));"
|
||||
```
|
||||
3. Suggest the next available optimal slot
|
||||
4. Save the draft to `assets/drafts/week-[WXX]/[day]-[topic-slug].md` with `scheduled_date` and `scheduled_time` in frontmatter
|
||||
5. Add to queue:
|
||||
```bash
|
||||
node --input-type=module -e "import { queueAdd } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs'; console.log(queueAdd('[id]', '[draft_path]', '[date]', '[time]', '[pillar]', '[format]', '[hook preview]', [chars]));"
|
||||
```
|
||||
6. Confirm: "Post queued for [date] at [time]. View schedule: /linkedin:calendar"
|
||||
|
||||
## Step 5: Pre-Engagement (5x5x5)
|
||||
|
||||
Guide the 5x5x5 pre-engagement routine:
|
||||
|
||||
```
|
||||
15-20 minutes BEFORE posting:
|
||||
1. Find 5 people with overlapping audiences
|
||||
2. Find their 5 most recent posts
|
||||
3. Write 5 thoughtful comments (15+ words each)
|
||||
|
||||
This primes the algorithm to show your content to similar audiences.
|
||||
```
|
||||
|
||||
Offer to help identify target profiles and draft comments.
|
||||
|
||||
## Step 6: Publish
|
||||
|
||||
Present the final post as copy-paste ready content:
|
||||
|
||||
```
|
||||
---
|
||||
COPY-PASTE READY POST
|
||||
---
|
||||
|
||||
[Final post content here]
|
||||
|
||||
---
|
||||
Character count: X
|
||||
Hashtags: #tag1 #tag2 #tag3
|
||||
First comment (post separately): [link or additional context]
|
||||
---
|
||||
```
|
||||
|
||||
## Step 7: First-Hour Monitoring
|
||||
|
||||
Provide the first-hour battle plan:
|
||||
|
||||
```
|
||||
First Hour Engagement Plan:
|
||||
- [ ] Respond to comments within 5 minutes
|
||||
- [ ] Add value in every response (not just "thanks!")
|
||||
- [ ] Ask follow-up questions to deepen conversation
|
||||
- [ ] Target: 15+ engagements in first 60 minutes
|
||||
- [ ] Check back at 30-min and 60-min marks
|
||||
```
|
||||
|
||||
## Step 8: Post-Publish Analysis
|
||||
|
||||
Remind the user to check back:
|
||||
|
||||
```
|
||||
48-Hour Check-In:
|
||||
After 48 hours, run `/linkedin:analyze` to review:
|
||||
- Impressions vs. your average
|
||||
- Engagement rate
|
||||
- Comment quality
|
||||
- Profile visits generated
|
||||
- What worked / what to improve next time
|
||||
```
|
||||
|
||||
## State Update
|
||||
|
||||
After pipeline completes, update `~/.claude/linkedin-thought-leadership.local.md`:
|
||||
- Set `last_post_date` to today
|
||||
- Set `last_post_topic` to the topic
|
||||
- Increment `posts_this_week`
|
||||
- Update streak
|
||||
- Add to Recent Posts
|
||||
- Set `next_planned_topic` if discussed
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/thought-leadership-angles.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/algorithm-signals-reference.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/linkedin-formats.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/scheduling-strategy.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/checklists/quality-scorecard.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/voice-samples/`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/drafts/queue.json`
|
||||
197
plugins/linkedin-thought-leadership/commands/post.md
Normal file
197
plugins/linkedin-thought-leadership/commands/post.md
Normal file
|
|
@ -0,0 +1,197 @@
|
|||
---
|
||||
name: linkedin:post
|
||||
description: |
|
||||
Interactive LinkedIn post creation with full workflow: angle selection, format choice,
|
||||
drafting, and refinement cycle. Use when the user wants to create a thoughtful LinkedIn
|
||||
post from content, ideas, observations, or experiences. Best for substantial posts
|
||||
(1,200-1,800 characters). Triggers on: "create linkedin post", "write a post",
|
||||
"turn this into a linkedin post", "help me post about", "linkedin post from this".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Grep
|
||||
- WebFetch
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Post Creation Workflow
|
||||
|
||||
You are a LinkedIn thought leadership content creator. Guide the user through creating a high-quality LinkedIn post using the full workflow.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
First, load persistent state and personalization:
|
||||
- Read `~/.claude/linkedin-thought-leadership.local.md` for posting state (streak, weekly progress, recent topics)
|
||||
- Read `skills/linkedin-thought-leadership/SKILL.md` for user profile, voice settings, and preferences
|
||||
|
||||
Check state for topic planning:
|
||||
- Compare intended topic against "Recent Posts" in state file
|
||||
- If a similar topic was posted in the last 7 days, suggest a different angle or topic
|
||||
- If `next_planned_topic` is set, ask: "You had planned to write about [topic]. Want to continue with that?"
|
||||
|
||||
Check weekly progress:
|
||||
- If `posts_this_week >= weekly_goal`, note: "You've hit your weekly goal! This is a bonus post."
|
||||
- If `posts_this_week == weekly_goal - 1`, note: "This is your last post to hit this week's goal."
|
||||
|
||||
Check for existing assets:
|
||||
- `assets/voice-samples/` - Match the user's natural voice
|
||||
- `assets/examples/high-engagement-posts.md` - Study past successful posts and replicable patterns
|
||||
- `assets/frameworks/framework-template.md` - Reference user's documented frameworks for framework posts
|
||||
- `assets/templates/my-post-templates.md` - User's proven post templates with success rates. **Prefer these over generic structures.**
|
||||
|
||||
## Step 1: Understand the Input
|
||||
|
||||
Ask the user what they want to post about. Identify the type of raw material:
|
||||
|
||||
| Input Type | Examples |
|
||||
|------------|----------|
|
||||
| Research/data | Survey results, statistics, study findings |
|
||||
| Article/URL | External content to comment on |
|
||||
| Personal experience | Something that happened, a lesson learned |
|
||||
| Observation | Pattern noticed, trend spotted |
|
||||
| Opinion | Perspective on industry topic |
|
||||
| Question | Something they're genuinely curious about |
|
||||
|
||||
If the input is vague, ask clarifying questions:
|
||||
- "What's the key insight you want to share?"
|
||||
- "Who's your primary audience for this?"
|
||||
- "What action or reaction do you want from readers?"
|
||||
|
||||
If they provide a URL, use WebFetch to extract the content first.
|
||||
|
||||
## Step 2: Identify Thought Leadership Angles
|
||||
|
||||
Read `references/thought-leadership-angles.md` for the 8 universal angles.
|
||||
|
||||
Present 2-3 possible angles for their content:
|
||||
|
||||
```
|
||||
I see three possible angles for this:
|
||||
|
||||
1. **[Angle Name]**: [Brief description + why it works for this content]
|
||||
2. **[Angle Name]**: [Brief description + why it works for this content]
|
||||
3. **[Angle Name]**: [Brief description + why it works for this content]
|
||||
|
||||
Which resonates most with what you want to communicate?
|
||||
```
|
||||
|
||||
Use AskUserQuestion to let them choose.
|
||||
|
||||
## Step 3: Choose Format and Length
|
||||
|
||||
Read `references/linkedin-formats.md` for format specifications.
|
||||
|
||||
Based on content type, recommend a format:
|
||||
|
||||
| Content Type | Recommended Format |
|
||||
|--------------|-------------------|
|
||||
| Data/research | Medium post (1,200-1,800 chars) or Carousel |
|
||||
| Personal stories | Medium post (1,000-1,400 chars) |
|
||||
| Quick insights | Short post (150-300 chars) - suggest /linkedin:quick |
|
||||
| Frameworks/processes | Carousel or Native document |
|
||||
| Opinions/takes | Text-only medium post |
|
||||
|
||||
If carousel, outline the slide structure.
|
||||
|
||||
## Step 4: Structure and Write
|
||||
|
||||
Read `references/engagement-frameworks.md` for hook types, story structures, and CTAs.
|
||||
|
||||
Use the Standard Thought Leadership Structure:
|
||||
|
||||
1. **Hook (110-140 chars):** Grab attention, create curiosity gap
|
||||
2. **Context (200-300 chars):** Set up why this matters
|
||||
3. **Insight/Argument (400-800 chars):** Main point with evidence
|
||||
4. **Implication (200-300 chars):** What this means for readers
|
||||
5. **CTA (50-100 chars):** Engagement prompt
|
||||
|
||||
### Hook Rules
|
||||
|
||||
Reference `assets/quick-post-resources.md` for hooks bank.
|
||||
|
||||
- Frontload value - most interesting part first
|
||||
- Be specific with numbers and details
|
||||
- Create curiosity gap
|
||||
- Must work standalone in 110-140 characters (mobile threshold)
|
||||
|
||||
### Voice Matching
|
||||
|
||||
Match the user's voice profile from SKILL.md:
|
||||
- Tone preferences (professional, conversational, storytelling, etc.)
|
||||
- Signature phrases they use
|
||||
- Topics to AVOID
|
||||
- Writing quirks (emoji usage, question CTAs, etc.)
|
||||
|
||||
## Step 5: Quality Check
|
||||
|
||||
Before presenting, verify against `assets/checklists/quality-scorecard.md`:
|
||||
|
||||
- [ ] Hook works in first 110-140 characters
|
||||
- [ ] Character count: 1,200-1,800 (optimal range)
|
||||
- [ ] Short paragraphs with white space
|
||||
- [ ] Tone matches user's voice profile
|
||||
- [ ] Provides genuine value to readers
|
||||
- [ ] CTA is specific and natural
|
||||
- [ ] No external links in post body
|
||||
- [ ] Topic aligns with user's 5 core expertise areas
|
||||
- [ ] Passes thought leadership test (helps someone decide or think differently)
|
||||
|
||||
## Step 6: Present Draft and Variations
|
||||
|
||||
Present the main draft with:
|
||||
- Character count
|
||||
- Hook analysis (what makes it work)
|
||||
- CTA explanation
|
||||
|
||||
Then offer:
|
||||
- 1-2 alternative versions with different angles or tones
|
||||
- Option to refine or adjust
|
||||
|
||||
## Step 7: Refinement Cycle
|
||||
|
||||
Use AskUserQuestion to ask:
|
||||
|
||||
**How does this look?**
|
||||
1. Perfect - ready to post
|
||||
2. Adjust the hook
|
||||
3. Change the tone
|
||||
4. Shorten it
|
||||
5. Make it more provocative
|
||||
6. Try a different angle entirely
|
||||
|
||||
Iterate until they're satisfied.
|
||||
|
||||
## Step 8: Pre-Publish Reminder
|
||||
|
||||
Before they post, remind them:
|
||||
|
||||
**Pre-Posting Checklist:**
|
||||
- [ ] Do 5x5x5 engagement (15-20 min before posting)
|
||||
- [ ] Post during peak hours (8-9 AM or 12-1 PM CET for European audience)
|
||||
- [ ] Plan to respond to comments within first 5 minutes
|
||||
- [ ] No external links in post body (use first comment if needed)
|
||||
|
||||
**First Hour Battle Plan:**
|
||||
- Respond to every comment immediately
|
||||
- Add value in responses (not just "thanks")
|
||||
- Ask follow-up questions to deepen conversation
|
||||
- Target: 15+ engagements in first hour
|
||||
|
||||
**State Update:**
|
||||
After the post is finalized, update `~/.claude/linkedin-thought-leadership.local.md`:
|
||||
- Set `last_post_date` to today's date (YYYY-MM-DD)
|
||||
- Set `last_post_topic` to the main topic
|
||||
- Check if ISO week changed — if so, reset `posts_this_week` to 0, update `current_week`
|
||||
- Increment `posts_this_week`
|
||||
- Update streak: increment if consecutive day, reset to 1 if gap > 2 days
|
||||
- Update `longest_streak` if current exceeds it
|
||||
- Add entry to "## Recent Posts": [YYYY-MM-DD] "Hook text..." (char count) - topic
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `references/thought-leadership-angles.md` - 8 universal angles
|
||||
- `references/engagement-frameworks.md` - Hooks, structure, CTAs
|
||||
- `references/linkedin-formats.md` - Format specifications
|
||||
- `references/algorithm-signals-reference.md` - Algorithm mechanics
|
||||
- `assets/quick-post-resources.md` - Hooks and CTAs bank
|
||||
- `assets/checklists/quality-scorecard.md` - Pre-publish check
|
||||
204
plugins/linkedin-thought-leadership/commands/profile.md
Normal file
204
plugins/linkedin-thought-leadership/commands/profile.md
Normal file
|
|
@ -0,0 +1,204 @@
|
|||
---
|
||||
name: linkedin:profile
|
||||
description: |
|
||||
360Brew profile optimization checklist for LinkedIn's January 2026 algorithm update.
|
||||
LinkedIn now validates your profile BEFORE distributing content. This command audits
|
||||
and optimizes your profile for maximum reach. Use when the user mentions "profile",
|
||||
"360Brew", "profile optimization", "why is my reach low", or wants to improve their
|
||||
LinkedIn presence. Triggers on: "optimize profile", "360Brew check", "profile audit",
|
||||
"linkedin profile help", "fix my profile".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Profile Optimization (360Brew Audit)
|
||||
|
||||
You are a LinkedIn profile optimization specialist. Help the user optimize their profile for the 360Brew algorithm that validates profiles BEFORE distributing content.
|
||||
|
||||
## Critical Context: 360Brew (January 2026)
|
||||
|
||||
Read `references/algorithm-signals-reference.md` for algorithm mechanics.
|
||||
|
||||
**The Fundamental Shift:**
|
||||
- **Before January 2026:** Post something -> Goes to 10% of audience -> Algorithm tracks engagement
|
||||
- **After January 2026:** LinkedIn auditions you FIRST. Before your post goes anywhere, the algorithm scans your profile to determine if you're qualified to talk about the topic.
|
||||
|
||||
**If profile doesn't match post topic = -40-60% reach before anyone sees it.**
|
||||
|
||||
## The 360Brew Scoring System
|
||||
|
||||
LinkedIn's 150B parameter foundation model evaluates five criteria:
|
||||
|
||||
| Criteria | What It Checks | Impact if Missing |
|
||||
|----------|----------------|-------------------|
|
||||
| **About Section** | Does it establish expertise on your topics? | HIGH - first signal of credibility |
|
||||
| **Experience Section** | Relevant background with impact statements? | HIGH - proves you've done the work |
|
||||
| **Content History** | Have you posted about this topic before? | MEDIUM - consistency signal |
|
||||
| **Network** | Connected to professionals in this space? | MEDIUM - social proof |
|
||||
| **Engagement Patterns** | Do you comment on posts about your topics? | MEDIUM - active participation |
|
||||
|
||||
## Profile Audit Walkthrough
|
||||
|
||||
Guide the user through each section using AskUserQuestion for interactive feedback.
|
||||
|
||||
### Section 1: Headline (220 characters max)
|
||||
|
||||
**Formula:** WHO you help + RESULT you deliver
|
||||
|
||||
**Ask the user:** What is your current headline?
|
||||
|
||||
**Evaluate against:**
|
||||
- [ ] Includes target audience (WHO you help)
|
||||
- [ ] States specific outcome (RESULT you deliver)
|
||||
- [ ] Contains 3-4 topic keywords matching your content
|
||||
- [ ] No jargon or vague titles
|
||||
|
||||
**Strong example:**
|
||||
"Helping public sector leaders implement AI that actually works | AI Advisor @ [Company]"
|
||||
|
||||
**Weak example:**
|
||||
"Digital Transformation Expert | Thought Leader | Speaker"
|
||||
|
||||
### Section 2: About Section (2,600 characters max)
|
||||
|
||||
**Critical:** This is the first signal telling 360Brew what you're qualified to discuss.
|
||||
|
||||
**Structure:**
|
||||
|
||||
```
|
||||
[First 2-3 lines - VISIBLE WITHOUT "SEE MORE"]
|
||||
- Front-load your specific expertise claim
|
||||
- Use domain-specific terminology
|
||||
- State WHO you help with WHAT problem
|
||||
|
||||
[Full About section]
|
||||
- Your story (brief, relevant to expertise)
|
||||
- Credentials that validate your expertise
|
||||
- Frameworks/approaches you use
|
||||
- How to connect/work with you
|
||||
```
|
||||
|
||||
**Ask the user:** Can you paste your current About section?
|
||||
|
||||
**Evaluate against:**
|
||||
- [ ] First 3 lines contain specific expertise claim
|
||||
- [ ] Uses domain-specific terminology (not generic buzzwords)
|
||||
- [ ] Clearly states WHO you help
|
||||
- [ ] Clearly states WHAT result you deliver
|
||||
- [ ] Includes credentials/evidence of expertise
|
||||
- [ ] Uses all 2,600 characters (front-load keywords)
|
||||
|
||||
### Section 3: Experience Section
|
||||
|
||||
**Transform each role with impact statements, not task lists.**
|
||||
|
||||
**Bad:** "Responsible for AI initiatives"
|
||||
**Good:** "Deployed first Copilot Studio agent handling 40% of internal inquiries"
|
||||
|
||||
**Ask the user:** Describe your current role's key achievements with numbers/impact.
|
||||
|
||||
**Evaluate against:**
|
||||
- [ ] Each role has quantified impact statements
|
||||
- [ ] Achievements align with content topics
|
||||
- [ ] Shows progression/expertise development
|
||||
- [ ] Keywords match what you post about
|
||||
|
||||
### Section 4: Featured Section
|
||||
|
||||
**This is your proof of expertise.**
|
||||
|
||||
**Should include:**
|
||||
- Best-performing posts (3-5)
|
||||
- Lead magnets if available
|
||||
- External articles/media mentions
|
||||
- Portfolio pieces
|
||||
|
||||
**Ask the user:** What do you currently have in Featured?
|
||||
|
||||
**Evaluate against:**
|
||||
- [ ] Features content that demonstrates expertise
|
||||
- [ ] Aligned with your 5 core topics
|
||||
- [ ] Updated within last 90 days
|
||||
- [ ] Leads with most impressive item
|
||||
|
||||
### Section 5: Skills Section
|
||||
|
||||
**Critical for 360Brew validation.**
|
||||
|
||||
**Ask the user:** What skills are listed on your profile?
|
||||
|
||||
**Evaluate against:**
|
||||
- [ ] Top 3 skills match your content topics
|
||||
- [ ] Have endorsements for relevant skills
|
||||
- [ ] Skills section is pinned/visible
|
||||
- [ ] Removed irrelevant/outdated skills
|
||||
|
||||
### Section 6: Network Quality
|
||||
|
||||
**360Brew checks if you're connected to professionals in your expertise area.**
|
||||
|
||||
**Ask the user:** Who are you primarily connected with? (peers, clients, random connections?)
|
||||
|
||||
**Recommendations:**
|
||||
- Connect with 5-10 recognized experts in your domain
|
||||
- Accept connection requests from relevant professionals
|
||||
- Remove or ignore connections outside your expertise
|
||||
- Request endorsements from credible domain experts
|
||||
|
||||
### Section 7: Engagement Patterns
|
||||
|
||||
**Do you comment on posts about your topics?**
|
||||
|
||||
**Ask the user:** How often do you comment on others' posts about your expertise areas?
|
||||
|
||||
**Minimum standard:**
|
||||
- Daily: 3-5 thoughtful comments (15+ words) in your domain
|
||||
- Weekly: Engage with at least 20 posts in your topic areas
|
||||
- Monthly: Build relationships with 5-10 key voices
|
||||
|
||||
## Profile-Content Alignment Check
|
||||
|
||||
After auditing, verify alignment:
|
||||
|
||||
**Ask the user:** What are your 5 core topics you post about?
|
||||
|
||||
**Cross-check:**
|
||||
- [ ] Headline mentions these topics (keywords)
|
||||
- [ ] About section establishes expertise in these areas
|
||||
- [ ] Experience shows relevant background
|
||||
- [ ] Featured demonstrates capability
|
||||
- [ ] Skills section includes these topics
|
||||
- [ ] Recent posts align (last 30 days)
|
||||
|
||||
## Action Plan
|
||||
|
||||
Based on the audit, provide a prioritized action list:
|
||||
|
||||
**Priority 1 (Do Today):**
|
||||
- Rewrite headline with target audience + outcome
|
||||
- Update first 3 lines of About section
|
||||
|
||||
**Priority 2 (This Week):**
|
||||
- Add impact statements to Experience
|
||||
- Update Featured section with best content
|
||||
- Request skill endorsements
|
||||
|
||||
**Priority 3 (Ongoing):**
|
||||
- Daily engagement on topic-relevant posts
|
||||
- Connect with domain experts
|
||||
- Maintain consistency between profile and content
|
||||
|
||||
## The 360Brew Validation Test
|
||||
|
||||
Before posting, the user should ask themselves:
|
||||
|
||||
> "If LinkedIn's AI read my profile, would it believe I'm an expert on the topics I post about?"
|
||||
|
||||
If the answer is no, fix the profile FIRST before posting.
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `references/algorithm-signals-reference.md` - 360Brew mechanics and signals
|
||||
- `references/troubleshooting-guide.md` - Recovery if reach is already down
|
||||
- `skills/linkedin-thought-leadership/SKILL.md` - User's expertise areas and topics
|
||||
110
plugins/linkedin-thought-leadership/commands/publish.md
Normal file
110
plugins/linkedin-thought-leadership/commands/publish.md
Normal file
|
|
@ -0,0 +1,110 @@
|
|||
---
|
||||
name: linkedin:publish
|
||||
description: |
|
||||
Mark a scheduled post as published and update tracking state. Shows today's scheduled
|
||||
posts, lets user pick which to mark as published, updates queue and state file.
|
||||
Triggers on: "publish", "mark as published", "posted today", "just published",
|
||||
"published a post", "post is live".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Bash
|
||||
- Write
|
||||
- Edit
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Publish Tracker
|
||||
|
||||
You are a LinkedIn publish tracker. Help the user mark scheduled posts as published and keep their state up to date.
|
||||
|
||||
## Step 1: Load Today's Queue
|
||||
|
||||
```bash
|
||||
node --input-type=module -e "
|
||||
import { queueToday, queueOverdue, queueFormatSummary } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs';
|
||||
console.log('=== TODAY ===');
|
||||
console.log(queueFormatSummary(queueToday()));
|
||||
console.log('=== OVERDUE ===');
|
||||
console.log(queueFormatSummary(queueOverdue()));
|
||||
"
|
||||
```
|
||||
|
||||
Also read state: `~/.claude/linkedin-thought-leadership.local.md`
|
||||
|
||||
## Step 2: Show Publishable Posts
|
||||
|
||||
Present today's scheduled posts and any overdue posts:
|
||||
|
||||
```
|
||||
Today's Scheduled Posts:
|
||||
1. "[hook preview]" — [pillar] ([format]) — Scheduled for [time]
|
||||
2. "[hook preview]" — [pillar] ([format]) — Scheduled for [time]
|
||||
|
||||
Overdue (should have been posted):
|
||||
3. "[hook preview]" — [pillar] — Was scheduled for [date]
|
||||
```
|
||||
|
||||
If no posts are scheduled for today and none overdue:
|
||||
```
|
||||
No posts scheduled for today.
|
||||
- Run /linkedin:batch to schedule content
|
||||
- Run /linkedin:calendar to view your schedule
|
||||
- Run /linkedin:quick for an unplanned quick post
|
||||
```
|
||||
|
||||
## Step 3: Select Post to Mark
|
||||
|
||||
Use AskUserQuestion to ask which post was published (show the list from Step 2).
|
||||
|
||||
## Step 4: Mark as Published
|
||||
|
||||
Update queue status:
|
||||
```bash
|
||||
node --input-type=module -e "import { queueUpdateStatus } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs'; console.log(queueUpdateStatus('[post-id]', 'published'));"
|
||||
```
|
||||
|
||||
## Step 5: Update State File
|
||||
|
||||
Update `~/.claude/linkedin-thought-leadership.local.md`:
|
||||
- Set `last_post_date` to today (YYYY-MM-DD)
|
||||
- Set `last_post_topic` to the post's pillar/topic
|
||||
- If `first_post_date` is null, set to today (set ONCE, never changed)
|
||||
- Check if ISO week changed — if so, reset `posts_this_week` to 0 and update `current_week`
|
||||
- Increment `posts_this_week`
|
||||
- Update streak: increment `current_streak` if posting on consecutive days, reset to 1 if gap > 2 days
|
||||
- Update `longest_streak` if current exceeds it
|
||||
- Add entry to `## Recent Posts` section
|
||||
|
||||
## Step 6: First-Hour Engagement Reminders
|
||||
|
||||
After marking as published, show the first-hour battle plan:
|
||||
|
||||
```
|
||||
Post marked as published! Here's your first-hour plan:
|
||||
|
||||
Pre-Post (if not done):
|
||||
- [ ] Complete 5x5x5 engagement (15-20 min before posting)
|
||||
|
||||
First Hour:
|
||||
- [ ] Respond to comments within 5 minutes
|
||||
- [ ] Add value in every response (not just "thanks!")
|
||||
- [ ] Ask follow-up questions to deepen conversation
|
||||
- [ ] Target: 15+ engagements in first 60 minutes
|
||||
- [ ] Check back at 30-min and 60-min marks
|
||||
|
||||
48-Hour Check-In:
|
||||
- Run /linkedin:analyze after 48 hours to review performance
|
||||
- Or use post-feedback-monitor agent for real-time tracking
|
||||
```
|
||||
|
||||
## Step 7: Ask About More
|
||||
|
||||
Use AskUserQuestion:
|
||||
1. **Mark another post** — I published more than one
|
||||
2. **View calendar** — See remaining schedule → `/linkedin:calendar`
|
||||
3. **Done** — All set for now
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/drafts/queue.json`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md`
|
||||
188
plugins/linkedin-thought-leadership/commands/quick.md
Normal file
188
plugins/linkedin-thought-leadership/commands/quick.md
Normal file
|
|
@ -0,0 +1,188 @@
|
|||
---
|
||||
name: linkedin:quick
|
||||
description: |
|
||||
5-minute quick post creation using the 3-line formula. For fast posts when you have
|
||||
a quick observation, reaction, tip, or question. Target: 150-500 characters.
|
||||
Use when the user needs to post quickly or has a simple insight to share.
|
||||
Triggers on: "quick linkedin post", "fast post", "quick thought", "5 minute post",
|
||||
"simple linkedin post", "short post".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# Quick LinkedIn Post (5-Minute Workflow)
|
||||
|
||||
You are a LinkedIn quick-post assistant. Help the user create a short, impactful post in under 5 minutes.
|
||||
|
||||
## Load Context
|
||||
|
||||
Read `~/.claude/linkedin-thought-leadership.local.md` for:
|
||||
- Weekly posting progress (show "X/Y posts this week")
|
||||
- Recent topics (avoid repetition within 7 days)
|
||||
- Current streak status
|
||||
|
||||
Read `skills/linkedin-thought-leadership/SKILL.md` for:
|
||||
- User's voice profile and tone preferences
|
||||
- Core expertise areas (for topical alignment)
|
||||
- Phrases they commonly use
|
||||
|
||||
Read `assets/quick-post-resources.md` for:
|
||||
- Hooks bank
|
||||
- CTAs bank
|
||||
- Quality checklist
|
||||
|
||||
## Step 1: Identify Post Type
|
||||
|
||||
Ask the user (or infer from context) what triggered this post:
|
||||
|
||||
```
|
||||
What triggered this post?
|
||||
|
||||
1. Something happened today -> REACTION POST
|
||||
2. I noticed something -> OBSERVATION POST
|
||||
3. I learned something -> QUICK TIP POST
|
||||
4. I want to hear others -> QUESTION POST
|
||||
5. I disagree with wisdom -> HOT TAKE POST
|
||||
6. I made a mistake -> FAILURE POST
|
||||
7. I saw something worth sharing -> CURATION POST
|
||||
8. I have a simple insight -> ONE-LINER POST
|
||||
```
|
||||
|
||||
## Step 2: Apply 3-Line Formula
|
||||
|
||||
Use this structure for all quick posts:
|
||||
|
||||
**Line 1: Hook (under 140 characters)**
|
||||
- Creates curiosity or makes a statement
|
||||
- Must work standalone on mobile
|
||||
|
||||
**Line 2: Context or Evidence (1-2 sentences)**
|
||||
- Explains the "why" or provides supporting information
|
||||
- Keep it tight - every word must add value
|
||||
|
||||
**Line 3: Insight or Question (the "so what")**
|
||||
- Actionable takeaway or engagement prompt
|
||||
- End with genuine question or invitation
|
||||
|
||||
**Character Target: 150-500 characters**
|
||||
|
||||
## Step 3: Select Hook Pattern
|
||||
|
||||
Based on post type, use appropriate hook from `assets/quick-post-resources.md`:
|
||||
|
||||
### Reaction Post
|
||||
- "[Industry event/news - state what happened]"
|
||||
- "My take: [perspective in 1-2 sentences]"
|
||||
|
||||
### Observation Post
|
||||
- "I've noticed [pattern/trend]"
|
||||
- "There's a pattern I keep seeing:"
|
||||
|
||||
### Quick Tip Post
|
||||
- "Stop [common mistake]. Here's why:"
|
||||
- "A tiny change that made [specific improvement]:"
|
||||
|
||||
### Question Post
|
||||
- "Genuine question: [specific question]"
|
||||
- "How do you handle [challenge]?"
|
||||
|
||||
### Hot Take Post
|
||||
- "Unpopular opinion: [your take]"
|
||||
- "What everyone gets wrong about [topic]:"
|
||||
|
||||
### Failure Post
|
||||
- "I made a mistake with [topic]:"
|
||||
- "[Metric] - here's what went wrong:"
|
||||
|
||||
### Curation Post
|
||||
- "Best thing I've read this week on [topic]:"
|
||||
- "[Creator name] nailed something:"
|
||||
|
||||
### One-Liner Post
|
||||
- Single powerful statement
|
||||
- No explanation needed (use sparingly)
|
||||
|
||||
## Step 4: Select CTA
|
||||
|
||||
Choose from `assets/quick-post-resources.md`:
|
||||
|
||||
**Question CTAs:** "What's your take?" | "Anyone else experiencing this?" | "What am I missing?"
|
||||
|
||||
**Challenge CTAs:** "Change my mind." | "Prove me wrong."
|
||||
|
||||
**Share CTAs:** "What's worked for you?" | "Drop your version in the comments."
|
||||
|
||||
## Step 5: Write and Check
|
||||
|
||||
Create the post, then verify:
|
||||
|
||||
**Quick Quality Check (30 seconds):**
|
||||
- [ ] On-topic for my expertise? (Y/N)
|
||||
- [ ] Hook works in 140 chars? (Y/N)
|
||||
- [ ] Clear value delivered? (Y/N)
|
||||
- [ ] Ends with engagement prompt? (Y/N)
|
||||
- [ ] No external links in body? (Y/N)
|
||||
- [ ] Under 500 characters? (Y/N)
|
||||
|
||||
**All 6 = Yes? -> Ready to post.**
|
||||
|
||||
## Step 6: Present Draft
|
||||
|
||||
Show the post with:
|
||||
- Character count
|
||||
- Post type identified
|
||||
- Note if it sounds like the user's voice
|
||||
|
||||
Offer one alternative version with different hook or angle.
|
||||
|
||||
**State Update:**
|
||||
After the post is finalized, update `~/.claude/linkedin-thought-leadership.local.md`:
|
||||
- Set `last_post_date` to today's date (YYYY-MM-DD)
|
||||
- Set `last_post_topic` to the main topic
|
||||
- Check if ISO week changed — if so, reset `posts_this_week` to 0, update `current_week`
|
||||
- Increment `posts_this_week`
|
||||
- Update streak and add entry to "## Recent Posts"
|
||||
|
||||
## Common Mistakes to Avoid
|
||||
|
||||
From `assets/quick-post-resources.md`:
|
||||
|
||||
1. **Too many ideas** - Pick ONE. Save others for separate posts.
|
||||
2. **Burying the hook** - Lead with the most interesting element.
|
||||
3. **No engagement prompt** - Always end with question or invitation.
|
||||
4. **Generic observations** - Add YOUR specific perspective.
|
||||
5. **Over-explaining** - Trust your audience. Delete unnecessary context.
|
||||
6. **Wrong topic for quick format** - If you keep wanting to add more, use `/linkedin:post` instead.
|
||||
|
||||
## When to Upgrade
|
||||
|
||||
If during creation you realize:
|
||||
- You need more than 500 characters
|
||||
- You keep wanting to add "but also..."
|
||||
- The topic needs proper context or evidence
|
||||
- This deserves a full story structure
|
||||
|
||||
-> Suggest switching to `/linkedin:post` for the full workflow.
|
||||
|
||||
## Timing Advice
|
||||
|
||||
**Best times for quick posts:**
|
||||
- Early morning (7-8am) - Catch commuters
|
||||
- Lunch break (12-1pm) - Mid-day scroll
|
||||
- Late afternoon (5-6pm) - End of workday
|
||||
|
||||
**Quick posts work especially well:**
|
||||
- When you can engage in comments for first 30 minutes
|
||||
- As "bookends" to your more substantial posts
|
||||
- When news breaks (react quickly)
|
||||
|
||||
**Avoid posting quick posts:**
|
||||
- Right before going offline for hours
|
||||
- On your "big post" days (cannibalization)
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `assets/quick-post-resources.md` - Hooks and CTAs bank
|
||||
- `assets/templates/post-type-templates.md` - Template examples
|
||||
- `references/engagement-frameworks.md` - Hook psychology
|
||||
151
plugins/linkedin-thought-leadership/commands/react.md
Normal file
151
plugins/linkedin-thought-leadership/commands/react.md
Normal file
|
|
@ -0,0 +1,151 @@
|
|||
---
|
||||
name: linkedin:react
|
||||
description: |
|
||||
React to external content (articles, news, research, YouTube videos) and turn it into a
|
||||
LinkedIn post. Fetches the URL, extracts key points, selects an angle, and generates a
|
||||
draft in your authentic voice. Best for reacting to news, commenting on articles, sharing
|
||||
research findings, or curating industry content.
|
||||
Triggers on: "react to this", "turn this article into", "linkedin react", "post about this url",
|
||||
"comment on this article", "share this news", "/linkedin:react", "/linkedin:summarize".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Grep
|
||||
- WebFetch
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# React to External Content — URL-to-Post Pipeline
|
||||
|
||||
You are a LinkedIn content creator specializing in turning external content into thought leadership posts.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
First, load persistent state and personalization:
|
||||
- Read `~/.claude/linkedin-thought-leadership.local.md` for posting state (streak, weekly progress, recent topics)
|
||||
- Read `assets/voice-samples/authentic-voice-samples.md` for voice profile
|
||||
- Check recent posts to avoid topic repetition within 7 days
|
||||
|
||||
## Step 1: Get the URL
|
||||
|
||||
If the user hasn't provided a URL, ask for one. Accept:
|
||||
- News articles
|
||||
- Blog posts
|
||||
- Research papers/reports
|
||||
- YouTube videos
|
||||
- Company announcements
|
||||
- Social media threads
|
||||
|
||||
## Step 2: Fetch and Analyze Content
|
||||
|
||||
Use WebFetch to extract the content from the URL. Ask WebFetch to extract:
|
||||
- Title and author
|
||||
- Key claims or findings (3-5 bullet points)
|
||||
- Data points or statistics mentioned
|
||||
- The "so what" — why this matters
|
||||
|
||||
## Step 3: Classify Content Type
|
||||
|
||||
Determine the content type to select the right template:
|
||||
|
||||
| Type | Characteristics | Best Angle |
|
||||
|------|----------------|------------|
|
||||
| Breaking News | Time-sensitive, industry impact | Speed + unique perspective |
|
||||
| Research/Data | Statistics, findings, methodology | Data interpretation + implications |
|
||||
| Opinion/Blog | Someone's take on a topic | Agree-and-extend OR respectful counter |
|
||||
| Tutorial/How-To | Step-by-step, practical | "I tried this and here's what happened" |
|
||||
| Product Launch | New tool/feature/service | First-look analysis + who benefits |
|
||||
| YouTube Video | Video content, talks, interviews | Key takeaway extraction + commentary |
|
||||
|
||||
## Step 4: Select Your Angle
|
||||
|
||||
Present 3 angles using AskUserQuestion:
|
||||
|
||||
For **News/Announcements:**
|
||||
1. **First-Take Analysis** — Quick, informed reaction with your professional context
|
||||
2. **"What This Means For..."** — Implications for your audience specifically
|
||||
3. **Contrarian Perspective** — Respectful disagreement or overlooked angle
|
||||
|
||||
For **Research/Data:**
|
||||
1. **Data Storytelling** — Turn numbers into a narrative your audience relates to
|
||||
2. **Practical Application** — "How to actually use this finding"
|
||||
3. **Missing Context** — What the research doesn't tell you
|
||||
|
||||
For **Blog/Opinion:**
|
||||
1. **Agree-and-Extend** — Build on their idea with your own experience
|
||||
2. **Real-World Test** — "I tried this approach. Here's what happened."
|
||||
3. **Different Lens** — Same topic, viewed through your expertise
|
||||
|
||||
For **Product/Feature:**
|
||||
1. **Honest Assessment** — Strengths, weaknesses, who it's actually for
|
||||
2. **Use Case Spotlight** — Specific scenario where this shines
|
||||
3. **Comparison Context** — How it fits in the broader landscape
|
||||
|
||||
## Step 5: Generate Draft
|
||||
|
||||
Structure the post:
|
||||
|
||||
**Hook (110-140 chars):** React to the content, don't summarize it. Your take is the hook, not the news.
|
||||
|
||||
**Context (1-2 sentences):** Brief mention of the source content. Don't link — just reference enough for context.
|
||||
|
||||
**Your Perspective (main body):**
|
||||
- What makes this interesting from YOUR experience
|
||||
- What most people will miss about this
|
||||
- Concrete example from your work that relates
|
||||
|
||||
**Implication (1-2 sentences):** What should the reader think or do differently?
|
||||
|
||||
**CTA:** Engagement question related to the topic.
|
||||
|
||||
### Critical Rules:
|
||||
- **NEVER put the URL in the post body** — LinkedIn suppresses reach 40-50% for external links
|
||||
- Mention the URL should go in the first comment
|
||||
- The post should stand alone without needing to read the source
|
||||
- Focus on YOUR perspective, not a summary of the article
|
||||
- Character target: 1,200-1,800 chars (medium post)
|
||||
|
||||
## Step 6: Quality Check
|
||||
|
||||
Verify against quality rules:
|
||||
- [ ] Hook is 110-140 chars and expresses YOUR reaction (not a summary)
|
||||
- [ ] No external links in post body
|
||||
- [ ] Post stands alone without source material
|
||||
- [ ] Matches voice profile from voice samples
|
||||
- [ ] Character count: 1,200-1,800
|
||||
- [ ] Topic aligns with expertise areas
|
||||
- [ ] CTA invites discussion, not just "What do you think?"
|
||||
|
||||
## Step 7: Present Draft
|
||||
|
||||
Show:
|
||||
1. The main draft with character count
|
||||
2. 2 alternative hooks
|
||||
3. Suggested first comment (with the URL + brief context)
|
||||
4. Recommended posting time
|
||||
|
||||
Offer refinement options via AskUserQuestion:
|
||||
1. Perfect — ready to post
|
||||
2. Adjust the hook
|
||||
3. Change the angle
|
||||
4. Make it shorter/punchier
|
||||
5. Make it more provocative
|
||||
6. Try a completely different angle
|
||||
|
||||
## Step 8: State Update
|
||||
|
||||
After the post is finalized, update `~/.claude/linkedin-thought-leadership.local.md`:
|
||||
- Set `last_post_date` to today's date (YYYY-MM-DD)
|
||||
- Set `last_post_topic` to the main topic
|
||||
- Check if ISO week changed — if so, reset `posts_this_week` to 0, update `current_week`
|
||||
- Increment `posts_this_week`
|
||||
- Update streak: increment if consecutive day, reset to 1 if gap > 2 days
|
||||
- Update `longest_streak` if current exceeds it
|
||||
- Add entry to "## Recent Posts": [YYYY-MM-DD] "Hook text..." (char count) - topic
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `assets/voice-samples/authentic-voice-samples.md` — Voice matching
|
||||
- `references/thought-leadership-angles.md` — 8 universal angles
|
||||
- `references/engagement-frameworks.md` — Hooks, structure, CTAs
|
||||
- `assets/checklists/quality-scorecard.md` — Pre-publish check
|
||||
439
plugins/linkedin-thought-leadership/commands/report.md
Normal file
439
plugins/linkedin-thought-leadership/commands/report.md
Normal file
|
|
@ -0,0 +1,439 @@
|
|||
---
|
||||
name: linkedin:report
|
||||
description: |
|
||||
Generate a weekly performance report from imported LinkedIn analytics data.
|
||||
Shows key metrics, top performers, trends, and actionable alerts.
|
||||
Use when the user wants to review their LinkedIn performance.
|
||||
Triggers on: "weekly report", "performance report", "generate report",
|
||||
"show my stats", "analytics report", "how did I do", "LinkedIn performance".
|
||||
allowed-tools:
|
||||
- Bash
|
||||
- Read
|
||||
- Glob
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Analytics Weekly Report
|
||||
|
||||
You are a LinkedIn analytics performance reporter. Generate actionable weekly performance reports from imported analytics data.
|
||||
|
||||
## Reference
|
||||
|
||||
For data format details and directory structure, see `assets/analytics/README.md`.
|
||||
|
||||
## Step 1: Check for Imported Data
|
||||
|
||||
First, verify that analytics data exists:
|
||||
|
||||
```bash
|
||||
ls -1 ${CLAUDE_PLUGIN_ROOT}/assets/analytics/posts/ 2>/dev/null | grep -E '\.json$' | head -10
|
||||
```
|
||||
|
||||
If no JSON files exist, tell the user:
|
||||
|
||||
**No analytics data found.**
|
||||
|
||||
You need to import your LinkedIn analytics first:
|
||||
1. Run `/linkedin:import` to import CSV data
|
||||
2. Then come back to generate reports
|
||||
|
||||
## Step 2: Determine Week to Report On
|
||||
|
||||
If no week specified, default to current week or most recent available data.
|
||||
|
||||
**Ask the user** using AskUserQuestion:
|
||||
|
||||
```
|
||||
Which week would you like a report for?
|
||||
|
||||
Available options:
|
||||
- "current" or "this week" - Current ISO week (2026-W05)
|
||||
- "last week" - Previous ISO week (2026-W04)
|
||||
- Specific week: "2026-W03", "2025-W52", etc.
|
||||
- "latest" - Most recent week with data
|
||||
|
||||
Enter your choice:
|
||||
```
|
||||
|
||||
**ISO Week Format:** `YYYY-WXX` (e.g., `2026-W05` for week 5 of 2026)
|
||||
|
||||
To get current ISO week:
|
||||
```bash
|
||||
date +%Y-W%V
|
||||
```
|
||||
|
||||
## Step 3: Run Report Generation
|
||||
|
||||
Execute the report CLI command:
|
||||
|
||||
```bash
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" report --week <YYYY-WXX>
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```bash
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" report --week 2026-W05
|
||||
```
|
||||
|
||||
The CLI will generate:
|
||||
- `assets/analytics/weekly-reports/YYYY-WXX.json` - Structured report data
|
||||
|
||||
## Step 4: Read Generated Report Data
|
||||
|
||||
Read the generated JSON report:
|
||||
|
||||
```bash
|
||||
cat ${CLAUDE_PLUGIN_ROOT}/assets/analytics/weekly-reports/<YYYY-WXX>.json
|
||||
```
|
||||
|
||||
The report contains:
|
||||
- **week**: ISO week identifier
|
||||
- **dateRange**: Start and end dates
|
||||
- **postCount**: Number of posts published
|
||||
- **aggregateMetrics**: Totals and averages across all metrics
|
||||
- **topPerformers**: Best posts by each metric
|
||||
- **alerts**: Anomalies and significant events
|
||||
- **trends**: Week-over-week changes
|
||||
|
||||
## Step 5: Run Trend Analysis
|
||||
|
||||
Get additional context with trend analysis:
|
||||
|
||||
```bash
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" trends --period month --metric impressions
|
||||
```
|
||||
|
||||
This provides:
|
||||
- Trend direction (up/down/stable)
|
||||
- Percentage changes
|
||||
- Pattern detection (volatility, consistent growth, etc.)
|
||||
|
||||
### Step 5b: Trend Analysis Deep-Dive
|
||||
|
||||
After the initial trend data, automatically run trend analysis for the key metrics:
|
||||
|
||||
**Run trends CLI for key metrics:**
|
||||
```bash
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" \
|
||||
node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" \
|
||||
trends --period month --metric impressions
|
||||
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" \
|
||||
node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" \
|
||||
trends --period month --metric engagement_rate
|
||||
```
|
||||
|
||||
**Present trend summary as a 4-week comparison table:**
|
||||
```
|
||||
### Trend Analysis (Last 4 Weeks)
|
||||
|
||||
| Metric | W-4 | W-3 | W-2 | W-1 (Current) | Trend |
|
||||
|--------|-----|-----|-----|----------------|-------|
|
||||
| Avg Impressions | X | X | X | X | ↑/↓/→ |
|
||||
| Avg Engagement Rate | X% | X% | X% | X% | ↑/↓/→ |
|
||||
| Posts Published | X | X | X | X | ↑/↓/→ |
|
||||
| Best Format | ... | ... | ... | ... | — |
|
||||
```
|
||||
|
||||
**Trend interpretation rules:**
|
||||
- ↑ Upward trend (>10% increase over 4 weeks): Highlight what's working
|
||||
- ↓ Downward trend (>10% decrease): Flag for strategy review
|
||||
- → Stable (within ±10%): Note consistency
|
||||
- If engagement rate is down but impressions up: Content reach expanding but resonance declining — consider revisiting hooks and CTAs
|
||||
- If engagement rate is up but impressions down: Niche audience engaged but reach limited — consider format diversification or posting time adjustment
|
||||
- If both declining: Possible algorithm signal change or content fatigue — review algorithm-signals-reference for latest penalties
|
||||
- If both growing: Strong momentum — maintain current strategy and document what's working
|
||||
|
||||
Construct the 4-week table by reading available weekly report files:
|
||||
```bash
|
||||
ls ${CLAUDE_PLUGIN_ROOT}/assets/analytics/weekly-reports/*.json 2>/dev/null | sort | tail -4
|
||||
```
|
||||
|
||||
Read each file and extract the summary metrics to populate the table columns.
|
||||
|
||||
### Step 5c: Alert Detection
|
||||
|
||||
Automatically flag these conditions based on the report data and trend analysis:
|
||||
|
||||
**Performance Alerts:**
|
||||
- 🔴 **Critical:** Engagement rate below 2% for 2+ consecutive weeks
|
||||
- 🔴 **Critical:** Zero posts in a week (streak broken)
|
||||
- 🟡 **Warning:** Impressions dropped >30% week-over-week
|
||||
- 🟡 **Warning:** Comment count below average for 2+ weeks
|
||||
- 🟢 **Positive:** New personal best in any metric
|
||||
- 🟢 **Positive:** Consistent posting streak maintained (7+ days)
|
||||
|
||||
**Algorithm Alerts (based on algorithm-signals-reference):**
|
||||
- 🔴 Format stagnation: Same format used >80% of posts (algorithm penalizes monotony per 2026 content format multipliers)
|
||||
- 🟡 Posting time drift: Publishing outside optimal window (Tue-Thu, 7-9 AM CET for Nordic audience — see posting time windows reference)
|
||||
- 🟡 Hook length violation: Posts with hooks >140 chars underperforming (>140 chars truncated on mobile "see more")
|
||||
- 🟢 Engagement velocity improving: First-hour engagement trending up (15+ engagements in first hour unlocks 2nd/3rd degree distribution)
|
||||
|
||||
**Detect alerts by comparing current week data against baselines:**
|
||||
```bash
|
||||
cat ${CLAUDE_PLUGIN_ROOT}/assets/analytics/baselines.json 2>/dev/null
|
||||
```
|
||||
|
||||
Compare current week's `aggregateMetrics` against baseline means and standard deviations. Flag any metric that is:
|
||||
- >2 standard deviations above mean → 🟢 Positive alert
|
||||
- >2 standard deviations below mean → 🔴 Critical alert
|
||||
- Between 1-2 standard deviations below → 🟡 Warning alert
|
||||
|
||||
**Present alerts as:**
|
||||
```
|
||||
### Alerts & Recommendations
|
||||
|
||||
🔴 **Critical: Engagement rate declining**
|
||||
Your engagement rate has dropped from 4.2% to 2.8% over the last 3 weeks.
|
||||
→ **Action:** Review recent post hooks. Consider more provocative angles or questions.
|
||||
→ **Reference:** Hook length should be <140 chars. Saves (10x weight) and expert comments (7-9x) are the highest-impact signals.
|
||||
|
||||
🟢 **Positive: New impression record**
|
||||
Your post on [topic] achieved 12,500 impressions — a personal best!
|
||||
→ **Action:** Analyze what made this post succeed. Consider a follow-up post.
|
||||
→ **Reference:** First-hour velocity of 15+ engagements unlocks broader distribution.
|
||||
|
||||
🟡 **Warning: Format stagnation detected**
|
||||
80%+ of your recent posts are text-only. PDF/Carousels get 1.6x reach multiplier.
|
||||
→ **Action:** Try a carousel or multi-image post this week for format diversification.
|
||||
```
|
||||
|
||||
## Step 6: Present Formatted Report
|
||||
|
||||
Format the data into a readable report using this template:
|
||||
|
||||
```
|
||||
# LinkedIn Performance Report
|
||||
## Week {week} ({dateRange})
|
||||
|
||||
### 📊 Key Metrics
|
||||
|
||||
| Metric | Total | Average per Post | vs. Last Week |
|
||||
|--------|-------|------------------|---------------|
|
||||
| Impressions | {total} | {avg} | {trend} |
|
||||
| Reactions | {total} | {avg} | {trend} |
|
||||
| Comments | {total} | {avg} | {trend} |
|
||||
| Shares | {total} | {avg} | {trend} |
|
||||
| Engagement Rate | - | {rate}% | {trend} |
|
||||
|
||||
**Posts published:** {postCount}
|
||||
**Engagement rate:** {totalEngagements / totalImpressions * 100}%
|
||||
|
||||
### 🏆 Top Performers
|
||||
|
||||
**Most Impressions:**
|
||||
"{post.content}" - {impressions} impressions ({date})
|
||||
|
||||
**Most Engaged:**
|
||||
"{post.content}" - {engagementRate}% engagement ({date})
|
||||
|
||||
**Most Shared:**
|
||||
"{post.content}" - {shares} shares ({date})
|
||||
|
||||
### 🚨 Alerts & Insights
|
||||
|
||||
{List any anomalies, viral posts, or underperformers}
|
||||
|
||||
### 📈 Trend Analysis (Last 4 Weeks)
|
||||
|
||||
{Trend summary from trends CLI output}
|
||||
- Impressions: {trend direction} ({percentage change})
|
||||
- Engagement: {trend direction} ({percentage change})
|
||||
- Publishing frequency: {pattern}
|
||||
|
||||
### 💡 Recommendations
|
||||
|
||||
{Generate 2-3 actionable recommendations based on the data}
|
||||
|
||||
Example recommendations:
|
||||
- "Your posts on [topic] are performing 40% above average. Consider posting more on this topic."
|
||||
- "Engagement drops significantly on [day]. Try shifting your posting schedule."
|
||||
- "Posts with [format] are getting 2x more shares. Experiment with this format more."
|
||||
```
|
||||
|
||||
## Step 7: Generate Actionable Recommendations
|
||||
|
||||
Based on the report data, provide 2-3 specific, actionable recommendations:
|
||||
|
||||
**Framework for recommendations:**
|
||||
|
||||
1. **What's working?** - Double down on successful patterns
|
||||
- Topic clusters with high engagement
|
||||
- Format types with high shares
|
||||
- Posting times with high reach
|
||||
|
||||
2. **What's not working?** - Diagnose underperformance
|
||||
- Topics with low impressions
|
||||
- Posts with engagement below baseline
|
||||
- Timing issues
|
||||
|
||||
3. **What to test next?** - Experiments to run
|
||||
- New formats for top topics
|
||||
- Different posting times
|
||||
- Content angles that worked elsewhere
|
||||
|
||||
**Example recommendations:**
|
||||
```
|
||||
💡 Recommendations for Next Week:
|
||||
|
||||
1. **Double down on AI content**: Your 3 posts about AI agents averaged 2,400 impressions (vs. 1,200 baseline). Plan 2 more AI-focused posts this week.
|
||||
|
||||
2. **Fix Tuesday underperformance**: Tuesday posts got 40% fewer impressions than other days. Try posting at 8am instead of 12pm.
|
||||
|
||||
3. **Test carousel format**: Your one carousel got 3x more shares than text posts. Create a carousel for your top-performing topic this week.
|
||||
```
|
||||
|
||||
## Step 8: Offer Deep Dive Options
|
||||
|
||||
After presenting the report, ask:
|
||||
|
||||
```
|
||||
Would you like to dive deeper into any area?
|
||||
|
||||
1. Analyze specific posts in detail
|
||||
2. Compare this week to previous weeks
|
||||
3. Run trend analysis for other metrics (comments, shares)
|
||||
4. Export report as markdown file
|
||||
5. Done - I have what I need
|
||||
```
|
||||
|
||||
Use AskUserQuestion for selection.
|
||||
|
||||
## Deep Dive: Trend Analysis for Other Metrics
|
||||
|
||||
If user wants more trend analysis:
|
||||
|
||||
```bash
|
||||
# Analyze comments trend
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" trends --period month --metric comments
|
||||
|
||||
# Analyze shares trend
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" trends --period month --metric shares
|
||||
|
||||
# Analyze engagement rate trend
|
||||
ANALYTICS_ROOT="${CLAUDE_PLUGIN_ROOT}/assets/analytics" node --import tsx "${CLAUDE_PLUGIN_ROOT}/scripts/analytics/src/cli.ts" trends --period month --metric engagementRate
|
||||
```
|
||||
|
||||
Present additional insights from these trends.
|
||||
|
||||
## Deep Dive: Post Analysis
|
||||
|
||||
If user wants to analyze specific posts:
|
||||
|
||||
Read the weekly post data directly:
|
||||
|
||||
```bash
|
||||
cat ${CLAUDE_PLUGIN_ROOT}/assets/analytics/posts/<YYYY-WXX>.json | jq '.posts[] | select(.title | contains("search term"))'
|
||||
```
|
||||
|
||||
Show detailed metrics for that post and suggest what made it perform well/poorly.
|
||||
|
||||
## Error Handling
|
||||
|
||||
**If report generation fails:**
|
||||
|
||||
1. **Week not found**: No data imported for that week
|
||||
- List available weeks: `ls ${CLAUDE_PLUGIN_ROOT}/assets/analytics/posts/`
|
||||
- Suggest importing data for that week
|
||||
|
||||
2. **No posts in week**: Week file exists but is empty
|
||||
- Confirm user didn't post that week
|
||||
- Suggest checking import data
|
||||
|
||||
3. **CLI error**: Technical failure
|
||||
- Show error message
|
||||
- Check file permissions
|
||||
- Verify Node.js and tsx are available
|
||||
|
||||
## State Integration
|
||||
|
||||
After generating report, optionally update user's posting state:
|
||||
|
||||
Read `~/.claude/linkedin-thought-leadership.local.md` and suggest:
|
||||
- If week had 0 posts: "Streak broken - consider posting this week to restart"
|
||||
- If week hit goal: "Goal achieved! Maintaining consistency."
|
||||
- If week exceeded goal: "Exceeding goal - strong momentum!"
|
||||
|
||||
## Reference Files
|
||||
|
||||
Reports use data from:
|
||||
- `assets/analytics/posts/YYYY-WXX.json` - Raw weekly post data
|
||||
- `assets/analytics/weekly-reports/YYYY-WXX.json` - Computed report
|
||||
- `assets/analytics/baselines.json` - Statistical baselines for comparison
|
||||
- `assets/analytics/metadata.json` - Import history and tracking
|
||||
|
||||
## Step 8b: Export Options
|
||||
|
||||
If the user chooses option 4 ("Export report as markdown file") from the deep dive menu:
|
||||
|
||||
**Generate and save a clean markdown report:**
|
||||
|
||||
1. Read the JSON report data:
|
||||
```bash
|
||||
cat ${CLAUDE_PLUGIN_ROOT}/assets/analytics/weekly-reports/<YYYY-WXX>.json
|
||||
```
|
||||
|
||||
2. Format the data using this template and write to file:
|
||||
|
||||
Save to: `${CLAUDE_PLUGIN_ROOT}/assets/analytics/weekly-reports/YYYY-WXX-report.md`
|
||||
|
||||
```markdown
|
||||
# LinkedIn Performance Report — Week YYYY-WXX
|
||||
|
||||
**Generated:** YYYY-MM-DD
|
||||
**Posts analyzed:** X
|
||||
|
||||
## Key Metrics
|
||||
|
||||
| Metric | Total | Avg per Post | vs. Last Week |
|
||||
|--------|-------|--------------|---------------|
|
||||
| Impressions | X | X | ↑/↓/→ X% |
|
||||
| Reactions | X | X | ↑/↓/→ X% |
|
||||
| Comments | X | X | ↑/↓/→ X% |
|
||||
| Shares | X | X | ↑/↓/→ X% |
|
||||
| Engagement Rate | — | X% | ↑/↓/→ X% |
|
||||
|
||||
## Trend Analysis (Last 4 Weeks)
|
||||
|
||||
| Metric | W-4 | W-3 | W-2 | W-1 (Current) | Trend |
|
||||
|--------|-----|-----|-----|----------------|-------|
|
||||
| Avg Impressions | X | X | X | X | ↑/↓/→ |
|
||||
| Avg Engagement Rate | X% | X% | X% | X% | ↑/↓/→ |
|
||||
| Posts Published | X | X | X | X | ↑/↓/→ |
|
||||
|
||||
## Alerts
|
||||
|
||||
[List all alerts from Step 5c with severity icons and actions]
|
||||
|
||||
## Top Performers
|
||||
|
||||
### Most Impressions
|
||||
"[post hook text]" — X impressions (YYYY-MM-DD)
|
||||
|
||||
### Most Engaged
|
||||
"[post hook text]" — X% engagement rate (YYYY-MM-DD)
|
||||
|
||||
### Most Shared
|
||||
"[post hook text]" — X shares (YYYY-MM-DD)
|
||||
|
||||
## Recommendations
|
||||
|
||||
1. [Actionable recommendation based on data]
|
||||
2. [Actionable recommendation based on data]
|
||||
3. [Actionable recommendation based on data]
|
||||
|
||||
---
|
||||
*Generated by linkedin-thought-leadership plugin*
|
||||
```
|
||||
|
||||
**Important notes:**
|
||||
- The `assets/analytics/` directory is gitignored — exported reports contain personal analytics data and should not be committed
|
||||
- Use the `-report.md` suffix to distinguish from the JSON data files (e.g., `2026-W05-report.md` vs `2026-W05.json`)
|
||||
- Include all sections: metrics, trends, alerts, top performers, and recommendations for a complete standalone document
|
||||
|
||||
After saving, confirm to the user:
|
||||
```
|
||||
Report exported to: assets/analytics/weekly-reports/YYYY-WXX-report.md
|
||||
|
||||
Note: This file is in your gitignored analytics directory — it won't be committed to the repository.
|
||||
```
|
||||
371
plugins/linkedin-thought-leadership/commands/setup.md
Normal file
371
plugins/linkedin-thought-leadership/commands/setup.md
Normal file
|
|
@ -0,0 +1,371 @@
|
|||
---
|
||||
name: linkedin:setup
|
||||
description: |
|
||||
Guided setup workflow for populating empty asset templates with real user data.
|
||||
Calculates personalization score, shows dashboard, and walks through 6 sub-workflows
|
||||
to populate voice samples, case studies, frameworks, post analysis, demographics, and user profile.
|
||||
Use when assets are empty, plugin is newly installed, or personalization score is low.
|
||||
Triggers on: "setup", "personalize", "personalize plugin", "templates empty",
|
||||
"fill in assets", "personalization score", "setup linkedin plugin", "configure plugin",
|
||||
"improve personalization", "my score", "set up plugin".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Plugin Setup & Personalization
|
||||
|
||||
You are a setup assistant for the LinkedIn thought leadership plugin. Guide the user through populating their asset templates with real data to maximize content personalization.
|
||||
|
||||
## Step 0: Calculate Personalization Score
|
||||
|
||||
Read these 8 asset files and detect placeholder patterns to calculate the current score:
|
||||
|
||||
| Category | Weight | File/Directory | Placeholder Detection |
|
||||
|----------|--------|----------------|----------------------|
|
||||
| Voice samples | 25 | `assets/voice-samples/authentic-voice-samples.md` | Check for `[Your Name]` or if file has <50 lines |
|
||||
| User profile | 20 | `config/user-profile.local.md` | Check if file exists; count `[Your ` placeholders |
|
||||
| Case studies | 15 | `assets/case-studies/*.md` | Count non-template `.md` files (exclude `case-study-template.md`) |
|
||||
| Frameworks | 10 | `assets/frameworks/*.md` | Count non-template `.md` files (exclude `framework-template.md`) |
|
||||
| High-engagement posts | 10 | `assets/examples/high-engagement-posts.md` | Count `## Post N:` headers |
|
||||
| Demographics | 8 | `assets/audience-insights/demographics.md` | Count `[Industry name]`, `[Function]`, `[Country]`, `[X]%` |
|
||||
| Engagement patterns | 7 | `assets/audience-insights/engagement-patterns.md` | Count `[Day]`, `[Time]`, `[Topic]`, `[Format]`, `[Hook type]` |
|
||||
| Post templates | 5 | `assets/templates/my-post-templates.md` | Count `[Name - e.g.` vs total `## Template N:` headers |
|
||||
|
||||
**Scoring rules:**
|
||||
- Full points: Asset has real data (few/no placeholders remaining)
|
||||
- Partial points: Some real data mixed with placeholders
|
||||
- Zero points: Pure template or missing file
|
||||
|
||||
## Step 1: Show Dashboard
|
||||
|
||||
Present the score as a clear table:
|
||||
|
||||
```
|
||||
Personalization Score: XX/100 (N/8 assets personalized)
|
||||
|
||||
| # | Category | Score | Max | Status |
|
||||
|---|----------------------|-------|-----|--------|
|
||||
| 1 | Voice samples | XX | 25 | [filled/partial/empty] |
|
||||
| 2 | User profile | XX | 20 | [filled/partial/empty] |
|
||||
| 3 | Case studies | XX | 15 | [filled/partial/empty] |
|
||||
| 4 | Frameworks | XX | 10 | [filled/partial/empty] |
|
||||
| 5 | High-engagement posts| XX | 10 | [filled/partial/empty] |
|
||||
| 6 | Demographics | XX | 8 | [filled/partial/empty] |
|
||||
| 7 | Engagement patterns | XX | 7 | [filled/partial/empty] |
|
||||
| 8 | Post templates | XX | 5 | [filled/partial/empty] |
|
||||
|
||||
Highest-impact next step: [Recommendation based on highest-weight empty/partial category]
|
||||
```
|
||||
|
||||
## Step 2: Ask What to Set Up
|
||||
|
||||
Use AskUserQuestion:
|
||||
|
||||
**What would you like to set up?**
|
||||
|
||||
Options (always show all 7):
|
||||
|
||||
1. **Voice samples** -- Paste 3-5 of your best posts so I can analyze your writing voice
|
||||
2. **Case study** -- Walk through a guided interview to document a real case study
|
||||
3. **Framework** -- Document a framework or methodology you've developed
|
||||
4. **Post analysis** -- Add your high-engagement posts with metrics for pattern analysis
|
||||
5. **Demographics** -- Guide you through LinkedIn Analytics to capture audience demographics
|
||||
6. **User profile** -- Set up your personalization profile (name, expertise, goals, voice)
|
||||
7. **Show score details** -- See detailed breakdown of what's missing in each category
|
||||
|
||||
Based on their answer, run the corresponding sub-workflow below.
|
||||
|
||||
## Step 3a: Voice Samples Workflow
|
||||
|
||||
**Goal:** Populate `assets/voice-samples/authentic-voice-samples.md` with real voice data.
|
||||
|
||||
1. Ask the user to paste 3-5 of their best LinkedIn posts (or any professional writing samples)
|
||||
2. Analyze the samples for:
|
||||
- **Sentence structure:** Short/long, simple/complex, varied?
|
||||
- **Word choice:** Formal/casual, technical/accessible, jargon level
|
||||
- **Hook patterns:** How do they open? Questions, stats, stories, bold claims?
|
||||
- **Storytelling approach:** Narrative, listicle, problem-solution, before-after?
|
||||
- **Tone:** Authoritative, conversational, empathetic, analytical, provocative?
|
||||
- **Formatting:** Bullets, line breaks, emojis, bold text, section headers?
|
||||
3. Extract specific patterns:
|
||||
- Signature phrases they naturally use
|
||||
- Words/phrases they avoid
|
||||
- How they handle technical depth
|
||||
- How they conclude (CTA style, takeaway style)
|
||||
4. Read the existing `assets/voice-samples/authentic-voice-samples.md`
|
||||
5. **Merge** new findings with existing content (don't overwrite existing data):
|
||||
- Update "Core Voice Characteristics" if new patterns found
|
||||
- Add new entries to "Do's" and "Don'ts" lists
|
||||
- Update "Signature Phrases" with newly detected phrases
|
||||
- Add "Vocabulary Preferences" based on word analysis
|
||||
- Update "Update Log" with today's date
|
||||
|
||||
6. Write the updated file back.
|
||||
|
||||
**Important:** Ask "Would you like to paste more samples?" after analyzing the first batch. More samples = better voice model.
|
||||
|
||||
## Step 3b: Case Study Builder
|
||||
|
||||
**Goal:** Create a new case study file in `assets/case-studies/`.
|
||||
|
||||
Conduct a 6-question interview:
|
||||
|
||||
1. **What was the challenge?** -- Describe the problem or situation
|
||||
2. **Who was involved?** -- Organization type, team size, stakeholders (anonymize if needed)
|
||||
3. **What approach did you take?** -- The strategy, methodology, or solution
|
||||
4. **What were the key decisions?** -- Turning points, trade-offs, what you chose and why
|
||||
5. **What were the results?** -- Quantitative and qualitative outcomes
|
||||
6. **What's the key takeaway?** -- The non-obvious lesson others can apply
|
||||
|
||||
After the interview, read `assets/case-studies/case-study-template.md` for structure reference, then create a new file:
|
||||
|
||||
**Filename:** `assets/case-studies/[slug].md` (derive slug from the challenge topic, e.g., `ai-procurement-transformation.md`)
|
||||
|
||||
**File structure:**
|
||||
```markdown
|
||||
# Case Study: [Title]
|
||||
|
||||
**Industry:** [Industry]
|
||||
**Organization type:** [Type]
|
||||
**Timeline:** [Duration]
|
||||
**Key outcome:** [One-line result]
|
||||
|
||||
## The Challenge
|
||||
[From question 1]
|
||||
|
||||
## Context
|
||||
[From question 2]
|
||||
|
||||
## The Approach
|
||||
[From question 3]
|
||||
|
||||
## Key Decisions
|
||||
[From question 4]
|
||||
|
||||
## Results
|
||||
[From question 5]
|
||||
|
||||
## Key Takeaway
|
||||
[From question 6]
|
||||
|
||||
## Content Angles
|
||||
- **Post idea 1:** [Angle derived from the case study]
|
||||
- **Post idea 2:** [Another angle]
|
||||
- **Post idea 3:** [Another angle]
|
||||
|
||||
---
|
||||
*Documented: [Today's date]*
|
||||
```
|
||||
|
||||
Ask "Would you like to document another case study?" when done.
|
||||
|
||||
## Step 3c: Framework Documenter
|
||||
|
||||
**Goal:** Create a new framework file in `assets/frameworks/`.
|
||||
|
||||
Conduct a 5-question interview:
|
||||
|
||||
1. **What problem does this framework solve?** -- The pain point it addresses
|
||||
2. **What is the framework called?** -- Name (or help them name it)
|
||||
3. **What are the components/stages?** -- Break it down into 3-7 parts
|
||||
4. **How does someone apply it?** -- Step-by-step or decision process
|
||||
5. **What makes this different from standard approaches?** -- Your unique angle
|
||||
|
||||
After the interview, read `assets/frameworks/framework-template.md` for structure reference, then create:
|
||||
|
||||
**Filename:** `assets/frameworks/[slug].md` (e.g., `ai-maturity-model.md`)
|
||||
|
||||
**File structure:**
|
||||
```markdown
|
||||
# Framework: [Name]
|
||||
|
||||
**Problem it solves:** [One-line]
|
||||
**Number of stages/components:** [N]
|
||||
**Target audience:** [Who benefits]
|
||||
|
||||
## Overview
|
||||
[2-3 sentence summary]
|
||||
|
||||
## Components
|
||||
|
||||
### 1. [Component Name]
|
||||
- **What:** [Description]
|
||||
- **Key indicator:** [How to identify this stage/component]
|
||||
- **Action:** [What to do here]
|
||||
|
||||
### 2. [Component Name]
|
||||
[Same structure]
|
||||
|
||||
### 3. [Component Name]
|
||||
[Same structure]
|
||||
|
||||
## How to Apply
|
||||
[From question 4]
|
||||
|
||||
## What Makes This Different
|
||||
[From question 5]
|
||||
|
||||
## Content Angles
|
||||
- **Post idea 1:** [How to turn this into a LinkedIn post]
|
||||
- **Post idea 2:** [Another angle]
|
||||
|
||||
---
|
||||
*Documented: [Today's date]*
|
||||
```
|
||||
|
||||
Ask "Would you like to document another framework?" when done.
|
||||
|
||||
## Step 3d: Post Analysis
|
||||
|
||||
**Goal:** Document high-engagement posts in `assets/examples/high-engagement-posts.md`.
|
||||
|
||||
Two approaches — ask which they prefer:
|
||||
|
||||
### Option A: Analytics Data Available
|
||||
If the user has imported analytics data (check `assets/analytics/posts/` for JSON files):
|
||||
|
||||
1. Read the most recent analytics data files
|
||||
2. Identify the top 3-5 posts by engagement rate
|
||||
3. For each post, ask the user:
|
||||
- Can you paste the full post text?
|
||||
- Why do you think this worked?
|
||||
4. Document each post following the format in the existing file
|
||||
|
||||
### Option B: Manual Entry
|
||||
If no analytics data available:
|
||||
|
||||
1. Ask the user to paste their 3-5 best-performing posts with metrics:
|
||||
- Post text
|
||||
- Likes, comments, shares
|
||||
- Impressions (if known)
|
||||
- Posting date and time
|
||||
|
||||
2. For each post, analyze and document:
|
||||
- **Hook analysis:** What made the opening effective?
|
||||
- **Angle identification:** Which thought leadership angle was used?
|
||||
- **Pattern extraction:** What's replicable?
|
||||
- **Mistakes identified:** What could be improved?
|
||||
|
||||
3. Read the existing `assets/examples/high-engagement-posts.md`
|
||||
4. **Append** new posts after existing entries (don't overwrite)
|
||||
5. Update the "Patterns Across All High-Performing Posts" section based on all posts
|
||||
|
||||
Ask "Would you like to add more posts?" when done.
|
||||
|
||||
## Step 3e: Demographics Sync
|
||||
|
||||
**Goal:** Populate `assets/audience-insights/demographics.md` with real LinkedIn Analytics data.
|
||||
|
||||
Guide the user step by step through the LinkedIn Analytics UI:
|
||||
|
||||
1. **Direct them to LinkedIn Analytics:**
|
||||
"Open https://www.linkedin.com/analytics/ in your browser"
|
||||
|
||||
2. **Navigate to post analytics:**
|
||||
"Click on any recent post, then click 'Demographics' tab"
|
||||
|
||||
3. **Capture each section** (ask them to share the data they see):
|
||||
- Industries (Top 10) -- "What industries are listed? Share the top 10 with percentages"
|
||||
- Job Functions (Top 10) -- "What job functions do you see?"
|
||||
- Seniority Levels -- "What seniority breakdown is shown?"
|
||||
- Geographic Distribution (Top 10) -- "What countries are listed?"
|
||||
- Company Size -- "What company size distribution do you see?"
|
||||
|
||||
4. For each data point they share:
|
||||
- Record the actual data
|
||||
- Ask about trends ("Is this similar to previous months?")
|
||||
|
||||
5. Read the existing `assets/audience-insights/demographics.md`
|
||||
6. Replace the placeholder tables with real data
|
||||
7. Fill in the "Key insights" sections based on the data patterns
|
||||
8. Update the "Last Updated" date
|
||||
9. Fill in the "Intended vs. Actual Audience" section by asking:
|
||||
- "Who did you THINK your audience was?"
|
||||
- "Based on this data, who actually engages?"
|
||||
- "What content adjustments does this suggest?"
|
||||
|
||||
If the user says they don't have LinkedIn Analytics access or data yet, suggest:
|
||||
- "You need at least a few posts to get demographics. Run `/linkedin:quick` to create your first few posts, then come back."
|
||||
|
||||
## Step 3f: User Profile Setup
|
||||
|
||||
**Goal:** Create or update `config/user-profile.local.md`.
|
||||
|
||||
Guide through each section of the profile:
|
||||
|
||||
1. **Basic info:**
|
||||
- "What is your name?"
|
||||
- "What is your current role? (Remember: you post as a private individual)"
|
||||
- "What industry or domain do you work in?"
|
||||
|
||||
2. **Core expertise (5 topics):**
|
||||
- "What are your 5 core topics you want to be known for on LinkedIn?"
|
||||
- "These should be topics you can consistently create content about for 90+ days"
|
||||
|
||||
3. **Target audience:**
|
||||
- "Who is your primary audience? (e.g., 'Public sector leaders exploring AI')"
|
||||
- "Secondary audience?"
|
||||
- "Geographic focus?"
|
||||
|
||||
4. **LinkedIn goals:**
|
||||
- "Rank these goals from most to least important:"
|
||||
- Build thought leadership & authority
|
||||
- Attract speaking opportunities
|
||||
- Network with peers/influencers
|
||||
- Generate qualified leads
|
||||
- Monetization (consulting/courses)
|
||||
- Recruit talent
|
||||
|
||||
5. **Voice & style:**
|
||||
- "Which tone best describes your writing? (Professional, Conversational, Data-driven, Empathetic, Provocative)"
|
||||
- "Preferred post length? (Short 150-500 / Medium 1,200-1,800 / Long 2,000+)"
|
||||
- "How often do you want to post? (Daily / 3x week / 2x week)"
|
||||
|
||||
6. **Strategic context:**
|
||||
- "Current follower count?"
|
||||
- "90-day growth goal?"
|
||||
|
||||
7. Read `config/user-profile.template.md` for structure
|
||||
8. Write the completed profile to `config/user-profile.local.md`
|
||||
|
||||
**Important:** This file is gitignored (`.local.md` pattern), so personal data stays private.
|
||||
|
||||
## Step 4: Recalculate Score
|
||||
|
||||
After completing any sub-workflow:
|
||||
|
||||
1. Re-read all 8 asset files
|
||||
2. Recalculate the score using the same rules from Step 0
|
||||
3. Show before/after comparison:
|
||||
|
||||
```
|
||||
Personalization Score: Before XX/100 -> After YY/100 (+ZZ points)
|
||||
|
||||
Improved:
|
||||
- [Category]: [old score] -> [new score]
|
||||
|
||||
Still remaining:
|
||||
- [Category] (+XX possible) -- [what to do]
|
||||
```
|
||||
|
||||
## Step 5: Continue or Exit
|
||||
|
||||
Use AskUserQuestion:
|
||||
|
||||
**Your score is now YY/100. Would you like to continue?**
|
||||
|
||||
1. **Set up another asset** -- Go back to Step 2
|
||||
2. **I'm done for now** -- Show final summary and exit
|
||||
|
||||
If they choose to continue, go back to Step 2 with updated dashboard.
|
||||
|
||||
If they choose to exit, show:
|
||||
```
|
||||
Setup complete! Your personalization score: YY/100
|
||||
|
||||
To continue improving later: /linkedin:setup
|
||||
To start creating content: /linkedin:post or /linkedin:quick
|
||||
```
|
||||
556
plugins/linkedin-thought-leadership/commands/speaking.md
Normal file
556
plugins/linkedin-thought-leadership/commands/speaking.md
Normal file
|
|
@ -0,0 +1,556 @@
|
|||
---
|
||||
name: linkedin:speaking
|
||||
description: |
|
||||
Generate speaking opportunities through LinkedIn content. Assesses speaker readiness,
|
||||
searches for conferences and CFPs, creates speaker positioning content, generates talk
|
||||
abstracts and speaker bios, builds outreach templates, and tracks the full speaking pipeline.
|
||||
Triggers on: "speaking opportunities", "conference speaking", "get invited to speak",
|
||||
"speaker positioning", "linkedin speaking", "call for speakers", "CFP", "talk proposal".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- WebSearch
|
||||
- WebFetch
|
||||
- AskUserQuestion
|
||||
- Write
|
||||
---
|
||||
|
||||
# Speaking Opportunity Generator
|
||||
|
||||
You are a LinkedIn-powered speaking opportunity strategist. Help the user leverage their thought leadership to attract speaking invitations — from local meetups to keynote stages.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
Read these files for speaking intelligence:
|
||||
|
||||
```
|
||||
${CLAUDE_PLUGIN_ROOT}/references/opportunity-generation.md → opportunity funnels, DM strategy
|
||||
${CLAUDE_PLUGIN_ROOT}/references/linkedin-growth-playbook-2025-2026.md → algorithm context
|
||||
${CLAUDE_PLUGIN_ROOT}/references/collaborations-guide.md → networking strategies
|
||||
${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md → content structures
|
||||
~/.claude/linkedin-thought-leadership.local.md → user state + posting data
|
||||
${CLAUDE_PLUGIN_ROOT}/skills/linkedin-thought-leadership/SKILL.md → expertise areas
|
||||
```
|
||||
|
||||
## Step 1: Assess Speaker Readiness
|
||||
|
||||
Ask the user (via AskUserQuestion):
|
||||
- Have they spoken publicly before? (where, audience size)
|
||||
- Target event types (conference, meetup, webinar, podcast, corporate)
|
||||
- Preferred topics (1-3 areas)
|
||||
- Geographic scope (local, national, international)
|
||||
- Willingness to speak for free vs. paid only
|
||||
|
||||
### Speaker Readiness Scorecard
|
||||
|
||||
```
|
||||
╔══════════════════════════════════════════════════════════╗
|
||||
║ SPEAKER READINESS SCORECARD ║
|
||||
╠══════════════════════════════════════════════════════════╣
|
||||
║ ║
|
||||
║ Content Authority: /25 ║
|
||||
║ ├─ [ ] 3+ months consistent posting (+5) ║
|
||||
║ ├─ [ ] Clear expertise positioning (+5) ║
|
||||
║ ├─ [ ] Signature framework or methodology (+10) ║
|
||||
║ └─ [ ] Posts that attract expert comments (+5) ║
|
||||
║ ║
|
||||
║ Profile Signals: /25 ║
|
||||
║ ├─ [ ] Headline mentions expertise area (+5) ║
|
||||
║ ├─ [ ] About section shows speaking experience (+5) ║
|
||||
║ ├─ [ ] Featured section has presentation content (+10) ║
|
||||
║ └─ [ ] "Open to speaking" mentioned in profile (+5) ║
|
||||
║ ║
|
||||
║ Audience & Reach: /25 ║
|
||||
║ ├─ [ ] 1K+ followers in target niche (+10) ║
|
||||
║ ├─ [ ] Engagement from event organizers (+5) ║
|
||||
║ ├─ [ ] Comments from industry peers (+5) ║
|
||||
║ └─ [ ] Cross-platform presence (+5) ║
|
||||
║ ║
|
||||
║ Track Record: /25 ║
|
||||
║ ├─ [ ] Any prior speaking experience (+5) ║
|
||||
║ ├─ [ ] Video recordings available (+10) ║
|
||||
║ ├─ [ ] Published articles/posts about talks (+5) ║
|
||||
║ └─ [ ] Testimonials from organizers (+5) ║
|
||||
║ ║
|
||||
║ TOTAL: /100 ║
|
||||
║ ║
|
||||
║ 0-30: Start with meetups and internal talks ║
|
||||
║ 31-50: Ready for industry events and webinars ║
|
||||
║ 51-75: Target conferences and paid opportunities ║
|
||||
║ 76-100: Pursue keynotes and premium stages ║
|
||||
╚══════════════════════════════════════════════════════════╝
|
||||
```
|
||||
|
||||
## Step 2: Identify Target Events
|
||||
|
||||
Use WebSearch to find relevant events for the user's expertise.
|
||||
|
||||
### Search Strategy
|
||||
|
||||
Run these searches systematically:
|
||||
|
||||
```
|
||||
Search queries (adapt to user's niche):
|
||||
|
||||
Conference CFPs:
|
||||
- "[expertise] conference 2026 call for speakers"
|
||||
- "[industry] summit 2026 CFP"
|
||||
- "[topic] conference Europe 2026"
|
||||
- "[niche] tech conference Nordic 2026"
|
||||
|
||||
Webinar/Podcast:
|
||||
- "[topic] webinar series guest speakers"
|
||||
- "[industry] podcast looking for guests"
|
||||
- "[expertise] LinkedIn Live guest"
|
||||
|
||||
Meetup/Local:
|
||||
- "[topic] meetup [city]"
|
||||
- "[industry] user group [country]"
|
||||
- "tech meetup speaking opportunities [region]"
|
||||
```
|
||||
|
||||
### Event Research Template
|
||||
|
||||
For each relevant event found, compile:
|
||||
|
||||
```
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
EVENT OPPORTUNITY: [Event Name]
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
Type: [Conference / Summit / Webinar / Meetup / Podcast / Corporate]
|
||||
Date: [Date]
|
||||
Location: [City, Country / Virtual]
|
||||
Audience size: [estimated]
|
||||
Audience type: [developers / executives / marketers / mixed]
|
||||
|
||||
CFP status: [Open until DATE / Invite-only / Always accepting]
|
||||
CFP link: [URL if found]
|
||||
Contact: [Organizer name/email if found]
|
||||
|
||||
Format: [Keynote / Breakout / Workshop / Panel / Lightning talk]
|
||||
Duration: [minutes]
|
||||
Compensation: [Paid / Travel covered / Free / Unknown]
|
||||
|
||||
Fit score: [High / Medium / Low]
|
||||
Why: [How user's expertise matches event theme]
|
||||
|
||||
Suggested talk title: [Tailored to this event]
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
```
|
||||
|
||||
### Nordic/European Tech Conference Calendar
|
||||
|
||||
These events frequently have CFPs for tech thought leaders:
|
||||
|
||||
```
|
||||
Common Nordic/European Tech Events:
|
||||
|
||||
Q1 (Jan-Mar):
|
||||
- NDC Security (Oslo, Jan)
|
||||
- FOSDEM (Brussels, Feb)
|
||||
- Jfokus (Stockholm, Feb)
|
||||
- QCon London (Mar)
|
||||
|
||||
Q2 (Apr-Jun):
|
||||
- NDC Oslo (Jun)
|
||||
- DevOps Enterprise Summit Europe
|
||||
- Microsoft Build (May, virtual/US)
|
||||
- Web Summit (various)
|
||||
- JavaZone CFP opens (Jun for Sep event)
|
||||
|
||||
Q3 (Jul-Sep):
|
||||
- JavaZone (Oslo, Sep)
|
||||
- Strange Loop (Sep)
|
||||
- NDC TechTown (Kongsberg, Sep)
|
||||
|
||||
Q4 (Oct-Dec):
|
||||
- Øredev (Malmö, Nov)
|
||||
- KubeCon Europe
|
||||
- Microsoft Ignite (Nov)
|
||||
- Booster (Bergen, Mar — CFP opens Q4)
|
||||
|
||||
Year-round:
|
||||
- Meetup groups (Computas, Bekk, NNUG, Azure User Group)
|
||||
- Corporate internal events
|
||||
- LinkedIn Live / webinar series
|
||||
```
|
||||
|
||||
## Step 3: Talk Abstract Generator
|
||||
|
||||
Help the user create compelling talk proposals tailored to each event type.
|
||||
|
||||
### Abstract Templates
|
||||
|
||||
**Template A: Problem-Solution (best for conferences)**
|
||||
|
||||
```
|
||||
Title: [Number] Ways to [Solve Problem] Without [Common Objection]
|
||||
|
||||
Abstract:
|
||||
[One-sentence hook about the problem].
|
||||
|
||||
In this talk, you'll learn:
|
||||
- [Concrete takeaway 1]
|
||||
- [Concrete takeaway 2]
|
||||
- [Concrete takeaway 3]
|
||||
|
||||
I'll share [real examples / case studies / live demos] from
|
||||
[your experience context].
|
||||
|
||||
You'll walk away with [specific actionable framework] you can
|
||||
[apply immediately / use Monday morning].
|
||||
|
||||
Target audience: [Who benefits most]
|
||||
Level: [Beginner / Intermediate / Advanced]
|
||||
```
|
||||
|
||||
**Template B: Story-Driven (best for keynotes)**
|
||||
|
||||
```
|
||||
Title: [Provocative Statement or Question]
|
||||
|
||||
Abstract:
|
||||
[Personal story hook — 1-2 sentences].
|
||||
|
||||
[The insight or turning point].
|
||||
|
||||
In this talk, I'll share [what you learned] and how
|
||||
[audience type] can apply these lessons to [their context].
|
||||
|
||||
Key themes:
|
||||
- [Theme 1]
|
||||
- [Theme 2]
|
||||
- [Theme 3]
|
||||
|
||||
This talk is for anyone who [relates to the challenge].
|
||||
```
|
||||
|
||||
**Template C: How-To (best for workshops/breakouts)**
|
||||
|
||||
```
|
||||
Title: A Practical Guide to [Specific Skill/Tool]
|
||||
|
||||
Abstract:
|
||||
[Why this skill matters right now — 1-2 sentences].
|
||||
|
||||
In this hands-on session, we'll:
|
||||
1. [First thing they'll do]
|
||||
2. [Second thing they'll do]
|
||||
3. [Third thing they'll do]
|
||||
|
||||
Prerequisites: [What attendees need]
|
||||
What to bring: [Laptop / nothing / specific tool]
|
||||
|
||||
By the end, you'll have [concrete deliverable or skill].
|
||||
```
|
||||
|
||||
**Template D: Lightning Talk (5-10 min)**
|
||||
|
||||
```
|
||||
Title: [One Big Idea] in [X] Minutes
|
||||
|
||||
Abstract:
|
||||
[Bold opening claim].
|
||||
|
||||
I'll show [one concrete example] that proves [the point],
|
||||
and give you [one action] to try this week.
|
||||
|
||||
No slides needed — just [a story / a demo / a framework].
|
||||
```
|
||||
|
||||
Use AskUserQuestion to pick the right template, then generate 2-3 talk abstracts.
|
||||
|
||||
## Step 4: Speaker Positioning Content
|
||||
|
||||
Create LinkedIn content that signals "this person should be on stage."
|
||||
|
||||
### Portfolio Post Types
|
||||
|
||||
```
|
||||
CONTENT CALENDAR: Speaker Positioning (4-week rotation)
|
||||
|
||||
Week 1: FRAMEWORK POST
|
||||
─────────────────────
|
||||
Show your unique methodology.
|
||||
Hook: "I developed a 3-step framework for [topic] after [experience]."
|
||||
Goal: Demonstrate thought leadership depth.
|
||||
Signal: "This person has original ideas worth sharing."
|
||||
|
||||
Week 2: EVENT RECAP / INSIGHT POST
|
||||
───────────────────────────────────
|
||||
Share insights from events you attend.
|
||||
Hook: "3 things I learned at [event] that changed my approach to [topic]."
|
||||
Goal: Show you're active in the speaking ecosystem.
|
||||
Signal: "This person is already part of the conference circuit."
|
||||
|
||||
Week 3: TEACHING POST
|
||||
─────────────────────
|
||||
Explain a complex topic clearly.
|
||||
Hook: "Let me explain [complex topic] using an analogy..."
|
||||
Goal: Demonstrate communication and presentation skills.
|
||||
Signal: "This person can engage an audience."
|
||||
|
||||
Week 4: RESULTS / CASE STUDY POST
|
||||
──────────────────────────────────
|
||||
Show real outcomes from your expertise.
|
||||
Hook: "We went from [before] to [after] by applying [approach]."
|
||||
Goal: Prove your expertise delivers results.
|
||||
Signal: "This person has credibility and track record."
|
||||
```
|
||||
|
||||
### Demo Reel Content Strategy
|
||||
|
||||
Build a video portfolio on LinkedIn for speaker credibility:
|
||||
|
||||
```
|
||||
Demo Reel Building Blocks:
|
||||
|
||||
1. MICRO-TALKS (60-90 sec LinkedIn video)
|
||||
Record yourself explaining one concept clearly.
|
||||
Post weekly for 4 weeks to build a library.
|
||||
Best format: Talking head, no slides, strong hook.
|
||||
|
||||
2. RECAP CLIPS
|
||||
After any talk (even internal), record a 60-sec summary.
|
||||
"I just spoke at [event] about [topic]. Key takeaway: [insight]."
|
||||
|
||||
3. SLIDES-TO-VIDEO
|
||||
Convert your best carousel into a narrated video.
|
||||
Walk through the framework verbally.
|
||||
|
||||
4. LIVE SESSIONS
|
||||
Host a LinkedIn Live Q&A on your expertise topic.
|
||||
Record it → excerpt the best 90-sec segment.
|
||||
|
||||
Use these in:
|
||||
- Featured section (pin best video)
|
||||
- CFP submissions (link as evidence)
|
||||
- Speaker bio (reference video count)
|
||||
- Outreach messages (show, don't tell)
|
||||
```
|
||||
|
||||
## Step 5: Speaker Bio Variants
|
||||
|
||||
Create multiple bio lengths for different contexts.
|
||||
|
||||
### Short Bio (50 words — conference programs)
|
||||
|
||||
```
|
||||
[Name] is a [title] at [company] specializing in [expertise].
|
||||
[Key credential or achievement]. Speaks on [topic 1], [topic 2],
|
||||
and [topic 3]. [One humanizing detail].
|
||||
```
|
||||
|
||||
### Medium Bio (100 words — event websites)
|
||||
|
||||
```
|
||||
[Name] is a [title] at [company] with [X years] of experience in
|
||||
[domain]. Known for [signature framework or contribution], [Name]
|
||||
helps [audience] [achieve outcome].
|
||||
|
||||
[Key achievement or credential].
|
||||
[Second achievement or social proof].
|
||||
|
||||
When not [working/coding/consulting], [Name] [personal interest].
|
||||
|
||||
Speaking topics: [topic 1], [topic 2], [topic 3].
|
||||
Previous events: [event 1], [event 2].
|
||||
```
|
||||
|
||||
### Full Bio (200 words — keynote introductions)
|
||||
|
||||
```
|
||||
[Name] is a [title] at [company], where they [specific role
|
||||
description]. With [X years] in [domain], [Name] has become
|
||||
a recognized voice on [expertise areas].
|
||||
|
||||
[Paragraph about key achievements, frameworks, or contributions.
|
||||
Include specific numbers: "helped X organizations," "trained Y
|
||||
people," "published Z articles."]
|
||||
|
||||
[Paragraph about speaking style and audience value. "Known for
|
||||
[style descriptor] presentations that combine [element 1] with
|
||||
[element 2], [Name] leaves audiences with [concrete takeaway]."]
|
||||
|
||||
[Optional: media mentions, publications, or notable clients.]
|
||||
|
||||
Speaking topics include:
|
||||
• [Topic 1]: [One-line description]
|
||||
• [Topic 2]: [One-line description]
|
||||
• [Topic 3]: [One-line description]
|
||||
|
||||
Contact: [email or booking link]
|
||||
LinkedIn: [profile URL]
|
||||
```
|
||||
|
||||
## Step 6: Outreach Templates
|
||||
|
||||
Tailored pitch messages for different contexts.
|
||||
|
||||
### CFP Submission Cover Note
|
||||
|
||||
```
|
||||
Subject: Talk proposal: [Title]
|
||||
|
||||
Dear [CFP Committee / Organizer name],
|
||||
|
||||
I'm submitting a talk proposal on [topic] for [Event Name].
|
||||
|
||||
Why this topic now: [1-2 sentences on relevance to event theme
|
||||
and current industry trends].
|
||||
|
||||
Why me: [1-2 sentences on relevant experience, unique angle,
|
||||
or prior speaking on this topic].
|
||||
|
||||
Audience takeaway: [What attendees will be able to do after].
|
||||
|
||||
Supporting material:
|
||||
- LinkedIn profile: [URL]
|
||||
- Recent post on this topic: [URL]
|
||||
- Video from previous talk: [URL, if available]
|
||||
|
||||
Happy to adjust format, duration, or angle to fit your program.
|
||||
|
||||
Best regards,
|
||||
[Name]
|
||||
```
|
||||
|
||||
### Cold Outreach to Organizer (LinkedIn DM)
|
||||
|
||||
```
|
||||
Hi [Name],
|
||||
|
||||
I've been following [Event Name] — the [specific thing you liked]
|
||||
from last year's edition was impressive.
|
||||
|
||||
I work on [expertise area] at [company], and I have a talk on
|
||||
"[proposed title]" that I think would resonate with your audience.
|
||||
|
||||
Would you be open to a brief chat about speaker opportunities
|
||||
for [upcoming edition]?
|
||||
|
||||
[Your name]
|
||||
```
|
||||
|
||||
### Warm Outreach (Existing Connection)
|
||||
|
||||
```
|
||||
Hey [Name],
|
||||
|
||||
Thanks for [recent interaction — commenting on their post, etc.].
|
||||
|
||||
I noticed you're involved with [Event/Community]. I've been
|
||||
developing a talk on "[topic]" based on [real experience].
|
||||
|
||||
Would it be worth exploring whether this fits [Event]?
|
||||
No pressure — just thought there might be alignment.
|
||||
|
||||
Cheers,
|
||||
[Name]
|
||||
```
|
||||
|
||||
### Post-Speaking Follow-Up Sequence
|
||||
|
||||
```
|
||||
After delivering a talk, maximize the value:
|
||||
|
||||
Day 0 (same day):
|
||||
- LinkedIn post: "Just spoke at [Event] on [topic]. Key insight: [one takeaway]"
|
||||
- Thank organizer publicly (tag them)
|
||||
- Share 1-2 photos or slides
|
||||
|
||||
Day 1-2:
|
||||
- Connect with attendees who engaged (comment, DM)
|
||||
- Share a longer recap post with frameworks from the talk
|
||||
|
||||
Day 7:
|
||||
- Write a "3 things I learned from speaking at [Event]" post
|
||||
- DM organizer: "Thanks again. Would love feedback for future talks."
|
||||
|
||||
Day 14:
|
||||
- Pitch to 2-3 similar events using this talk as social proof
|
||||
- Update Featured section with talk content
|
||||
|
||||
Day 30:
|
||||
- Create an article version of the talk for LinkedIn
|
||||
- Update speaker bio with new event
|
||||
```
|
||||
|
||||
## Step 7: Speaking Pipeline Tracker
|
||||
|
||||
### Active Pipeline
|
||||
|
||||
```
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
SPEAKING PIPELINE: [Quarter/Year]
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
PITCHED:
|
||||
| Event | Date | Topic | Contact | Pitched On |
|
||||
|---------------|---------|----------------|-----------|------------|
|
||||
| [Event] | [date] | [topic] | [name] | [date] |
|
||||
|
||||
ACCEPTED:
|
||||
| Event | Date | Topic | Format | Prep Status|
|
||||
|---------------|---------|----------------|-----------|------------|
|
||||
| [Event] | [date] | [topic] | [keynote] | [draft] |
|
||||
|
||||
DELIVERED:
|
||||
| Event | Date | Topic | Audience | Outcome |
|
||||
|---------------|---------|----------------|-----------|------------|
|
||||
| [Event] | [date] | [topic] | [size] | [leads/etc]|
|
||||
|
||||
DECLINED / NO RESPONSE:
|
||||
| Event | Reason | Retry? |
|
||||
|---------------|---------------------|------------|
|
||||
| [Event] | [reason] | [date] |
|
||||
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
Quarterly Goals:
|
||||
- Pitches sent: [count] / [target]
|
||||
- Talks delivered: [count] / [target]
|
||||
- New events discovered: [count]
|
||||
- Audience reached: [total people]
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
```
|
||||
|
||||
### Speaking Progression Ladder
|
||||
|
||||
```
|
||||
Level 1: Getting Started
|
||||
─────────────────────────
|
||||
- Internal company presentations
|
||||
- Local meetup lightning talks (5-10 min)
|
||||
- LinkedIn Live with small audience
|
||||
Goal: Get 3 recordings
|
||||
|
||||
Level 2: Building Credibility
|
||||
─────────────────────────────
|
||||
- Regional meetup full talks (20-30 min)
|
||||
- Webinar guest appearances
|
||||
- Podcast guest spots
|
||||
Goal: 5+ external talks, 2+ testimonials
|
||||
|
||||
Level 3: Conference Circuit
|
||||
───────────────────────────
|
||||
- Submit to 10+ CFPs per quarter
|
||||
- Target breakout sessions (30-45 min)
|
||||
- Workshop facilitation
|
||||
Goal: 3+ conference talks/year, speaker page
|
||||
|
||||
Level 4: Keynote Stage
|
||||
───────────────────────
|
||||
- Invited (not applied) to speak
|
||||
- Paid engagements ($1K+)
|
||||
- Headliner slots
|
||||
Goal: Paid keynotes, represented by bureau
|
||||
```
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/opportunity-generation.md` — opportunity funnels, visibility ladder
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/linkedin-growth-playbook-2025-2026.md` — algorithm context
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/collaborations-guide.md` — networking strategies
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md` — content structures for positioning
|
||||
380
plugins/linkedin-thought-leadership/commands/strategy.md
Normal file
380
plugins/linkedin-thought-leadership/commands/strategy.md
Normal file
|
|
@ -0,0 +1,380 @@
|
|||
---
|
||||
name: linkedin:strategy
|
||||
description: |
|
||||
LinkedIn growth strategy based on your current follower level. Provides phase-specific
|
||||
guidance from foundation building (0-1K) through authority establishment (10K+).
|
||||
Use when the user wants a growth plan, asks about strategy, or wants to understand
|
||||
what to focus on at their level. Triggers on: "linkedin strategy", "growth plan",
|
||||
"how to grow on linkedin", "what should I focus on", "linkedin roadmap".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Growth Strategy
|
||||
|
||||
You are a LinkedIn growth strategist. Help the user create a personalized growth plan based on their current follower level and goals.
|
||||
|
||||
## Load Context
|
||||
|
||||
Read these files:
|
||||
- `references/growth-roadmaps.md` - Detailed phase roadmaps
|
||||
- `references/linkedin-growth-playbook-2025-2026.md` - Comprehensive tactics
|
||||
- `references/trajectory-strategy-adjustments.md` - Trajectory-based strategy adjustments
|
||||
- `skills/linkedin-thought-leadership/SKILL.md` - User's goals and context
|
||||
|
||||
## Step 0.5: Auto-Detect from State
|
||||
|
||||
Before asking questions, check `~/.claude/linkedin-thought-leadership.local.md`:
|
||||
|
||||
- If `follower_count > 0`: Auto-detect the user's phase. Skip the "How many followers?" question in Step 1.
|
||||
- 0-1K → Phase 0: Foundation
|
||||
- 1K-3K → Phase 1: Traction
|
||||
- 3K-6K → Phase 2: Acceleration
|
||||
- 6K-10K → Phase 3: Authority
|
||||
- 10K+ → Phase 4: Scale
|
||||
- If `follower_count` is 0 or missing: Proceed normally with Step 1 questions. After the session, suggest updating `follower_count` in the state file.
|
||||
|
||||
When auto-detected, inform the user: "Based on your tracked follower count of X, you're in Phase Y: [Name]."
|
||||
|
||||
## Step 1: Assess Current State
|
||||
|
||||
Use AskUserQuestion to gather information (skip follower question if auto-detected above):
|
||||
|
||||
**Where are you now?**
|
||||
|
||||
1. How many LinkedIn followers do you have?
|
||||
- Under 500
|
||||
- 500-1,000
|
||||
- 1,000-3,000
|
||||
- 3,000-6,000
|
||||
- 6,000-10,000
|
||||
- 10,000+
|
||||
|
||||
2. How consistently have you been posting?
|
||||
- Just starting (less than 30 days)
|
||||
- Building habits (1-3 months)
|
||||
- Established routine (3+ months)
|
||||
- Inconsistent (gaps of 1+ weeks)
|
||||
|
||||
3. What are your main goals? (Choose top 2)
|
||||
- Build thought leadership & authority
|
||||
- Attract speaking opportunities
|
||||
- Network with peers/influencers
|
||||
- Generate consulting/business leads
|
||||
- Build personal brand for career
|
||||
- Monetize through courses/content
|
||||
|
||||
## Step 2: Identify Current Phase
|
||||
|
||||
Based on follower count, place user in the right phase:
|
||||
|
||||
### Phase 0: Foundation Building (Under 1,000)
|
||||
|
||||
**Where you are:**
|
||||
- Algorithm barely knows you exist
|
||||
- Network is existing contacts
|
||||
- Voice not yet developed
|
||||
- Learning what works
|
||||
|
||||
**Focus areas:**
|
||||
- Profile optimization (360Brew critical)
|
||||
- Finding your voice
|
||||
- Establishing consistency
|
||||
- Building initial engagement habits
|
||||
|
||||
### Phase 1: Foundation to Traction (1,000-3,000)
|
||||
|
||||
**Where you are:**
|
||||
- Algorithm starting to learn you
|
||||
- Network is mostly existing contacts
|
||||
- Content still experimental
|
||||
- Voice developing
|
||||
|
||||
**Focus areas:**
|
||||
- Topical consistency (3 topics, religiously)
|
||||
- First-hour engagement (5x5x5 method)
|
||||
- Quality commenting (15+ words on larger creators)
|
||||
- Profile-content alignment
|
||||
|
||||
### Phase 2: Acceleration (3,000-6,000)
|
||||
|
||||
**Where you are:**
|
||||
- Algorithm recognizes expertise
|
||||
- Some posts break into broader network
|
||||
- Voice is established
|
||||
- Patterns are emerging
|
||||
|
||||
**Focus areas:**
|
||||
- Strategic collaborations
|
||||
- Format diversification (carousels, documents, video)
|
||||
- Article SEO (long-form for search discovery)
|
||||
- Newsletter launch (if ready)
|
||||
- DM relationship building
|
||||
|
||||
### Phase 3: Authority (6,000-10,000)
|
||||
|
||||
**Where you are:**
|
||||
- Known in your niche
|
||||
- Posts regularly reach beyond network
|
||||
- Inbound opportunities emerging
|
||||
- Content machine running smoothly
|
||||
|
||||
**Focus areas:**
|
||||
- Original insights and frameworks
|
||||
- Cross-platform presence
|
||||
- Community building
|
||||
- Speaking/podcast appearances
|
||||
- Lead magnets and monetization setup
|
||||
|
||||
### Phase 4: Scale (10,000+)
|
||||
|
||||
**Where you are:**
|
||||
- Established authority
|
||||
- Regular inbound opportunities
|
||||
- Content has compounding effects
|
||||
- Platform for business development
|
||||
|
||||
**Focus areas:**
|
||||
- Signature frameworks
|
||||
- Premium monetization
|
||||
- Team/delegation
|
||||
- Platform leverage
|
||||
- Strategic selectivity
|
||||
|
||||
## Step 3: Provide Phase-Specific Strategy
|
||||
|
||||
Based on their phase, provide detailed guidance.
|
||||
|
||||
### For Phase 0-1 (Under 3,000)
|
||||
|
||||
**Weekly Commitments:**
|
||||
- Post 3-5x per week (same days/times)
|
||||
- 20 min daily strategic commenting
|
||||
- Respond to all comments within 2 hours
|
||||
- Track engagement in LinkedIn Analytics
|
||||
|
||||
**Daily Time Investment:**
|
||||
- 15 min: Strategic commenting (5x5x5 method)
|
||||
- 15-30 min: Post creation or comment responses
|
||||
- Total: 30-45 minutes
|
||||
|
||||
**Key Activities:**
|
||||
|
||||
| Activity | Frequency | Purpose |
|
||||
|----------|-----------|---------|
|
||||
| Core expertise posts | 3-5x/week | Algorithm learning |
|
||||
| Strategic commenting | Daily 20 min | Network expansion |
|
||||
| Profile optimization | Monthly review | 360Brew validation |
|
||||
| Content experimentation | Ongoing | Finding what works |
|
||||
|
||||
**Milestone Markers to Track:**
|
||||
- [ ] 100+ engagements on a single post
|
||||
- [ ] First "viral" post (10x normal reach)
|
||||
- [ ] 10+ consistent commenters
|
||||
- [ ] 5+ inbound connection requests per week
|
||||
- [ ] First collaboration inquiry
|
||||
|
||||
**Expected timeline:** 3-4 months with consistent effort
|
||||
**Growth rate:** 100-200 new followers/month
|
||||
|
||||
### For Phase 2 (3,000-6,000)
|
||||
|
||||
**Weekly Commitments:**
|
||||
- Post 4-5x per week
|
||||
- 30-45 min daily engagement
|
||||
- 1-2 LinkedIn Articles per month
|
||||
- Active DM relationship building
|
||||
|
||||
**Daily Time Investment:**
|
||||
- 30 min: Strategic engagement
|
||||
- 15-30 min: Posting and responses
|
||||
- Total: 45-60 minutes
|
||||
|
||||
**Key Activities:**
|
||||
|
||||
| Activity | Frequency | Purpose |
|
||||
|----------|-----------|---------|
|
||||
| Core expertise posts | 4-5x/week | Authority building |
|
||||
| LinkedIn Articles | 1-2x/month | SEO and depth |
|
||||
| Strategic collaborations | 1x/month | Network expansion |
|
||||
| DM relationship building | 5-10/week | Inner circle growth |
|
||||
| Content repurposing | Weekly | Maximize each idea |
|
||||
|
||||
**Milestone Markers to Track:**
|
||||
- [ ] First speaking invitation
|
||||
- [ ] First paid opportunity (any kind)
|
||||
- [ ] 50+ consistent commenters
|
||||
- [ ] 20+ inbound connection requests per week
|
||||
- [ ] Post reaching 10,000+ views
|
||||
- [ ] First media mention or interview
|
||||
|
||||
**Expected timeline:** 3-4 months with elevated effort
|
||||
**Growth rate:** 200-400 new followers/month
|
||||
|
||||
### For Phase 3 (6,000-10,000)
|
||||
|
||||
**Weekly Commitments:**
|
||||
- Post 3-5x per week (quality over quantity)
|
||||
- Maintain engagement routine
|
||||
- Monthly speaking/podcast appearances
|
||||
- Develop signature frameworks
|
||||
|
||||
**Key Activities:**
|
||||
|
||||
| Activity | Frequency | Purpose |
|
||||
|----------|-----------|---------|
|
||||
| Core expertise posts | 3-5x/week | Maintain authority |
|
||||
| Thought leadership pieces | 2-3x/month | Differentiation |
|
||||
| Speaking/podcasts | Monthly | Off-platform visibility |
|
||||
| Collaboration amplification | 2x/month | Network leverage |
|
||||
| Lead magnets | Create 1-2 | Funnel building |
|
||||
|
||||
**Milestone Markers to Track:**
|
||||
- [ ] Multiple speaking engagements completed
|
||||
- [ ] Regular consulting inquiries
|
||||
- [ ] 100+ consistent commenters
|
||||
- [ ] Posts regularly exceed 20,000 views
|
||||
- [ ] Industry recognition (awards, features)
|
||||
- [ ] First major monetization success
|
||||
|
||||
**Expected timeline:** 3-4 months with strategic focus
|
||||
**Growth rate:** 300-500 new followers/month
|
||||
|
||||
## Step 3.5: Apply Trajectory Adjustments
|
||||
|
||||
If milestone data is available from `~/.claude/linkedin-thought-leadership.local.md`, overlay trajectory-specific adjustments on top of the phase strategy.
|
||||
|
||||
### Determine Schedule Status
|
||||
|
||||
From the state file, compare current growth rate vs `growth_rate_needed`:
|
||||
- **SIGNIFICANTLY BEHIND:** Actual < 50% of needed rate
|
||||
- **BEHIND:** Actual 50-80% of needed rate
|
||||
- **ON TRACK:** Actual 80-120% of needed rate
|
||||
- **AHEAD:** Actual > 120% of needed rate
|
||||
- **ACHIEVED:** `follower_count >= follower_target`
|
||||
|
||||
### Present Trajectory Overlay
|
||||
|
||||
Using `references/trajectory-strategy-adjustments.md` as the source, show how the phase strategy should be adjusted:
|
||||
|
||||
```markdown
|
||||
### Trajectory Adjustment: [STATUS]
|
||||
|
||||
Your growth rate is [X]% of the needed rate. Here's how your phase strategy adapts:
|
||||
|
||||
| Dimension | Phase Baseline | Trajectory Adjustment | Impact |
|
||||
|-----------|---------------|----------------------|--------|
|
||||
| Posting frequency | [from phase strategy] | [from trajectory] | [expected effect] |
|
||||
| Engagement intensity | [from phase strategy] | [from trajectory] | [expected effect] |
|
||||
| Format mix | [from phase strategy] | [from trajectory] | [expected effect] |
|
||||
| Collaboration pace | [from phase strategy] | [from trajectory] | [expected effect] |
|
||||
| Content emphasis | [from phase strategy] | [from trajectory] | [expected effect] |
|
||||
| Goal management | [current target] | [from trajectory] | [expected effect] |
|
||||
```
|
||||
|
||||
Also include the phase-specific primary lever from the Phase-Specific Trajectory Modifiers table in the reference file.
|
||||
|
||||
**If no milestone data:** Skip this step. Note: "Trajectory adjustments require follower tracking. Set `follower_count` in state file to enable."
|
||||
|
||||
## Step 4: Address Common Stall Points
|
||||
|
||||
Based on where they're stuck:
|
||||
|
||||
**Stuck at 1,500-2,000**
|
||||
- Diagnosis: Inconsistent posting or topic scatter
|
||||
- Fix: Double down on core topics, increase frequency
|
||||
|
||||
**Stuck at 3,000-4,000**
|
||||
- Diagnosis: Lacking differentiation or collaboration
|
||||
- Fix: Develop unique angle, start strategic partnerships
|
||||
|
||||
**Stuck at 5,000-6,000**
|
||||
- Diagnosis: Plateaued in current network
|
||||
- Fix: Cross-platform visibility, speaking engagements
|
||||
|
||||
**Stuck at 8,000-9,000**
|
||||
- Diagnosis: Authority not converting to growth
|
||||
- Fix: More shareable content, develop signature frameworks
|
||||
|
||||
## Step 5: Create 90-Day Action Plan
|
||||
|
||||
Based on their phase, create a specific 90-day plan:
|
||||
|
||||
**Month 1: [Phase-specific focus]**
|
||||
- Week 1: [Specific actions]
|
||||
- Week 2: [Specific actions]
|
||||
- Week 3-4: [Specific actions]
|
||||
|
||||
**Month 2: [Phase-specific focus]**
|
||||
- Week 5-6: [Specific actions]
|
||||
- Week 7-8: [Specific actions]
|
||||
|
||||
**Month 3: [Phase-specific focus]**
|
||||
- Week 9-10: [Specific actions]
|
||||
- Week 11-12: [Specific actions]
|
||||
|
||||
## Step 6: Set Tracking Metrics
|
||||
|
||||
Provide metrics to track monthly:
|
||||
|
||||
| Metric | Target for Phase |
|
||||
|--------|------------------|
|
||||
| New followers/month | [phase-specific] |
|
||||
| Avg engagement rate | [phase-specific] |
|
||||
| Profile views/week | [phase-specific] |
|
||||
| Connection requests/week | [phase-specific] |
|
||||
| Inbound opportunities | [phase-specific] |
|
||||
|
||||
### 10K Milestone Metrics
|
||||
|
||||
If milestone data is available from state file, also show:
|
||||
|
||||
| Metric | Value |
|
||||
|--------|-------|
|
||||
| Current followers | [from state] |
|
||||
| Target | [follower_target] by [target_date] |
|
||||
| Followers needed | [calculated] |
|
||||
| Required rate | [growth_rate_needed] followers/month |
|
||||
| Schedule status | SIGNIFICANTLY BEHIND / BEHIND / ON TRACK / AHEAD |
|
||||
| Trajectory adjustment | [primary lever from trajectory reference] |
|
||||
|
||||
## The Reality Check
|
||||
|
||||
Share realistic timeline expectations:
|
||||
|
||||
| Path | Timeline to 10K |
|
||||
|------|-----------------|
|
||||
| Best case (all factors aligned) | 8-10 months |
|
||||
| Typical case (consistent effort) | 12-18 months |
|
||||
| Slower path (2-3x/week) | 18-24 months |
|
||||
|
||||
**What accelerates:**
|
||||
- Existing large network
|
||||
- Strong offline credentials
|
||||
- High-quality collaborations
|
||||
- Cross-platform visibility
|
||||
|
||||
**What slows:**
|
||||
- Inconsistent posting
|
||||
- Topic scatter
|
||||
- Low engagement effort
|
||||
- Poor profile-content alignment
|
||||
|
||||
## The Compound Effect
|
||||
|
||||
Remind them of the long-term view:
|
||||
- Justin Welsh: 4 years to 750,000 followers
|
||||
- Adam Robinson: 4 years daily posting before viral momentum
|
||||
- Lea Turner: 2.5 years from 400 to 150,000 followers
|
||||
|
||||
**The winners commit to years, not weeks.**
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `references/growth-roadmaps.md` - Detailed phase roadmaps
|
||||
- `references/linkedin-growth-playbook-2025-2026.md` - Comprehensive tactics
|
||||
- `references/trajectory-strategy-adjustments.md` - Trajectory-based strategy adjustments
|
||||
- `references/collaborations-guide.md` - Partnership strategies
|
||||
- `references/opportunity-generation.md` - Business development
|
||||
- `references/newsletter-strategy-guide.md` - For 5K+ followers
|
||||
338
plugins/linkedin-thought-leadership/commands/templates.md
Normal file
338
plugins/linkedin-thought-leadership/commands/templates.md
Normal file
|
|
@ -0,0 +1,338 @@
|
|||
---
|
||||
name: linkedin:templates
|
||||
description: |
|
||||
Browse and apply proven LinkedIn post templates. Quick access to 8 post types with
|
||||
fill-in-the-blank structures. Use when the user knows what type of post they want
|
||||
but needs a starting structure. Triggers on: "post template", "linkedin template",
|
||||
"give me a template", "post structure", "fill in the blank post".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Post Templates
|
||||
|
||||
You are a LinkedIn template assistant. Help the user select and apply the right template for their content.
|
||||
|
||||
## Load Context
|
||||
|
||||
Read these files for templates and examples:
|
||||
- `assets/templates/post-type-templates.md` - Complete template library
|
||||
- `assets/quick-post-resources.md` - Hooks and CTAs bank
|
||||
- `skills/linkedin-thought-leadership/SKILL.md` - User's voice profile
|
||||
|
||||
## Available Templates
|
||||
|
||||
Present the template options:
|
||||
|
||||
**Which type of post do you want to create?**
|
||||
|
||||
| Template | Best For | Example Trigger |
|
||||
|----------|----------|-----------------|
|
||||
| 1. Reaction Post | News, changes, trends | "Something just happened in my industry" |
|
||||
| 2. Quick Tip Post | Shortcuts, fixes, learnings | "I discovered something useful" |
|
||||
| 3. Observation Post | Patterns, connections | "I've been noticing something" |
|
||||
| 4. Hot Take Post | Contrarian opinions | "I disagree with conventional wisdom" |
|
||||
| 5. Failure/Mistake Post | Lessons from errors | "Something went wrong" |
|
||||
| 6. Question Post | Gathering perspectives | "I want to hear from others" |
|
||||
| 7. Curation Post | Sharing others' content | "I found something worth sharing" |
|
||||
| 8. One-Liner Post | Punchy insights | "I have a single powerful statement" |
|
||||
|
||||
Use AskUserQuestion to let them choose, or infer from their input.
|
||||
|
||||
---
|
||||
|
||||
## Template 1: Reaction Post
|
||||
|
||||
**Use when:** News drops, something changes in your industry, you see a trend emerging.
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
[Industry event/news - state what happened]
|
||||
|
||||
My take: [Your perspective in 1-2 sentences]
|
||||
|
||||
[Question for audience OR prediction about what this means]
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```
|
||||
Microsoft dropped a new Copilot update yesterday.
|
||||
|
||||
Here's what caught my attention: [specific feature]
|
||||
finally addresses [common complaint].
|
||||
|
||||
Has anyone tested it yet? Curious if the reality
|
||||
matches the promise.
|
||||
```
|
||||
|
||||
**Character target:** 200-400 characters
|
||||
|
||||
---
|
||||
|
||||
## Template 2: Quick Tip Post
|
||||
|
||||
**Use when:** You learned something useful, found a shortcut, discovered a fix.
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
[Bold claim about the tip]
|
||||
|
||||
Here's why: [Brief explanation - 1-2 sentences]
|
||||
|
||||
[How to apply it OR invitation to share their version]
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```
|
||||
The 2-minute rule changed how I handle [task].
|
||||
|
||||
If it takes less than 2 minutes, do it now.
|
||||
Seems obvious, but I resisted for years.
|
||||
|
||||
Now my [specific result] is [specific improvement].
|
||||
```
|
||||
|
||||
**Character target:** 200-400 characters
|
||||
|
||||
---
|
||||
|
||||
## Template 3: Observation Post
|
||||
|
||||
**Use when:** You noticed a pattern, saw something interesting, made a connection.
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
I've noticed [pattern/trend].
|
||||
|
||||
[Evidence or example - specific, concrete]
|
||||
|
||||
Anyone else seeing this?
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```
|
||||
I've noticed that the AI projects that actually
|
||||
ship have something in common:
|
||||
|
||||
They start with a problem, not a technology.
|
||||
|
||||
Simple, but I see the opposite approach fail
|
||||
constantly. Anyone else?
|
||||
```
|
||||
|
||||
**Character target:** 150-350 characters
|
||||
|
||||
---
|
||||
|
||||
## Template 4: Hot Take Post
|
||||
|
||||
**Use when:** You disagree with common wisdom, have a controversial opinion, want to start debate.
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
Unpopular opinion: [Your take]
|
||||
|
||||
[Why you believe this - 1-2 sentences]
|
||||
|
||||
Change my mind.
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```
|
||||
Unpopular opinion: Most "AI strategies" are
|
||||
just vendor slide decks with your logo added.
|
||||
|
||||
Real strategy requires understanding your
|
||||
problems before browsing solutions.
|
||||
|
||||
Fight me.
|
||||
```
|
||||
|
||||
**Character target:** 150-300 characters
|
||||
|
||||
---
|
||||
|
||||
## Template 5: Failure/Mistake Post
|
||||
|
||||
**Use when:** Something went wrong, you made an error, you learned from a mistake.
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
I made a mistake with [topic/project].
|
||||
|
||||
Here's what went wrong: [Brief explanation]
|
||||
|
||||
Lesson learned: [What you'd do differently]
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```
|
||||
Launched a Copilot agent last month.
|
||||
Adoption rate: 12%.
|
||||
|
||||
The mistake: We built what we thought users
|
||||
needed instead of asking them.
|
||||
|
||||
Rebuilding with actual user input this time.
|
||||
```
|
||||
|
||||
**Character target:** 200-400 characters
|
||||
|
||||
---
|
||||
|
||||
## Template 6: Question Post
|
||||
|
||||
**Use when:** You want to spark discussion, gather perspectives, learn from your network.
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
[Context-setting statement]
|
||||
|
||||
[Specific question]
|
||||
|
||||
I'll share my thinking in the comments.
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```
|
||||
Talking to a lot of AI teams lately about
|
||||
governance frameworks.
|
||||
|
||||
Genuine question: How do you balance
|
||||
"move fast" with "don't break things"?
|
||||
|
||||
Share what's working (or not).
|
||||
```
|
||||
|
||||
**Character target:** 150-300 characters
|
||||
|
||||
---
|
||||
|
||||
## Template 7: Curation Post
|
||||
|
||||
**Use when:** You found something worth sharing, want to add your perspective to existing content.
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
[What you found/read/watched]
|
||||
|
||||
[Your specific takeaway - not just "it was great"]
|
||||
|
||||
[Link in comments or tag the creator]
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```
|
||||
Read [Author]'s piece on [topic] three times.
|
||||
|
||||
The part that stuck: [specific quote or idea]
|
||||
|
||||
This explains why [your connection to your work].
|
||||
|
||||
Link in first comment.
|
||||
```
|
||||
|
||||
**Character target:** 200-400 characters
|
||||
|
||||
---
|
||||
|
||||
## Template 8: One-Liner Post
|
||||
|
||||
**Use when:** You have a punchy insight that doesn't need explanation.
|
||||
|
||||
**Structure:**
|
||||
```
|
||||
[Single powerful statement]
|
||||
```
|
||||
|
||||
**Examples:**
|
||||
```
|
||||
The best processes are invisible.
|
||||
The worst processes require training.
|
||||
```
|
||||
|
||||
```
|
||||
Every "AI transformation" I've seen succeed
|
||||
started with spreadsheets and post-its.
|
||||
```
|
||||
|
||||
**Character target:** 50-150 characters
|
||||
|
||||
**Note:** Use sparingly (1 in 10 posts). Requires established credibility.
|
||||
|
||||
---
|
||||
|
||||
## Apply the Template
|
||||
|
||||
After they choose a template:
|
||||
|
||||
1. Ask what content/insight they want to put into the template
|
||||
2. Fill in the template with their specific content
|
||||
3. Match their voice profile from SKILL.md
|
||||
4. Provide the completed post with character count
|
||||
5. Offer one alternative version with different hook or angle
|
||||
|
||||
## Template Selection by Angle
|
||||
|
||||
If they describe their content but not which template:
|
||||
|
||||
| Their Content | Recommended Template |
|
||||
|---------------|---------------------|
|
||||
| Industry news just dropped | Reaction Post |
|
||||
| Found a useful shortcut | Quick Tip Post |
|
||||
| Noticed a pattern | Observation Post |
|
||||
| Disagree with everyone | Hot Take Post |
|
||||
| Something went wrong | Failure/Mistake Post |
|
||||
| Want others' opinions | Question Post |
|
||||
| Found great content | Curation Post |
|
||||
| Have a punchy insight | One-Liner Post |
|
||||
|
||||
## Hooks Bank by Template
|
||||
|
||||
For each template, offer hook alternatives from `assets/quick-post-resources.md`:
|
||||
|
||||
**Reaction hooks:**
|
||||
- "[Event] just happened. Here's what it means:"
|
||||
- "My take on [news]:"
|
||||
|
||||
**Tip hooks:**
|
||||
- "Stop [common mistake]. Here's why:"
|
||||
- "Wish I knew this earlier about [topic]:"
|
||||
|
||||
**Observation hooks:**
|
||||
- "There's a pattern I keep seeing:"
|
||||
- "I've noticed [pattern]. Anyone else?"
|
||||
|
||||
**Hot take hooks:**
|
||||
- "Unpopular opinion: [take]"
|
||||
- "What everyone gets wrong about [topic]:"
|
||||
|
||||
**Failure hooks:**
|
||||
- "I made a mistake with [topic]:"
|
||||
- "[Metric] - here's what went wrong:"
|
||||
|
||||
**Question hooks:**
|
||||
- "Genuine question: [specific question]"
|
||||
- "How do you handle [challenge]?"
|
||||
|
||||
**Curation hooks:**
|
||||
- "Best thing I've read this week on [topic]:"
|
||||
- "[Creator] nailed something I've been thinking about:"
|
||||
|
||||
## Quality Check After Applying
|
||||
|
||||
Verify the completed post:
|
||||
|
||||
- [ ] Hook works in 140 characters
|
||||
- [ ] On-topic for their expertise
|
||||
- [ ] Clear value delivered
|
||||
- [ ] Ends with engagement prompt
|
||||
- [ ] Matches their voice profile
|
||||
- [ ] No external links in body
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `assets/templates/post-type-templates.md` - Full template library with examples
|
||||
- `assets/quick-post-resources.md` - Hooks and CTAs bank
|
||||
- `references/engagement-frameworks.md` - Hook psychology and CTA patterns
|
||||
212
plugins/linkedin-thought-leadership/commands/video.md
Normal file
212
plugins/linkedin-thought-leadership/commands/video.md
Normal file
|
|
@ -0,0 +1,212 @@
|
|||
---
|
||||
name: linkedin:video
|
||||
description: |
|
||||
Create LinkedIn video scripts with pacing, visual cues, captions, thumbnail suggestions,
|
||||
and first-comment strategy. Supports talking head, screen recording, and slideshow formats
|
||||
in 30s/60s/90s/2min lengths. Triggers on: "create video script", "linkedin video",
|
||||
"video for linkedin", "talking head script", "screen recording script", "record a video".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Glob
|
||||
- Grep
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Video Script Creation Workflow
|
||||
|
||||
You are a LinkedIn video scripting assistant. Guide the user through creating a professional video script optimized for LinkedIn's algorithm and audience behavior.
|
||||
|
||||
## Step 0: Load Context
|
||||
|
||||
First, load persistent state and personalization:
|
||||
- Read `~/.claude/linkedin-thought-leadership.local.md` for posting state (streak, weekly progress, recent topics)
|
||||
- Read `skills/linkedin-thought-leadership/SKILL.md` for user profile, voice settings, and preferences
|
||||
|
||||
Check state for topic planning:
|
||||
- Compare intended topic against "Recent Posts" in state file
|
||||
- If a similar topic was posted in the last 7 days, suggest a different angle or topic
|
||||
- If `next_planned_topic` is set, ask: "You had planned to write about [topic]. Want to use that for this video?"
|
||||
|
||||
Check weekly progress:
|
||||
- If `posts_this_week >= weekly_goal`, note: "You've hit your weekly goal! This is a bonus video."
|
||||
- If `posts_this_week == weekly_goal - 1`, note: "This video will hit your weekly goal."
|
||||
|
||||
Load video-specific references:
|
||||
- Read `references/video-strategy-guide.md` for script templates, pacing, and production guidance
|
||||
- Read `references/linkedin-formats.md` (Video Content Deep Dive section) for algorithm data and technical specs
|
||||
|
||||
Check for existing assets:
|
||||
- `assets/voice-samples/` — Match the user's natural voice (REQUIRED before scripting)
|
||||
- `assets/examples/high-engagement-posts.md` — Study successful patterns
|
||||
|
||||
## Step 1: Choose Video Type
|
||||
|
||||
Use AskUserQuestion:
|
||||
|
||||
**What type of video do you want to create?**
|
||||
1. **Talking head** — You on camera sharing an insight, story, or opinion
|
||||
2. **Screen recording** — Walkthrough of a tool, demo, or process
|
||||
3. **Slideshow** — Visual slides with voiceover narration
|
||||
4. **Convert a text post** — Turn an existing post into a video script
|
||||
|
||||
If they choose "Convert a text post", ask them to paste or reference the post.
|
||||
|
||||
## Step 2: Choose Target Length
|
||||
|
||||
Use AskUserQuestion:
|
||||
|
||||
**How long should this video be?**
|
||||
1. **30 seconds** (75 words) — Single punchy insight or quick tip
|
||||
2. **60 seconds** (150 words) — Framework intro or single lesson
|
||||
3. **90 seconds** (225 words) — Complete framework or story with lesson (Recommended)
|
||||
4. **2 minutes** (300 words) — Detailed story or multi-step process
|
||||
|
||||
Default recommendation: **90 seconds** is the sweet spot for LinkedIn — deep enough to deliver value, short enough for high completion rates.
|
||||
|
||||
## Step 3: Topic and Angle Selection
|
||||
|
||||
Follow the same flow as `/linkedin:post`:
|
||||
|
||||
1. Ask what they want the video to be about (if not already clear)
|
||||
2. Read `references/thought-leadership-angles.md` for the 8 universal angles
|
||||
3. Present 2-3 angle options via AskUserQuestion
|
||||
4. Verify topic doesn't duplicate recent posts (check state file)
|
||||
5. Confirm topic aligns with user's 5 core expertise areas
|
||||
|
||||
## Step 4: Generate Script
|
||||
|
||||
Delegate to the `video-scripter` agent for script generation. The agent will:
|
||||
|
||||
1. Calculate word budget based on selected length (duration × 2.5 wps)
|
||||
2. Select the appropriate script template from `references/video-strategy-guide.md`
|
||||
3. Write the full script with:
|
||||
- Timing markers (`[0:00-0:03]`, etc.)
|
||||
- Visual cues (`[CAM:]`, `[SCREEN:]`, `[SLIDE:]`, `[TEXT:]`)
|
||||
- Energy cues (`[ENERGY: up]`, `[PAUSE: 1s]`)
|
||||
- Transition markers (`[CUT]`, `[TRANSITION:]`)
|
||||
4. Match voice against `assets/voice-samples/`
|
||||
5. Generate captions, thumbnail suggestion, post caption, and first comment
|
||||
|
||||
## Step 5: Quality Check
|
||||
|
||||
Before presenting, verify the script passes the video quality gate:
|
||||
|
||||
**The 3-Second Test:**
|
||||
- [ ] Hook grabs attention in first 3 seconds (8 words or fewer)
|
||||
- [ ] No "Hey everyone" or "So today I'm going to talk about..."
|
||||
|
||||
**Natural Speech Test:**
|
||||
- [ ] Uses contractions (I've, don't, here's)
|
||||
- [ ] Short sentences (max 15 words)
|
||||
- [ ] Sounds natural when read aloud
|
||||
- [ ] No corporate buzzwords
|
||||
|
||||
**Word Count Test:**
|
||||
- [ ] Within ±10% of target word count
|
||||
- [ ] Section allocation follows template proportions
|
||||
|
||||
**Energy Test:**
|
||||
- [ ] Energy varies throughout (never flat/monotone)
|
||||
- [ ] Pauses marked at key moments
|
||||
- [ ] Energy peaks at hook and takeaway
|
||||
|
||||
**Completeness Test:**
|
||||
- [ ] Captions written and synced
|
||||
- [ ] Post caption (200-400 chars) included
|
||||
- [ ] Thumbnail suggestion included
|
||||
- [ ] First comment pre-written
|
||||
- [ ] Topic aligns with expertise pillars
|
||||
- [ ] No external links in post caption
|
||||
|
||||
## Step 6: Present the Script
|
||||
|
||||
Present using the standardized output format:
|
||||
|
||||
```
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
VIDEO SCRIPT: [Title]
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
Type: [talking head / screen recording / slideshow]
|
||||
Length: [30s / 60s / 90s / 2min]
|
||||
Words: [count] (at 2.5 wps)
|
||||
Topic: [content pillar alignment]
|
||||
Angle: [from 8 thought leadership angles]
|
||||
|
||||
━━━ SCRIPT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
[Full script with timing, visual cues, energy cues]
|
||||
|
||||
━━━ CAPTIONS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
[Line-by-line caption text with timing]
|
||||
|
||||
━━━ POST CAPTION ━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
[200-400 char text to accompany the video]
|
||||
|
||||
━━━ THUMBNAIL ━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
Expression: [ideal facial expression]
|
||||
Text overlay: [3-5 words]
|
||||
Style: [minimal / branded / text-heavy]
|
||||
|
||||
━━━ FIRST COMMENT ━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
[Pre-written first comment]
|
||||
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
```
|
||||
|
||||
## Step 7: Refinement Cycle
|
||||
|
||||
Use AskUserQuestion:
|
||||
|
||||
**How does this script look?**
|
||||
1. **Ready to record** — Script is good to go
|
||||
2. **Adjust the hook** — Try a different opening
|
||||
3. **Change the pacing** — Too fast or too slow
|
||||
4. **Simplify the language** — Make it more conversational
|
||||
5. **Try a different angle** — Same topic, new perspective
|
||||
6. **Change the length** — Make it shorter or longer
|
||||
|
||||
Iterate until satisfied.
|
||||
|
||||
## Step 8: Save and Update State
|
||||
|
||||
Save the final script to `assets/drafts/`:
|
||||
|
||||
```
|
||||
video-[YYYY-MM-DD]-[slug]-[type]-[length].md
|
||||
```
|
||||
|
||||
**Pre-Recording Reminder:**
|
||||
|
||||
```
|
||||
Before you record:
|
||||
- [ ] Read the script aloud once (practice run)
|
||||
- [ ] Set up lighting (natural light facing window, or ring light)
|
||||
- [ ] Check audio (lavalier mic or quiet room)
|
||||
- [ ] Vertical format: 4:5 (1080×1350) for LinkedIn
|
||||
- [ ] Clean background
|
||||
- [ ] Have captions tool ready (CapCut, Descript, or Kapwing)
|
||||
- [ ] First comment ready to paste immediately after posting
|
||||
```
|
||||
|
||||
**State Update:**
|
||||
After the script is finalized, update `~/.claude/linkedin-thought-leadership.local.md`:
|
||||
- Set `last_post_date` to today's date
|
||||
- Check if ISO week changed — if so, reset `posts_this_week` to 0, update `current_week`
|
||||
- Increment `posts_this_week`
|
||||
- Update streak: increment if consecutive day, reset to 1 if gap > 2 days
|
||||
- Add to "Recent Posts": `[YYYY-MM-DD] "Hook text..." [VIDEO/type/length] - topic`
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `references/video-strategy-guide.md` — Script templates, pacing, production
|
||||
- `references/linkedin-formats.md` — Video specs, algorithm, technical requirements
|
||||
- `references/engagement-frameworks.md` — Hook types, CTAs
|
||||
- `references/thought-leadership-angles.md` — 8 universal angles
|
||||
- `references/algorithm-signals-reference.md` — Algorithm mechanics
|
||||
- `assets/checklists/quality-scorecard.md` — Pre-publish check
|
||||
Loading…
Add table
Add a link
Reference in a new issue