Connect content to a useful next step
Read the author's context and the runtime contract. Use linkedin-copywriter for the actual grounded draft; this skill handles native delivery and engagement workflows.
For the bundled content-to-pipeline setup, read the LinkedIn kit. It links the author's scaffold, Notion board, native watcher, qualification template, DM framework and downloadable funnel.
| Work | Native surface |
|---|---|
| Draft artifact and owned post data | Posts |
| Review, schedule and broadcast delivery | Publishing |
| Durable viewers, followers, connections and engagement | Signals |
| Working qualification/enrichment rows | Tables |
| New DM and warm follow-up cadence | Sequences |
| Existing-thread reply | Messages / Unibox |
For daily engagers of named public LinkedIn profiles, prefer the native one-table Profile Watcher. Get real profile URLs, preview the current configuration and per-cycle credit cap, and preserve the returned hash. Creating or resuming it starts paid recurring collection; it is not the disabled three-table blueprint. Keep a stable create request ID across ambiguous retries.
Add qualification only after inspecting the actual table columns and the user's company/persona rubric. The bundled prompt reads existing evidence and has a separate paid AI run. Calibrate a bounded sample before auto-run. Hold missing required enrichment, keep company and person fit independent, and retain the exact engager's source-post attribution. Watcher collection, qualification, resource delivery and Sequence enrollment are separate operations; do not imply one automatically performs the next.
Discover the chosen motion with oxygen capabilities search "LinkedIn content and warm engagement" --json, then hydrate only its commands. Public/third-party research uses the current native public-research catalog where available; connected-account actions have their own limits and scope. Do not silently substitute another provider.
For a lead-magnet post, verify the resource URL and promise. Inspect the exact author/account, copy, media and schedule before requested publication. Record the Post and Publishing IDs and read back delivery state.
For comment-to-resource or network capture, inspect the capture window, dedupe keys, pagination and freshness. Separate capture from auto-enrollment. A standing outreach grant must specify the eligible cohort, destination Sequence, limits and stop conditions. Engagement alone does not establish fit or permission for broader outreach.
Owned-post public comments belong to the Publishing community queue. Check its freshness before trusting an empty queue. Use the native reply preview and content-bound approval action; do not manufacture approval or retry an unknown external effect.
For analytics, inspect current owned-post summary/detail commands. Read coverage and freshness alongside totals; null means unavailable. Preserve source/post/event IDs through qualification and Sequence results. Monitoring belongs to hosted subscriptions or Workflows.
Return the draft/published state, resource URL, captured/qualified/held counts where available, and native object links. Avoid equating post reach with attributable pipeline.
