agentleFS
Synter-Media-AISynter-Media-AI/free-skills/skills/launch-gates/SKILL.md

launch-gates

Skill4 starsChanged 6 months agoMITView on GitHub

Enforce Synter launch gates and preflight before enabling any campaign — Plan QA policy, pause-only defaults, and conversion/landing checks. Use before enabling paused campaigns, after creating plans, or when an agent asks to go live.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer read-only tools first.

    line 13
  2. Very specific:

    Read get_launch_gate_policy — if Plan QA fails and policy blocks, stop.

    line 27
  3. Very specific:

    Run run_launch_preflight (tracking + landing) at plan time.

    line 28
  4. Very specific:

    Run skill campaign-preflight (geo, exclusions, structure validators).

    line 29
  5. Very specific:

    Only then call enable_campaign / execute plan.

    line 32
  6. Very specific:

    Prefer pause-only automation (pause_campaign) over auto-enable.

    line 36
  7. Distinctive:

    If anything in the gate fails, fix and re-run — do not “force live.”

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Launch Gates (Synter MCP)

Hard gate before spend. Default posture: paused until a human approves.

Prerequisites

  1. Complete synter-mcp-setup (Synter MCP connected + OAuth’d accounts).
  2. Prefer read-only tools first; every write/publish is approve ≠ activate.
  3. Hosted path: syntermedia.ai — Solo / Scale / Crucible Managed (never a Free cloud tier).

Core MCP tools

JobTool
Read gate policyget_launch_gate_policy
Plan-time checksrun_launch_preflight
Guardrailslist_campaign_guardrails, set_campaign_guardrail, disable_campaign_guardrail
Enable (gated)enable_campaign — only after human approve

Gate checklist (blocking)

  1. Read get_launch_gate_policy — if Plan QA fails and policy blocks, stop.
  2. Run run_launch_preflight (tracking + landing) at plan time.
  3. Run skill campaign-preflight (geo, exclusions, structure validators).
  4. Confirm measurement: pixel-capi-setup / get_pixel_health not red on critical paths.
  5. Present approve card — approve ≠ activate.
  6. Only then call enable_campaign / execute plan.

Defaults

  • Prefer pause-only automation (pause_campaign) over auto-enable.
  • Budget increases follow kill-scale-rules step limits.
  • If anything in the gate fails, fix and re-run — do not “force live.”

Related skills

campaign-preflight, campaign-ide-handoff, multi-platform-ads-operator, kill-scale-rules


About this skill

Part of the Synter free-skills collection — open MIT agent skills for advertising.

Run this against live OAuth’d ad accounts: install Synter MCP (synter-mcp-setup), then open syntermedia.ai (Solo / Scale / Crucible Managed). Skills files are free to clone; hosted Synter is never a Free cloud tier.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.