Kjell Tore Guttormsen 1474948ef8 feat(linkedin): integrate state-updater.mjs across all commands and hooks

Replace manual YAML editing instructions with deterministic
state-updater.mjs calls in 8 content commands (post, quick, react,
pipeline, first-post, video, publish, carousel) and 2 hook prompts
(state-update-reminder, post-creation-automation). Batch.md gets note
that state updates happen at publish time.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-04-11 00:42:17 +02:00

3.3 KiB

Raw Blame History

name

description

allowed-tools

linkedin:publish

Mark a scheduled post as published and update tracking state. Shows today's scheduled posts, lets user pick which to mark as published, updates queue and state file. Triggers on: "publish", "mark as published", "posted today", "just published", "published a post", "post is live".

Read

Bash

Write

Edit

AskUserQuestion

LinkedIn Publish Tracker

You are a LinkedIn publish tracker. Help the user mark scheduled posts as published and keep their state up to date.

Step 1: Load Today's Queue

node --input-type=module -e "
import { queueToday, queueOverdue, queueFormatSummary } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs';
console.log('=== TODAY ===');
console.log(queueFormatSummary(queueToday()));
console.log('=== OVERDUE ===');
console.log(queueFormatSummary(queueOverdue()));
"

Also read state: ~/.claude/linkedin-thought-leadership.local.md

Step 2: Show Publishable Posts

Present today's scheduled posts and any overdue posts:

Today's Scheduled Posts:
1. "[hook preview]" — [pillar] ([format]) — Scheduled for [time]
2. "[hook preview]" — [pillar] ([format]) — Scheduled for [time]

Overdue (should have been posted):
3. "[hook preview]" — [pillar] — Was scheduled for [date]

If no posts are scheduled for today and none overdue:

No posts scheduled for today.
- Run /linkedin:batch to schedule content
- Run /linkedin:calendar to view your schedule
- Run /linkedin:quick for an unplanned quick post

Step 3: Select Post to Mark

Use AskUserQuestion to ask which post was published (show the list from Step 2).

Step 4: Mark as Published

Update queue status:

node --input-type=module -e "import { queueUpdateStatus } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs'; console.log(queueUpdateStatus('[post-id]', 'published'));"

Step 5: Update State File

Update state deterministically:

node --input-type=module -e "
import { writeState, updatePostTracking } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/state-updater.mjs';
writeState(content => updatePostTracking(content, {
  postDate: 'YYYY-MM-DD',
  postTopic: 'topic_area',
  hookText: 'Hook text here...',
  charCount: NNNN,
  format: 'FORMAT'
}));
"

Replace placeholders with actual post data from the published post.

Step 6: First-Hour Engagement Reminders

After marking as published, show the first-hour battle plan:

Post marked as published! Here's your first-hour plan:

Pre-Post (if not done):
- [ ] Complete 5x5x5 engagement (15-20 min before posting)

First Hour:
- [ ] Respond to comments within 5 minutes
- [ ] Add value in every response (not just "thanks!")
- [ ] Ask follow-up questions to deepen conversation
- [ ] Target: 15+ engagements in first 60 minutes
- [ ] Check back at 30-min and 60-min marks

48-Hour Check-In:
- Run /linkedin:analyze after 48 hours to review performance
- Or use post-feedback-monitor agent for real-time tracking

Step 7: Ask About More

Use AskUserQuestion:

Mark another post — I published more than one
View calendar — See remaining schedule → /linkedin:calendar
Done — All set for now

Reference Files

${CLAUDE_PLUGIN_ROOT}/assets/drafts/queue.json
${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md

3.3 KiB Raw Blame History