| name | |
| description | Create LinkedIn content using service-based authority principles. Use when drafting posts, profile sections, or comments that build trust through teaching rather than self-promotion. |
LinkedIn Content Creator
Trust is permanent; attention is fleeting.
Trigger phrases: "linkedin post", "linkedin content", "profile", "headline", "about section"
Core Philosophy: Service Over Self-Promotion
The shift: Replace trophies with maps. Instead of announcing wins, reveal the journey and frameworks that enabled success.
The Translation Test
Every achievement must pass this test before posting:
| Internal Win | Portable Principle |
|---|---|
| "Restructured sales team" | "The One-Page Org Chart Rule" |
| "Launched product in 3 months" | "The 3-Week Sprint Framework" |
| "Reduced churn by 40%" | "The Early Warning Checklist" |
| "Raised Series A" | "The Investor Narrative Arc" |
Ask: "What can someone else apply from this without access to my specific context?"
Content Framework: CLIC Structure
Every post follows Conflict → Lesson → Illustration → Conversation:
Examples:
- "Everyone says X. They're wrong."
- "I failed at [specific thing] for 3 years."
- "The advice that almost killed my startup..."
2. Lesson (The Map)
Deliver the portable insight or framework.
Structure as:
- Numbered steps (3-5 max)
- Named framework ("The XYZ Method")
- Before/After contrast
3. Illustration (The Proof)
Ground the lesson in specific, concrete detail.
Include:
- Specific numbers when possible
- Named tools or approaches
- Time-bound outcomes
4. Conversation (The Bridge)
End with a question or invitation, never a mic drop.
Examples:
- "What's your version of this?"
- "Where does this break down for you?"
- "What would you add?"
Profile Architecture of Proof
Formula: I help [specific audience] [achieve specific outcome] through [mechanism]
| Weak | Strong |
|---|---|
| "Senior PM at TechCorp" | "I help product teams ship faster with async decision frameworks" |
| "Blockchain expert" | "Making Web3 onboarding not suck for enterprises" |
| "Experienced leader" | "Building compliance systems that don't slow teams down" |
About Section: The Vulnerability Framework
- Lead with a past failure (builds trust)
- What you learned (the insight)
- Your unique framework (the value prop)
- Who you serve best (the filter)
- How to engage (the CTA)
Experience: Mechanisms, Not Activities
Transform job descriptions into legacy statements:
| Activity | Mechanism |
|---|---|
| "Managed a team of 12" | "Built the hiring playbook now used across 4 offices" |
| "Launched mobile app" | "Created the 2-week prototype framework adopted company-wide" |
| "Improved metrics" | "Designed the feedback loop that reduced churn 40%" |
Featured Section: Tangible Proof
Populate with:
- Anchor articles (your best long-form thinking)
- Templates (downloadable, actionable tools)
- Short videos (under 90 seconds, one specific insight)
Language of Quiet Confidence
| Remove | Why |
|---|---|
| "Crushed it" | Ego-driven, no value |
| "Thought leader" | Self-proclaimed, never earned |
| "Excited to announce" | Everyone uses it, invisible |
| "Humbled and honored" | False modesty pattern |
| "Game-changer" | Overused, no specificity |
Words to Use
| Pattern | Example |
|---|---|
| Active mechanism verbs | "Built", "Designed", "Shipped", "Tested" |
| Named frameworks | "The 3-Horizon Method", "The RICE Framework" |
| "We" language | Credit process over individual |
| Specific numbers | "37% improvement" not "significant gains" |
| Time bounds | "Over 6 months" not "eventually" |
The "We" Rule
Default to "we" unless the point specifically requires "I":
- "We discovered that..." (credit the process)
- "The team built..." (credit collaborators)
- "I was wrong about..." (own failures personally)
Content Cadence Protocol
Output: One bullet point in a "content seeds" note.
Weekly Creation Block (60 minutes)
Turn one seed into a full post using CLIC structure.
Process:
- Pick the seed with most tension (10 min)
- Draft the post (30 min)
- Edit for ego-removal (15 min)
- Add conversation hook (5 min)
Generosity Loop (5 minutes daily)
Comment thoughtfully on 2-3 others' posts.
Quality bar: Would you save this comment? Does it add a new angle?
Comment formula: [Specific agreement/disagreement] + [Your related experience] + [Question]
Metrics That Matter
Track (Authority Metrics)
- Inbound message quality: Do messages reference your frameworks by name?
- Speaking invitations: Are you being asked to share your approach?
- Featured section engagement: Downloads, views, shares
- "How did you learn that?": Questions about your methodology
Post Templates
Here's what I mean:
[Specific example of the wrong approach] [What I thought would happen] [What actually happened]
The fix was surprisingly simple: [Framework name]
[3-5 bullet points of the framework]
This changed my approach because [insight].
Where have you seen this pattern?
### The Framework Reveal
[Counterintuitive statement about common practice]
After [experience], I developed the [Framework Name]:
Step 1: [Action] [One sentence explanation]
Step 2: [Action] [One sentence explanation]
Step 3: [Action] [One sentence explanation]
The key insight: [The non-obvious principle]
What's your version of this?
### The Generous Comment (for others' posts)
[Specific phrase from their post] landed hard.
I've seen this play out as [your brief experience].
One thing I'd add: [your contribution].
What's your take on [related question]?
</templates>
---
<quality_checks>
## Quality Checks
Before posting, verify:
1. **Service Test:** Does this give the reader something they can use?
2. **Ego Scan:** Remove any "crushed it" / "thought leader" / "game-changer" language
3. **Translation Test:** Is the principle portable beyond your specific context?
4. **Specificity Check:** Are there concrete numbers, timeframes, or named frameworks?
5. **Conversation Test:** Does it end with a genuine question, not a statement?
6. **The Delete Test:** If this post disappeared, would anyone's day be worse?
</quality_checks>
---
<skill_compositions>
## Works Well With
- **dmitrii-writing-style** — Authentic voice for LinkedIn content
- **cv-knowledge-query** — Source achievements to transform into frameworks
- **generate-story-bank** — Interview stories often make great LinkedIn posts
- **ultrathink** — For strategic content planning and positioning decisions
</skill_compositions>
---
## Anti-Patterns
**The Humble Brag**
"I'm so humbled to announce that I was named Top 10..."
→ Share what you learned that got you there.
**The Motivational Poster**
"Hard work pays off. Never give up."
→ Share a specific story with a specific lesson.
**The Announcement Without Value**
"Excited to announce I've joined Company!"
→ Share what problem you're now solving and why it matters.
**The Thread That Should Be a Post**
Don't artificially break up short content for engagement.
→ If it's under 300 words, it's a single post.
**The Self-Reply Ladder**
Adding multiple comments to your own post for algorithmic boost.
→ If you have more to say, edit the original or write a follow-up post.
---
*Now: what LinkedIn content are we creating?*