Youtube Search
ZeroPointRepo/youtube-skills
A skill your agent uses when the user wants to find YouTube content on any topic: searching for videos or channels, finding creators who cover a subject, discovering tutorials, talks, or expert…
Design lifecycle marketing / CRM journeys across the customer lifecycle.
Install Lifecycle CRM Plan
$ npx skills add mohitagw15856/pm-claude-skills --skill lifecycle-crm-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills lifecycle-crm-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/lifecycle-crm-plan .claude/skills/lifecycle-crm-plan && rm -rf skills-srcUse ~/.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/
Install the "lifecycle-crm-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/lifecycle-crm-plan into .claude/skills/lifecycle-crm-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lifecycle-crm-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/lifecycle-crm-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill lifecycle-crm-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills lifecycle-crm-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/lifecycle-crm-plan .agents/skills/lifecycle-crm-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lifecycle-crm-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/lifecycle-crm-plan into .agents/skills/lifecycle-crm-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lifecycle-crm-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill lifecycle-crm-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills lifecycle-crm-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/lifecycle-crm-plan .cursor/skills/lifecycle-crm-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lifecycle-crm-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/lifecycle-crm-plan into .cursor/skills/lifecycle-crm-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lifecycle-crm-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/lifecycle-crm-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill lifecycle-crm-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills lifecycle-crm-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/lifecycle-crm-plan .gemini/skills/lifecycle-crm-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lifecycle-crm-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/lifecycle-crm-plan into .gemini/skills/lifecycle-crm-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lifecycle-crm-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills lifecycle-crm-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill lifecycle-crm-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/lifecycle-crm-plan .github/skills/lifecycle-crm-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lifecycle-crm-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/lifecycle-crm-plan into .github/skills/lifecycle-crm-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lifecycle-crm-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill lifecycle-crm-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills lifecycle-crm-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/lifecycle-crm-plan .opencode/skills/lifecycle-crm-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lifecycle-crm-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/lifecycle-crm-plan into .opencode/skills/lifecycle-crm-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lifecycle-crm-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lifecycle-crm-plan- GitHub stars
- 1.4k
- Token cost
- ~886 tokens
- SKILL.md length
- 399 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design lifecycle marketing / CRM journeys across the customer lifecycle.
- Asked to plan onboarding emails
- SKILL.md covers Required Inputs, Output Format, Quality Checks and Anti-Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Lifecycle/CRM campaigns
What it does
Lifecycle CRM Plan is an agent skill from mohitagw15856/pm-claude-skills. Design lifecycle marketing / CRM journeys across the customer lifecycle. Use when asked to plan onboarding emails, lifecycle/CRM campaigns, drip sequences, re-engagement or winback flows, or a messaging calendar. Produces a lifecycle plan — stage map, the trigger/message/goal for each journey, channel & timing, segmentation, suppression rules, and success metrics.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Product metrics and Customer success. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to plan onboarding emails
- Lifecycle/CRM campaigns
- A messaging calendar
Example prompts
- “/lifecycle-crm-plan”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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 CRM Plan loads about 886 tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 399 words of instructions outside code blocks.
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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 399 words, ~886 tokens.
Download SKILL.mdSave it as
.claude/skills/lifecycle-crm-plan/SKILL.md (or your agent's skills folder).- name
- lifecycle-crm-plan
- description
- Design lifecycle marketing / CRM journeys across the customer lifecycle. Use when asked to plan onboarding emails, lifecycle/CRM campaigns, drip sequences, re-engagement or winback flows, or a messaging calendar. Produces a lifecycle plan — stage map, the trigger/message/goal for each journey, channel & timing, segmentation, suppression rules, and success metrics.
Lifecycle / CRM Plan Skill
Lifecycle marketing is the difference between a product people sign up for and one they actually use. This skill maps the customer lifecycle to triggered journeys — each with a clear job — so messaging is behaviour-driven and purposeful, not a batch-and-blast newsletter that trains people to ignore you.
Required Inputs
Ask for these only if they aren't already provided:
- Product & lifecycle stages — what the journey from signup → active → loyal → churned looks like.
- The key moments — activation milestone, the "aha", upgrade triggers, and churn signals.
- Channels available — email, push, in-app, SMS — and any consent/deliverability constraints.
- Goal — the lifecycle metric to move (activation %, D30 retention, expansion, winback rate).
Output Format
Lifecycle / CRM Plan: [product]
1. Lifecycle map — the stages and the one behaviour you want at each (signup → activate → habit → expand → renew; with winback for lapsed).
2. Journey table — the core deliverable:
| Journey | Trigger (behaviour, not date) | Audience/segment | Message & goal | Channel | Timing | Success metric | Exit/suppression |
|---|---|---|---|---|---|---|---|
| Onboarding | signed up, not activated | new, no key action | get to first value | email + in-app | t+0, t+1d, t+3d | activation % | activated → exit |
| Winback | inactive 30d | was active | reason to return | t+30, t+37 | reactivation % | returned → exit |
3. Segmentation — the few segments that change the message (by behaviour/value, not vanity demographics).
4. Timing & frequency — cadence rules and a global frequency cap / suppression so journeys don't collide or fatigue.
5. Measurement — per-journey metric, holdout group to prove incrementality, and the deliverability guardrails (bounce/spam/unsub watch).
Show full SKILL.md (162 more words)Show less
Quality Checks
- Journeys are behaviour-triggered, not date-batched
- Every journey has an explicit goal, success metric, and exit condition
- A global frequency cap / suppression prevents message collisions and fatigue
- A holdout group is used to measure incrementality, not just open/click rates
- Segmentation is based on behaviour/value, not vanity attributes
Anti-Patterns
- Do not batch-and-blast — untriggered, irrelevant sends train users to ignore and unsubscribe
- Do not measure success by opens/clicks alone — tie journeys to the lifecycle outcome (activation, retention, revenue) with a holdout
- Do not forget exit conditions — a user who already activated should not keep getting "activate now" emails
- Do not ignore frequency capping — overlapping journeys are how you fatigue and burn a list
- Do not skip deliverability guardrails — a great journey in the spam folder reaches no one
Based On
Lifecycle marketing / behavioural CRM practice — trigger-based journeys, segmentation, and incrementality testing with holdouts.
Example Trigger Phrases
- "Plan onboarding emails."
- "Plan our lifecycle campaigns."
- "Design drip and winback flows."
- "Build a CRM messaging calendar."
© mohitagw15856, MIT. 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 skills/lifecycle-crm-plan of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Lifecycle CRM Plan 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lifecycle CRM Plan this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~886 | Automated safety check: Pass | MIT | |
| Youtube SearchZeroPointRepo/youtube-skills | 1k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| YtZeroPointRepo/youtube-skills | 1k | 1 repos | ~951 | Automated safety check: Pass | MIT | |
| Loki Modedavila7/claude-code-templates | 33k | 7 repos | ~7.1k | Automated safety check: Warn | MIT | |
| Account Researchexplorium-ai/gtm-skills | 185 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Positive Reply Scoringgrowthenginenowoslawski/coldoutboundskills | 753 | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Yt
ZeroPointRepo/youtube-skills
A skill your agent uses when YouTube is relevant: pasted video links or IDs, @handles, quick video lookups, summaries, channel latest uploads, topic search, or any request involving YouTube content…
Loki Mode
davila7/claude-code-templates
Multi-agent autonomous startup system for Claude Code. An agent skill from davila7/claude-code-templates.
Account Research
explorium-ai/gtm-skills
Account research skill for Claude Code and Codex: generate a high-signal company intelligence brief including firmographics, technographics, funding history, hiring signals, business events, recent…
Positive Reply Scoring
growthenginenowoslawski/coldoutboundskills
Pulls replies from a Smartlead campaign, classifies each as positive/neutral/negative/OOO/bounce/unsubscribe using Claude, and reports the positive reply rate — the north-star metric for cold email.
Expansion Retention
tech-leads-club/agent-skills
When the user wants to reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Lifecycle CRM Plan
What does Lifecycle CRM Plan do?
Design lifecycle marketing / CRM journeys across the customer lifecycle. Lifecycle CRM Plan is an agent skill from mohitagw15856/pm-claude-skills. Design lifecycle marketing / CRM journeys across the customer lifecycle.
When should I use Lifecycle CRM Plan?
Lifecycle CRM Plan fits situations like: asked to plan onboarding emails; lifecycle/CRM campaigns; A messaging calendar.
How do I install Lifecycle CRM Plan in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill lifecycle-crm-plan -a claude-code`. Or copy the skill folder (skills/lifecycle-crm-plan in mohitagw15856/pm-claude-skills) into .claude/skills/lifecycle-crm-plan in your project. Claude Code loads it when a task matches its description.
How do I install Lifecycle CRM Plan in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill lifecycle-crm-plan -a codex`. Or copy the skill folder (skills/lifecycle-crm-plan in mohitagw15856/pm-claude-skills) into .agents/skills/lifecycle-crm-plan in your project. Codex loads it when a task matches its description.
Can I use Lifecycle CRM Plan 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 mohitagw15856/pm-claude-skills --skill lifecycle-crm-plan -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-crm-plan, .gemini/skills/lifecycle-crm-plan, .github/skills/lifecycle-crm-plan and .opencode/skills/lifecycle-crm-plan in your project.
What does Lifecycle CRM Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Lifecycle CRM Plan is instructions for the agent only.
Does Lifecycle CRM Plan 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 CRM Plan 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 CRM Plan use?
Lifecycle CRM Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lifecycle CRM Plan use?
About 886 tokens (SKILL.md is roughly 3.5k 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 CRM Plan?
Skills that share tags, products or a category with Lifecycle CRM Plan: Youtube Search (ZeroPointRepo/youtube-skills, 1k stars), Yt (ZeroPointRepo/youtube-skills, 1k stars), Loki Mode (davila7/claude-code-templates, 33k stars) and Account Research (explorium-ai/gtm-skills, 185 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lifecycle CRM Plan?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.