lifecycle
Skill0 starsChanged 8 months agoMITView on GitHub
Customer lifecycle touchpoints. Identifies milestone customers (post-purchase, renewal, at-risk, upsell) and drafts personalized outreach. Automated/ongoing. Octopus colors: Green (outreach) + Yellow (personalization data).
6 other projects use a version of this.
Adopted by
Most recently taken up by
- matthewdonsemail-lab/logtheir own version, first seen Nov 15, 2026
- UnBergant/bergant-workflowtheir own version, first seen Nov 8, 2026
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- violetfleming47/deal-intelligencetheir own version, first seen Oct 25, 2026
- ali-demirbas/claude-lifecycletheir own version, first seen Jul 17, 2026
- Deepanshu418/claude-code-elysiatheir own version, first seen Feb 27, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- matthewdonsemail-lab/log★ 63same name
- UnBergant/bergant-workflow★ 5same name
- ali-demirbas/claude-lifecycle★ 4same name
- violetfleming47/deal-intelligence★ 4same name
- Deepanshu418/claude-code-elysia★ 2same name
- BrightGold70/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read departments/commercial/knowledge/ or departments/after-sales/knowledge/ for customer data
- Distinctive: line 56
Never mention competitors in outreach
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/lifecycle: Customer Lifecycle Touchpoints
Octopus Colors: Green (Marketer) + Yellow (Researcher)
Process
- Read
departments/commercial/knowledge/ordepartments/after-sales/knowledge/for customer data - Identify milestone customers (Yellow):
- 30-day post-purchase: satisfaction check-in
- Quarterly: relationship maintenance
- Renewal approaching (60 days out): renewal offer
- Usage drop-off or inactivity: re-engagement
- Upsell opportunity: based on purchase history or behavior
- At-risk signals: complaints, missed payments, competitor mentions
- Draft touchpoint messages (Green):
- Personalize to customer's specific product/service
- Match tone to relationship stage
- Include one relevant value-add (tip, offer, content)
- Present to Chairman
Output Format
# Lifecycle Touchpoints: [Date]
## High Priority (review and send)
### [Customer Name] - [Trigger: renewal/at-risk/upsell]
**Context:** [What triggered this, relationship history]
**Draft Message:**
[Ready-to-send message]
**Channel:** [email/WhatsApp/phone]
**Approval:** [ ] Send [ ] Edit [ ] Skip
## Automated (send without review if trust level allows)
### [Customer Name] - [Trigger: 30-day check-in]
[Message]
## Summary
- Total touchpoints: [count]
- High priority (Chairman review): [count]
- Automated: [count]Rules
- At-risk and renewal customers ALWAYS require Chairman review (approval gate)
- Routine check-ins can auto-send once trust level is "mature"
- Never mention competitors in outreach
- Log all touchpoints to
departments/commercial/knowledge/touchpoints.mdor equivalent
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
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.

