Ads Human Handoff

Escalate automation conversations to human ad experts for Meta (Facebook/Instagram), Google Ads, TikTok Ads, and YouTube Ads operations.

Security Scan

The skill is an instruction-only ‘human handoff’ helper for ad platforms and its requirements and instructions are internally consistent, but the package has no provenance (no homepage or source) so you should vet what account data you pass into it before use.

Purpose & Capability

The name, description, and runtime instructions all focus on creating handoff packets and escalation routing for ad platforms; that matches. Minor inconsistency: the Platform Notes emphasize Meta/Google/TikTok/YouTube as primary scope while the 'high-signal keywords' and examples also list Amazon/Shopify/DSP — this is a small scope-document mismatch but not a functional red flag.

Instruction Scope

SKILL.md is purely procedural guidance (classify, short answer, checklist, structured handoff payload) and does not instruct the agent to read local files, environment variables, run shell commands, or transmit data to any hidden endpoints. It stays within the stated purpose of preparing handoff packets and escalation criteria.

Install Mechanism

No install spec and no code files are included (instruction-only). Nothing will be written to disk or fetched during install based on the provided metadata.

Credentials

The skill declares no required environment variables, credentials, or config paths. The handoff payload expects account and campaign identifiers (reasonable for its purpose) — those may contain sensitive/account-level info, so users should avoid passing secrets or full credentials into the skill.

Persistence & Privilege

always is false and there is no indication the skill modifies agent/system configs or requests permanent presence. Model invocation defaults are unchanged; autonomous invocation is allowed by the platform default but the skill does not request elevated persistence.

Assessment

This skill is instruction-only and appears to do what it says (create structured handoff packets for ad platforms). However: 1) the package has no homepage or repository — verify the publisher or test in a controlled environment before relying on it; 2) do not send full credentials or highly sensitive PII (billing info, full account passwords) into handoff payloads — only include the minimum identifiers needed (account_id, campaign_id, timeline, last_change); 3) confirm the human recipients/processes you will escalate to (who will receive tickets and how); 4) test with non-sensitive dummy data to ensure output format and escalation criteria meet your security and compliance needs; 5) monitor skill use/logging and consider restricting autonomous invocation if you want manual control over escalations.

Purpose

Core mission:

• handoff packet creation, escalation routing

This skill is specialized for advertising workflows and should output actionable plans rather than generic advice.

When To Trigger

Use this skill when the user asks for:

• ad execution guidance tied to business outcomes
• growth decisions involving revenue, roas, cpa, or budget efficiency
• platform-level actions for: Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads
• this specific capability: handoff packet creation, escalation routing

High-signal keywords:

• ads, advertising, campaign, growth, revenue, profit
• roas, cpa, roi, budget, bidding, traffic, conversion, funnel
• meta, googleads, tiktokads, youtubeads, amazonads, shopifyads, dsp

Input Contract

Required:

• question: user issue or decision request
• context: account, campaign, and objective context
• urgency_level

Optional:

• error_message
• screenshots_or_logs
• preferred_response_style

Output Contract

1. Direct Answer
2. Root Cause Hypothesis
3. Immediate Actions
4. Escalation Criteria
5. Follow-up Questions

Workflow

1. Classify question type (how-to, diagnosis, policy, strategy).
2. Provide shortest valid answer first.
3. Add context-aware action checklist.
4. Flag escalation if risk or uncertainty is high.
5. Return follow-up fields only if required.

Decision Rules

• If answer confidence is low, state uncertainty and propose verification steps.
• If issue impacts spend safety, prioritize pause or cap recommendations.
• If user asks unsupported action, hand off with exact context package.

Platform Notes

Primary scope:

• Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads

Platform behavior guidance:

• Keep recommendations channel-aware; do not collapse all channels into one generic plan.
• For Meta and TikTok Ads, prioritize creative testing cadence.
• For Google Ads and Amazon Ads, prioritize demand-capture and query/listing intent.
• For DSP/programmatic, prioritize audience control and frequency governance.

Constraints And Guardrails

• Never fabricate metrics or policy outcomes.
• Separate observed facts from assumptions.
• Use measurable language for each proposed action.
• Include at least one rollback or stop-loss condition when spend risk exists.

Failure Handling And Escalation

• If critical inputs are missing, ask for only the minimum required fields.
• If platform constraints conflict, show trade-offs and a safe default.
• If confidence is low, mark it explicitly and provide a validation checklist.
• If high-risk issues appear (policy, billing, tracking breakage), escalate with a structured handoff payload.

Code Examples

Quick Triage JSON

{
  "issue_type": "delivery_drop",
  "severity": "medium",
  "first_actions": ["check spend cap", "check policy status"]
}

Handoff Payload

ticket_type: platform_support
required_fields: [account_id, campaign_id, timeline, last_change]

Examples

Example 1: Delivery suddenly dropped

Input:

• Campaign impressions down 60%
• No recent manual changes

Output focus:

• probable causes
• first 3 checks
• escalation trigger

Example 2: Policy rejection question

Input:

• Ad rejected with vague reason
• User wants fastest fix

Output focus:

• policy interpretation
• rewrite direction
• approval retry order

Example 3: Need human support now

Input:

• Billing or account lock issue
• Launch deadline is today

Output focus:

• handoff packet
• urgency level
• required owner and ETA

Quality Checklist

• Required sections are complete and non-empty
• Trigger keywords include at least 3 registry terms
• Input and output contracts are operationally testable
• Workflow and decision rules are capability-specific
• Platform references are explicit and concrete
• At least 3 practical examples are included