c747ab6ee6
- Session-start hook: welcome message with getting-started steps on first run - Session-start hook: prominent personalization score section when score is 0 - Router: condensed 4-option menu for users who haven't posted yet - Post/quick commands: non-blocking readiness check for unpersonalized state - Post-creation hook: inline 5x5x5 engagement ritual explanation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.8 KiB
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 the user about the 5x5x5 engagement ritual:
5x5x5 Engagement Ritual (15-20 min before AND in the first hour after posting):
- 5 comments — find 5 people with overlapping audiences and leave thoughtful comments on their recent posts
- 5 connection requests — send personalized requests to people who engaged with your niche today
- 5 replies — reply to every comment on YOUR post within the first hour
This signals active participation to LinkedIn's algorithm and boosts your post's initial distribution.
4. Content Logging Note: The post topic and hook should be logged to the state file when the session ends (handled by Stop hook).
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.