Update to ACA

{
  "description": "Generate a week of on-brand content in ACA. Use when the user says \"generate this week's content\", \"I need [N] LinkedIn posts about [topic]\", \"write a content batch\", \"fill the content queue\", \"make ad creatives for [product]\", or asks for multi-piece content tied to a brand voice. Plans ideas, matches them to an ACA blueprint, and starts generation through the ACA connector.",
  "included_files": [],
  "name": "aca-content-week",
  "skill_md_contents": "---\nname: aca-content-week\ndescription: Generate a week of on-brand content in ACA. Use when the user says \"generate this week's content\", \"I need [N] LinkedIn posts about [topic]\", \"write a content batch\", \"fill the content queue\", \"make ad creatives for [product]\", or asks for multi-piece content tied to a brand voice. Plans ideas, matches them to an ACA blueprint, and starts generation through the ACA connector.\nlicense: MIT\ncompatibility: Requires the ACA connector (OAuth sign-in, no API key).\nmetadata:\n  author: ACA\n  version: \"1.1\"\n  homepage: https://www.automatedclientacquisition.com/mcp\n---\n\n# Generate a week of content in ACA\n\nACA's content engine produces on-brand assets through blueprints. This skill plans an idea batch, saves it, starts generation on a matching active blueprint, and tracks the jobs. Scheduling and publishing happen in the ACA app.\n\n## Rules\n\n- Use the ACA connector only. Never ask for vendor API keys or run SQL/API calls.\n- Ask before any write. Show the idea batch before `create_content_ideas`.\n- Match the requested format to a real blueprint and its pipeline. Never silently use the wrong one.\n- `start_content_generation` only runs on an active blueprint, sends prompts to AI providers, and consumes billable credits that cannot be undone. Confirm the blueprint, pipeline, item count, and that it costs credits before every call.\n- A blueprint created here with `create_blueprint` is an inactive draft. The user reviews and activates it at `/blueprints/{id}` before it can generate.\n- Generated content stays unapproved and unpublished. Approval, autopilots, scheduling, and publishing happen at `/autopilots` and `/publish-queue`.\n- For long-running video jobs, set expectations and check `list_content_generation_jobs` no faster than every 30 seconds.\n- If a tool result includes `plan_note` or `plan.limitation`, relay it as a plain fact. Never promote plans, pricing, or upgrades.\n\n## Workflow\n\n### 1. Clarify the brief\n\nCapture:\n\n- Format: LinkedIn posts, tweets, carousels, videos, ads, articles\n- Topic or theme\n- Count (default 5 for a week)\n- Offer and buyer context\n- Brand voice to match\n\nCall `get_started` to see whether the workspace has products and ICPs. Brand voice and product details are not readable through the connector; if the user has not described them, ask for a short summary or route to `aca-icp-onboarding`.\n\n### 2. Pick the blueprint\n\nCall `list_blueprints` (use `active_only: true` when you only want ones that can generate now), then `get_blueprint` on the likely match to confirm its pipeline and purpose.\n\nConnector pipelines: `social_media_post`, `rich_article`, `instagram_carousel`, `image_only`, `ugc_video`, `generative_video_oneshot`, `video_script`, `storyboard_video_longform`.\n\n- Active blueprint matches: use it.\n- Only an inactive match exists: tell the user to activate it at `/blueprints/{id}`.\n- No match: draft a blueprint in chat (name, description, pipeline, master prompt). After approval, call `create_blueprint`; it lands as an inactive draft for the user to review and activate.\n\n### 3. Build the idea batch\n\nCall `list_content_ideas` to avoid duplicating existing ideas. Draft slightly more ideas than needed. Each idea has:\n\n- Short title\n- Keywords\n- Content framework (for example: contrarian take, story, how-to, teardown, listicle)\n- Emotional triggers or angle\n\nShow the batch and ask which to keep. After approval, call `create_content_ideas` (up to 25 per call).\n\n### 4. Start generation\n\nConfirm cost first: \"This starts {N} items on {blueprint} ({pipeline}) and uses billable credits. Go?\"\n\nAfter a clear yes, call `start_content_generation` with `blueprint_id`, `pipeline`, and `items` (up to 10 per call; each item carries an `idea_id` or `idea_title`).\n\nTrack progress with `list_content_generation_jobs`. Report statuses as returned.\n\n### 5. Review and schedule in the app\n\nGenerated pieces are unapproved and unpublished. Send the user to review them, then schedule or publish at `/publish-queue`, or set up a recurring autopilot at `/autopilots`.\n\nSuggested posting slots if the user asks:\n\n- LinkedIn: Tue to Thu, 8am or 12pm user-local\n- X/Twitter: Mon to Fri, 9am or 3pm user-local\n- Instagram: Wed to Sun, 11am or 7pm user-local\n\n## Output format\n\n```text\nContent batch: {theme}\nFormat: {format} ({pipeline})\nBlueprint: {blueprint} ({active|draft, activate at /blueprints/{id}})\nIdeas saved: {N}\n\nJobs:\n- {job_id}: {idea_title} - {status}\n\nNext: {track | review and schedule at /publish-queue | activate blueprint}\n```\n\n## Skill chaining\n\nPreserve the workspace, relevant IDs, the user's brief, and approval state when continuing into another ACA skill. If the user asked for execution and a downstream condition is met, continue into the next skill; otherwise end with the handoff block.\n\n**Upstream**\n- Called by `aca-kickoff`, `aca-weekly-rhythm`, `aca-auto-research`, `aca-lead-magnet-brainstorm`, or campaign plans that need supporting content.\n\n**Auto-continue conditions**\n- No offer, ICP, or brand context: continue to `aca-icp-onboarding`.\n- Jobs started: continue to `aca-pipeline-status` for tracking.\n- Content supports an outbound offer: continue to `aca-campaign-strategy`.\n\n**Stop before chaining when**\n- Saving ideas or creating a blueprint the user has not approved.\n- Starting billable generation without a confirmed yes.\n- The next step is approval, scheduling, or publishing (app only).\n\n**Downstream skills**\n- `aca-icp-onboarding`: create missing context.\n- `aca-pipeline-status`: track generation jobs.\n- `aca-campaign-strategy`: use content as campaign support.\n- `aca-weekly-rhythm`: add content into the operating cadence.\n\n**Handoff block**\n\n```text\nChain state: {continue|needs_approval|blocked|complete}\nNext skill: {aca-skill-name|none}\nReason: {why this handoff is or is not needed}\nCarry forward: {workspace, blueprint_id, pipeline, idea_ids, job_id, approvals, constraints}\n```\n\n## ACA tools used\n\n- `get_started`\n- `list_blueprints`, `get_blueprint`, `create_blueprint`\n- `list_content_ideas`, `create_content_ideas`\n- `start_content_generation`, `list_content_generation_jobs`\n\n## ACA app pages\n\n- Edit or activate a blueprint: `https://www.automatedclientacquisition.com/blueprints/{id}`\n- Review, schedule, publish: `https://www.automatedclientacquisition.com/publish-queue`\n- Autopilots: `https://www.automatedclientacquisition.com/autopilots`\n- Brand voice and products: `https://www.automatedclientacquisition.com/assets?tab=brands`, `?tab=products`\n"
}