craft-linkedin-post
Generate an engaging LinkedIn post using proven storytelling frames. Use when you want to share learnings, celebrate wins, or build professional visibility.
What this skill does
# Craft LinkedIn Post
Generate an engaging LinkedIn post optimized for developer audiences using proven storytelling frameworks.
## Arguments
`$ARGUMENTS` - The topic, story idea, or content you want to share
## Workflow
### Step 1: Gather Context
If `$ARGUMENTS` is insufficient, use AskUserQuestion to gather:
**Question 1: Post Type** (header: "Post Type")
- Learning/Mistake (share what you learned the hard way)
- Behind the Build (how you built something)
- Win/Milestone (celebrate an achievement)
- Opinion/Take (share a perspective)
- Quick Tip (tactical advice)
**Question 2: Goal** (header: "Goal")
- Build authority (establish expertise)
- Start discussion (spark conversation)
- Share value (help others)
- Announce something (news, milestone)
- Connect (relate to audience)
### Step 2: Select Storytelling Frame
Based on post type, apply the appropriate frame:
#### Frame 1: Learning the Hard Way
```text
[Bold opening about the mistake]
Last [timeframe], I [what you did wrong].
Here's what happened:
→ [Consequence 1]
→ [Consequence 2]
→ [Consequence 3]
The lesson: [Key insight]
What's a lesson you learned the hard way?
```
#### Frame 2: Behind the Build
```text
[What you built and why it matters]
Here's what nobody tells you about building [X]:
1. [Surprising challenge + how you solved it]
2. [Unexpected discovery]
3. [What you'd do differently]
The biggest lesson: [Key insight]
Have you built something similar?
```
#### Frame 3: Before/After
```text
[The dramatic contrast]
Before: [Specific pain point]
After: [Specific improvement]
Here's what changed:
Step 1: [First change]
Step 2: [Second change]
Step 3: [Third change]
The key insight: [What made the biggest difference]
```
#### Frame 4: Contrarian Take
```text
Unpopular opinion: [Your view]
I know this goes against [common wisdom].
But here's what I've seen:
→ [Evidence 1]
→ [Evidence 2]
→ [Evidence 3]
[Nuanced conclusion]
What's your experience?
```
#### Frame 5: Quick Win
```text
A simple trick that [benefit]:
[Describe the technique]
Why it works:
→ [Reason 1]
→ [Reason 2]
I use this [when/how often].
What's your go-to hack?
```
### Step 3: Craft the Hook
The first 1-2 lines determine if people click "see more."
**Hook Techniques:**
| Type | Example |
| --- | --- |
| Dramatic moment | "At 2 AM, I got the call no engineer wants." |
| Surprising statement | "Our most productive engineer writes the least code." |
| Honest confession | "I deleted 10,000 lines of code. My manager thanked me." |
| Bold claim | "Everyone's doing microservices wrong. Including us." |
| Question | "Why do we still write documentation nobody reads?" |
### Step 4: Apply Formatting Best Practices
**Structure:**
- One sentence per line
- Use line breaks liberally (no walls of text)
- Bullet points with → or • for lists
- Bold key phrases sparingly
- End with a question or CTA
**Length:**
- Optimal: 150-300 words
- Too short: Lacks substance
- Too long: People won't finish
**Engagement elements:**
- End with a question that invites sharing
- Tag relevant people (if appropriate)
- 3-5 relevant hashtags (at end)
### Step 5: Generate Post
Produce a complete, ready-to-post LinkedIn update:
```markdown
## LinkedIn Post
---
[Hook line that makes people want to click "see more"]
[Second line that builds on the hook]
[Body content using selected storytelling frame]
[Key insight or takeaway]
[CTA - Question that invites engagement]
#hashtag1 #hashtag2 #hashtag3
---
### Optimization Notes
- **Hook strength:** [Assessment]
- **Storytelling frame:** [Which frame used]
- **Engagement prompt:** [What you're asking]
- **Best posting time:** [Suggestion based on audience]
```
### Step 6: Offer Variations
After presenting the post, offer:
1. **Hook alternatives** - Different opening approaches
2. **Tone adjustment** - More/less formal or casual
3. **Length variants** - Shorter version or expanded version
4. **Different frame** - Same content, different structure
## Example Usage
```bash
# With topic
/soft-skills:craft-linkedin-post I learned why you shouldn't deploy on Friday
# With story idea
/soft-skills:craft-linkedin-post We reduced our deploy time from 30 minutes to 3 minutes
# Start with questions
/soft-skills:craft-linkedin-post
```
## Output
Present a complete, ready-to-post LinkedIn update with:
1. **The post itself** - Formatted and ready to copy
2. **Hook assessment** - Strength of the opening
3. **Hashtag suggestions** - Relevant tags
4. **Posting tips** - Timing and engagement advice
5. **Alternative versions** - If applicable
## Quality Checklist
Before posting:
- [ ] Hook makes people want to click "see more"
- [ ] Contains specific details (not generic statements)
- [ ] Has emotional texture (not just facts)
- [ ] Clear takeaway for the reader
- [ ] Ends with engagement prompt
- [ ] Formatted with line breaks (no walls of text)
- [ ] 3-5 relevant hashtags
## Anti-Patterns to Avoid
- Generic statements without specifics
- Corporate jargon ("leveraging synergies")
- All wins, no vulnerability
- Missing call-to-action
- Walls of text (no line breaks)
- More than 5-7 hashtags
- Tagging people who didn't contribute
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.