refactor(linkedin)!: rename plugin linkedin-thought-leadership → linkedin-studio (v3.0.0)
BREAKING CHANGE: the marketplace slug, the agent namespace (linkedin-studio:<agent>), and the runtime state-file path (~/.claude/linkedin-studio.local.md) all change. Reinstall required; existing state migrated in place (post metrics, streak, history preserved). The /linkedin:* commands are unchanged — the command namespace is set per-command in frontmatter and was always independent of the plugin slug. Functionality is byte-identical to v2.4.0; this release is pure identity. - dir + manifests: plugins/linkedin-studio + plugin.json + root marketplace.json - agent namespace updated in commands/newsletter.md (only functional invoker) - state path updated in 4 hook scripts + topic-rotation prompt + state template - catch-all skill dir renamed skills/linkedin-studio (5 functional skills unchanged) - docs + version bump to 3.0.0 across README badge, CHANGELOG, root README/CLAUDE.md - historical records (CHANGELOG past entries, docs/ build artifacts, config-audit v5.0.0 snapshots) intentionally retain the old slug Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
9df3de795c
commit
b6bb61246b
196 changed files with 164 additions and 138 deletions
126
plugins/linkedin-studio/config/user-profile.template.md
Normal file
126
plugins/linkedin-studio/config/user-profile.template.md
Normal file
|
|
@ -0,0 +1,126 @@
|
|||
# User Profile Configuration
|
||||
|
||||
Copy this file to `user-profile.local.md` and customize for your needs.
|
||||
|
||||
```bash
|
||||
cp config/user-profile.template.md config/user-profile.local.md
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## PERSONALIZATION SETTINGS
|
||||
|
||||
### User Profile Context
|
||||
|
||||
**Name:** [Your Name]
|
||||
**Current Role:** [Your Role] (posting as private individual, not representing employer)
|
||||
**Organization:** [Not disclosed / Your Company]
|
||||
**Industry/Domain:** [Your Industry]
|
||||
|
||||
**Important Disclaimer:** All articles and posts are written as a private individual. Views expressed are personal and do not represent any employer.
|
||||
|
||||
**Core Expertise Areas (5 topics):**
|
||||
1. [Topic 1]
|
||||
2. [Topic 2]
|
||||
3. [Topic 3]
|
||||
4. [Topic 4]
|
||||
5. [Topic 5]
|
||||
|
||||
**Target Audience:**
|
||||
- **Primary:** [Who are you primarily writing for?]
|
||||
- **Secondary:** [Secondary audience]
|
||||
- **Geographic focus:** [Region/Country]
|
||||
|
||||
**LinkedIn Goals (ranked by priority):**
|
||||
1. [ ] Build thought leadership & authority
|
||||
2. [ ] Attract speaking opportunities
|
||||
3. [ ] Network with peers/influencers
|
||||
4. [ ] Generate qualified leads
|
||||
5. [ ] Monetization (consulting/courses)
|
||||
6. [ ] Recruit talent
|
||||
|
||||
---
|
||||
|
||||
### Voice & Style Profile
|
||||
|
||||
**Tone Preferences (select what applies):**
|
||||
- [ ] Professional & authoritative
|
||||
- [ ] Conversational & approachable
|
||||
- [ ] Storytelling-focused
|
||||
- [ ] Data-driven & analytical
|
||||
- [ ] Empathetic & supportive
|
||||
- [ ] Provocative & contrarian
|
||||
|
||||
**Content Style Mix:**
|
||||
- Story-based posts
|
||||
- Framework/how-to posts
|
||||
- Data/research posts
|
||||
- Opinion/commentary posts
|
||||
- Case study posts
|
||||
- Personal reflection posts
|
||||
|
||||
**Signature Elements:**
|
||||
- **Key frameworks you've developed:** [Your frameworks, or "None yet"]
|
||||
- **Recurring themes/angles:** [Your themes]
|
||||
- **Phrases you commonly use:** [Your phrases]
|
||||
- **Topics to AVOID:** [Topics you never discuss]
|
||||
|
||||
**Writing Quirks & Preferences:**
|
||||
- **Preferred post length:** [Short 150-500 / Medium 1,200-1,800 / Long 2,000+]
|
||||
- **Emoji usage:** [None / Minimal 1-2 / Moderate 3-5]
|
||||
- **Question style CTAs:** [Always / Sometimes / Never]
|
||||
- **Use of personal anecdotes:** [Always / Sometimes / Rarely]
|
||||
- **Technical depth:** [Beginner / Intermediate / Advanced / Adaptive]
|
||||
|
||||
---
|
||||
|
||||
### Voice Profile Summary
|
||||
|
||||
**[Your Name] writes with:**
|
||||
|
||||
1. **[Quality 1]:** [Description]
|
||||
2. **[Quality 2]:** [Description]
|
||||
3. **[Quality 3]:** [Description]
|
||||
4. **[Quality 4]:** [Description]
|
||||
5. **[Quality 5]:** [Description]
|
||||
|
||||
**DO:**
|
||||
- [What you always do in your writing]
|
||||
- [Another thing you do]
|
||||
|
||||
**DON'T:**
|
||||
- [What you never do]
|
||||
- [Another thing to avoid]
|
||||
|
||||
**Universal anti-patterns (keep these — they hold for every author):**
|
||||
- **Modell-/navne-katalog.** Do not reel off product names, model names, or
|
||||
benchmarks for completeness. Pick ONE concrete, verifiable (preferably local)
|
||||
case over a list — a name-dump is a jargon wall to a non-technical reader.
|
||||
- **Fullstendighet over leser-handling.** Serve what the primary reader can DO
|
||||
from their chair, not everything the author knows. Completeness is not a virtue.
|
||||
- **Selvrefererende overhead-åpning.** No meta-commentary about what the text will
|
||||
or will not do, no warm-ups. Start on the reader's problem.
|
||||
- **«ikke bare X, men Y», reflex rule-of-three, tacked-on summaries, hedging.**
|
||||
|
||||
**Language:** [English / Norwegian / Other]
|
||||
|
||||
---
|
||||
|
||||
### Strategic Context
|
||||
|
||||
**Current LinkedIn Status:**
|
||||
- **Follower count:** [Your current count]
|
||||
- **90-day growth goal:** [Your goal]
|
||||
- **Posting frequency:** [Daily / 3x week / 2x week]
|
||||
- **Optimal posting times:** [Your best times, or "To be determined"]
|
||||
|
||||
---
|
||||
|
||||
### Asset Utilization Preferences
|
||||
|
||||
**When creating content, Claude should:**
|
||||
- [ ] Check `/assets/examples/` for past post patterns
|
||||
- [ ] Reference frameworks from `/assets/frameworks/`
|
||||
- [ ] Pull case studies from `/assets/case-studies/`
|
||||
- [ ] Incorporate voice samples from `/assets/voice-samples/`
|
||||
- [ ] Use research/data from `/assets/research/`
|
||||
Loading…
Add table
Add a link
Reference in a new issue