Agent skill
activate
Push the campaign-ready list into the configured sequencer (capability sequencer_push) — the final stage.
Filed under Outbound email.
From kkrlstrm/gtm-pipeline · 9 skill entries · 16 · pushed 2026-09-29
What it does when it runs
Push the campaign-ready list into the configured sequencer (capability sequencer_push) — the final stage. Reads the storage export, builds the campaign payload, and pushes via the chosen sequencer's manifest/adapter, behind a deterministic preflight (do-not-contact applied, QA clean) and an always-on activation gate. Use when the user wants to "push to the sequencer", "create the campaign", "activate list N", or "send to lemlist".
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- Read
- Bash
- Actions present in the files
- shell
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/kkrlstrm/gtm-pipeline.git /tmp/gtm-pipeline git -C /tmp/gtm-pipeline sparse-checkout set ".claude/skills/activate" mkdir -p ~/.claude/skills/activate cp -R "/tmp/gtm-pipeline/.claude/skills/activate/." ~/.claude/skills/activate/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from kkrlstrm/gtm-pipeline/blob/3fdc07a14e4f3991eba66ec2e8a9feb8fec4a197/.claude/skills/activate/SKILL.md, which is licensed APACHE-2.0 (repository). 62 words, 0 headings.
Input (list_id, optional campaign name + steps): $ARGUMENTS
Execute activation: read agents/activate/agent.md and follow it exactly — bootstrap
(config + the sequencer provider's manifest; confirm its key is set), build leads via
storage/cli.py export at the deepest completed stage, present the activation summary
(Gate #4) for confirmation, then push via the sequencer adapter
(--capability sequencer_push). Report the campaign id + imported/skipped/failed counts.
Need help setting it up?
This page tells you what activate does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.