Agent skill

Lifecycle Mapping for Automation

by gtmagents in gtmagents/gtm-agents

Frames marketing automation around lifecycle stages, signals, touches and SLAs, with worksheets for onboarding, expansion, renewal and churn-prevention journeys.

Apache-2.0Auto-check passedMarketing & SEO

Install Lifecycle Mapping for Automation

skills CLI
$ npx skills add gtmagents/gtm-agents --skill lifecycle-mapping -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gtmagents/gtm-agents lifecycle-mapping --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/marketing-automation/skills/lifecycle-mapping .claude/skills/lifecycle-mapping && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lifecycle-mapping
GitHub stars
413
Used in
1 other repo
Token cost
~927 tokens
SKILL.md length
408 words
Files
1
Skills in repo
127
Repo updated
First seen
Licence
Apache-2.0

At a glance

Frames marketing automation around lifecycle stages, signals, touches and SLAs, with worksheets for onboarding, expansion, renewal and churn-prevention journeys.

  • Works in 5 steps: Stage Definition – awareness,… → Signal Library – activation events,… → Touch Architecture – how many touches… → …
  • Blueprinting onboarding, expansion, renewal or churn-prevention journeys
  • SKILL.md covers When to Use, Framework, Templates and Tips, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill gives a five-part framework for lining automation up with where an account sits in its lifecycle. You define the stages (awareness, activation, adoption, expansion and advocacy, adjusted to the business), list the signals that move accounts between them, set how many touches each stage gets and through which channels, write an SLA matrix with entry and exit criteria, owner, response time and success metrics, and reserve slots for experiments.

The text includes templates for a lifecycle heat map of stage against metric and automation coverage, an SLA worksheet, a journey backlog board, a KPI guardrails sheet and a weekly status packet. Tips include limiting simultaneous journeys per contact, adding manual checkpoints for high-touch segments, locking KPIs before building and pairing each automation change with a rip-cord procedure. A five-stage campaign blueprint for larger GTM initiatives opens with briefing and alignment, then architecture.

When your agent uses it

  • Blueprinting onboarding, expansion, renewal or churn-prevention journeys
  • Aligning automation programs with account stages, ICP tiers or health scores
  • Auditing existing programs for gaps or over-saturation

Example prompts

  • “Map our onboarding and renewal journeys to lifecycle stages, with an SLA matrix for each one.”
  • “Audit our email nurture programs and show which stages get too many touches.”
  • “Draft a lifecycle heat map of stage, metric and automation coverage for our SaaS accounts.”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Stage Definition – awareness, activation, adoption, expansion, advocacy (customize per business).
  2. Signal Library – activation events, product usage milestones, score thresholds, purchase behaviors.
  3. Touch Architecture – how many touches per stage, channel mix, personal vs automated.
  4. SLA Matrix – entry/exit criteria, owner, response time, success metrics.
  5. Experiment Layer – embed test slots to iterate hooks, cadences, or offers per stage.

What it can do on your machine

Read from SKILL.md and the folder at commit 78e0419. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lifecycle Mapping for Automation loads about 927 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 408 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~927

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gtmagents/gtm-agents at commit 78e0419, republished under its Apache-2.0 licence (© gtmagents). 408 words, ~927 tokens.

Download SKILL.mdSave it as .claude/skills/lifecycle-mapping/SKILL.md (or your agent's skills folder).
name
lifecycle-mapping
description
Use when designing automation programs aligned to lifecycle stages, SLAs, and GTM objectives.

Lifecycle Mapping Frameworks Skill

When to Use

  • Blueprinting onboarding, expansion, renewal, or churn-prevention journeys.
  • Aligning automation programs with account stages, ICP tiers, or health scores.
  • Auditing existing programs for gaps or over-saturation.

Framework

  1. Stage Definition – awareness, activation, adoption, expansion, advocacy (customize per business).
  2. Signal Library – activation events, product usage milestones, score thresholds, purchase behaviors.
  3. Touch Architecture – how many touches per stage, channel mix, personal vs automated.
  4. SLA Matrix – entry/exit criteria, owner, response time, success metrics.
  5. Experiment Layer – embed test slots to iterate hooks, cadences, or offers per stage.

Templates

  • Lifecycle heat map (stage vs metric vs automation coverage).
  • SLA worksheet (stage, trigger, owner, time-to-response, fallback).
  • Journey backlog board (ideas, prioritized, building, live, measuring).
  • GTM Agents Campaign Planning Checklist – captures marketing director playbook @puerto/README.md#183-212.
  • KPI Guardrails Sheet – track reach, engagement, SQL impact, CAC payback with min/max thresholds.
  • Status Packet Template – weekly single-slide update mirroring GTM Agents project-manager format @puerto/TEAM-STRUCTURE.md#193-204.

Tips

  • Limit simultaneous journeys per contact; define prioritization rules.
  • Include manual checkpoints (CSM/AE) for high-touch segments.
  • Document every assumption so experiments can deliberately challenge them.
  • Lock KPIs before build starts and refuse scope creep until metrics + owners are confirmed.
  • Borrow GTM Agents's cadence: Plan → Build → QA → Launch → Inspect so reporting lines know when to approve or intervene.
  • Pair every automation change with a "rip-cord" procedure the Sales Director or Ops Lead can trigger if leading indicators degrade.
Show full SKILL.md (178 more words)Show less

GTM Agents Campaign Blueprint (Adopted)

Use this five-stage blueprint when large GTM initiatives require orchestration across demand gen, lifecycle, and RevOps teams:

  1. Stage 1 – Briefing & Alignment
    • Confirm objective, ICP, offer, timeline, and budget.
    • Capture cross-functional stakeholders (Marketing Director, Sales Director, RevOps Lead) and escalation paths.
  2. Stage 2 – Architecture
    • Map lifecycle stages to channels + automations.
    • Define entry/exit criteria, personalization logic, and compliance constraints.
    • Assign data availability checks (Serena) + documentation pulls (Context7) if needed.
  3. Stage 3 – Build & QA
    • Break work into swimlanes (journey build, content, data, QA) and track in backlog.
    • Require Playwright or similar browser QA for every externally facing experience.
  4. Stage 4 – Launch & Monitor
    • Set Day 0/Day 7 KPI guardrails (e.g., form conversion ≥ 4%, unsubscribe ≤ 0.4%).
    • Route anomalies to the Operations Lead with a rollback procedure.
  5. Stage 5 – Inspect & Iterate
    • Use Sequential Thinking to run structured retros (what worked, what failed, hypotheses for next wave).
    • Feed learnings back into lifecycle heat map + SLA matrix.

Status Reporting Template

Campaign: <Name>
Week Ending: <Date>

1. Highlights (wins, blockers, escalations)
2. KPI Snapshot (target vs actual vs guardrail)
3. Journey Coverage (stage, channel, live %)
4. Next 5 Actions (owner, due date)
5. Risks & Decisions Needed (include GTM Agents-style RAG)

Use this template to sync with Sales Director, Partnership Manager, and Project Manager counterparts each week.


© gtmagents, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/marketing-automation/skills/lifecycle-mapping of gtmagents/gtm-agents.

Open the folder on GitHubat commit 78e0419

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gtmagents/gtm-agents, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Lifecycle Mapping for Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lifecycle Mapping for Automation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lifecycle Mapping for Automation this skillgtmagents/gtm-agents4131 repos~927Automated safety check: PassApache-2.0
B2b Brand Marketingarnabbagxd/Brand-building-skills720—~2.4kAutomated safety check: PassMIT
One Page Marketingwondelai/skills2.4k—~5.6kAutomated safety check: PassMIT
No Lead Left Behind Lead Treatment Auditzapier/gtm-cheat-codes342—~319Automated safety check: PassMIT
Marketing Funnel Planmohitagw15856/pm-claude-skills1.4k—~845Automated safety check: PassMIT
GTM Engineeringtech-leads-club/agent-skills7k—~4.8kAutomated safety check: PassCustom licence

Similar skills

  • B2b Brand Marketing

    arnabbagxd/Brand-building-skills

    Build and execute brand marketing strategy for B2B companies — thought leadership, ABM brand layer, trust signals, LinkedIn presence, long sales cycle brand touchpoints, and enterprise credibility.

    720 GitHub stars~2.4k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • One Page Marketing

    wondelai/skills

    Build a complete marketing plan covering the full customer journey from stranger to raving fan.

    2.4k GitHub stars~5.6k tokensUpdated 27 days ago
    Marketing & SEOAuto-check passed
  • Official

    Audit lead handling quality across GTM systems and identify missed or low-quality follow-up.

    342 GitHub stars~319 tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed
  • Marketing Funnel Plan

    mohitagw15856/pm-claude-skills

    Plan a full-funnel marketing strategy from awareness to retention.

    1.4k GitHub stars~845 tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • GTM Engineering

    tech-leads-club/agent-skills

    Designs go-to-market automation and AI agent workflows for revenue teams, built on the idea that architecture and context matter more than any single tool.

    7k GitHub stars~4.8k tokensUpdated 18 days ago
    Productivity & AutomationAuto-check passed
  • Daily Lead Steward

    zapier/gtm-cheat-codes

    Official

    Maintain a daily review cockpit for high-intent leads and hand-raisers.

    342 GitHub stars~258 tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed

More from gtmagents/gtm-agents

All 127 skills in this repo
  • Enrichment Data Sourcing

    gtmagents/gtm-agents

    Chooses and orders data providers for email, phone, company and intent enrichment, with waterfall sequences and credit-saving tactics across 150+ sources.

    413 GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check passed
  • Cold Email Personalization

    gtmagents/gtm-agents

    Writes personalized B2B cold emails from prospect research, using a gated workflow, a quality rubric and follow-up sequences.

    413 GitHub starsUsed in 1 repo~853 tokens
    Auto-check passed
  • Discovery Call Playbook

    gtmagents/gtm-agents

    Structures sales discovery calls with a PREP routine, a five-part call flow, a question bank, a qualification scorecard and a follow-up recap email.

    413 GitHub starsUsed in 1 repo~368 tokens
    Auto-check passed
  • Social Selling

    gtmagents/gtm-agents

    A skill your agent uses when engaging prospects through LinkedIn, communities, and social channels to spark warm conversations and meetings.

    413 GitHub starsUsed in 1 repo~431 tokens
    Auto-check passed
  • Drip Campaigns

    gtmagents/gtm-agents

    A skill your agent uses when you need to map sequenced nurture flows with pacing, storytelling arcs, and value ladders.

    413 GitHub starsUsed in 1 repo~310 tokens
    Auto-check passed
  • Editorial Ops

    gtmagents/gtm-agents

    A skill your agent uses when planning multi-channel editorial calendars, enforcing publishing cadences, and coordinating distribution workflows across GTM teams.

    413 GitHub starsUsed in 1 repo~821 tokens
    Auto-check passed

Questions about Lifecycle Mapping for Automation

What does Lifecycle Mapping for Automation do?

Frames marketing automation around lifecycle stages, signals, touches and SLAs, with worksheets for onboarding, expansion, renewal and churn-prevention journeys. This skill gives a five-part framework for lining automation up with where an account sits in its lifecycle. You define the stages (awareness, activation, adoption, expansion and advocacy, adjusted to the business), list the signals that move accounts between them, set how many touches each stage gets and through which channels, write an SLA matrix with entry and exit criteria, owner, response time and success metrics, and reserve slots for experiments.

When should I use Lifecycle Mapping for Automation?

Lifecycle Mapping for Automation fits situations like: blueprinting onboarding, expansion, renewal or churn-prevention journeys; aligning automation programs with account stages, ICP tiers or health scores; auditing existing programs for gaps or over-saturation.

How do I install Lifecycle Mapping for Automation in Claude Code?

Run `npx skills add gtmagents/gtm-agents --skill lifecycle-mapping -a claude-code`. Or copy the skill folder (plugins/marketing-automation/skills/lifecycle-mapping in gtmagents/gtm-agents) into .claude/skills/lifecycle-mapping in your project. Claude Code loads it when a task matches its description.

How do I install Lifecycle Mapping for Automation in Codex?

Run `npx skills add gtmagents/gtm-agents --skill lifecycle-mapping -a codex`. Or copy the skill folder (plugins/marketing-automation/skills/lifecycle-mapping in gtmagents/gtm-agents) into .agents/skills/lifecycle-mapping in your project. Codex loads it when a task matches its description.

Can I use Lifecycle Mapping for Automation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gtmagents/gtm-agents --skill lifecycle-mapping -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lifecycle-mapping, .gemini/skills/lifecycle-mapping, .github/skills/lifecycle-mapping and .opencode/skills/lifecycle-mapping in your project.

What does Lifecycle Mapping for Automation need to run?

SKILL.md names no scripts, command-line tools or credentials: Lifecycle Mapping for Automation is instructions for the agent only.

Does Lifecycle Mapping for Automation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Lifecycle Mapping for Automation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lifecycle Mapping for Automation use?

Lifecycle Mapping for Automation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lifecycle Mapping for Automation use?

About 927 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lifecycle Mapping for Automation?

Skills that share tags, products or a category with Lifecycle Mapping for Automation: B2b Brand Marketing (arnabbagxd/Brand-building-skills, 720 stars), One Page Marketing (wondelai/skills, 2.4k stars), No Lead Left Behind Lead Treatment Audit (zapier/gtm-cheat-codes, 342 stars) and Marketing Funnel Plan (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lifecycle Mapping for Automation?

gtmagents (a GitHub user) maintains it in gtmagents/gtm-agents, which has 413 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on April 3, 2026.

Source: gtmagents/gtm-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.