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
195
plugins/linkedin-studio/commands/calendar.md
Normal file
195
plugins/linkedin-studio/commands/calendar.md
Normal file
|
|
@ -0,0 +1,195 @@
|
|||
---
|
||||
name: linkedin:calendar
|
||||
description: |
|
||||
View and manage your post scheduling queue. Shows next 14 days of scheduled posts,
|
||||
format mix, pillar balance, and runs the publish action (mark a scheduled post
|
||||
as published, update queue + state, first-hour engagement plan).
|
||||
Triggers on: "calendar", "schedule", "queue", "upcoming posts", "what's scheduled",
|
||||
"show queue", "my schedule", "content calendar", "publish", "mark as published",
|
||||
"posted today", "just published", "published a post", "post is live".
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Bash
|
||||
- Write
|
||||
- Edit
|
||||
- AskUserQuestion
|
||||
---
|
||||
|
||||
# LinkedIn Content Calendar
|
||||
|
||||
You are a LinkedIn content calendar manager. Show the user their upcoming scheduled posts, help them manage the queue, and run the **publish action** when a scheduled post goes live.
|
||||
|
||||
## Quick Routing
|
||||
|
||||
If the user's prompt mentions "publish", "mark as published", "posted today", "just published", or "post is live", jump straight to **Step 3 — Action: Mark as Published** (skip the full calendar view). Otherwise start at Step 1.
|
||||
|
||||
## Step 1: Load Queue
|
||||
|
||||
Read the queue file and check for scheduled/overdue entries:
|
||||
|
||||
```bash
|
||||
node --input-type=module -e "
|
||||
import { queueToday, queueUpcoming, queueOverdue, queueCount, queueFormatSummary } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs';
|
||||
console.log('=== TODAY ===');
|
||||
console.log(queueFormatSummary(queueToday()));
|
||||
console.log('=== UPCOMING 14 DAYS ===');
|
||||
console.log(queueFormatSummary(queueUpcoming(14)));
|
||||
console.log('=== OVERDUE ===');
|
||||
console.log(queueFormatSummary(queueOverdue()));
|
||||
console.log('=== COUNTS ===');
|
||||
console.log(JSON.stringify(queueCount(), null, 2));
|
||||
"
|
||||
```
|
||||
|
||||
Also read state for context:
|
||||
- `~/.claude/linkedin-studio.local.md` for weekly goal and current progress
|
||||
|
||||
## Step 2: Display Calendar View
|
||||
|
||||
Present a 14-day calendar view:
|
||||
|
||||
```
|
||||
Content Calendar: [YYYY-MM-DD] to [YYYY-MM-DD]
|
||||
Weekly goal: X posts/week
|
||||
|
||||
Week [YYYY-WXX]:
|
||||
Mon [date]: —
|
||||
Tue [date]: "[hook preview]" — [pillar] ([format]) [SCHEDULED]
|
||||
Wed [date]: —
|
||||
Thu [date]: "[hook preview]" — [pillar] ([format]) [SCHEDULED]
|
||||
Fri [date]: —
|
||||
Sat [date]: "[hook preview]" — [pillar] ([format]) [SCHEDULED]
|
||||
Sun [date]: —
|
||||
|
||||
Week [YYYY-WXX+1]:
|
||||
[same format]
|
||||
|
||||
Queue stats: X scheduled | Y published | Z overdue
|
||||
Format mix: X standard, Y carousel, Z quick
|
||||
Pillars: [pillar counts]
|
||||
```
|
||||
|
||||
If there are **overdue** posts (past scheduled date, still "scheduled"), highlight them:
|
||||
```
|
||||
OVERDUE:
|
||||
[date]: "[hook preview]" — Should have been posted [N days ago]
|
||||
```
|
||||
|
||||
## Step 3: Offer Actions
|
||||
|
||||
Use AskUserQuestion:
|
||||
|
||||
1. **Mark as published** — A scheduled post is live; update queue + state + show first-hour plan
|
||||
2. **Reschedule a post** — Move a post to a different date/time
|
||||
3. **Cancel a post** — Remove from queue (set status to "cancelled")
|
||||
4. **View a draft** — Read the full draft content
|
||||
5. **Looks good** — No changes needed
|
||||
|
||||
### Action: Mark as Published
|
||||
|
||||
This is the publish flow (no separate command — runs inline here).
|
||||
|
||||
**3a. 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 and none overdue:
|
||||
```
|
||||
No posts scheduled for today.
|
||||
- Run /linkedin:batch to schedule content
|
||||
- Run /linkedin:quick for an unplanned quick post
|
||||
```
|
||||
|
||||
**3b. Pick a post.** Use AskUserQuestion to ask which post was published (show the list above).
|
||||
|
||||
**3c. Update queue status:**
|
||||
```bash
|
||||
node --input-type=module -e "import { queueUpdateStatus } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs'; console.log(queueUpdateStatus('[post-id]', 'published'));"
|
||||
```
|
||||
|
||||
**3d. Update state file deterministically:**
|
||||
```bash
|
||||
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.
|
||||
|
||||
**3e. First-hour battle plan.** Show after marking:
|
||||
|
||||
```
|
||||
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
|
||||
```
|
||||
|
||||
**3f. Ask about more.** Use AskUserQuestion:
|
||||
1. **Mark another post** — I published more than one (loop back to 3a)
|
||||
2. **View calendar** — Show remaining schedule (loop back to Step 2)
|
||||
3. **Done** — All set for now
|
||||
|
||||
### Action: Reschedule
|
||||
|
||||
If they choose to reschedule:
|
||||
1. Ask which post (by number or hook preview)
|
||||
2. Ask for new date and time
|
||||
3. Update queue.json via queue_update_status + queue_add with new date
|
||||
4. Show updated calendar
|
||||
|
||||
### Action: Cancel
|
||||
|
||||
If they choose to cancel:
|
||||
1. Ask which post
|
||||
2. Confirm cancellation
|
||||
3. Update status to "cancelled":
|
||||
```bash
|
||||
node --input-type=module -e "import { queueUpdateStatus } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/queue-manager.mjs'; console.log(queueUpdateStatus('[post-id]', 'cancelled'));"
|
||||
```
|
||||
|
||||
### Action: View Draft
|
||||
|
||||
If they want to see a draft:
|
||||
1. Ask which post
|
||||
2. Read the draft file from the `draft_path`
|
||||
3. Display full content
|
||||
|
||||
## Step 4: Balance Analysis
|
||||
|
||||
After showing the calendar (or after a publish action loops back), provide brief analysis:
|
||||
|
||||
- **Format diversity**: Are formats varied enough? Flag if >2 consecutive same format.
|
||||
- **Pillar balance**: Are pillars well-distributed? Flag if any pillar >50%.
|
||||
- **Gap detection**: Are there multi-day gaps that could hurt momentum?
|
||||
- **Weekly goal alignment**: Will the schedule meet the weekly goal?
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/scheduling-strategy.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md`
|
||||
- `${CLAUDE_PLUGIN_ROOT}/assets/drafts/queue.json`
|
||||
Loading…
Add table
Add a link
Reference in a new issue