ACA pipeline status report
This is a read-only operating brief across ACA. It should be short, specific, and useful.
Rules
- Do not mutate state.
- Omit empty sections unless the workspace is completely empty.
- Surface genuine blockers plainly: disconnected senders, stalled imports, failed generation jobs, active campaigns with no leads, or paused sequences that the user expected to run.
- If a tool call fails, report the partial result and name the failed call.
Workflow
Run independent reads:
list_campaigns with active and paused filterslist_linkedin_import_jobs for running and failed importslist_apify_leads_import_jobs for running and failed importslist_generation_jobs for queued, processing, review, and failed jobslist_autopilotslist_email_sequenceslist_email_mailboxeslist_lead_lists- Optional:
list_pool_entries for content pool health
For each active campaign, call get_campaign or list_campaign_leads only when needed to explain a problem or identify recent activity.
Output structure
ACA Status - {timestamp}
CAMPAIGNS
- {N} active, {N} paused.
- Needs attention: {campaign} - {reason}
LEADS
- Imports running: {N}
- Recent list/build status: {summary}
EMAIL
- Mailboxes connected: {N}
- Active sequences: {N}
CONTENT
- Jobs in progress: {N}
- Jobs needing review: {N}
- Failed jobs: {N}
AUTOMATION
- Autopilots active: {N}
Nothing else needs attention.
Edge cases
- Empty workspace: say "Nothing running" and route to
aca-kickoff.
- User asks for a date range: adjust the filters where tools support it, otherwise say which sections are current-state only.
- Agency user asks for all clients: call
list_accessible_organizations, loop with switch_organization, collect compact metrics, then switch back.
Skill chaining
This skill participates in the ACA chain. Preserve the selected ACA org, relevant IDs, user brief, approval state, and any generated artifacts when continuing into another ACA skill. If the user asked for execution and a downstream condition is met, continue into the next skill automatically; otherwise end with the handoff block.
Upstream
- Called after launches, during daily checks, or by
aca-weekly-rhythm.
Auto-continue conditions
- Workspace empty -> continue to
aca-kickoff.
- Main bottleneck unclear -> continue to
aca-auto-research.
- Deliverability or sender blocker -> continue to
aca-deliverability-incident-response or aca-sender-health.
- Replies need review -> continue to
aca-positive-reply-scoring.
Stop before chaining when
- Read-only unless the downstream skill asks for approval.
Downstream skills
aca-kickoff - start empty workspace.aca-auto-research - choose the next best action.aca-deliverability-incident-response - triage campaign/send problems.aca-positive-reply-scoring - review replies.aca-weekly-rhythm - turn status into an operating plan.
Handoff block
Chain state: {continue|needs_approval|blocked|complete}
Next skill: {aca-skill-name|none}
Reason: {why this handoff is or is not needed}
Carry forward: {org_id/name, product_id, icp_id, lead_list_id, campaign_id, sequence_id, job_id, approvals, constraints}
ACA tools used
list_accessible_organizations, switch_organizationlist_campaigns, get_campaign, list_campaign_leadslist_linkedin_import_jobs, list_apify_leads_import_jobslist_generation_jobs, get_generation_joblist_autopilotslist_email_sequences, list_email_mailboxeslist_lead_listslist_pool_entries
1---2name: aca-pipeline-status3description: Get a read-only status report on everything running in ACA right now: active campaigns, in-flight imports, content generation jobs, autopilots, email sequences, lead lists, and recent activity. Use when the user says "what's running", "status report", "morning brief", "what's happening in ACA", "give me a summary", or "anything need attention".4license: MIT5---67# ACA pipeline status report89This is a read-only operating brief across ACA. It should be short, specific, and useful.1011## Rules1213- Do not mutate state.14- Omit empty sections unless the workspace is completely empty.15- Surface genuine blockers plainly: disconnected senders, stalled imports, failed generation jobs, active campaigns with no leads, or paused sequences that the user expected to run.16- If a tool call fails, report the partial result and name the failed call.1718## Workflow1920Run independent reads:21221. `list_campaigns` with active and paused filters232. `list_linkedin_import_jobs` for running and failed imports243. `list_apify_leads_import_jobs` for running and failed imports254. `list_generation_jobs` for queued, processing, review, and failed jobs265. `list_autopilots`276. `list_email_sequences`287. `list_email_mailboxes`298. `list_lead_lists`309. Optional: `list_pool_entries` for content pool health3132For each active campaign, call `get_campaign` or `list_campaign_leads` only when needed to explain a problem or identify recent activity.3334## Output structure3536```text37ACA Status - {timestamp}3839CAMPAIGNS40- {N} active, {N} paused.41- Needs attention: {campaign} - {reason}4243LEADS44- Imports running: {N}45- Recent list/build status: {summary}4647EMAIL48- Mailboxes connected: {N}49- Active sequences: {N}5051CONTENT52- Jobs in progress: {N}53- Jobs needing review: {N}54- Failed jobs: {N}5556AUTOMATION57- Autopilots active: {N}5859Nothing else needs attention.60```6162## Edge cases6364- Empty workspace: say "Nothing running" and route to `aca-kickoff`.65- User asks for a date range: adjust the filters where tools support it, otherwise say which sections are current-state only.66- Agency user asks for all clients: call `list_accessible_organizations`, loop with `switch_organization`, collect compact metrics, then switch back.6768## Skill chaining6970This skill participates in the ACA chain. Preserve the selected ACA org, relevant IDs, user brief, approval state, and any generated artifacts when continuing into another ACA skill. If the user asked for execution and a downstream condition is met, continue into the next skill automatically; otherwise end with the handoff block.7172**Upstream**73- Called after launches, during daily checks, or by `aca-weekly-rhythm`.7475**Auto-continue conditions**76- Workspace empty -> continue to `aca-kickoff`.77- Main bottleneck unclear -> continue to `aca-auto-research`.78- Deliverability or sender blocker -> continue to `aca-deliverability-incident-response` or `aca-sender-health`.79- Replies need review -> continue to `aca-positive-reply-scoring`.8081**Stop before chaining when**82- Read-only unless the downstream skill asks for approval.8384**Downstream skills**85- `aca-kickoff` - start empty workspace.86- `aca-auto-research` - choose the next best action.87- `aca-deliverability-incident-response` - triage campaign/send problems.88- `aca-positive-reply-scoring` - review replies.89- `aca-weekly-rhythm` - turn status into an operating plan.9091**Handoff block**9293```text94Chain state: {continue|needs_approval|blocked|complete}95Next skill: {aca-skill-name|none}96Reason: {why this handoff is or is not needed}97Carry forward: {org_id/name, product_id, icp_id, lead_list_id, campaign_id, sequence_id, job_id, approvals, constraints}98```99100## ACA tools used101102- `list_accessible_organizations`, `switch_organization`103- `list_campaigns`, `get_campaign`, `list_campaign_leads`104- `list_linkedin_import_jobs`, `list_apify_leads_import_jobs`105- `list_generation_jobs`, `get_generation_job`106- `list_autopilots`107- `list_email_sequences`, `list_email_mailboxes`108- `list_lead_lists`109- `list_pool_entries`
seguelaCedric