agentleFS
victordelrosalvictordelrosal/chairman/.claude/skills/lifecycle/SKILL.md

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

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
  1. Very specific:

    Read departments/commercial/knowledge/ or departments/after-sales/knowledge/ for customer data

    line 14
  2. Distinctive:

    Never mention competitors in outreach

    line 56

“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.

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

/lifecycle: Customer Lifecycle Touchpoints

Octopus Colors: Green (Marketer) + Yellow (Researcher)

Process

  1. Read departments/commercial/knowledge/ or departments/after-sales/knowledge/ for customer data
  2. 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
  3. Draft touchpoint messages (Green):
    • Personalize to customer's specific product/service
    • Match tone to relationship stage
    • Include one relevant value-add (tip, offer, content)
  4. 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.md or equivalent

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.