# Create LinkedIn content Human Guide

## What This Is For
Draft LinkedIn post variants that sound like a real human practitioner, not a LinkedIn thought-leader persona. It gives the agent a clearer input/output frame for social content: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Create LinkedIn content agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for create LinkedIn content.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Create LinkedIn content guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- `~/.goose-skills/config.json` → `voice_guides.linkedin`
- `~/.goose-skills/voice-guides/voice-linkedin.md` (default path)
- **Fallback prompt** — no guide found. Three options:
- (a) Paste a path to an existing guide
- (b) Run `/generate-voice-guide --platforms linkedin` now to create one (recommended)
- (c) Proceed with a neutral default (warn that variants will sound generic)
- **Length:** 150–500 words per variant (LinkedIn rewards longer than X but shorter than a blog post)
- **Bullets:** arrow style (`→`) for workflow steps — this is LinkedIn-native
- **Numbered steps:** emoji numbers `1️⃣ 2️⃣ 3️⃣` allowed sparingly for installation/quickstart type posts
- **"Why this matters" beat:** every post should have one — LinkedIn audiences want the *so what?* more explicitly than X audiences
- **Hashtags:** 0–2 max. Prefer zero.
- **CTAs:** "Link in comments" pattern is LinkedIn-native; inline links are fine too. Avoid "Follow me for more."

## Decision Points And Nuance
The original skill emphasizes: Quick Start, Inputs, Voice Guide Resolution, LinkedIn-Specific Defaults ★, Workflow, Phase 1 — Load the voice guide, Phase 2 — Parse the brief and decide variant count, Phase 3 — Generate variants with LinkedIn-appropriate framings, Phase 4 — Self-check against the voice guide, Phase 5 — Save outputs.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- | Flag | Required | Default |
- **CTAs:** "Link in comments" pattern is LinkedIn-native; inline links are fine too. Avoid "Follow me for more."
- **Openings:** more scene-setting is ok (1–2 lines of context before the hook). Unlike X, you don't have to hook-first.
- Same as `create-x-content` Phase 1 — load voice guide, extract banned phrases, hook patterns, format rules, dos/don'ts, examples.
- **Never open with "I'm humbled" or "Grateful for..."** — LinkedIn performative cringe. The voice guide should flag these; honor it.

## Copy-And-Paste Prompt
```text
Use the Create LinkedIn content human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the gooseworks-ai/goose-skills skill entry for `create-linkedin-content`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Create LinkedIn Content

Draft LinkedIn post variants that sound like a real human practitioner, not a LinkedIn thought-leader persona. Reads a voice guide the user has already generated (or prompts to create one), produces multiple framings of the same idea, and saves each variant as its own markdown file with frontmatter.

**This is an agent-executed skill** — the agent does the drafting and self-check inline. No Python script.

Mirrors `create-x-content` structurally; differences are marked ★.

## Quick Start

```
/create-linkedin-content --brief "New open-source CLI that turns Figma files into React components. Called figma2react. Free, MIT licensed."
```

Or interactively:
```
/create-linkedin-content
```

## Inputs

| Flag | Required | Default |
|------|----------|---------|
| `--brief` | Yes (asked interactively if missing) | — |
| `--variants` | No | Skill decides based on brief richness (2–5) |
| `--voice-guide` | No | Resolved via chain below |
| `--output` | No | `./content/YYYY-MM-DD-<topic-slug>/` |
| `--topic` | No | Derived from brief |

## Voice Guide Resolution

Resolve in this order, stop at first hit:

1. `--voice-guide <path>` flag
2. `~/.goose-skills/config.json` → `voice_guides.linkedin`
3. `~/.goose-skills/voice-guides/voice-linkedin.md` (default path)
4. **Fallback prompt** — no guide found. Three options:
   - (a) Paste a path to an existing guide
   - (b) Run `/generate-voice-guide --platforms linkedin` now to create one (recommended)
   - (c) Proceed with a neutral default (warn that variants will sound generic)

## LinkedIn-Specific Defaults ★

Apply these unless the voice guide explicitly says otherwise:

- **Length:** 150–500 words per variant (LinkedIn rewards longer than X but shorter than a blog post)
- **Bullets:** arrow style (`→`) for workflow steps — this is LinkedIn-native
- **Numbered steps:** emoji numbers `1️⃣ 2️⃣ 3️⃣` allowed sparingly for installation/quickstart type posts
- **"Why this matters" beat:** every post should have one — LinkedIn audiences want the *so what?* more explicitly than X audiences
- **Hashtags:** 0–2 max. Prefer zero.
- **CTAs:** "Link in comments" pattern is LinkedIn-native; inline links are fine too. Avoid "Follow me for more."
- **Openings:** more scene-setting is ok (1–2 lines of context before the hook). Unlike X, you don't have to hook-first.

## Workflow

### Phase 1 — Load the voice guide

Same as `create-x-content` Phase 1 — load voice guide, extract banned phrases, hook patterns, format rules, dos/don'ts, examples.

### Phase 2 — Parse the brief and decide variant count

Same 2–5 decision rubric. LinkedIn briefs often warrant fewer variants than X because LinkedIn posts are longer and the audience expects more narrative coherence — 3 strong framings usually beats 5.

### Phase 3 — Generate variants with LinkedIn-appropriate framings

Framings tuned for LinkedIn (subset of the X framings, plus a few LinkedIn-native ones):

| Framing | Structure | When to use |
|---------|-----------|-------------|
| `builder-story` ★ | "I built X. Here's why. Here's what I learned." | LinkedIn-native — builder stories outperform tactical posts here |
| `product-launch` ★ | Clear hook + 2-step quickstart + link | New tool/product announcements |
| `problem-first` | Open with the pain, then solution | Universal |
| `ecosystem-map` | Curated list of N related tools/companies | Landscape posts |
| `contrarian-insight` | "Your X might be worth more than Y" | Opinion pieces with a fresh take |
| `workflow-tutorial` | Arrow-bulleted step-by-step, with numbers | Tactical how-tos (denser than X version) |

### Phase 4 — Self-check against the voice guide

Same 4 checks as `create-x-content`:
1. Banned phrase check