feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command
Add /ultraresearch-local for structured research combining local codebase analysis with external knowledge via parallel agent swarms. Produces research briefs with triangulation, confidence ratings, and source quality assessment. New command: /ultraresearch-local with modes --quick, --local, --external, --fg. New agents: research-orchestrator (opus), docs-researcher, community-researcher, security-researcher, contrarian-researcher, gemini-bridge (all sonnet). New template: research-brief-template.md. Integration: --research flag in /ultraplan-local accepts pre-built research briefs (up to 3), enriches the interview and exploration phases. Planning orchestrator cross-references brief findings during synthesis. Design principle: Context Engineering — right information to right agent at right time. Research briefs are structured artifacts in the pipeline: ultraresearch → brief → ultraplan --research → plan → ultraexecute. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen
commit
40986575b6
150 changed files with 34216 additions and 0 deletions
72
assets/README.md
Normal file
72
assets/README.md
Normal file
|
|
@ -0,0 +1,72 @@
|
|||
# Personal LinkedIn Assets
|
||||
|
||||
This folder contains YOUR personalized content, frameworks, and insights that make this skill uniquely valuable to you.
|
||||
|
||||
## How Assets Are Used
|
||||
|
||||
When you ask Claude to create content, it will:
|
||||
1. Check your PERSONALIZATION SETTINGS in SKILL.md
|
||||
2. Reference relevant assets from these folders
|
||||
3. Blend your authentic voice/examples with LinkedIn best practices
|
||||
4. Generate content that sounds like YOU, optimized for the algorithm
|
||||
|
||||
## Folder Structure
|
||||
|
||||
### `/examples/`
|
||||
Store your best-performing posts for pattern analysis. Claude will study these to understand what works for YOUR audience and replicate those patterns in new content.
|
||||
|
||||
### `/templates/`
|
||||
Your custom post templates. When you develop a structure that works consistently, save it here so Claude can apply it to new content.
|
||||
|
||||
### `/frameworks/`
|
||||
Your proprietary frameworks, models, and methodologies. When creating content, Claude will reference YOUR frameworks instead of generic ones.
|
||||
|
||||
### `/case-studies/`
|
||||
Real examples from your work. Claude uses these for credibility and specificity instead of making up generic scenarios.
|
||||
|
||||
### `/research/`
|
||||
Industry research, data, and trends specific to your domain. Helps Claude create data-driven posts with current, relevant information.
|
||||
|
||||
### `/voice-samples/`
|
||||
Examples of your authentic writing from various contexts. Claude analyzes these to match your natural voice and style.
|
||||
|
||||
### `/audience-insights/`
|
||||
Your analytics, demographics, and engagement patterns. Claude uses this to optimize content for YOUR specific audience, not generic best practices.
|
||||
|
||||
### `/competitors/`
|
||||
Analysis of peers and influencers in your space. Helps identify content gaps and opportunities for differentiation.
|
||||
|
||||
## Maintenance Schedule
|
||||
|
||||
### Weekly (5 minutes)
|
||||
- Add your best post from the week to `/examples/`
|
||||
- Update posting time insights in `/audience-insights/engagement-patterns.md`
|
||||
|
||||
### Monthly (15 minutes)
|
||||
- Analyze patterns in `/examples/` and document learnings
|
||||
- Update demographics in `/audience-insights/` based on LinkedIn analytics
|
||||
- Add any new frameworks developed to `/frameworks/`
|
||||
|
||||
### Quarterly (30 minutes)
|
||||
- Refresh industry data in `/research/`
|
||||
- Update competitor analysis in `/competitors/`
|
||||
- Review and refine voice samples in `/voice-samples/`
|
||||
|
||||
## Priority Hierarchy
|
||||
|
||||
If there's a conflict between:
|
||||
- Generic best practices (in `/references/`)
|
||||
- Your personal patterns (in `/assets/`)
|
||||
|
||||
→ Claude will prioritize YOUR patterns (with optimization suggestions if needed)
|
||||
|
||||
**Exception:** If your patterns actively harm algorithmic reach (external links, engagement bait), Claude will flag this and suggest alignment with platform mechanics while maintaining your authentic voice.
|
||||
|
||||
## Getting Started
|
||||
|
||||
1. **Week 1:** Fill in PERSONALIZATION SETTINGS in SKILL.md (15 minutes)
|
||||
2. **Week 2-4:** Add 2-3 voice samples to `/voice-samples/` (20 minutes)
|
||||
3. **Month 2:** Start populating `/examples/` with your successful posts (ongoing)
|
||||
4. **Month 3:** Add frameworks and case studies as they develop (ongoing)
|
||||
|
||||
The more you populate these folders, the more personalized and valuable this skill becomes. Think of it as a system that learns YOUR patterns over time.
|
||||
78
assets/analytics/README.md
Normal file
78
assets/analytics/README.md
Normal file
|
|
@ -0,0 +1,78 @@
|
|||
# LinkedIn Analytics Data
|
||||
|
||||
This directory contains imported analytics data from LinkedIn CSV exports.
|
||||
|
||||
## How to Import
|
||||
|
||||
1. Go to [LinkedIn Creator Analytics](https://www.linkedin.com/analytics/creator/content/)
|
||||
2. Click **Export** to download a CSV of your content analytics
|
||||
3. Save the CSV file to `exports/` directory
|
||||
4. Run `/linkedin:import` in Claude Code
|
||||
|
||||
## Directory Structure
|
||||
|
||||
```
|
||||
analytics/
|
||||
├── exports/ # Place LinkedIn CSV exports here
|
||||
├── posts/ # Auto-generated: imported post data (JSON)
|
||||
├── weekly-reports/ # Auto-generated: weekly performance reports (JSON)
|
||||
└── README.md # This file
|
||||
```
|
||||
|
||||
## Data Format
|
||||
|
||||
### Post Analytics (posts/*.json)
|
||||
|
||||
Each file contains a batch of imported posts:
|
||||
|
||||
```json
|
||||
{
|
||||
"batchId": "batch-...",
|
||||
"importedAt": "2026-01-29T...",
|
||||
"exportFilename": "content-analytics.csv",
|
||||
"dateRange": { "from": "2026-01-13", "to": "2026-01-28" },
|
||||
"postCount": 8,
|
||||
"posts": [
|
||||
{
|
||||
"id": "abc123",
|
||||
"title": "First 100 chars of post...",
|
||||
"publishedDate": "2026-01-28",
|
||||
"metrics": {
|
||||
"impressions": 4523,
|
||||
"reactions": 87,
|
||||
"comments": 23,
|
||||
"shares": 12,
|
||||
"clicks": 156,
|
||||
"engagementRate": 6.15
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### Weekly Reports (weekly-reports/*.json)
|
||||
|
||||
Generated via `/linkedin:report`. Contains:
|
||||
- Summary metrics (totals, averages)
|
||||
- Top and underperforming posts
|
||||
- Week-over-week trends
|
||||
- Performance alerts (spikes, drops)
|
||||
|
||||
## CLI Usage
|
||||
|
||||
The analytics CLI can also be invoked directly:
|
||||
|
||||
```bash
|
||||
# Import a CSV export
|
||||
ANALYTICS_ROOT=./assets/analytics node --import tsx scripts/analytics/src/cli.ts import <filename>
|
||||
|
||||
# Generate weekly report
|
||||
ANALYTICS_ROOT=./assets/analytics node --import tsx scripts/analytics/src/cli.ts report --week 2026-W05
|
||||
|
||||
# Analyze trends
|
||||
ANALYTICS_ROOT=./assets/analytics node --import tsx scripts/analytics/src/cli.ts trends --period month --metric impressions
|
||||
```
|
||||
|
||||
## Privacy
|
||||
|
||||
All data in this directory (except this README) is gitignored. Your analytics data stays local.
|
||||
0
assets/analytics/ab-tests/.gitkeep
Normal file
0
assets/analytics/ab-tests/.gitkeep
Normal file
211
assets/audience-insights/demographics.md
Normal file
211
assets/audience-insights/demographics.md
Normal file
|
|
@ -0,0 +1,211 @@
|
|||
# Audience Demographics
|
||||
|
||||
Track WHO is actually engaging with your content. LinkedIn Analytics provides this data for free - use it to understand your real audience vs. your intended audience.
|
||||
|
||||
## How to Access This Data
|
||||
|
||||
1. Go to LinkedIn Analytics: https://www.linkedin.com/analytics/
|
||||
2. Click on any post
|
||||
3. Navigate to "Demographics" tab
|
||||
4. Review data monthly and update this file
|
||||
|
||||
---
|
||||
|
||||
## Current Demographics (Last Updated: [Date])
|
||||
|
||||
### Industries (Top 10)
|
||||
|
||||
Based on LinkedIn Analytics → Post Analytics → Demographics
|
||||
|
||||
| Rank | Industry | % of Engagement | Trend |
|
||||
|------|----------|----------------|--------|
|
||||
| 1 | [Industry name] | [X]% | [↑/→/↓] |
|
||||
| 2 | [Industry name] | [X]% | [↑/→/↓] |
|
||||
| 3 | [Industry name] | [X]% | [↑/→/↓] |
|
||||
| 4 | [Industry name] | [X]% | [↑/→/↓] |
|
||||
| 5 | [Industry name] | [X]% | [↑/→/↓] |
|
||||
| 6 | [Industry name] | [X]% | [↑/→/↓] |
|
||||
| 7 | [Industry name] | [X]% | [↑/→/↓] |
|
||||
| 8 | [Industry name] | [X]% | [↑/→/↓] |
|
||||
| 9 | [Industry name] | [X]% | [↑/→/↓] |
|
||||
| 10 | [Industry name] | [X]% | [↑/→/↓] |
|
||||
|
||||
**Key insights:**
|
||||
- [Observation 1 - e.g., "60% from government sector, higher than expected"]
|
||||
- [Observation 2 - e.g., "Tech companies underrepresented vs. my assumptions"]
|
||||
- [Implication - e.g., "Should increase public sector case studies"]
|
||||
|
||||
---
|
||||
|
||||
### Job Functions (Top 10)
|
||||
|
||||
| Rank | Function | % of Engagement | Trend |
|
||||
|------|----------|----------------|--------|
|
||||
| 1 | [Function] | [X]% | [↑/→/↓] |
|
||||
| 2 | [Function] | [X]% | [↑/→/↓] |
|
||||
| 3 | [Function] | [X]% | [↑/→/↓] |
|
||||
| 4 | [Function] | [X]% | [↑/→/↓] |
|
||||
| 5 | [Function] | [X]% | [↑/→/↓] |
|
||||
| 6 | [Function] | [X]% | [↑/→/↓] |
|
||||
| 7 | [Function] | [X]% | [↑/→/↓] |
|
||||
| 8 | [Function] | [X]% | [↑/→/↓] |
|
||||
| 9 | [Function] | [X]% | [↑/→/↓] |
|
||||
| 10 | [Function] | [X]% | [↑/→/↓] |
|
||||
|
||||
**Key insights:**
|
||||
- [Who is actually engaging]
|
||||
- [Implication for content framing]
|
||||
|
||||
---
|
||||
|
||||
### Seniority Levels
|
||||
|
||||
| Level | % of Engagement | Change vs. Last Month |
|
||||
|-------|----------------|----------------------|
|
||||
| Entry level | [X]% | [+/-X%] |
|
||||
| Individual contributor | [X]% | [+/-X%] |
|
||||
| Manager | [X]% | [+/-X%] |
|
||||
| Director | [X]% | [+/-X%] |
|
||||
| VP | [X]% | [+/-X%] |
|
||||
| C-level | [X]% | [+/-X%] |
|
||||
| Owner/Partner | [X]% | [+/-X%] |
|
||||
|
||||
**Key insights:**
|
||||
- **Dominant level:** [Which level engages most]
|
||||
- **Decision-maker presence:** [% at Director+ level]
|
||||
- **Content implication:** [How technical/strategic should content be?]
|
||||
|
||||
---
|
||||
|
||||
### Geographic Distribution (Top 10 Countries)
|
||||
|
||||
| Rank | Country | % of Engagement | Trend |
|
||||
|------|---------|----------------|--------|
|
||||
| 1 | [Country] | [X]% | [↑/→/↓] |
|
||||
| 2 | [Country] | [X]% | [↑/→/↓] |
|
||||
| 3 | [Country] | [X]% | [↑/→/↓] |
|
||||
| 4 | [Country] | [X]% | [↑/→/↓] |
|
||||
| 5 | [Country] | [X]% | [↑/→/↓] |
|
||||
| 6 | [Country] | [X]% | [↑/→/↓] |
|
||||
| 7 | [Country] | [X]% | [↑/→/↓] |
|
||||
| 8 | [Country] | [X]% | [↑/→/↓] |
|
||||
| 9 | [Country] | [X]% | [↑/→/↓] |
|
||||
| 10 | [Country] | [X]% | [↑/→/↓] |
|
||||
|
||||
**Key insights:**
|
||||
- **Primary market:** [Where most engagement comes from]
|
||||
- **Time zone implications:** [Optimal posting times]
|
||||
- **Regional context:** [Does content need localization?]
|
||||
|
||||
---
|
||||
|
||||
### Company Size (Of Engagers)
|
||||
|
||||
| Size | % of Engagement | Trend |
|
||||
|------|----------------|--------|
|
||||
| 1-10 employees | [X]% | [↑/→/↓] |
|
||||
| 11-50 | [X]% | [↑/→/↓] |
|
||||
| 51-200 | [X]% | [↑/→/↓] |
|
||||
| 201-500 | [X]% | [↑/→/↓] |
|
||||
| 501-1000 | [X]% | [↑/→/↓] |
|
||||
| 1001-5000 | [X]% | [↑/→/↓] |
|
||||
| 5001-10000 | [X]% | [↑/→/↓] |
|
||||
| 10000+ | [X]% | [↑/→/↓] |
|
||||
|
||||
**Key insights:**
|
||||
- **Dominant segment:** [Enterprise/Mid-market/SMB]
|
||||
- **Content implication:** [Scale of examples, budget assumptions]
|
||||
- **Opportunity:** [Underserved segment to target]
|
||||
|
||||
---
|
||||
|
||||
## Intended vs. Actual Audience
|
||||
|
||||
### Who I Thought My Audience Was
|
||||
- **Industries:** [Your original assumptions]
|
||||
- **Roles:** [Your original assumptions]
|
||||
- **Seniority:** [Your original assumptions]
|
||||
- **Geography:** [Your original assumptions]
|
||||
|
||||
### Who My Audience Actually Is
|
||||
- **Industries:** [Reality from data above]
|
||||
- **Roles:** [Reality from data above]
|
||||
- **Seniority:** [Reality from data above]
|
||||
- **Geography:** [Reality from data above]
|
||||
|
||||
### Strategic Implications
|
||||
|
||||
**Content adjustments needed:**
|
||||
1. [Adjustment 1 - e.g., "Increase public sector examples, decrease startup references"]
|
||||
2. [Adjustment 2 - e.g., "Frame for Director-level, not just technical ICs"]
|
||||
3. [Adjustment 3 - e.g., "Add European regulatory context"]
|
||||
|
||||
**Opportunities identified:**
|
||||
1. [Opportunity 1 - e.g., "Large enterprise segment underserved by competitors"]
|
||||
2. [Opportunity 2 - e.g., "Growing Nordic audience interested in topic X"]
|
||||
|
||||
---
|
||||
|
||||
## Follower vs. Engager Analysis
|
||||
|
||||
**Important distinction:**
|
||||
- Your followers = who follows you
|
||||
- Your engagers = who actually interacts with content
|
||||
|
||||
Often these are different groups. LinkedIn prioritizes showing your content to engagers, not just followers.
|
||||
|
||||
### Follower Demographics
|
||||
[If you have LinkedIn Premium, note follower demographics here]
|
||||
- [Key differences from engager demographics]
|
||||
|
||||
### Insight
|
||||
[What the difference between followers and engagers tells you]
|
||||
|
||||
---
|
||||
|
||||
## Competitive Audience Analysis
|
||||
|
||||
How does your audience compare to key competitors/peers?
|
||||
|
||||
| Peer | Their Primary Industry | Their Seniority Level | Difference from Mine |
|
||||
|------|----------------------|---------------------|---------------------|
|
||||
| [Name] | [Industry] | [Level] | [What's different] |
|
||||
| [Name] | [Industry] | [Level] | [What's different] |
|
||||
| [Name] | [Industry] | [Level] | [What's different] |
|
||||
|
||||
**Content gap opportunity:**
|
||||
[Where your unique audience positioning creates content opportunities]
|
||||
|
||||
---
|
||||
|
||||
## Month-over-Month Trends
|
||||
|
||||
### [Current Month] vs. [Previous Month]
|
||||
|
||||
**Industry shifts:**
|
||||
- [What changed and why]
|
||||
|
||||
**Seniority shifts:**
|
||||
- [What changed and why]
|
||||
|
||||
**Geographic shifts:**
|
||||
- [What changed and why]
|
||||
|
||||
**Analysis:**
|
||||
[What these trends indicate about content resonance and audience evolution]
|
||||
|
||||
---
|
||||
|
||||
## Update Schedule
|
||||
|
||||
- **Monthly:** Update all demographics from LinkedIn Analytics
|
||||
- **Quarterly:** Deep analysis of trends and strategic implications
|
||||
- **Yearly:** Major review of intended vs. actual audience fit
|
||||
|
||||
---
|
||||
|
||||
## Update Log
|
||||
|
||||
- **[Date]:** Initial demographics captured
|
||||
- **[Date]:** Observed [significant change] in [demographic category]
|
||||
- **[Date]:** Shifted content strategy based on [insight]
|
||||
267
assets/audience-insights/engagement-patterns.md
Normal file
267
assets/audience-insights/engagement-patterns.md
Normal file
|
|
@ -0,0 +1,267 @@
|
|||
# My Audience Engagement Patterns
|
||||
|
||||
Track YOUR audience's specific behaviors and preferences here. This data is more valuable than generic "best practices" because it's based on YOUR actual results.
|
||||
|
||||
## Update Frequency
|
||||
|
||||
**Weekly (5 minutes):** Update posting times and add best-performing topic from the week
|
||||
**Monthly (15 minutes):** Deep dive into patterns, update demographics, analyze format performance
|
||||
|
||||
---
|
||||
|
||||
## Best Posting Times (Based on MY Data)
|
||||
|
||||
**Important:** These should be YOUR times based on YOUR analytics, not generic advice. Track this in LinkedIn Analytics under "Post impressions by time of day."
|
||||
|
||||
### Primary Posting Windows
|
||||
1. **[Day] at [Time]:** Avg. impressions: [X] | Avg. engagement: [Y]
|
||||
- Why this works: [e.g., "My audience (public sector leaders) checks LinkedIn during lunch break"]
|
||||
|
||||
2. **[Day] at [Time]:** Avg. impressions: [X] | Avg. engagement: [Y]
|
||||
- Why this works: [Your analysis]
|
||||
|
||||
3. **[Day] at [Time]:** Avg. impressions: [X] | Avg. engagement: [Y]
|
||||
- Why this works: [Your analysis]
|
||||
|
||||
### Worst Posting Times (To Avoid)
|
||||
- [Day/Time]: [Why it underperforms for YOUR audience]
|
||||
- [Day/Time]: [Why it underperforms for YOUR audience]
|
||||
|
||||
**Update Log:**
|
||||
- [Date]: [Change observed - e.g., "Tuesday 2pm now outperforms Friday 8am"]
|
||||
|
||||
---
|
||||
|
||||
## Top-Performing Topics (Last 90 Days)
|
||||
|
||||
Track which topics YOUR audience actually engages with, not what you think they should care about.
|
||||
|
||||
1. **[Topic]:** Avg. engagement: [X] | Posts: [Y]
|
||||
- Best-performing post example: [Brief description]
|
||||
- Why it resonates: [Your analysis]
|
||||
|
||||
2. **[Topic]:** Avg. engagement: [X] | Posts: [Y]
|
||||
- Best-performing post example: [Brief description]
|
||||
- Why it resonates: [Your analysis]
|
||||
|
||||
3. **[Topic]:** Avg. engagement: [X] | Posts: [Y]
|
||||
- Best-performing post example: [Brief description]
|
||||
- Why it resonates: [Your analysis]
|
||||
|
||||
### Topics That Surprisingly Underperformed
|
||||
- **[Topic]:** [Why you thought it would work] → [Why it didn't]
|
||||
- **[Topic]:** [Analysis]
|
||||
|
||||
**Implication for content strategy:**
|
||||
[What you'll do differently based on this data]
|
||||
|
||||
---
|
||||
|
||||
## Format Performance (MY Audience)
|
||||
|
||||
Based on YOUR analytics, not generic benchmarks. Track in LinkedIn Analytics and your own spreadsheet.
|
||||
|
||||
### Format Rankings (By Engagement)
|
||||
1. **[Format - e.g., "Story-based posts"]:**
|
||||
- Avg. impressions: [X]
|
||||
- Avg. engagement rate: [Y%]
|
||||
- Best time to post: [When]
|
||||
- Character sweet spot: [Range]
|
||||
|
||||
2. **[Format - e.g., "Framework posts"]:**
|
||||
- Avg. impressions: [X]
|
||||
- Avg. engagement rate: [Y%]
|
||||
- Best time to post: [When]
|
||||
- Character sweet spot: [Range]
|
||||
|
||||
3. **[Format - e.g., "Data/research posts"]:**
|
||||
- [Same metrics]
|
||||
|
||||
4. **[Format - e.g., "Case study posts"]:**
|
||||
- [Same metrics]
|
||||
|
||||
### Visual Content Performance
|
||||
- **Posts with images:** Avg. engagement: [X] vs text-only: [Y]
|
||||
- **Posts with documents:** Avg. engagement: [X]
|
||||
- **Posts with carousels:** Avg. engagement: [X]
|
||||
- **Video posts:** Avg. engagement: [X]
|
||||
|
||||
**Your insights:**
|
||||
[What format performs best for YOUR audience and why]
|
||||
|
||||
---
|
||||
|
||||
## Hook Types That Work for ME
|
||||
|
||||
Not all hook styles work for all audiences. Track which hooks YOUR audience responds to.
|
||||
|
||||
### Top-Performing Hook Styles
|
||||
1. **[Hook type - e.g., "Counterintuitive stat"]**
|
||||
- Example: [Actual hook you used]
|
||||
- Avg. engagement: [X]
|
||||
- Why it works for your audience: [Analysis]
|
||||
|
||||
2. **[Hook type - e.g., "Bold contrarian statement"]**
|
||||
- Example: [Actual hook]
|
||||
- Avg. engagement: [X]
|
||||
- Why it works: [Analysis]
|
||||
|
||||
3. **[Hook type - e.g., "Personal story opening"]**
|
||||
- Example: [Actual hook]
|
||||
- Avg. engagement: [X]
|
||||
- Why it works: [Analysis]
|
||||
|
||||
### Hook Styles That Don't Work for YOUR Audience
|
||||
- **[Hook type]:** [Why it underperforms with your specific audience]
|
||||
- **[Hook type]:** [Why it underperforms]
|
||||
|
||||
---
|
||||
|
||||
## CTA Performance Analysis
|
||||
|
||||
Which calls-to-action actually drive engagement from YOUR audience?
|
||||
|
||||
### High-Performing CTAs
|
||||
1. **[CTA type - e.g., "Specific implementation question"]**
|
||||
- Example: "Which stage is your organization in?"
|
||||
- Avg. comments generated: [X]
|
||||
|
||||
2. **[CTA type]**
|
||||
- Example: [Actual CTA]
|
||||
- Avg. comments generated: [X]
|
||||
|
||||
### Low-Performing CTAs (To Avoid)
|
||||
- **[CTA type]:** [Why YOUR audience doesn't respond to this]
|
||||
|
||||
---
|
||||
|
||||
## Audience Demographics (Who Actually Engages)
|
||||
|
||||
Based on LinkedIn Analytics → Analytics → Demographics of people who interacted with your posts
|
||||
|
||||
### Industries (Top 5)
|
||||
1. [Industry]: [% of engagement]
|
||||
2. [Industry]: [% of engagement]
|
||||
3. [Industry]: [% of engagement]
|
||||
4. [Industry]: [% of engagement]
|
||||
5. [Industry]: [% of engagement]
|
||||
|
||||
**Insight:** [What this means for content focus]
|
||||
|
||||
### Job Functions (Top 5)
|
||||
1. [Function]: [% of engagement]
|
||||
2. [Function]: [% of engagement]
|
||||
3. [Function]: [% of engagement]
|
||||
4. [Function]: [% of engagement]
|
||||
5. [Function]: [% of engagement]
|
||||
|
||||
**Insight:** [How this should shape your content]
|
||||
|
||||
### Seniority Levels
|
||||
- C-level: [%]
|
||||
- VP/Director: [%]
|
||||
- Manager: [%]
|
||||
- Individual contributor: [%]
|
||||
- Entry level: [%]
|
||||
|
||||
**Insight:** [Technical depth and framing implications]
|
||||
|
||||
### Geographic Distribution (Top 5 Countries)
|
||||
1. [Country]: [%]
|
||||
2. [Country]: [%]
|
||||
3. [Country]: [%]
|
||||
4. [Country]: [%]
|
||||
5. [Country]: [%]
|
||||
|
||||
**Insight:** [Time zone and regional context considerations]
|
||||
|
||||
### Company Size (Of Engagers)
|
||||
- 1-10 employees: [%]
|
||||
- 11-50: [%]
|
||||
- 51-200: [%]
|
||||
- 201-500: [%]
|
||||
- 501-1000: [%]
|
||||
- 1001-5000: [%]
|
||||
- 5001-10000: [%]
|
||||
- 10000+: [%]
|
||||
|
||||
**Insight:** [Scale and organizational context implications]
|
||||
|
||||
---
|
||||
|
||||
## Content Length Performance (YOUR Data)
|
||||
|
||||
Track the optimal length for YOUR audience, not generic advice.
|
||||
|
||||
- **800-1000 characters:** Avg. engagement: [X]
|
||||
- **1000-1200 characters:** Avg. engagement: [X]
|
||||
- **1200-1500 characters:** Avg. engagement: [X]
|
||||
- **1500-1900 characters:** Avg. engagement: [X]
|
||||
- **1900+ characters:** Avg. engagement: [X]
|
||||
|
||||
**Your sweet spot:** [Range that consistently performs best]
|
||||
**Why:** [Your analysis of why this works for your audience]
|
||||
|
||||
---
|
||||
|
||||
## Engagement Velocity Patterns
|
||||
|
||||
How quickly does YOUR content gain traction?
|
||||
|
||||
### First Hour Performance
|
||||
- **Average engagement in first 60 minutes:** [X] likes, [Y] comments
|
||||
- **Threshold for algorithm boost:** [Based on your data, when does reach accelerate?]
|
||||
- **Your current hit rate:** [% of posts that hit the threshold]
|
||||
|
||||
### 24-Hour Patterns
|
||||
- **Most engagement happens in:** [Time window - e.g., "First 3 hours"]
|
||||
- **Secondary surge times:** [If applicable]
|
||||
- **Typical engagement curve:** [Description of how your posts perform over 24 hours]
|
||||
|
||||
---
|
||||
|
||||
## Strategic Insights (The "So What")
|
||||
|
||||
Based on all the data above, what should you do differently?
|
||||
|
||||
### Content Strategy Adjustments
|
||||
1. **More of this:** [What data says you should double down on]
|
||||
2. **Less of this:** [What data says isn't working]
|
||||
3. **Test this:** [New hypotheses based on patterns]
|
||||
|
||||
### Audience Alignment
|
||||
- **Who you thought your audience was:** [Original assumption]
|
||||
- **Who actually engages:** [Reality based on data]
|
||||
- **Strategic implication:** [How content should shift]
|
||||
|
||||
### Competitive Edge Opportunities
|
||||
Based on YOUR unique audience makeup:
|
||||
- **Gap 1:** [Underserved need you could fill]
|
||||
- **Gap 2:** [Content angle competitors miss]
|
||||
- **Gap 3:** [Format opportunity]
|
||||
|
||||
---
|
||||
|
||||
## Monthly Comparison
|
||||
|
||||
Track month-over-month to see if patterns are stable or shifting.
|
||||
|
||||
### [Current Month]
|
||||
- Avg. impressions per post: [X]
|
||||
- Avg. engagement per post: [Y]
|
||||
- Follower growth: [+X]
|
||||
- Best-performing topic: [Topic]
|
||||
- Best-performing format: [Format]
|
||||
|
||||
### [Previous Month]
|
||||
- [Same metrics for comparison]
|
||||
|
||||
**Key changes:** [What's different and why]
|
||||
|
||||
---
|
||||
|
||||
## Update Log
|
||||
|
||||
- **[Date]:** [Significant finding - e.g., "Discovered Thursday posts now outperform Tuesday"]
|
||||
- **[Date]:** [Pattern shift - e.g., "Framework posts have overtaken story posts in engagement"]
|
||||
- **[Date]:** [Audience insight - e.g., "Realize 60% of engagers are from enterprise, not SMB"]
|
||||
216
assets/case-studies/case-study-template.md
Normal file
216
assets/case-studies/case-study-template.md
Normal file
|
|
@ -0,0 +1,216 @@
|
|||
# Case Study: [Project Name / Organization]
|
||||
|
||||
Real examples from your work provide credibility and specificity that generic scenarios can't match. Use this template to document case studies Claude can reference in posts.
|
||||
|
||||
---
|
||||
|
||||
## Case Study Overview
|
||||
|
||||
**Project name:** [e.g., "RAG Implementation at [Organization]"]
|
||||
**Organization type:** [e.g., "Large public sector organization, 5000+ employees"]
|
||||
**Industry:** [e.g., "Government / Transportation"]
|
||||
**Timeline:** [e.g., "January - June 2024 (6 months)"]
|
||||
**Your role:** [e.g., "AI Advisor, led implementation"]
|
||||
|
||||
**One-sentence summary:** [e.g., "Implemented contextual retrieval RAG system that reduced manual document processing time by 40% while improving answer accuracy."]
|
||||
|
||||
---
|
||||
|
||||
## The Challenge
|
||||
|
||||
### Business Context
|
||||
[What was happening in the organization that created the need?]
|
||||
- [Context point 1]
|
||||
- [Context point 2]
|
||||
|
||||
### Specific Problem
|
||||
[What specific pain point were you solving?]
|
||||
- **Symptom 1:** [Observable problem]
|
||||
- **Symptom 2:** [Observable problem]
|
||||
- **Root cause:** [What was actually driving the symptoms]
|
||||
|
||||
### Why It Mattered
|
||||
- **Impact on operations:** [How problem affected daily work]
|
||||
- **Cost/time implications:** [Quantifiable impact if available]
|
||||
- **Strategic importance:** [Why leadership cared]
|
||||
|
||||
### Previous Attempts
|
||||
[What had they tried before that didn't work?]
|
||||
- **Attempt 1:** [What they did] → [Why it failed]
|
||||
- **Attempt 2:** [What they did] → [Why it failed]
|
||||
|
||||
---
|
||||
|
||||
## The Approach
|
||||
|
||||
### Initial Assessment
|
||||
[How you diagnosed the situation]
|
||||
- **Key finding 1:** [What you discovered]
|
||||
- **Key finding 2:** [What you discovered]
|
||||
- **Strategic decision:** [Based on findings, what approach did you choose?]
|
||||
|
||||
### Solution Design
|
||||
[What you built/implemented - be specific]
|
||||
|
||||
**Architecture:**
|
||||
- [Component 1 and why]
|
||||
- [Component 2 and why]
|
||||
- [Component 3 and why]
|
||||
|
||||
**Key decisions:**
|
||||
1. **[Decision 1 - e.g., "Used Azure AI Search vs. building custom"]**
|
||||
- Why: [Rationale]
|
||||
- Trade-off: [What you gave up]
|
||||
|
||||
2. **[Decision 2]**
|
||||
- Why: [Rationale]
|
||||
- Trade-off: [What you gave up]
|
||||
|
||||
### Implementation Timeline
|
||||
- **Week 1-2:** [Phase 1 activities]
|
||||
- **Week 3-6:** [Phase 2 activities]
|
||||
- **Week 7-12:** [Phase 3 activities]
|
||||
- **Ongoing:** [Maintenance/iteration]
|
||||
|
||||
### Challenges Encountered
|
||||
**Challenge 1:** [What went wrong]
|
||||
- How we addressed it: [Solution]
|
||||
- Learning: [What you'd do differently]
|
||||
|
||||
**Challenge 2:** [What went wrong]
|
||||
- How we addressed it: [Solution]
|
||||
- Learning: [What you'd do differently]
|
||||
|
||||
---
|
||||
|
||||
## The Results
|
||||
|
||||
### Quantitative Outcomes
|
||||
- **[Metric 1]:** [Before] → [After] ([X%] improvement)
|
||||
- **[Metric 2]:** [Before] → [After] ([X%] improvement)
|
||||
- **[Metric 3]:** [Before] → [After] ([X%] improvement)
|
||||
|
||||
**ROI:** [If calculable - cost vs. benefit]
|
||||
|
||||
### Qualitative Outcomes
|
||||
- **User feedback:** [What people said]
|
||||
- **Process improvements:** [Non-quantifiable benefits]
|
||||
- **Capability development:** [New skills/capacities gained]
|
||||
|
||||
### Unexpected Benefits
|
||||
[Things you didn't anticipate but that emerged]
|
||||
- [Benefit 1]
|
||||
- [Benefit 2]
|
||||
|
||||
---
|
||||
|
||||
## Key Learnings
|
||||
|
||||
### What Worked
|
||||
1. **[Tactic/approach]:** [Why it was effective]
|
||||
2. **[Tactic/approach]:** [Why it was effective]
|
||||
3. **[Tactic/approach]:** [Why it was effective]
|
||||
|
||||
### What Didn't Work
|
||||
1. **[Approach that failed]:** [Why + what you learned]
|
||||
2. **[Approach that failed]:** [Why + what you learned]
|
||||
|
||||
### Non-Obvious Insights
|
||||
[The lessons that only came from doing the work]
|
||||
- [Insight 1]
|
||||
- [Insight 2]
|
||||
- [Insight 3]
|
||||
|
||||
### Replicable Patterns
|
||||
[What from this case can transfer to other contexts?]
|
||||
- [Pattern 1]
|
||||
- [Pattern 2]
|
||||
|
||||
---
|
||||
|
||||
## LinkedIn Post Angles
|
||||
|
||||
### Angle 1: Results-First Post
|
||||
**Hook:** "We reduced [metric] by [X%] in [timeframe]. Here's the system we built..."
|
||||
|
||||
**Structure:**
|
||||
- Lead with compelling result
|
||||
- Brief context (the challenge)
|
||||
- High-level solution overview
|
||||
- 1-2 key decisions that mattered most
|
||||
- CTA: Ask if they face similar challenge
|
||||
|
||||
**Best for:** Building credibility, attracting similar opportunities
|
||||
|
||||
---
|
||||
|
||||
### Angle 2: Before/After Transformation
|
||||
**Hook:** "Six months ago, [organization] was [painful situation]. Today, [transformed situation]. Here's what changed..."
|
||||
|
||||
**Structure:**
|
||||
- Paint the before picture
|
||||
- Turning point / moment of decision
|
||||
- The intervention
|
||||
- The after state
|
||||
- Key enabler of transformation
|
||||
- CTA: Ask where others are in similar journey
|
||||
|
||||
**Best for:** Storytelling, emotional engagement
|
||||
|
||||
---
|
||||
|
||||
### Angle 3: Single Decision Deep-Dive
|
||||
**Hook:** "The decision to [specific choice] was controversial. Here's why it was right..."
|
||||
|
||||
**Structure:**
|
||||
- The decision point
|
||||
- Arguments against
|
||||
- Why we chose it anyway
|
||||
- How it played out
|
||||
- What we learned
|
||||
- CTA: Ask what others would have done
|
||||
|
||||
**Best for:** Thought leadership, showing expertise
|
||||
|
||||
---
|
||||
|
||||
### Angle 4: Failure Lessons
|
||||
**Hook:** "[Approach] should have worked. It didn't. Here's what we learned..."
|
||||
|
||||
**Structure:**
|
||||
- What we tried that failed
|
||||
- Why we thought it would work
|
||||
- What actually happened
|
||||
- The pivot
|
||||
- The learning
|
||||
- CTA: Ask if others have failed similarly
|
||||
|
||||
**Best for:** Authenticity, building trust through vulnerability
|
||||
|
||||
---
|
||||
|
||||
## Confidentiality & Permissions
|
||||
|
||||
**Public information:** [What can be shared freely]
|
||||
**Anonymized information:** [What can be shared if org name removed]
|
||||
**Confidential:** [What cannot be shared]
|
||||
**Permission level:** [What you've been cleared to discuss publicly]
|
||||
|
||||
**Client approval:** [Date if you got explicit permission to use as case study]
|
||||
|
||||
---
|
||||
|
||||
## Supporting Materials
|
||||
|
||||
**Screenshots/diagrams:** [If available, note location]
|
||||
**Metrics dashboard:** [If you have data visualization]
|
||||
**Testimonials:** [If you have quotes from stakeholders]
|
||||
**Press coverage:** [If project was publicly recognized]
|
||||
|
||||
---
|
||||
|
||||
## Update Log
|
||||
|
||||
- **[Date]:** Initial case study documentation
|
||||
- **[Date]:** Added outcome metrics after 6-month mark
|
||||
- **[Date]:** Updated with long-term results
|
||||
135
assets/checklists/quality-scorecard.md
Normal file
135
assets/checklists/quality-scorecard.md
Normal file
|
|
@ -0,0 +1,135 @@
|
|||
# Post Quality Scorecard (Pre-Publish Check)
|
||||
|
||||
Use this scorecard before publishing ANY post to predict performance.
|
||||
|
||||
---
|
||||
|
||||
## Scoring System
|
||||
|
||||
Rate each criterion 0-3:
|
||||
- 0 = Missing/Poor
|
||||
- 1 = Basic
|
||||
- 2 = Good
|
||||
- 3 = Excellent
|
||||
|
||||
---
|
||||
|
||||
## Profile Alignment (Weight: 2x)
|
||||
|
||||
| Criterion | Score | Notes |
|
||||
|-----------|-------|-------|
|
||||
| Topic matches your 5 core areas | /3 | Algorithm checks expertise |
|
||||
| Consistent with recent content | /3 | Topical authority signal |
|
||||
| Language/tone matches profile | /3 | Authenticity marker |
|
||||
| **Subtotal** | /9 x 2 = **/18** | |
|
||||
|
||||
---
|
||||
|
||||
## Hook Strength (Weight: 2x)
|
||||
|
||||
| Criterion | Score | Notes |
|
||||
|-----------|-------|-------|
|
||||
| Works in 140 characters | /3 | Mobile threshold |
|
||||
| Creates curiosity gap | /3 | Click-through driver |
|
||||
| Promises clear value | /3 | Worth reading? |
|
||||
| **Subtotal** | /9 x 2 = **/18** | |
|
||||
|
||||
---
|
||||
|
||||
## Dwell Time Potential (Weight: 1.5x)
|
||||
|
||||
| Criterion | Score | Notes |
|
||||
|-----------|-------|-------|
|
||||
| Length 1,200-1,800 characters | /3 | Optimal range |
|
||||
| White space formatting | /3 | Easy to read |
|
||||
| Encourages re-reading | /3 | Saves, bookmarks |
|
||||
| **Subtotal** | /9 x 1.5 = **/13.5** | |
|
||||
|
||||
---
|
||||
|
||||
## Engagement Triggers (Weight: 1.5x)
|
||||
|
||||
| Criterion | Score | Notes |
|
||||
|-----------|-------|-------|
|
||||
| CTA invites 15+ word comments | /3 | High-value engagement |
|
||||
| Shareable (others want to amplify) | /3 | Viral potential |
|
||||
| Save-worthy (reference value) | /3 | Top algorithm signal |
|
||||
| **Subtotal** | /9 x 1.5 = **/13.5** | |
|
||||
|
||||
---
|
||||
|
||||
## Format Optimization (Weight: 1x)
|
||||
|
||||
| Criterion | Score | Notes |
|
||||
|-----------|-------|-------|
|
||||
| Right format for content | /3 | Carousel/text/image |
|
||||
| Mobile-optimized | /3 | 70% mobile users |
|
||||
| No external links in body | /3 | Avoid penalty |
|
||||
| **Subtotal** | /9 x 1 = **/9** | |
|
||||
|
||||
---
|
||||
|
||||
## Voice Authenticity (Weight: 1x)
|
||||
|
||||
| Criterion | Score | Notes |
|
||||
|-----------|-------|-------|
|
||||
| Sounds like the author (not generic AI) | /3 | Check against voice samples |
|
||||
| Uses natural contractions and phrasing | /3 | Conversational, not formal |
|
||||
| Includes specific personal detail or anecdote | /3 | Personal observation or reference |
|
||||
| **Subtotal** | /9 x 1 = **/9** | |
|
||||
|
||||
---
|
||||
|
||||
## Total Score: /81
|
||||
|
||||
### Pass/Fail Thresholds
|
||||
|
||||
| Score | Action |
|
||||
|-------|--------|
|
||||
| **57+** | Excellent - post with confidence |
|
||||
| **46-56** | Good - consider one improvement |
|
||||
| **34-45** | Review needed - improve weakest area |
|
||||
| **Under 34** | Don't post - rework significantly |
|
||||
|
||||
---
|
||||
|
||||
## 360Brew Validation (Critical)
|
||||
|
||||
Before posting, verify your profile passes the 360Brew test:
|
||||
|
||||
- [ ] Profile clearly shows expertise in post topic
|
||||
- [ ] Headline includes relevant keywords
|
||||
- [ ] Recent activity supports topical authority
|
||||
- [ ] Featured section demonstrates credibility
|
||||
|
||||
**If profile doesn't support the post topic, fix profile FIRST.**
|
||||
|
||||
---
|
||||
|
||||
## Quick Score (30-Second Version)
|
||||
|
||||
For quick posts, use this simplified check:
|
||||
|
||||
1. On-topic for my expertise? (Y/N)
|
||||
2. Hook works in 140 chars? (Y/N)
|
||||
3. Clear value delivered? (Y/N)
|
||||
4. Ends with engagement prompt? (Y/N)
|
||||
5. No external links in body? (Y/N)
|
||||
|
||||
**All 5 = Yes? -> Post it.**
|
||||
**Any No? -> Fix first.**
|
||||
|
||||
---
|
||||
|
||||
## Pre-Publish Basic Checklist
|
||||
|
||||
Before finalizing any post, verify:
|
||||
|
||||
- [ ] Hook works in first 110-140 characters
|
||||
- [ ] Character count within optimal range
|
||||
- [ ] Short paragraphs with white space
|
||||
- [ ] Tone is authentic, not corporate
|
||||
- [ ] Provides genuine value to readers
|
||||
- [ ] CTA is specific and natural
|
||||
- [ ] Passes the "mobile test" (readable on phone)
|
||||
- [ ] Passes thought leadership test: Does it help someone make a better decision or think differently?
|
||||
1
assets/drafts/.gitkeep
Normal file
1
assets/drafts/.gitkeep
Normal file
|
|
@ -0,0 +1 @@
|
|||
# This directory stores content drafts
|
||||
238
assets/frameworks/framework-template.md
Normal file
238
assets/frameworks/framework-template.md
Normal file
|
|
@ -0,0 +1,238 @@
|
|||
# [Framework Name - e.g., "The 3-Stage RAG Maturity Model"]
|
||||
|
||||
## Overview
|
||||
|
||||
**One-sentence description:** [What this framework does - e.g., "A diagnostic tool for assessing and advancing organizational RAG implementation from basic to advanced."]
|
||||
|
||||
**Problem it solves:** [What challenge this addresses - e.g., "Most organizations don't know where they are in their RAG journey or what to do next."]
|
||||
|
||||
**Who it's for:** [Target audience - e.g., "Enterprise architects and AI leaders implementing RAG solutions."]
|
||||
|
||||
---
|
||||
|
||||
## The Framework
|
||||
|
||||
[Detailed explanation of your framework - be specific about the components, stages, or elements]
|
||||
|
||||
### Component 1: [Name - e.g., "Stage 1: Basic RAG"]
|
||||
|
||||
**Definition:** [Clear description]
|
||||
|
||||
**Characteristics:**
|
||||
- [Key trait 1]
|
||||
- [Key trait 2]
|
||||
- [Key trait 3]
|
||||
|
||||
**Common challenges at this stage:**
|
||||
- [Challenge 1]
|
||||
- [Challenge 2]
|
||||
|
||||
**What success looks like:**
|
||||
[Measurable outcomes]
|
||||
|
||||
---
|
||||
|
||||
### Component 2: [Name - e.g., "Stage 2: Enhanced RAG"]
|
||||
|
||||
**Definition:** [Clear description]
|
||||
|
||||
**Characteristics:**
|
||||
- [Key trait 1]
|
||||
- [Key trait 2]
|
||||
- [Key trait 3]
|
||||
|
||||
**Common challenges at this stage:**
|
||||
- [Challenge 1]
|
||||
- [Challenge 2]
|
||||
|
||||
**What success looks like:**
|
||||
[Measurable outcomes]
|
||||
|
||||
---
|
||||
|
||||
### Component 3: [Name - e.g., "Stage 3: Advanced RAG"]
|
||||
|
||||
**Definition:** [Clear description]
|
||||
|
||||
**Characteristics:**
|
||||
- [Key trait 1]
|
||||
- [Key trait 2]
|
||||
- [Key trait 3]
|
||||
|
||||
**Common challenges at this stage:**
|
||||
- [Challenge 1]
|
||||
- [Challenge 2]
|
||||
|
||||
**What success looks like:**
|
||||
[Measurable outcomes]
|
||||
|
||||
---
|
||||
|
||||
## How to Use This Framework
|
||||
|
||||
**Diagnostic questions:**
|
||||
1. [Question to determine current stage/position]
|
||||
2. [Question to identify gaps]
|
||||
3. [Question to prioritize next steps]
|
||||
|
||||
**Implementation pathway:**
|
||||
1. [Step 1]
|
||||
2. [Step 2]
|
||||
3. [Step 3]
|
||||
|
||||
---
|
||||
|
||||
## LinkedIn Post Angle Options
|
||||
|
||||
When creating posts about this framework, here are proven angles:
|
||||
|
||||
### Angle 1: Framework Introduction
|
||||
**Hook:** "Most [target audience] struggle with [problem]. I developed a framework that [solution]."
|
||||
|
||||
**Structure:**
|
||||
- Introduce the problem
|
||||
- Present the framework overview
|
||||
- Briefly explain each component
|
||||
- Provide diagnostic question
|
||||
- CTA: Ask where they are in the framework
|
||||
|
||||
**Expected engagement:** [Medium-High for framework lovers]
|
||||
|
||||
---
|
||||
|
||||
### Angle 2: Deep Dive on One Component
|
||||
**Hook:** "[Stage/Component Name] is where most [target audience] get stuck. Here's why..."
|
||||
|
||||
**Structure:**
|
||||
- Focus on single component in depth
|
||||
- Common mistakes at this stage
|
||||
- How to progress to next level
|
||||
- Real example if available
|
||||
- CTA: Ask about their experience at this stage
|
||||
|
||||
**Expected engagement:** [High for people at that stage]
|
||||
|
||||
---
|
||||
|
||||
### Angle 3: Case Study Application
|
||||
**Hook:** "We helped [Company/Org Type] move from [Stage A] to [Stage B] in [Time]. Here's how..."
|
||||
|
||||
**Structure:**
|
||||
- Starting situation (Stage A characteristics)
|
||||
- Challenge/tension
|
||||
- Intervention using framework
|
||||
- Results (Stage B outcomes)
|
||||
- Key lesson
|
||||
- CTA: Ask what stage they're at
|
||||
|
||||
**Expected engagement:** [Very High - specificity + results]
|
||||
|
||||
---
|
||||
|
||||
### Angle 4: Contrarian Take
|
||||
**Hook:** "Everyone talks about [common approach]. But the framework shows that [contrarian insight]."
|
||||
|
||||
**Structure:**
|
||||
- Challenge conventional wisdom
|
||||
- Explain why most approaches fail (using framework lens)
|
||||
- Present alternative pathway
|
||||
- Evidence from your framework
|
||||
- CTA: Ask if they've experienced this
|
||||
|
||||
**Expected engagement:** [High if insight is strong]
|
||||
|
||||
---
|
||||
|
||||
## Visual Assets
|
||||
|
||||
**Diagram location:** [Path to visual in /visual-assets/ folder if applicable]
|
||||
|
||||
**Visual description:** [Describe the diagram - useful for recreating in posts]
|
||||
|
||||
**When to use visuals:**
|
||||
- Introduction posts (show full framework)
|
||||
- LinkedIn carousel (break down each component)
|
||||
- Workshop/webinar materials
|
||||
|
||||
---
|
||||
|
||||
## Real-World Results
|
||||
|
||||
Document actual results from applying this framework:
|
||||
|
||||
### Case 1: [Organization/Context]
|
||||
- **Starting point:** [Where they were]
|
||||
- **Applied framework:** [How]
|
||||
- **Outcome:** [Measurable result]
|
||||
- **Timeline:** [Duration]
|
||||
|
||||
### Case 2: [Organization/Context]
|
||||
- **Starting point:** [Where they were]
|
||||
- **Applied framework:** [How]
|
||||
- **Outcome:** [Measurable result]
|
||||
- **Timeline:** [Duration]
|
||||
|
||||
### Case 3: [Organization/Context]
|
||||
- [Same structure]
|
||||
|
||||
**Aggregate impact:**
|
||||
[Overall statistics if you have multiple implementations]
|
||||
|
||||
---
|
||||
|
||||
## Common Misconceptions
|
||||
|
||||
What people get wrong about this framework:
|
||||
|
||||
1. **Misconception:** [What they think]
|
||||
- **Reality:** [Actual truth]
|
||||
- **Why it matters:** [Implication]
|
||||
|
||||
2. **Misconception:** [What they think]
|
||||
- **Reality:** [Actual truth]
|
||||
- **Why it matters:** [Implication]
|
||||
|
||||
---
|
||||
|
||||
## Evolution of This Framework
|
||||
|
||||
**Origin:** [How you developed this - gives credibility]
|
||||
|
||||
**Refinements over time:**
|
||||
- **Version 1.0:** [Initial version]
|
||||
- **Version 2.0:** [What you changed based on real-world application]
|
||||
- **Current version:** [Latest insights]
|
||||
|
||||
**Future development:**
|
||||
[Where you're taking this next]
|
||||
|
||||
---
|
||||
|
||||
## Integration with Other Frameworks
|
||||
|
||||
If this framework connects to or builds on other methodologies:
|
||||
|
||||
**Complements:** [Other frameworks it works with]
|
||||
**Differs from:** [What makes this unique vs. similar approaches]
|
||||
**Can be combined with:** [Synergistic frameworks]
|
||||
|
||||
---
|
||||
|
||||
## Credibility Markers
|
||||
|
||||
When referencing this framework in posts, use these credibility indicators:
|
||||
|
||||
- ✅ "Developed over [X] projects with [Y] organizations"
|
||||
- ✅ "Validated through [specific results]"
|
||||
- ✅ "Based on [research/analysis] of [data set]"
|
||||
- ❌ Avoid: "Revolutionary", "Game-changing", other hype
|
||||
|
||||
**Authority stance:** [How you position yourself - e.g., "Practitioner sharing what worked, not guru claiming universal truth"]
|
||||
|
||||
---
|
||||
|
||||
## Update Log
|
||||
|
||||
- **[Date]:** Created framework based on [initial observations]
|
||||
- **[Date]:** Refined after [new learnings/applications]
|
||||
- **[Date]:** Added [new component/insight]
|
||||
1
assets/plans/.gitkeep
Normal file
1
assets/plans/.gitkeep
Normal file
|
|
@ -0,0 +1 @@
|
|||
# This directory stores content plans
|
||||
212
assets/quick-post-resources.md
Normal file
212
assets/quick-post-resources.md
Normal file
|
|
@ -0,0 +1,212 @@
|
|||
# Quick Post Resources
|
||||
|
||||
Copy-paste hooks and CTAs for fast post creation.
|
||||
|
||||
---
|
||||
|
||||
## Hooks Bank
|
||||
|
||||
Copy these hooks and customize for your topic:
|
||||
|
||||
### Data/Numbers Hooks
|
||||
- "After [number] [time period], here's what I've learned:"
|
||||
- "[Percentage] of [group] are doing this wrong:"
|
||||
- "Tracked [metric] for [duration]. The results:"
|
||||
- "[Number] [thing] that [outcome]:"
|
||||
|
||||
### Story Hooks
|
||||
- "This morning, something clicked:"
|
||||
- "Had a conversation yesterday that shifted my thinking:"
|
||||
- "True story from this week:"
|
||||
- "What I didn't expect when I [action]:"
|
||||
|
||||
### Contrarian Hooks
|
||||
- "Stop [common advice]. Here's why:"
|
||||
- "The advice that's actually hurting you:"
|
||||
- "What everyone gets wrong about [topic]:"
|
||||
- "I used to believe [common belief]. Not anymore."
|
||||
|
||||
### Question Hooks
|
||||
- "Why doesn't anyone talk about [overlooked topic]?"
|
||||
- "Am I the only one who thinks [observation]?"
|
||||
- "Honest question: How do you handle [challenge]?"
|
||||
- "When did [problematic trend] become normal?"
|
||||
|
||||
### Curiosity Hooks
|
||||
- "There's a pattern I keep seeing:"
|
||||
- "Something doesn't add up about [topic]:"
|
||||
- "The thing that surprised me most about [experience]:"
|
||||
- "Hidden in plain sight:"
|
||||
|
||||
### Authority Hooks
|
||||
- "After [years/experience] in [field], one truth:"
|
||||
- "The framework that changed my approach to [topic]:"
|
||||
- "What I tell everyone who asks about [topic]:"
|
||||
- "The non-obvious lesson from [experience]:"
|
||||
|
||||
### Urgency Hooks
|
||||
- "If you're struggling with [problem], read this:"
|
||||
- "Save this for when [situation] happens:"
|
||||
- "Before you [common action], consider this:"
|
||||
- "Don't make the same mistake I made with [topic]:"
|
||||
|
||||
---
|
||||
|
||||
## Hook Formulas by Angle
|
||||
|
||||
### Contrarian
|
||||
- "Unpopular opinion: [your take]"
|
||||
- "Everyone's talking about X. Nobody's talking about Y."
|
||||
- "The advice that worked in [year] is hurting you now."
|
||||
- "What if [common practice] is actually the problem?"
|
||||
|
||||
### Validating
|
||||
- "Tried [approach]. Results after [timeframe]:"
|
||||
- "The data confirms what we suspected about [topic]."
|
||||
- "Proof that [strategy] actually works:"
|
||||
- "After testing for [duration], here's what I found."
|
||||
|
||||
### Curious
|
||||
- "Genuine question: Why do we [common practice]?"
|
||||
- "I've been thinking about [observation]. Anyone else?"
|
||||
- "What's stopping us from [alternative approach]?"
|
||||
- "Why does [pattern] keep happening?"
|
||||
|
||||
### Helpful
|
||||
- "A tiny change that made [specific improvement]:"
|
||||
- "Wish I knew this earlier about [topic]:"
|
||||
- "The simple fix for [common problem]:"
|
||||
- "Save this for when you [situation]."
|
||||
|
||||
### Surprised
|
||||
- "I was wrong about [topic]. Here's what changed:"
|
||||
- "Didn't see this coming:"
|
||||
- "This result surprised me:"
|
||||
- "Plot twist in my [project/work]:"
|
||||
|
||||
### Frustrated
|
||||
- "Can we stop pretending [myth] is true?"
|
||||
- "This needs to change in [industry/topic]:"
|
||||
- "Tired of seeing [problematic pattern]."
|
||||
- "Why are we still [outdated practice]?"
|
||||
|
||||
### Excited
|
||||
- "This changes everything about [topic]:"
|
||||
- "Just discovered [thing]. Game changer."
|
||||
- "Finally, something that actually works for [problem]."
|
||||
- "This is why I'm excited about [development]."
|
||||
|
||||
### Reflective
|
||||
- "X years later, here's what actually mattered:"
|
||||
- "Looking back, the turning point was..."
|
||||
- "The lesson I keep relearning:"
|
||||
- "What I'd tell myself when I started:"
|
||||
|
||||
---
|
||||
|
||||
## CTAs Bank
|
||||
|
||||
End with one of these to prompt engagement:
|
||||
|
||||
### Question CTAs (spark conversation)
|
||||
- "What's your take?"
|
||||
- "Anyone else experiencing this?"
|
||||
- "How do you handle this?"
|
||||
- "Agree or disagree?"
|
||||
- "What am I missing?"
|
||||
- "What would you add?"
|
||||
|
||||
### Challenge CTAs (invite debate)
|
||||
- "Change my mind."
|
||||
- "Fight me on this."
|
||||
- "Prove me wrong."
|
||||
- "Tell me I'm overthinking this."
|
||||
|
||||
### Share CTAs (gather perspectives)
|
||||
- "Drop your version in the comments."
|
||||
- "What's worked for you?"
|
||||
- "Share your example."
|
||||
- "I'll start: [your example]"
|
||||
|
||||
### Validation CTAs (build community)
|
||||
- "Like if you've been there."
|
||||
- "Repost if this resonates."
|
||||
- "Save this for later."
|
||||
- "Tag someone who needs to hear this." (Use sparingly - can trigger engagement bait detection)
|
||||
|
||||
### Follow-up CTAs (continue conversation)
|
||||
- "More on this tomorrow."
|
||||
- "Part 2 coming soon."
|
||||
- "DM me if you want the full breakdown."
|
||||
- "I'll share the details in comments."
|
||||
|
||||
---
|
||||
|
||||
## Quick Post Quality Checklist
|
||||
|
||||
Before posting, verify in 30 seconds:
|
||||
|
||||
- [ ] Hook works standalone in 140 characters (mobile "see more" threshold)
|
||||
- [ ] Under 500 characters total (if over, consider full workflow)
|
||||
- [ ] ONE clear point (not multiple competing ideas)
|
||||
- [ ] Ends with engagement prompt
|
||||
- [ ] Aligns with your 3-5 core topics (topical authority)
|
||||
- [ ] Provides value (insight, perspective, or question worth answering)
|
||||
- [ ] Sounds like YOU (not generic LinkedIn-speak)
|
||||
- [ ] No external links in post body (save for comments if needed)
|
||||
|
||||
---
|
||||
|
||||
## Timing for Quick Posts
|
||||
|
||||
### Best times
|
||||
- Early morning (7-8am local) - Catch commuters
|
||||
- Lunch break (12-1pm local) - Mid-day scroll
|
||||
- Late afternoon (5-6pm local) - End of workday wind-down
|
||||
|
||||
### Quick posts work especially well when:
|
||||
- You can engage in comments for the first 30 minutes
|
||||
- As "bookends" to your more substantial posts
|
||||
- When news breaks (react quickly, establish perspective)
|
||||
- During your audience's natural engagement windows
|
||||
|
||||
### Avoid posting quick posts:
|
||||
- Right before going offline for hours
|
||||
- When you won't be able to respond to comments
|
||||
- On your "big post" days (cannibalization)
|
||||
|
||||
---
|
||||
|
||||
## Common Mistakes to Avoid
|
||||
|
||||
1. **Too many ideas in one post**
|
||||
- Symptom: Post feels scattered, CTA is unclear
|
||||
- Fix: Pick ONE idea. Save others for separate posts.
|
||||
|
||||
2. **Burying the hook**
|
||||
- Symptom: Best part is in paragraph 3
|
||||
- Fix: Lead with the most interesting element
|
||||
|
||||
3. **No engagement prompt**
|
||||
- Symptom: People read but don't respond
|
||||
- Fix: Always end with question or invitation
|
||||
|
||||
4. **Generic observations**
|
||||
- Symptom: Could be written by anyone
|
||||
- Fix: Add YOUR specific perspective or experience
|
||||
|
||||
5. **Over-explaining**
|
||||
- Symptom: 400 characters explaining what could be said in 100
|
||||
- Fix: Trust your audience. Delete unnecessary context.
|
||||
|
||||
6. **Wrong topic for quick format**
|
||||
- Symptom: You keep wanting to add "but also..." and "and another thing..."
|
||||
- Fix: Switch to full workflow. This isn't a quick post topic.
|
||||
|
||||
7. **No connection to expertise**
|
||||
- Symptom: Random observation outside your lanes
|
||||
- Fix: Either connect to your core topics or skip it
|
||||
|
||||
8. **Engagement bait disguised as question**
|
||||
- Symptom: "Type 1 if you agree, 2 if you don't"
|
||||
- Fix: Ask genuine questions you care about answering
|
||||
283
assets/templates/carousel-templates.md
Normal file
283
assets/templates/carousel-templates.md
Normal file
|
|
@ -0,0 +1,283 @@
|
|||
# Carousel Templates
|
||||
|
||||
Slide-by-slide blueprints for LinkedIn carousels (PDF document posts). Carousels have the highest engagement rate of all LinkedIn formats (6.6%) because they maximize dwell time and encourage swipe completion.
|
||||
|
||||
## Universal Design Specs
|
||||
|
||||
- **Slide dimensions:** 1080 x 1350 px (4:5 portrait, recommended)
|
||||
- **Font:** Sans-serif, minimum 24pt body, 36pt+ headlines
|
||||
- **Colors:** Max 3 per carousel (background, text, accent)
|
||||
- **Text per slide:** 5-7 lines maximum
|
||||
- **Optimal length:** 5-8 slides (including cover and CTA). 7 slides is the sweet spot (18% better performance)
|
||||
- **Export format:** PDF
|
||||
- **Caption length:** 300-500 characters with hook and context
|
||||
|
||||
---
|
||||
|
||||
## Template 1: How-To Guide
|
||||
|
||||
**Best for:** Teaching a process, explaining a method, step-by-step instructions
|
||||
**Structure:** 6-8 slides
|
||||
|
||||
| Slide | Purpose | Content Pattern |
|
||||
|-------|---------|-----------------|
|
||||
| 1 | Cover/Hook | Bold question or promise: "How to [achieve X] in [timeframe]" |
|
||||
| 2 | Problem | "Most people [common mistake]. Here's what actually works." |
|
||||
| 3 | Step 1 | **Step name** + 2-3 lines of explanation |
|
||||
| 4 | Step 2 | **Step name** + 2-3 lines of explanation |
|
||||
| 5 | Step 3 | **Step name** + 2-3 lines of explanation |
|
||||
| 6 | Step 4 | **Step name** + 2-3 lines of explanation |
|
||||
| 7 | Step 5 | **Step name** + 2-3 lines of explanation |
|
||||
| 8 | Common mistakes | "3 mistakes to avoid: [quick list]" |
|
||||
| 9 | Summary | Recap all steps in a numbered list |
|
||||
| 10 | CTA | "Save this for later. Follow for more [topic]." |
|
||||
|
||||
**Cover slide formula:**
|
||||
```
|
||||
How to [specific outcome]
|
||||
(without [common pain point])
|
||||
|
||||
[Your name] | [Your title]
|
||||
```
|
||||
|
||||
**Step slide formula:**
|
||||
```
|
||||
Step [N]: [Action verb] + [Object]
|
||||
|
||||
[2-3 sentences explaining the step]
|
||||
|
||||
Pro tip: [One practical detail]
|
||||
```
|
||||
|
||||
**Caption template:**
|
||||
```
|
||||
Most [audience] struggle with [problem].
|
||||
|
||||
I've been doing [process] for [timeframe], and here's the method that consistently works.
|
||||
|
||||
Swipe through for the full breakdown.
|
||||
|
||||
Save this if you want to come back to it later.
|
||||
|
||||
#[topic] #[niche] #[format]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 2: Listicle / Top N
|
||||
|
||||
**Best for:** Curated lists, tool recommendations, lessons learned, tips
|
||||
**Structure:** 6-8 slides (1 item per slide)
|
||||
|
||||
| Slide | Purpose | Content Pattern |
|
||||
|-------|---------|-----------------|
|
||||
| 1 | Cover/Hook | "[N] [things] every [audience] should know about [topic]" |
|
||||
| 2 | Item 1 | **Name/Title** + Why it matters (2-3 lines) |
|
||||
| 3 | Item 2 | **Name/Title** + Why it matters |
|
||||
| 4 | Item 3 | **Name/Title** + Why it matters |
|
||||
| 5 | Item 4 | **Name/Title** + Why it matters |
|
||||
| 6 | Item 5 | **Name/Title** + Why it matters |
|
||||
| 7 | Item 6 | **Name/Title** + Why it matters |
|
||||
| 8 | Item 7 | **Name/Title** + Why it matters |
|
||||
| 9 | Bonus | "One more that most people miss: [unexpected item]" |
|
||||
| 10 | CTA | "Which one was new to you? Tell me in the comments." |
|
||||
|
||||
**Cover slide formula:**
|
||||
```
|
||||
[N] [things] that changed how I
|
||||
[outcome]
|
||||
|
||||
(#[N] surprised me the most)
|
||||
```
|
||||
|
||||
**Item slide formula:**
|
||||
```
|
||||
#[N]: [Item name]
|
||||
|
||||
[Why it matters in 2-3 lines]
|
||||
|
||||
[Optional: One specific example or data point]
|
||||
```
|
||||
|
||||
**Caption template:**
|
||||
```
|
||||
I spent [timeframe] learning about [topic].
|
||||
|
||||
Here are [N] things I wish someone told me from the start.
|
||||
|
||||
#[N] is the one most people get wrong.
|
||||
|
||||
Which one resonates most? Drop a number in the comments.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 3: Story / Before-After
|
||||
|
||||
**Best for:** Personal narratives, transformation stories, lessons from failure
|
||||
**Structure:** 6-8 slides
|
||||
|
||||
| Slide | Purpose | Content Pattern |
|
||||
|-------|---------|-----------------|
|
||||
| 1 | Cover/Hook | "How [situation] changed everything I knew about [topic]" |
|
||||
| 2 | Setting | "[Timeframe] ago, I was [situation]." |
|
||||
| 3 | Problem | "The problem: [specific challenge in 2-3 lines]" |
|
||||
| 4 | Turning point | "Then [event/realization] happened." |
|
||||
| 5 | What changed | "I started [new approach]. Here's what shifted:" |
|
||||
| 6 | Result 1 | **Before:** [old state] → **After:** [new state] |
|
||||
| 7 | Result 2 | **Before:** [old state] → **After:** [new state] |
|
||||
| 8 | Result 3 | **Before:** [old state] → **After:** [new state] |
|
||||
| 9 | Lesson | "The real lesson: [insight in 2-3 lines]" |
|
||||
| 10 | CTA | "Has this happened to you? I'd love to hear your story." |
|
||||
|
||||
**Cover slide formula:**
|
||||
```
|
||||
[Time period] ago, I [starting state].
|
||||
|
||||
Today, [current state].
|
||||
|
||||
Here's what changed.
|
||||
```
|
||||
|
||||
**Before/After slide formula:**
|
||||
```
|
||||
BEFORE:
|
||||
[Specific old behavior or result]
|
||||
|
||||
AFTER:
|
||||
[Specific new behavior or result]
|
||||
|
||||
The difference: [one-line insight]
|
||||
```
|
||||
|
||||
**Caption template:**
|
||||
```
|
||||
[Timeframe] ago, I made a mistake that [consequence].
|
||||
|
||||
Looking back, it was the best thing that could have happened.
|
||||
|
||||
Swipe through for the full story and the lesson I learned.
|
||||
|
||||
What's a mistake that turned into your biggest learning?
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 4: Comparison / vs.
|
||||
|
||||
**Best for:** Tool comparisons, approach differences, myth-busting, framework contrasts
|
||||
**Structure:** 6-8 slides
|
||||
|
||||
| Slide | Purpose | Content Pattern |
|
||||
|-------|---------|-----------------|
|
||||
| 1 | Cover/Hook | "[Option A] vs [Option B]: Which one actually works?" |
|
||||
| 2 | Context | "Everyone argues about [topic]. Here's what the data says." |
|
||||
| 3 | Dimension 1 | **[Criteria]:** A = [detail] / B = [detail] |
|
||||
| 4 | Dimension 2 | **[Criteria]:** A = [detail] / B = [detail] |
|
||||
| 5 | Dimension 3 | **[Criteria]:** A = [detail] / B = [detail] |
|
||||
| 6 | Dimension 4 | **[Criteria]:** A = [detail] / B = [detail] |
|
||||
| 7 | Dimension 5 | **[Criteria]:** A = [detail] / B = [detail] |
|
||||
| 8 | Summary table | Side-by-side with checkmarks/scores |
|
||||
| 9 | Verdict | "My recommendation: [nuanced answer based on context]" |
|
||||
| 10 | CTA | "Which one do you use? Agree or disagree with my verdict?" |
|
||||
|
||||
**Cover slide formula:**
|
||||
```
|
||||
[Option A] vs. [Option B]
|
||||
|
||||
I tested both.
|
||||
Here's what I found.
|
||||
```
|
||||
|
||||
**Comparison slide formula:**
|
||||
```
|
||||
[Criteria name]
|
||||
|
||||
[Option A]: [Rating or description]
|
||||
[Option B]: [Rating or description]
|
||||
|
||||
Winner: [A or B] (because [one-line reason])
|
||||
```
|
||||
|
||||
**Caption template:**
|
||||
```
|
||||
"Should I use [A] or [B]?"
|
||||
|
||||
I get asked this [frequency]. So I compared them across [N] dimensions.
|
||||
|
||||
The answer isn't what you'd expect.
|
||||
|
||||
Swipe through for the breakdown. My verdict is on slide [N].
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 5: Framework / Mental Model
|
||||
|
||||
**Best for:** Original frameworks, decision matrices, thinking models
|
||||
**Structure:** 6-8 slides
|
||||
|
||||
| Slide | Purpose | Content Pattern |
|
||||
|-------|---------|-----------------|
|
||||
| 1 | Cover/Hook | "The [Name] Framework: How to [outcome]" |
|
||||
| 2 | Problem | "Why most [audience] fail at [topic]" |
|
||||
| 3 | Overview | Visual diagram or named components of the framework |
|
||||
| 4 | Component 1 | **Name** + What it means + How to apply |
|
||||
| 5 | Component 2 | **Name** + What it means + How to apply |
|
||||
| 6 | Component 3 | **Name** + What it means + How to apply |
|
||||
| 7 | Component 4 | **Name** + What it means + How to apply |
|
||||
| 8 | Example | "Here's what it looks like in practice: [specific scenario]" |
|
||||
| 9 | Quick-start | "Start here: [simplest first step]" |
|
||||
| 10 | CTA | "Save this framework. Tag someone who needs it." |
|
||||
|
||||
**Cover slide formula:**
|
||||
```
|
||||
The [Name] Framework
|
||||
|
||||
[One-line promise of what it enables]
|
||||
|
||||
[Optional: diagram or visual representation]
|
||||
```
|
||||
|
||||
**Component slide formula:**
|
||||
```
|
||||
[Component Name]
|
||||
|
||||
What: [Definition in 1 line]
|
||||
Why: [Why it matters in 1 line]
|
||||
How: [Actionable step in 1-2 lines]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Caption Best Practices
|
||||
|
||||
Carousels need strong captions because the caption appears alongside the cover slide. A weak caption means no one swipes.
|
||||
|
||||
**Caption structure:**
|
||||
1. **Hook** (first line): Question, bold claim, or surprising stat
|
||||
2. **Context** (1-2 lines): Why this matters to your audience
|
||||
3. **Swipe prompt**: "Swipe through for..." or "Slide [N] is the one most miss"
|
||||
4. **Engagement CTA**: Question that invites comments
|
||||
5. **Hashtags**: 3-4 maximum, at the end
|
||||
|
||||
**Do:**
|
||||
- Reference a specific slide to create curiosity
|
||||
- Ask which point resonated most
|
||||
- Tell them to save it for later
|
||||
|
||||
**Don't:**
|
||||
- Write a long caption that says everything the slides say
|
||||
- Use "link in comments" (carousel IS the content)
|
||||
- Add more than 4 hashtags
|
||||
|
||||
## Carousel Quality Checklist
|
||||
|
||||
- [ ] Cover slide has a clear promise or question
|
||||
- [ ] Each slide has one point (not multiple ideas)
|
||||
- [ ] Text is readable on mobile without zooming (24pt+ body)
|
||||
- [ ] 5-8 slides total (7 is optimal. Completion drops 40% beyond 15)
|
||||
- [ ] Last slide has a clear CTA
|
||||
- [ ] Caption hooks attention and prompts swipe
|
||||
- [ ] Consistent font, colors, and layout across all slides
|
||||
- [ ] Exported as PDF, under 100 MB
|
||||
330
assets/templates/linkedin-article-template.md
Normal file
330
assets/templates/linkedin-article-template.md
Normal file
|
|
@ -0,0 +1,330 @@
|
|||
# LinkedIn Article Template
|
||||
|
||||
Use this template when creating LinkedIn Articles (long-form content, 1,500-2,500 words).
|
||||
|
||||
## Article Metadata
|
||||
|
||||
```yaml
|
||||
title: "[60-80 characters, keyword-rich]"
|
||||
target_length: 1500-2500 words
|
||||
reading_time: 8-12 minutes
|
||||
primary_keyword: "[main search term]"
|
||||
secondary_keywords: ["keyword2", "keyword3"]
|
||||
target_audience: "[specific reader profile]"
|
||||
article_goal: "[what should reader do/feel/know after reading]"
|
||||
```
|
||||
|
||||
## Article Structure
|
||||
|
||||
### Title (60-80 characters)
|
||||
|
||||
**Format options:**
|
||||
- How to [achieve outcome] (Without [common obstacle])
|
||||
- The [Number] [Things] That [Outcome]
|
||||
- Why [Common Belief] Is Wrong (And What to Do Instead)
|
||||
- What [Time Period] Taught Me About [Topic]
|
||||
- [Topic]: The Complete Guide for [Audience]
|
||||
|
||||
**Your title:**
|
||||
```
|
||||
[WRITE TITLE HERE]
|
||||
```
|
||||
|
||||
**Checklist:**
|
||||
- [ ] Contains primary keyword
|
||||
- [ ] Promises clear value
|
||||
- [ ] Under 80 characters
|
||||
- [ ] Not clickbait
|
||||
|
||||
---
|
||||
|
||||
### Opening Hook (First 2-3 paragraphs, 150-250 words)
|
||||
|
||||
**Purpose:** Grab attention, establish why this matters NOW, preview value
|
||||
|
||||
**Template:**
|
||||
```
|
||||
[Opening hook - surprising stat, bold claim, or compelling question]
|
||||
|
||||
[Why this matters to the reader - what problem does it solve?]
|
||||
|
||||
[What the reader will learn/gain from this article]
|
||||
|
||||
[Brief credibility statement - why you can speak on this]
|
||||
```
|
||||
|
||||
**Your opening:**
|
||||
```
|
||||
[WRITE OPENING HERE]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Context Section (200-400 words)
|
||||
|
||||
**Purpose:** Provide background needed to understand the main content
|
||||
|
||||
**Template:**
|
||||
```
|
||||
## The Background You Need
|
||||
|
||||
[Brief history or context of the topic]
|
||||
|
||||
[Current state of affairs]
|
||||
|
||||
[Why now is the right time to address this]
|
||||
|
||||
[Any key definitions or concepts needed]
|
||||
```
|
||||
|
||||
**Your context section:**
|
||||
```
|
||||
[WRITE CONTEXT HERE]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Main Content (1,000-1,800 words)
|
||||
|
||||
**Purpose:** Deliver the core value - insights, framework, how-to
|
||||
|
||||
**Structure options:**
|
||||
|
||||
**Option A: Numbered sections**
|
||||
```
|
||||
## 1. [First Main Point]
|
||||
|
||||
[Explanation of point]
|
||||
|
||||
[Example or evidence]
|
||||
|
||||
[How to apply this]
|
||||
|
||||
## 2. [Second Main Point]
|
||||
|
||||
[Repeat structure]
|
||||
|
||||
## 3. [Third Main Point]
|
||||
|
||||
[Repeat structure]
|
||||
```
|
||||
|
||||
**Option B: Problem-Solution**
|
||||
```
|
||||
## The Problem
|
||||
|
||||
[Detailed problem description]
|
||||
|
||||
## Why Traditional Approaches Fail
|
||||
|
||||
[Analysis of common approaches]
|
||||
|
||||
## A Better Approach
|
||||
|
||||
[Your solution/framework]
|
||||
|
||||
## How to Implement
|
||||
|
||||
[Step-by-step guidance]
|
||||
```
|
||||
|
||||
**Option C: Narrative**
|
||||
```
|
||||
## The Beginning
|
||||
|
||||
[Story setup]
|
||||
|
||||
## The Challenge
|
||||
|
||||
[What happened]
|
||||
|
||||
## The Turning Point
|
||||
|
||||
[Key realization]
|
||||
|
||||
## The Result
|
||||
|
||||
[Outcome and lessons]
|
||||
|
||||
## The Broader Application
|
||||
|
||||
[How readers can apply this]
|
||||
```
|
||||
|
||||
**Your main content:**
|
||||
```
|
||||
[WRITE MAIN CONTENT HERE]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Conclusion (150-250 words)
|
||||
|
||||
**Purpose:** Summarize, synthesize, and call to action
|
||||
|
||||
**Template:**
|
||||
```
|
||||
## What This Means for You
|
||||
|
||||
[Brief recap of key points - 2-3 sentences max]
|
||||
|
||||
[The bigger picture / why this matters]
|
||||
|
||||
[Specific next steps the reader can take]
|
||||
|
||||
[Call to action - discussion question or invitation to connect]
|
||||
```
|
||||
|
||||
**Your conclusion:**
|
||||
```
|
||||
[WRITE CONCLUSION HERE]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Article Footer
|
||||
|
||||
```
|
||||
---
|
||||
|
||||
[Optional: About the author section - 2-3 sentences]
|
||||
|
||||
[Optional: Related articles or resources]
|
||||
|
||||
[Tags/hashtags: 3-5 relevant]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Pre-Publication Checklist
|
||||
|
||||
### Content Quality
|
||||
- [ ] Title is compelling and keyword-optimized
|
||||
- [ ] Opening hooks the reader immediately
|
||||
- [ ] Main content delivers on the title's promise
|
||||
- [ ] Examples are specific and relevant
|
||||
- [ ] Conclusion has clear takeaways
|
||||
- [ ] Word count is 1,500-2,500
|
||||
|
||||
### SEO Optimization
|
||||
- [ ] Primary keyword in title
|
||||
- [ ] Primary keyword in first 100 words
|
||||
- [ ] Keywords naturally distributed throughout
|
||||
- [ ] Subheadings are descriptive
|
||||
- [ ] Images have alt text
|
||||
|
||||
### Formatting
|
||||
- [ ] Short paragraphs (3-4 sentences max)
|
||||
- [ ] Clear section headings
|
||||
- [ ] Bullet points for lists
|
||||
- [ ] Tables for comparisons
|
||||
- [ ] White space for readability
|
||||
- [ ] Mobile-friendly formatting
|
||||
|
||||
### Attribution
|
||||
- [ ] All sources credited
|
||||
- [ ] External links working
|
||||
- [ ] Quotes properly attributed
|
||||
- [ ] No plagiarism
|
||||
|
||||
---
|
||||
|
||||
## Promotion Timeline
|
||||
|
||||
### Pre-Publication (1 week before)
|
||||
|
||||
**Day -7:**
|
||||
- [ ] Tease the topic in a post (generate interest)
|
||||
|
||||
**Day -3:**
|
||||
- [ ] Second tease post (share one insight from article)
|
||||
|
||||
**Day -1:**
|
||||
- [ ] Engage actively with your network (5x5x5 method)
|
||||
|
||||
### Publication Day
|
||||
|
||||
**Morning (publication):**
|
||||
- [ ] Publish article
|
||||
- [ ] Create promotional post (not just a link)
|
||||
- [ ] Share key insight with article link in comments
|
||||
|
||||
**Throughout the day:**
|
||||
- [ ] Respond to all comments on article
|
||||
- [ ] Respond to all comments on promotional post
|
||||
- [ ] Thank people who share
|
||||
|
||||
### Post-Publication (1-4 weeks after)
|
||||
|
||||
**Week 1:**
|
||||
- [ ] Create 2-3 derivative posts from article content
|
||||
- [ ] Each post links back to full article in comments
|
||||
|
||||
**Week 2:**
|
||||
- [ ] Create carousel version of key points (if applicable)
|
||||
- [ ] Reference article in relevant conversations
|
||||
|
||||
**Week 3-4:**
|
||||
- [ ] Continue derivative content
|
||||
- [ ] Update article if new information emerges
|
||||
|
||||
### Ongoing
|
||||
|
||||
- [ ] Add to Featured section on profile
|
||||
- [ ] Reference in future relevant posts
|
||||
- [ ] Update quarterly if evergreen topic
|
||||
|
||||
---
|
||||
|
||||
## Promotional Post Template
|
||||
|
||||
Use this to promote your article (don't just share the link):
|
||||
|
||||
```
|
||||
[Hook - the most valuable insight from the article]
|
||||
|
||||
[Why this matters - 2-3 sentences]
|
||||
|
||||
[What the reader will learn - bullet points]
|
||||
- Point 1
|
||||
- Point 2
|
||||
- Point 3
|
||||
|
||||
[Tease - hint at something unexpected in the article]
|
||||
|
||||
[CTA - read the full article, link in comments]
|
||||
|
||||
---
|
||||
Comment #1: Full article here: [Link]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Article Ideas Starter
|
||||
|
||||
Generate article ideas by combining:
|
||||
|
||||
| Your Expertise | + | Format |
|
||||
|----------------|---|--------|
|
||||
| AI implementation | | Complete guide |
|
||||
| Low-code automation | | Step-by-step tutorial |
|
||||
| Public sector AI | | Lessons learned |
|
||||
| Microsoft ecosystem | | Comparison/analysis |
|
||||
| RAG architecture | | Framework/methodology |
|
||||
|
||||
**Example combinations:**
|
||||
- "AI Implementation: The Complete Guide for Public Sector Leaders"
|
||||
- "5 RAG Architecture Patterns I've Used Across 20+ Projects"
|
||||
- "Why Public Sector AI Projects Fail (And How to Fix Them)"
|
||||
- "Copilot Studio vs Power Automate: A Practical Comparison"
|
||||
- "Building Your First RAG System: A Step-by-Step Tutorial"
|
||||
|
||||
---
|
||||
|
||||
## Notes
|
||||
|
||||
- Articles get less initial reach but longer lifespan
|
||||
- Optimize for search (keywords in title, headings)
|
||||
- Link internally to your other articles
|
||||
- Update evergreen content quarterly
|
||||
- Feature best articles on profile
|
||||
249
assets/templates/my-post-templates.md
Normal file
249
assets/templates/my-post-templates.md
Normal file
|
|
@ -0,0 +1,249 @@
|
|||
# My Custom Post Templates
|
||||
|
||||
Save your proven post structures here. When you find a format that works consistently, document it so Claude can replicate the pattern.
|
||||
|
||||
---
|
||||
|
||||
## Template 1: [Name - e.g., "My Framework Introduction Template"]
|
||||
|
||||
**When to use:** [e.g., "When introducing a new framework or model I've developed"]
|
||||
|
||||
**Structure:**
|
||||
|
||||
```
|
||||
[HOOK - Counterintuitive stat or bold statement]
|
||||
(1-2 lines, <110 characters)
|
||||
|
||||
[CONTEXT - The problem this framework solves]
|
||||
(2-3 lines explaining why people struggle)
|
||||
|
||||
[FRAMEWORK INTRODUCTION]
|
||||
"I developed [Framework Name] to solve this."
|
||||
(Brief one-line description)
|
||||
|
||||
[COMPONENT BREAKDOWN]
|
||||
Stage 1: [Name]
|
||||
→ [Key characteristic in one line]
|
||||
|
||||
Stage 2: [Name]
|
||||
→ [Key characteristic in one line]
|
||||
|
||||
Stage 3: [Name]
|
||||
→ [Key characteristic in one line]
|
||||
|
||||
[IMPLICATION]
|
||||
"Most organizations are stuck at Stage 1.
|
||||
Here's what moving to Stage 2 unlocks..."
|
||||
(2-3 lines on practical value)
|
||||
|
||||
[CTA]
|
||||
"Which stage is your organization in?"
|
||||
```
|
||||
|
||||
**Why this works for me:**
|
||||
- [Reason 1 - e.g., "My audience loves actionable frameworks"]
|
||||
- [Reason 2 - e.g., "The diagnostic question always generates 15+ comments"]
|
||||
|
||||
**Example posts using this template:**
|
||||
- [Link to post 1]
|
||||
- [Link to post 2]
|
||||
|
||||
**Average engagement:** [Metrics]
|
||||
|
||||
---
|
||||
|
||||
## Template 2: [Name - e.g., "My Before/After Transformation Story"]
|
||||
|
||||
**When to use:** [e.g., "When sharing case study or project results"]
|
||||
|
||||
**Structure:**
|
||||
|
||||
```
|
||||
[HOOK - The transformation in numbers]
|
||||
"6 months ago: [painful metric]
|
||||
Today: [improved metric]"
|
||||
|
||||
[THE BEFORE]
|
||||
[Organization] was struggling with [specific problem].
|
||||
(Paint picture of pain - 3-4 lines)
|
||||
|
||||
[THE TURNING POINT]
|
||||
We decided to [key decision].
|
||||
Most teams choose [alternative]. Here's why we didn't...
|
||||
|
||||
[THE APPROACH]
|
||||
"Three things mattered:
|
||||
• [Element 1]
|
||||
• [Element 2]
|
||||
• [Element 3]"
|
||||
|
||||
[THE AFTER]
|
||||
Results:
|
||||
→ [Metric 1]: [Before] → [After]
|
||||
→ [Metric 2]: [Before] → [After]
|
||||
→ [Metric 3]: [Before] → [After]
|
||||
|
||||
[KEY LESSON]
|
||||
"The real breakthrough wasn't [expected thing].
|
||||
It was [non-obvious insight]."
|
||||
|
||||
[CTA]
|
||||
"What's been YOUR biggest lesson in [topic]?"
|
||||
```
|
||||
|
||||
**Why this works for me:**
|
||||
- [Reason 1]
|
||||
- [Reason 2]
|
||||
|
||||
**Average engagement:** [Metrics]
|
||||
|
||||
---
|
||||
|
||||
## Template 3: [Name - e.g., "My Contrarian Take"]
|
||||
|
||||
**When to use:** [e.g., "When challenging conventional wisdom in my field"]
|
||||
|
||||
**Structure:**
|
||||
|
||||
```
|
||||
[HOOK - Bold contrarian statement]
|
||||
"Everyone says [conventional wisdom].
|
||||
I think that's wrong."
|
||||
|
||||
[THE CONVENTIONAL APPROACH]
|
||||
Most [target audience] believe [common belief].
|
||||
(Explain the mainstream view fairly - 2-3 lines)
|
||||
|
||||
[WHY IT FAILS]
|
||||
But here's the problem...
|
||||
(2-3 specific reasons with examples)
|
||||
|
||||
[THE ALTERNATIVE]
|
||||
Instead, try this:
|
||||
→ [Alternative approach 1]
|
||||
→ [Alternative approach 2]
|
||||
→ [Alternative approach 3]
|
||||
|
||||
[EVIDENCE]
|
||||
"I've seen this play out across [X] projects:
|
||||
[Specific result/pattern you've observed]"
|
||||
|
||||
[NUANCE]
|
||||
"To be clear: [conventional wisdom] works if [specific condition].
|
||||
But for [your context], [your approach] is better because..."
|
||||
|
||||
[CTA]
|
||||
"What's your experience? Am I missing something?"
|
||||
```
|
||||
|
||||
**Why this works for me:**
|
||||
- [Reason 1]
|
||||
- [Reason 2]
|
||||
|
||||
**Average engagement:** [Metrics]
|
||||
|
||||
---
|
||||
|
||||
## Template 4: [Name - e.g., "My Failure Lesson Post"]
|
||||
|
||||
**When to use:** [e.g., "When sharing what didn't work to build trust"]
|
||||
|
||||
**Structure:**
|
||||
|
||||
```
|
||||
[HOOK - Admission of failure]
|
||||
"[Approach] should have worked.
|
||||
It failed spectacularly."
|
||||
|
||||
[SETUP]
|
||||
We were trying to [goal].
|
||||
The plan: [what you intended to do]
|
||||
On paper, perfect.
|
||||
|
||||
[THE FAILURE]
|
||||
"Here's what actually happened..."
|
||||
(Specific description of what went wrong - 3-4 lines)
|
||||
|
||||
[WHY IT FAILED]
|
||||
Looking back, three mistakes:
|
||||
1. [Mistake 1] - We assumed [wrong assumption]
|
||||
2. [Mistake 2] - We underestimated [factor]
|
||||
3. [Mistake 3] - We ignored [warning sign]
|
||||
|
||||
[THE PIVOT]
|
||||
"So we tried [different approach] instead.
|
||||
That worked because..."
|
||||
|
||||
[THE LEARNING]
|
||||
"Key lesson:
|
||||
[Non-obvious insight that only came from the failure]"
|
||||
|
||||
[CTA]
|
||||
"Have you failed at [topic] too? What did you learn?"
|
||||
```
|
||||
|
||||
**Why this works for me:**
|
||||
- [Reason 1]
|
||||
- [Reason 2]
|
||||
|
||||
**Average engagement:** [Metrics]
|
||||
|
||||
---
|
||||
|
||||
## Template 5: [Name - Your custom template]
|
||||
|
||||
**When to use:** [Context]
|
||||
|
||||
**Structure:**
|
||||
[Your proven structure]
|
||||
|
||||
**Why this works for me:**
|
||||
[Analysis]
|
||||
|
||||
**Average engagement:** [Metrics]
|
||||
|
||||
---
|
||||
|
||||
## Template Performance Comparison
|
||||
|
||||
| Template | Avg. Likes | Avg. Comments | Avg. Reach | Best Use Case |
|
||||
|----------|-----------|---------------|------------|---------------|
|
||||
| Framework Intro | [X] | [Y] | [Z] | [When] |
|
||||
| Before/After | [X] | [Y] | [Z] | [When] |
|
||||
| Contrarian | [X] | [Y] | [Z] | [When] |
|
||||
| Failure Lesson | [X] | [Y] | [Z] | [When] |
|
||||
|
||||
**Insights:**
|
||||
[What these patterns tell you about your audience preferences]
|
||||
|
||||
---
|
||||
|
||||
## Template Selection Guide
|
||||
|
||||
**Use Framework template when:**
|
||||
- Introducing new model/system
|
||||
- Teaching actionable process
|
||||
- Want high saves (reference value)
|
||||
|
||||
**Use Before/After template when:**
|
||||
- Have strong results to share
|
||||
- Building credibility
|
||||
- Want case study authority
|
||||
|
||||
**Use Contrarian template when:**
|
||||
- Challenging assumptions
|
||||
- Positioning unique POV
|
||||
- Want engagement/debate
|
||||
|
||||
**Use Failure template when:**
|
||||
- Building trust/authenticity
|
||||
- Sharing hard-won lessons
|
||||
- Want vulnerable connection
|
||||
|
||||
---
|
||||
|
||||
## Update Log
|
||||
|
||||
- [Date]: Created template 1 based on [successful posts]
|
||||
- [Date]: Refined template 2 after [pattern observation]
|
||||
- [Date]: Added template 3 for [new content type]
|
||||
525
assets/templates/post-type-templates.md
Normal file
525
assets/templates/post-type-templates.md
Normal file
|
|
@ -0,0 +1,525 @@
|
|||
# Post Type Templates
|
||||
|
||||
Quick-start templates for common LinkedIn post types. Copy, customize, and post.
|
||||
|
||||
---
|
||||
|
||||
## Template 1: Reaction Post
|
||||
|
||||
**Use when:** News drops, something changes in your industry, you see a trend emerging.
|
||||
|
||||
```
|
||||
[Industry event/news - state what happened]
|
||||
|
||||
My take: [Your perspective in 1-2 sentences]
|
||||
|
||||
[Question for audience OR prediction about what this means]
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Tech news reaction:**
|
||||
```
|
||||
OpenAI just announced [feature].
|
||||
|
||||
My take: This matters less for the tech and more for
|
||||
what it signals about where the industry is heading.
|
||||
|
||||
What do you think - genuine innovation or
|
||||
incremental improvement?
|
||||
```
|
||||
|
||||
**Industry change reaction:**
|
||||
```
|
||||
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.
|
||||
```
|
||||
|
||||
**Trend reaction:**
|
||||
```
|
||||
Third announcement about [trend] this week.
|
||||
|
||||
Either this is genuinely the next big thing,
|
||||
or we're all drinking the same Kool-Aid.
|
||||
|
||||
I'm cautiously optimistic. Where do you land?
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 2: Quick Tip Post
|
||||
|
||||
**Use when:** You learned something useful, found a shortcut, discovered a fix.
|
||||
|
||||
```
|
||||
[Bold claim about the tip]
|
||||
|
||||
Here's why: [Brief explanation - 1-2 sentences]
|
||||
|
||||
[How to apply it OR invitation to share their version]
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Tool tip:**
|
||||
```
|
||||
Stop manually formatting your LinkedIn posts.
|
||||
|
||||
I use [tool/technique] and it takes 30 seconds
|
||||
instead of 10 minutes.
|
||||
|
||||
Here's the exact workflow: [1-2 steps]
|
||||
|
||||
What's your time-saving hack?
|
||||
```
|
||||
|
||||
**Process tip:**
|
||||
```
|
||||
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].
|
||||
```
|
||||
|
||||
**Mindset tip:**
|
||||
```
|
||||
Before any important meeting, I ask one question:
|
||||
|
||||
"What's the one outcome that makes this worth everyone's time?"
|
||||
|
||||
Sounds simple. Cuts meeting time in half.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 3: Observation Post
|
||||
|
||||
**Use when:** You noticed a pattern, saw something interesting, made a connection.
|
||||
|
||||
```
|
||||
I've noticed [pattern/trend].
|
||||
|
||||
[Evidence or example - specific, concrete]
|
||||
|
||||
Anyone else seeing this?
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Industry observation:**
|
||||
```
|
||||
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?
|
||||
```
|
||||
|
||||
**Behavioral observation:**
|
||||
```
|
||||
Interesting pattern in my calendar this month:
|
||||
|
||||
The meetings that produced results had fewer
|
||||
than 5 people. The ones with 10+ produced... documents.
|
||||
|
||||
Starting to say no to large meetings.
|
||||
What's your threshold?
|
||||
```
|
||||
|
||||
**Market observation:**
|
||||
```
|
||||
Three companies in my network just paused
|
||||
their AI initiatives.
|
||||
|
||||
Not because of budget. Because they don't
|
||||
know what problem to solve.
|
||||
|
||||
Strategy before technology. Always.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 4: Hot Take Post
|
||||
|
||||
**Use when:** You disagree with common wisdom, have a controversial opinion, want to start debate.
|
||||
|
||||
```
|
||||
Unpopular opinion: [Your take]
|
||||
|
||||
[Why you believe this - 1-2 sentences]
|
||||
|
||||
Change my mind.
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Industry hot take:**
|
||||
```
|
||||
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.
|
||||
```
|
||||
|
||||
**Process hot take:**
|
||||
```
|
||||
Hot take: The problem with [common practice]
|
||||
isn't that it doesn't work.
|
||||
|
||||
It's that it works just well enough that
|
||||
we never question if there's a better way.
|
||||
|
||||
What "works" for you that might be holding you back?
|
||||
```
|
||||
|
||||
**Career hot take:**
|
||||
```
|
||||
Controversial: The best career advice isn't
|
||||
"find your passion."
|
||||
|
||||
It's "get really good at something useful,
|
||||
and passion often follows."
|
||||
|
||||
Agree or disagree?
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 5: Failure/Mistake Post
|
||||
|
||||
**Use when:** Something went wrong, you made an error, you learned from a mistake.
|
||||
|
||||
```
|
||||
I made a mistake with [topic/project].
|
||||
|
||||
Here's what went wrong: [Brief explanation]
|
||||
|
||||
Lesson learned: [What you'd do differently]
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Project failure:**
|
||||
```
|
||||
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.
|
||||
```
|
||||
|
||||
**Decision mistake:**
|
||||
```
|
||||
Spent 3 weeks optimizing the wrong metric.
|
||||
|
||||
Got so focused on [metric A] that I missed
|
||||
[metric B] collapsing.
|
||||
|
||||
Now I check the dashboard before the details.
|
||||
```
|
||||
|
||||
**Communication mistake:**
|
||||
```
|
||||
Sent a message that came across completely wrong.
|
||||
|
||||
What I meant: [intention]
|
||||
What they heard: [interpretation]
|
||||
|
||||
Learning to re-read everything from their perspective.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 6: Question Post
|
||||
|
||||
**Use when:** You want to spark discussion, gather perspectives, learn from your network.
|
||||
|
||||
```
|
||||
[Context-setting statement]
|
||||
|
||||
[Specific question]
|
||||
|
||||
I'll share my thinking in the comments.
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Industry question:**
|
||||
```
|
||||
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).
|
||||
```
|
||||
|
||||
**Career question:**
|
||||
```
|
||||
At what point does "being a generalist"
|
||||
become "not being an expert in anything"?
|
||||
|
||||
Genuinely wrestling with this.
|
||||
Where do you draw the line?
|
||||
```
|
||||
|
||||
**Tool question:**
|
||||
```
|
||||
Looking for recommendations:
|
||||
What's your go-to tool for [specific task]?
|
||||
|
||||
Currently using [current tool] but feeling
|
||||
like there's something better out there.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 7: Curation Post
|
||||
|
||||
**Use when:** You found something worth sharing, want to add your perspective to existing content.
|
||||
|
||||
```
|
||||
[What you found/read/watched]
|
||||
|
||||
[Your specific takeaway - not just "it was great"]
|
||||
|
||||
[Link in comments or tag the creator]
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Article curation:**
|
||||
```
|
||||
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.
|
||||
```
|
||||
|
||||
**Creator curation:**
|
||||
```
|
||||
[Creator name] nailed something I've been
|
||||
trying to articulate for months:
|
||||
|
||||
[Paraphrase their key point]
|
||||
|
||||
If you care about [topic], follow them.
|
||||
```
|
||||
|
||||
**Resource curation:**
|
||||
```
|
||||
Best thing I've read this week on [topic]:
|
||||
|
||||
[Brief summary of the insight]
|
||||
|
||||
Saving this for the next time I [relevant situation].
|
||||
|
||||
[Tag creator or link placement]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Template 8: One-Liner Post
|
||||
|
||||
**Use when:** You have a punchy insight that doesn't need explanation.
|
||||
|
||||
```
|
||||
[Single powerful statement]
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Wisdom one-liner:**
|
||||
```
|
||||
The best processes are invisible.
|
||||
The worst processes require training.
|
||||
```
|
||||
|
||||
**Observation one-liner:**
|
||||
```
|
||||
Every "AI transformation" I've seen succeed
|
||||
started with spreadsheets and post-its.
|
||||
```
|
||||
|
||||
**Contrarian one-liner:**
|
||||
```
|
||||
The companies with the best AI strategies
|
||||
are the ones not talking about AI.
|
||||
```
|
||||
|
||||
**Note:** One-liners work best when you've built enough credibility that people trust your perspective without explanation. Use sparingly - maybe 1 in 10 posts.
|
||||
|
||||
---
|
||||
|
||||
## Expertise-Specific Examples
|
||||
|
||||
### For AI/Tech Professionals
|
||||
|
||||
**Reaction:**
|
||||
```
|
||||
New Claude update just dropped with [feature].
|
||||
|
||||
First impression: This changes how I think
|
||||
about [specific use case].
|
||||
|
||||
Testing it today. What are you most curious about?
|
||||
```
|
||||
|
||||
**Observation:**
|
||||
```
|
||||
Noticed something in every successful AI pilot
|
||||
I've been part of:
|
||||
|
||||
The team spent more time on change management
|
||||
than on the technology.
|
||||
|
||||
Tech is the easy part.
|
||||
```
|
||||
|
||||
**Quick Tip:**
|
||||
```
|
||||
Prompt engineering tip that took me too long to learn:
|
||||
|
||||
Start with the output format you want,
|
||||
then work backwards to the instruction.
|
||||
|
||||
Sounds obvious. Changed everything.
|
||||
```
|
||||
|
||||
### For Leaders/Managers
|
||||
|
||||
**Hot Take:**
|
||||
```
|
||||
Unpopular opinion: Most leadership advice
|
||||
is written by people who haven't led in years.
|
||||
|
||||
Theory is important.
|
||||
So is what's actually working right now.
|
||||
|
||||
Who are you learning from?
|
||||
```
|
||||
|
||||
**Failure:**
|
||||
```
|
||||
Gave feedback yesterday that landed completely wrong.
|
||||
|
||||
My intention: Help them grow.
|
||||
Their experience: Felt criticized.
|
||||
|
||||
Working on leading with curiosity, not conclusions.
|
||||
```
|
||||
|
||||
**Question:**
|
||||
```
|
||||
Leaders: How do you create psychological safety
|
||||
in a remote team?
|
||||
|
||||
Genuine question.
|
||||
The old playbook doesn't quite translate.
|
||||
|
||||
What's working for you?
|
||||
```
|
||||
|
||||
### For Consultants/Advisors
|
||||
|
||||
**Curation:**
|
||||
```
|
||||
Best framework I've encountered this month
|
||||
for [specific challenge]:
|
||||
|
||||
[Brief description]
|
||||
|
||||
Changed how I approach [type of engagement].
|
||||
Full breakdown in comments.
|
||||
```
|
||||
|
||||
**Observation:**
|
||||
```
|
||||
Pattern I'm seeing across clients:
|
||||
|
||||
The ones moving fastest on AI started
|
||||
with their biggest pain point, not the
|
||||
most impressive use case.
|
||||
|
||||
Simple beats sexy.
|
||||
```
|
||||
|
||||
**One-Liner:**
|
||||
```
|
||||
The best consultants make themselves unnecessary.
|
||||
The worst ones create dependency.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## The 3-Line Post Formula
|
||||
|
||||
For most quick posts, use this structure:
|
||||
|
||||
**Line 1: Hook (under 140 characters)**
|
||||
Creates curiosity or makes a statement
|
||||
|
||||
**Line 2: Context or Evidence (1-2 sentences)**
|
||||
Explains the "why" or provides supporting information
|
||||
|
||||
**Line 3: Insight or Question (the "so what")**
|
||||
Actionable takeaway or engagement prompt
|
||||
|
||||
**Character Target: 150-500 characters**
|
||||
|
||||
Quick posts should be SHORT. The goal is engagement and presence, not depth. If you're over 500 characters, consider whether this should be a full workflow post instead.
|
||||
|
||||
---
|
||||
|
||||
## Angle Selection Guide
|
||||
|
||||
| Angle | Opening Pattern | Best For |
|
||||
|-------|-----------------|----------|
|
||||
| Contrarian | "Everyone says X, but..." | Challenging assumptions |
|
||||
| Validating | "Here's proof that X works..." | Reinforcing with evidence |
|
||||
| Curious | "I've been wondering why..." | Opening discussion |
|
||||
| Helpful | "Here's something that saved me..." | Practical value |
|
||||
| Surprised | "I didn't expect this, but..." | Discovery sharing |
|
||||
| Frustrated | "Can we talk about why..." | Calling out problems |
|
||||
| Excited | "Just discovered..." | Genuine enthusiasm |
|
||||
| Reflective | "After X years, I've learned..." | Wisdom sharing |
|
||||
|
||||
---
|
||||
|
||||
## Converting Quick Posts to Full Content
|
||||
|
||||
When a quick post performs exceptionally well, consider expanding:
|
||||
|
||||
**Signals a quick post deserves expansion:**
|
||||
- Comment depth (people asking follow-up questions)
|
||||
- Save rate is high (people want to reference later)
|
||||
- You have more to say that wouldn't fit
|
||||
- It connects to other ideas you've shared
|
||||
|
||||
**Expansion options:**
|
||||
- Turn into carousel (break insight into 6-8 slides)
|
||||
- Write the full story behind the observation
|
||||
- Create a framework around the tip
|
||||
- Develop a post series exploring the theme
|
||||
- Save for newsletter deep-dive
|
||||
|
||||
**Tracking for expansion:**
|
||||
Keep a simple list of quick posts that outperformed. Review monthly. These are your best candidates for full content development.
|
||||
317
assets/templates/weekly-content-calendar-2-3x.md
Normal file
317
assets/templates/weekly-content-calendar-2-3x.md
Normal file
|
|
@ -0,0 +1,317 @@
|
|||
# Weekly Content Calendar (2-3 Posts/Week)
|
||||
|
||||
Templates for planning low-frequency, high-quality LinkedIn content.
|
||||
|
||||
## Weekly Schedule Templates
|
||||
|
||||
### Option A: 2 Posts/Week
|
||||
|
||||
**Minimal viable presence for busy professionals**
|
||||
|
||||
| Day | Slot | Content Type | Purpose |
|
||||
|-----|------|--------------|---------|
|
||||
| Tuesday | 8:00 AM CET | Core Expertise | Peak engagement day |
|
||||
| Thursday | 8:00 AM CET | Story/Commentary | Personality building |
|
||||
|
||||
**Time investment:** 3-4 hours/week
|
||||
|
||||
| Activity | Time | When |
|
||||
|----------|------|------|
|
||||
| Content creation | 90 min | Weekend or Monday |
|
||||
| Pre-post engagement (5x5x5) | 30 min | Before each post (2x) |
|
||||
| Post engagement | 60 min | After each post (2x) |
|
||||
| Daily maintenance | 25 min | 5 min/day other days |
|
||||
|
||||
---
|
||||
|
||||
### Option B: 3 Posts/Week (Recommended)
|
||||
|
||||
**Balanced presence for sustainable growth**
|
||||
|
||||
| Day | Slot | Content Type | Purpose |
|
||||
|-----|------|--------------|---------|
|
||||
| Tuesday | 8:00 AM CET | Core Expertise | Authority building |
|
||||
| Wednesday | 12:00 PM CET | Quick Post/News | Maintain presence |
|
||||
| Thursday | 8:00 AM CET | In-depth/Story | Engagement driver |
|
||||
|
||||
**Time investment:** 4-5 hours/week
|
||||
|
||||
| Activity | Time | When |
|
||||
|----------|------|------|
|
||||
| Content creation | 120 min | Weekend or Monday |
|
||||
| Pre-post engagement | 45 min | Before each post (3x) |
|
||||
| Post engagement | 90 min | After each post (3x) |
|
||||
| Daily maintenance | 25 min | 5 min/day non-post days |
|
||||
|
||||
---
|
||||
|
||||
### Option C: 2 Posts + 1 Article/Month
|
||||
|
||||
**For established professionals building depth**
|
||||
|
||||
**Week 1:**
|
||||
| Day | Content |
|
||||
|-----|---------|
|
||||
| Tuesday | Regular post |
|
||||
| Wednesday | Article publication |
|
||||
| Thursday | Article promotion post |
|
||||
|
||||
**Weeks 2-4:**
|
||||
| Day | Content |
|
||||
|-----|---------|
|
||||
| Tuesday | Regular post |
|
||||
| Thursday | Regular post (or article derivative) |
|
||||
|
||||
---
|
||||
|
||||
## Monthly Planning Grid
|
||||
|
||||
### 8-Post Month (2x/week)
|
||||
|
||||
| Week | Tuesday | Thursday | Notes |
|
||||
|------|---------|----------|-------|
|
||||
| 1 | Expertise deep-dive | Personal story | Foundation |
|
||||
| 2 | Framework/how-to | Industry commentary | Education |
|
||||
| 3 | Case study | Trend analysis | Credibility |
|
||||
| 4 | Tool/resource share | Reflection/lesson | Value |
|
||||
|
||||
### 12-Post Month (3x/week)
|
||||
|
||||
| Week | Tuesday | Wednesday | Thursday |
|
||||
|------|---------|-----------|----------|
|
||||
| 1 | Expertise deep-dive | Quick news take | Personal story |
|
||||
| 2 | Framework post | Commentary | Case study |
|
||||
| 3 | How-to guide | News reaction | Trend analysis |
|
||||
| 4 | Resource share | Quick insight | Monthly reflection |
|
||||
|
||||
---
|
||||
|
||||
## Content Type Rotation
|
||||
|
||||
### For AI-Focused Creators
|
||||
|
||||
**Monthly mix (8-12 posts):**
|
||||
|
||||
| Type | Count | Examples |
|
||||
|------|-------|----------|
|
||||
| AI News/Commentary | 2-3 | New releases, announcements, trends |
|
||||
| Implementation How-to | 2-3 | Patterns, tutorials, lessons |
|
||||
| Strategy/Leadership | 1-2 | ROI, governance, decisions |
|
||||
| Tools/Resources | 1-2 | Comparisons, shares, templates |
|
||||
| Personal/Story | 1-2 | Experiences, reflections |
|
||||
|
||||
### Content Pillars Grid
|
||||
|
||||
Map your posts across pillars:
|
||||
|
||||
| Pillar | Week 1 | Week 2 | Week 3 | Week 4 |
|
||||
|--------|--------|--------|--------|--------|
|
||||
| AI News | X | | X | |
|
||||
| Implementation | | X | | X |
|
||||
| Strategy | | | X | |
|
||||
| Tools | | | | X |
|
||||
| Personal | X | | | |
|
||||
|
||||
---
|
||||
|
||||
## Weekly Workflow
|
||||
|
||||
### Sunday (30 min)
|
||||
|
||||
**Planning session:**
|
||||
- [ ] Review next week's calendar slots
|
||||
- [ ] Assign topics to each slot
|
||||
- [ ] Note any timely content opportunities
|
||||
- [ ] Check for relevant news to comment on
|
||||
|
||||
### Monday (90-120 min)
|
||||
|
||||
**Batch creation:**
|
||||
- [ ] Write/finalize all posts for the week
|
||||
- [ ] Prepare visuals if needed
|
||||
- [ ] Draft first comments (links, etc.)
|
||||
- [ ] Schedule or save drafts
|
||||
|
||||
### Posting Days (45-60 min each)
|
||||
|
||||
**Pre-post (15 min before):**
|
||||
- [ ] 5x5x5 engagement on target creators
|
||||
|
||||
**Post (2 min):**
|
||||
- [ ] Publish post
|
||||
- [ ] Add first comment with link (if applicable)
|
||||
|
||||
**Post-engagement (30-45 min after):**
|
||||
- [ ] Stay online for first hour
|
||||
- [ ] Respond to every comment
|
||||
- [ ] Engage with commenters' profiles
|
||||
|
||||
### Non-Posting Days (5-10 min)
|
||||
|
||||
**Maintenance:**
|
||||
- [ ] Check for comments to respond to
|
||||
- [ ] 3-5 quick engagements on feed
|
||||
- [ ] Note content ideas
|
||||
|
||||
### Friday (15 min)
|
||||
|
||||
**Week review:**
|
||||
- [ ] Check post performance
|
||||
- [ ] Note what worked/didn't
|
||||
- [ ] Capture ideas for next week
|
||||
- [ ] Update monthly tracking
|
||||
|
||||
---
|
||||
|
||||
## Monthly Planning Template
|
||||
|
||||
### Month: _______________
|
||||
|
||||
**Goals this month:**
|
||||
- Growth target: _____ new followers
|
||||
- Engagement target: _____ average comments
|
||||
- Content focus: _____
|
||||
|
||||
### Week 1: ___ to ___
|
||||
|
||||
| Date | Day | Topic | Type | Status |
|
||||
|------|-----|-------|------|--------|
|
||||
| | Tue | | | [ ] |
|
||||
| | Wed | | | [ ] |
|
||||
| | Thu | | | [ ] |
|
||||
|
||||
Notes: _____
|
||||
|
||||
### Week 2: ___ to ___
|
||||
|
||||
| Date | Day | Topic | Type | Status |
|
||||
|------|-----|-------|------|--------|
|
||||
| | Tue | | | [ ] |
|
||||
| | Wed | | | [ ] |
|
||||
| | Thu | | | [ ] |
|
||||
|
||||
Notes: _____
|
||||
|
||||
### Week 3: ___ to ___
|
||||
|
||||
| Date | Day | Topic | Type | Status |
|
||||
|------|-----|-------|------|--------|
|
||||
| | Tue | | | [ ] |
|
||||
| | Wed | | | [ ] |
|
||||
| | Thu | | | [ ] |
|
||||
|
||||
Notes: _____
|
||||
|
||||
### Week 4: ___ to ___
|
||||
|
||||
| Date | Day | Topic | Type | Status |
|
||||
|------|-----|-------|------|--------|
|
||||
| | Tue | | | [ ] |
|
||||
| | Wed | | | [ ] |
|
||||
| | Thu | | | [ ] |
|
||||
|
||||
Notes: _____
|
||||
|
||||
### Month-End Review
|
||||
|
||||
- Total posts: _____ / planned: _____
|
||||
- Average engagement rate: _____%
|
||||
- Best performing post: _____
|
||||
- Follower growth: _____
|
||||
- Lessons learned: _____
|
||||
|
||||
---
|
||||
|
||||
## Engagement Schedule
|
||||
|
||||
### Posting Days
|
||||
|
||||
| Time | Activity |
|
||||
|------|----------|
|
||||
| 7:45 AM | 5x5x5 pre-engagement |
|
||||
| 8:00 AM | Publish post |
|
||||
| 8:00-9:00 AM | Active engagement with comments |
|
||||
| 12:00 PM | Check for new comments, respond |
|
||||
| 5:00 PM | Final comment check |
|
||||
|
||||
### Non-Posting Days
|
||||
|
||||
| Time | Activity |
|
||||
|------|----------|
|
||||
| 8:00 AM | 5-minute feed scan |
|
||||
| 12:00 PM | Check for comments on recent posts |
|
||||
| Any time | Note content ideas when they occur |
|
||||
|
||||
---
|
||||
|
||||
## Quality Standards Checklist
|
||||
|
||||
**For low-frequency posting, each post must:**
|
||||
|
||||
- [ ] Contain genuine insight (not just observation)
|
||||
- [ ] Have a compelling hook (first 140 chars)
|
||||
- [ ] Be well-structured and formatted
|
||||
- [ ] Demonstrate clear expertise
|
||||
- [ ] Include engaging CTA
|
||||
- [ ] Connect to core topic areas
|
||||
- [ ] Be worth saving (the save test)
|
||||
|
||||
**If a post doesn't meet these standards, don't publish it.** Skip a slot rather than post mediocre content.
|
||||
|
||||
---
|
||||
|
||||
## Tracking Template
|
||||
|
||||
### Weekly Metrics
|
||||
|
||||
| Week | Posts | Avg Views | Avg Likes | Avg Comments | New Followers |
|
||||
|------|-------|-----------|-----------|--------------|---------------|
|
||||
| 1 | | | | | |
|
||||
| 2 | | | | | |
|
||||
| 3 | | | | | |
|
||||
| 4 | | | | | |
|
||||
|
||||
### Monthly Summary
|
||||
|
||||
| Metric | Target | Actual |
|
||||
|--------|--------|--------|
|
||||
| Posts published | | |
|
||||
| Average engagement rate | | |
|
||||
| Total new followers | | |
|
||||
| Best post (topic) | n/a | |
|
||||
| Opportunities generated | | |
|
||||
|
||||
---
|
||||
|
||||
## Adaptation Guidelines
|
||||
|
||||
### When to increase frequency
|
||||
|
||||
- Consistently exceeding engagement targets
|
||||
- Have more time available
|
||||
- Building toward specific goal (launch, event)
|
||||
- Growing faster than expected
|
||||
|
||||
### When to maintain 2-3x
|
||||
|
||||
- Meeting targets consistently
|
||||
- Time-constrained
|
||||
- Quality > quantity preference
|
||||
- Sustainable long-term pace
|
||||
|
||||
### When to decrease
|
||||
|
||||
- Quality suffering
|
||||
- Burnout signs
|
||||
- Major life/work demands
|
||||
- Better to pause than post poorly
|
||||
|
||||
---
|
||||
|
||||
## Notes
|
||||
|
||||
- Low frequency requires HIGHER quality per post
|
||||
- Engagement time matters more than posting time
|
||||
- Consistency matters more than frequency
|
||||
- Skip a post rather than post poorly
|
||||
- Review and adjust monthly
|
||||
227
assets/voice-samples/authentic-voice-samples.md
Normal file
227
assets/voice-samples/authentic-voice-samples.md
Normal file
|
|
@ -0,0 +1,227 @@
|
|||
# Authentic Voice Samples - Kjell Tore Guttormsen
|
||||
|
||||
These guidelines help Claude understand and replicate Kjell Tore's natural writing style for LinkedIn content.
|
||||
|
||||
## Voice Profile Summary
|
||||
|
||||
Kjell Tore does not have traditional writing samples to share. Instead, his voice is defined by the following characteristics which Claude should internalize and apply consistently.
|
||||
|
||||
---
|
||||
|
||||
## Core Voice Characteristics
|
||||
|
||||
### 1. Solution-Oriented Mindset
|
||||
- Every problem is presented as an opportunity
|
||||
- Never complains without offering a path forward
|
||||
- Focuses on "what can be done" rather than "what went wrong"
|
||||
- Sees challenges as interesting puzzles to solve
|
||||
|
||||
### 2. Factual Grounding
|
||||
- Statements are based on facts, not assumptions
|
||||
- If uncertain, acknowledges uncertainty openly
|
||||
- Prefers data and evidence over opinions
|
||||
- Avoids speculation presented as fact
|
||||
|
||||
### 3. Non-Judgmental Tone
|
||||
- Observes and explains without criticizing others
|
||||
- Builds up, never tears down
|
||||
- Avoids negative commentary about people, companies, or decisions
|
||||
- When discussing alternatives, frames as "different approaches" not "better/worse"
|
||||
|
||||
### 4. Curiosity and Openness
|
||||
- Genuinely interested in learning new things
|
||||
- Open to new ideas and approaches
|
||||
- Asks questions to understand, not to challenge
|
||||
- Embraces "I don't know" as a starting point for exploration
|
||||
|
||||
### 5. Storytelling Approach
|
||||
- Uses narrative techniques to make points memorable
|
||||
- Varies storytelling patterns based on content:
|
||||
- Hero's journey (transformation stories)
|
||||
- Problem-solution (practical content)
|
||||
- Before-after (showing change/improvement)
|
||||
- Discovery narrative (learning something new)
|
||||
- Day-in-the-life (practical application)
|
||||
- Shows rather than tells
|
||||
|
||||
### 6. Actionable Conclusions
|
||||
- Ends with something the reader can do
|
||||
- The more actionable, the better
|
||||
- If no clear action, provides a clear summary/takeaway
|
||||
- Never ends on a vague note
|
||||
|
||||
---
|
||||
|
||||
## Cross-Sample Analysis
|
||||
|
||||
### Do's (Things that sound like Kjell Tore)
|
||||
|
||||
- ✅ Start with stories or concrete examples before explaining concepts
|
||||
- ✅ Use clear, accessible language even for technical topics
|
||||
- ✅ Explain technical concepts thoroughly - assume intelligence, not knowledge
|
||||
- ✅ Show rather than tell - demonstrate with examples
|
||||
- ✅ End with actionable takeaways - what can the reader do NOW?
|
||||
- ✅ Vary storytelling techniques based on the content
|
||||
- ✅ Be genuinely helpful and supportive
|
||||
- ✅ Acknowledge complexity before simplifying
|
||||
- ✅ Use transitions like "What I've learned is..." to share insights
|
||||
- ✅ Frame discoveries as shared learning, not lecturing
|
||||
- ✅ Keep posts concise - short to medium length (800-1500 characters)
|
||||
|
||||
### Don'ts (Things Kjell Tore would NEVER say)
|
||||
|
||||
- ❌ Don't use buzzwords: "game-changer", "leverage", "synergy", "disrupt", "revolutionize"
|
||||
- ❌ Don't criticize people, companies, or decisions
|
||||
- ❌ Don't use self-deprecating humor
|
||||
- ❌ Don't make assumptions without facts
|
||||
- ❌ Don't write overly long posts (stay under 1500 characters for posts)
|
||||
- ❌ Don't use more than 1-2 emojis per post
|
||||
- ❌ Don't discuss politics, religion, or personal matters
|
||||
- ❌ Don't use em dashes (—) - use hyphens or alternatives instead
|
||||
- ❌ Don't start with "Let's dive deep into..."
|
||||
- ❌ Don't use excessive exclamation marks!!!
|
||||
- ❌ Don't use generic motivational phrases
|
||||
- ❌ Don't be preachy or lecture the reader
|
||||
- ❌ Don't use "we" when you mean "I" (be direct about personal experience)
|
||||
|
||||
---
|
||||
|
||||
## Signature Phrases
|
||||
|
||||
Use these naturally when appropriate - don't force them:
|
||||
|
||||
- "Let me show you..."
|
||||
- "What I've learned is..."
|
||||
- "Here is the secret to..."
|
||||
|
||||
These phrases signal a transition to insight or demonstration. Use them to introduce key points or revelations.
|
||||
|
||||
---
|
||||
|
||||
## Vocabulary Preferences
|
||||
|
||||
### Technical Terms - How to Handle
|
||||
|
||||
- **RAG (Retrieval-Augmented Generation):** Always explain on first use
|
||||
- **MCP (Model Context Protocol):** Explain what it enables, not just the acronym
|
||||
- **Copilot Studio:** Can assume some familiarity with Microsoft ecosystem
|
||||
- **Skills (Claude):** Explain as "reusable instruction sets" or similar
|
||||
- **Low-code:** Generally understood, but clarify scope if needed
|
||||
|
||||
**Principle:** Assume intelligence, not knowledge. Explain jargon without being condescending.
|
||||
|
||||
### Words/Phrases to AVOID
|
||||
|
||||
- "Game-changer"
|
||||
- "Revolutionary"
|
||||
- "Disruption" / "Disruptive"
|
||||
- "Leverage" (as a verb)
|
||||
- "Synergy"
|
||||
- "Deep dive" / "Let's dive deep"
|
||||
- "Unpack" (as in "let me unpack this")
|
||||
- "At the end of the day"
|
||||
- "It is what it is"
|
||||
- "Touch base"
|
||||
- "Circle back"
|
||||
- "Low-hanging fruit"
|
||||
|
||||
---
|
||||
|
||||
## Humor and Personality
|
||||
|
||||
- **Humor style:** Mostly absent in professional content. If humor appears, it's observational and gentle - never at anyone's expense
|
||||
- **Self-deprecation:** Never. Don't undermine your own credibility.
|
||||
- **Cultural references:** Avoid pop culture references. Stick to professional/work context.
|
||||
- **Analogies:** Use when helpful for explanation. Prefer technical or universal analogies over sports/culture-specific ones.
|
||||
|
||||
---
|
||||
|
||||
## Transitions and Flow
|
||||
|
||||
### How to Move Between Ideas
|
||||
|
||||
- Use questions: "So what does this mean for..."
|
||||
- Use signposting: "Three things matter here..."
|
||||
- Use revelation: "Here's what I discovered..."
|
||||
- Use contrast: "The common approach is X. But what actually works is Y."
|
||||
|
||||
### How to Conclude
|
||||
|
||||
- Always tie back to practical implications
|
||||
- End with a specific action the reader can take
|
||||
- If no action possible, summarize the key insight clearly
|
||||
- Occasionally invite discussion, but don't overuse "What do you think?" as a crutch
|
||||
|
||||
---
|
||||
|
||||
## Technical Depth Adaptation
|
||||
|
||||
Match technical depth to the target audience:
|
||||
|
||||
### For Leaders
|
||||
- High-level concepts
|
||||
- Business implications
|
||||
- Strategic decisions
|
||||
- ROI and outcomes
|
||||
- Avoid implementation details
|
||||
|
||||
### For Low-Code Developers
|
||||
- Practical tips and patterns
|
||||
- Step-by-step guidance
|
||||
- Tool-specific insights
|
||||
- Common pitfalls and solutions
|
||||
- Can include some technical detail
|
||||
|
||||
### For AI Architects
|
||||
- Technical depth welcome
|
||||
- Architecture patterns
|
||||
- Integration approaches
|
||||
- Trade-offs and decisions
|
||||
- Code snippets when relevant
|
||||
|
||||
### For Power Users
|
||||
- Productivity gains
|
||||
- Workflow improvements
|
||||
- Tool comparisons
|
||||
- Time-saving techniques
|
||||
- Practical shortcuts
|
||||
|
||||
**Key principle:** Always ensure technical content is well-explained and followable, regardless of depth. If you go technical, go all the way - don't half-explain.
|
||||
|
||||
---
|
||||
|
||||
## Language Guidelines
|
||||
|
||||
- **Always English** for all LinkedIn content
|
||||
- Clear, international English accessible to non-native speakers
|
||||
- Avoid idioms that don't translate well internationally
|
||||
- Prefer simple sentence structures for complex ideas
|
||||
- Never use em dashes (—) - use hyphens, commas, or separate sentences instead
|
||||
|
||||
---
|
||||
|
||||
## Instructions for Claude
|
||||
|
||||
When generating LinkedIn content for Kjell Tore:
|
||||
|
||||
1. **Start with his voice profile** (from this document)
|
||||
2. **Check the content pillar** - which audience is this for?
|
||||
3. **Choose appropriate storytelling technique** for the content type
|
||||
4. **Ensure actionable conclusion** - what can the reader DO?
|
||||
5. **Verify against Don'ts list** - no buzzwords, no criticism, no assumptions
|
||||
6. **Keep length in check** - 800-1500 characters for posts
|
||||
|
||||
**Priority:** Sound like Kjell Tore > Optimize for algorithm
|
||||
|
||||
**Exception:** If a phrase or approach would harm reach (external links, engagement bait), flag it but maintain his voice in everything else.
|
||||
|
||||
---
|
||||
|
||||
## Update Log
|
||||
|
||||
- 2025-11-30: Initial voice profile created based on interview
|
||||
|
||||
## Collected Post Samples
|
||||
|
||||
<!-- Posts are saved here automatically by the Stop hook after each session where content is created. -->
|
||||
<!-- The voice-trainer agent uses these for 6-dimension drift scoring. Needs 5+ samples for reliable results. -->
|
||||
Loading…
Add table
Add a link
Reference in a new issue