{"id":91526,"plugin_id":"plugin_asdk_app_6ad30793384c81919c4ff090fbeae35d","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-11T18:09:22.109Z","digest":"b70b37a17f3510bcf29e48c67340320bfb3f6e149fcd44ef227676b9f727cafe","against":null,"payload":{"description":"Route AdNeuron advertising requests to Meta or Google campaign agents, read-only reporting, optimization, or approved management workflows.","included_files":[],"name":"adneuron-campaign-router","skill_md_contents":"---\nname: adneuron-campaign-router\ndescription: Route AdNeuron advertising requests to Meta or Google campaign agents, read-only reporting, optimization, or approved management workflows.\n---\n# AdNeuron campaign router\n## Architecture\nSkills own conversation orchestration and agent step selection. MCP owns authenticated provider calls, validation evidence, and durable state when workflow endpoints are available. UI renders step progress, summaries, selections, warnings, and actual actionable approvals. Never claim a UI button has executed a provider action without a tool response.\n\n## Routing\n1. Determine intent: inspect/report, create, edit, pause/resume, remove, creative/assets, conversion tracking, optimize, or recover.\n2. Determine platform and exact workspace/account. Do not infer an account from the previous user if multiple accounts are eligible. Use read-only discovery before writes.\n3. Meta create/edit: follow `adneuron-meta-campaign-agent`. Google create/edit: follow `adneuron-google-campaign-agent`. For cross-platform analysis use `adneuron-reporting-optimization`.\n4. For every mutating flow apply `adneuron-workflow-state` safeguards. Account connection and synchronization are themselves potentially consequential; do not run as part of a read-only check.\n5. Use exact tool names in `references/tool-stage-map.json`, but rely on live tool schemas and server responses as authority. Missing tools are limitations, not reasons to invent API calls.\n\n## Shared eight-step agent\n1. Account: workspace, platform, account ID, currency, timezone, connection status.\n2. Access: permissions, assets, policy eligibility, destination readiness.\n3. Goal: objective, conversion or traffic outcome, campaign type.\n4. Settings: budget, bidding, schedule, location, demographics, placements.\n5. Assets: creative, Page/Instagram identity, Google ad groups, keywords, ads, conversion actions.\n6. Review: complete, readable plan with defaults, warnings, evidence and exact planned API action.\n7. Approval: explicit plan- and action-specific confirmation; creation defaults to paused where supported. Activation requires separate confirmation.\n8. Verification: provider IDs, actual state, partial failures, next actions; reconcile uncertain writes before retry.\n\nAt each step show `Step N of 8`, completed/missing fields, what happens next, and a concise choice/action. Never mark a step complete based on assumption. Do not ask again for fields already known and verified.\n\n## Product scope\nMeta image/video/carousel and Google Search are supported only when corresponding MCP tools are exposed and validated. Google Display/Demand Gen require distinct plans and explicit user selection. Do not silently broaden placements or enable unapproved spend. Respect tool and provider permissions.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}