human-handoff-coordinator_skill

This skill escalates ad automation discussions to human experts, delivering a clear handoff packet and escalation routing for Meta, Google, TikTok, and YouTube.
  • Python

2.6k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill human-handoff-coordinator

  • _meta.json310 B
  • metadata.json81 B
  • SKILL.md4.0 KB

Overview

This skill coordinates human handoffs for ad operations across Meta (Facebook/Instagram), Google Ads, TikTok Ads, and YouTube Ads. It creates structured handoff packets, triages escalation severity, and provides immediate, platform-aware actions to protect spend and restore performance. The goal is rapid, testable escalation that minimizes revenue impact.

How this skill works

The skill classifies the incoming request (how-to, diagnosis, policy, strategy) and returns a shortest-valid answer first, followed by a root-cause hypothesis and an action checklist. It generates a handoff payload when human intervention is required, including required fields, urgency, and owner recommendations. All guidance is channel-aware and includes at least one rollback/stop-loss condition when spend risk exists.

When to use it

  • You need a rapid, actionable escalation for delivery, billing, or policy issues affecting campaign performance.
  • You require a human-support packet for platform support or account team intervention.
  • You need a prioritized checklist to triage sudden drops in impressions, conversions, or spend anomalies.
  • You want platform-specific next steps for Meta, Google Ads, TikTok, or YouTube actions tied to revenue or ROAS goals.
  • You must decide whether to pause/cap spend versus continue testing under uncertainty.

Best practices

  • Provide minimum required inputs: question, account/campaign/context, and urgency_level before escalation.
  • State observed facts separately from hypotheses; include timestamps and recent changes.
  • Use channel-aware advice: prioritize creative cadence for Meta/TikTok and query intent for Google.
  • Always include a rollback/stop-loss threshold and clear escalation criteria.
  • If confidence is low, mark it and include validation steps and monitoring windows.

Example use cases

  • Delivery drop: supply impressions %, first three checks (spend cap, policy, creative), and escalation trigger if unresolved in X hours.
  • Policy rejection: interpret rejection, propose rewrite directions, and prepare approval retry order for review team.
  • Billing/account lock: produce a handoff packet with required fields, urgency level, owner, and ETA for account recovery.
  • Scaling decision: recommend bid/budget shifts tied to target ROAS and a monitoring plan with stop-loss caps.

FAQ

Provide the user question, account and campaign context (IDs, objectives), and urgency_level. Include error messages or screenshots when available.

How does the skill handle uncertainty?

It explicitly marks low confidence, lists verification steps, recommends safe defaults (pause/cap), and supplies a validation checklist for the human reviewer.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
human-handoff-coordinator skill by openclaw/skills | VeilStrat