feat(linkedin-thought-leadership): v1.1.0 — Q2 2026 feature release
9 improvements across 3 tracks: Onboarding: /linkedin:onboarding wizard, README Quick Start rewrite Content Quality: voice drift scoring, industry angle variants, /linkedin:carousel, /linkedin:react multi-URL comparison Analytics: automated week-rollover, day-of-week heatmap, month-over-month reports 25→27 commands. All Q2 ROADMAP items completed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen
parent
abf7322200
commit
1a8cc1942c
33 changed files with 1726 additions and 236 deletions
|
|
@ -1,71 +1,100 @@
|
|||
# Authentic Voice Samples - [Your Name]
|
||||
# Authentic Voice Samples - Kjell Tore Guttormsen
|
||||
|
||||
These guidelines help Claude understand and replicate [Your Name]'s natural writing style for LinkedIn content.
|
||||
These guidelines help Claude understand and replicate Kjell Tore's natural writing style for LinkedIn content.
|
||||
|
||||
## Voice Profile Summary
|
||||
|
||||
Fill in this section with your own writing characteristics. Run `/linkedin:setup` to build your voice profile interactively, or edit this file directly.
|
||||
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
|
||||
|
||||
<!-- Replace these with your own voice traits. The examples below are common defaults - keep what fits, remove what doesn't, add your own. -->
|
||||
### 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
|
||||
|
||||
### 1. [Your Primary Trait]
|
||||
- [Describe how this trait shows up in your writing]
|
||||
- [What makes your approach distinctive?]
|
||||
### 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
|
||||
|
||||
### 2. [Your Secondary Trait]
|
||||
- [Describe how this trait shows up in your writing]
|
||||
### 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"
|
||||
|
||||
### 3. [Your Third Trait]
|
||||
- [Describe how this trait shows up in your writing]
|
||||
### 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
|
||||
|
||||
<!-- Add more traits as needed. Most voice profiles have 4-6 core characteristics. -->
|
||||
### 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 [Your Name])
|
||||
### Do's (Things that sound like Kjell Tore)
|
||||
|
||||
<!-- Replace these with patterns from YOUR best-performing posts. Run /linkedin:setup to analyze your writing samples. The items below are common best practices you can keep as defaults. -->
|
||||
- ✅ 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)
|
||||
|
||||
- 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
|
||||
- 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'ts (Things [Your Name] would NEVER say)
|
||||
|
||||
<!-- Replace these with your personal anti-patterns. The items below are universal LinkedIn best practices. -->
|
||||
|
||||
- Don't use buzzwords: "game-changer", "leverage", "synergy", "disrupt", "revolutionize"
|
||||
- Don't criticize people, companies, or decisions
|
||||
- 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 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 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
|
||||
|
||||
<!-- Add 3-5 phrases that are distinctly yours. These help Claude maintain your voice. -->
|
||||
Use these naturally when appropriate - don't force them:
|
||||
|
||||
- "[Your phrase 1]"
|
||||
- "[Your phrase 2]"
|
||||
- "[Your phrase 3]"
|
||||
- "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.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -73,11 +102,11 @@ Fill in this section with your own writing characteristics. Run `/linkedin:setup
|
|||
|
||||
### Technical Terms - How to Handle
|
||||
|
||||
<!-- Replace with your domain-specific terms. Examples: -->
|
||||
|
||||
- **[Term 1]:** [How to explain/use it]
|
||||
- **[Term 2]:** [How to explain/use it]
|
||||
- **[Term 3]:** [How to explain/use it]
|
||||
- **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.
|
||||
|
||||
|
|
@ -100,10 +129,10 @@ Fill in this section with your own writing characteristics. Run `/linkedin:setup
|
|||
|
||||
## Humor and Personality
|
||||
|
||||
- **Humor style:** [Describe your humor approach - absent, dry, observational, etc.]
|
||||
- **Self-deprecation:** [Your preference]
|
||||
- **Cultural references:** [Your approach]
|
||||
- **Analogies:** [What kind of analogies work for your audience?]
|
||||
- **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.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -136,14 +165,14 @@ Match technical depth to the target audience:
|
|||
- ROI and outcomes
|
||||
- Avoid implementation details
|
||||
|
||||
### For Practitioners
|
||||
### 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 Technical Experts
|
||||
### For AI Architects
|
||||
- Technical depth welcome
|
||||
- Architecture patterns
|
||||
- Integration approaches
|
||||
|
|
@ -163,24 +192,36 @@ Match technical depth to the target audience:
|
|||
|
||||
## Language Guidelines
|
||||
|
||||
- Choose ONE language for all LinkedIn content and stick with it
|
||||
- **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 [Your Name]:
|
||||
When generating LinkedIn content for Kjell Tore:
|
||||
|
||||
1. **Start with the voice profile** (from this document)
|
||||
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 [Your Name] > Optimize for algorithm
|
||||
**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 the voice in everything else.
|
||||
**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