Kjell Tore Guttormsen
b6bb61246b
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>
32 lines
1.4 KiB
Markdown
32 lines
1.4 KiB
Markdown
LINKEDIN POST-CREATION AUTOMATION: If a LinkedIn content file was just written (post draft, article, or content — NOT config, state, scripts, or docs), perform these post-processing steps:
|
|
|
|
**1. Generate Alternative Hooks**
|
|
Create 3 alternative hooks for the content just written. Present them as:
|
|
```
|
|
Alternative hooks:
|
|
1. [hook 1] (X chars)
|
|
2. [hook 2] (X chars)
|
|
3. [hook 3] (X chars)
|
|
```
|
|
|
|
**2. Suggest Optimal Posting Time**
|
|
Based on the day of the week, suggest the next optimal posting window:
|
|
- Tuesday-Thursday: 8-9 AM or 12-1 PM CET (best)
|
|
- Monday/Friday: 9-10 AM CET (good)
|
|
- Weekend: 10-11 AM CET (lower reach but less competition)
|
|
|
|
**3. 5x5x5 Engagement Reminder**
|
|
Remind: 'Before posting, spend 15-20 minutes on 5x5x5 pre-engagement: find 5 people with overlapping audiences, comment thoughtfully on their recent posts.'
|
|
|
|
**4. Content Logging**
|
|
Note: State tracking is handled deterministically by `state-updater.mjs` via the Stop hook. Do not manually edit the state file YAML frontmatter.
|
|
|
|
**5. Voice Sample Suggestion**
|
|
|
|
After generating alternative hooks and posting time, add a brief note:
|
|
|
|
"Tip: Your post hook could become a voice sample. When the session ends, the Stop hook will ask if you'd like to save it to your voice profile."
|
|
|
|
This creates awareness of the voice extraction feature without interrupting the post-creation flow.
|
|
|
|
**Skip this** if the file written is a config file, state file (.local.md), script, hook, JSON, plan file, or documentation.
|