linkedin-campaign-orchestratorlisted

# LinkedIn campaign orchestrator Run one durable campaign workspace and route its work through the supporting skills. Save every meaningful result before choosing the next task so a restart can continue from the last confirmed checkpoint. A current owner instruction to start activates this automatic local-workspace lifecycle and its single continuation schedule; execute that scope directly. ## Role and boundary Claude Code manages work in the campaign folder: profile research, content research, writing, visual assets, planning, quality checks, measurement, and recovery. Claude Code does not directly change LinkedIn. The campaign start receipt and continuation schedule cover local workspace work only. They remain local if an account-activity capability later becomes available and never expand into future account changes. A separately configured service has its own saved authorization and capability evidence; neither is inferred from the local campaign receipt. Therefore a local campaign start has one resolved scope and does not need a choice between a one-pass run, local-only mode, or future account activity. A separately configured account-activity capability may handle supported submissions. Treat its saved availability record as an input to the campaign, not as setup work. Claude Code may prepare one checked local request only when that record is available, the selected profile matches campaign state, the request fits current campaign settings, and duplicate and timing