agentsclimarketplace
Sign in

Customer support vs ltv

Skill akhilkannur/marketing-agent-blueprints/skills/customer-support-vs-ltv

Checks if customers with high support ticket volume actually have higher or lower Lifetime Value.From its SKILL.md

Install
npx -y skills add akhilkannur/marketing-agent-blueprints --skill customer-support-vs-ltv

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

0.9 KB, 195 tokens by cl100k_base, as published. Nobody here has run it

Support Cost vs LTV

Core Instructions

You are a highly specialized AI agent focusing on CRO. Your mission is: Checks if customers with high support ticket volume actually have higher or lower Lifetime Value.

Implementation Workflow

Phase 1: Initialization & Seeding

  1. Check: Does support_ltv.csv exist?
  2. If Missing: Create support_ltv.csv using the sampleData provided in this blueprint.
  3. If Present: Load the data for processing.

Phase 2: The Loop

  1. Read: support_ltv.csv.
  2. Group: High Tickets (5+) vs Low.
  3. Compare: Avg LTV.
  4. Output: Save maintenance_cost_analysis.md.

Blueprint ID: customer-support-vs-ltv Source: Real AI Examples

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most customer support skills give in 195 tokens

Counted across 123 of the 124 authors here whose files we hold, read 2026-08-07

  • Call RUBE_SEARCH_TOOLS first to get current schemasin 12 of 123, across 4 files
  • Confirm connection status is ACTIVE before running workflowsin 12 of 123, across 4 files
  • Stop and ask for clarification if required inputs are missingin 9 of 123, across 2 files
  • Call RUBE_MANAGE_CONNECTIONS with the helpdesk toolkitin 9 of 123, across 2 files
  • Use both timestamp and ID for cursor navigationin 8 of 123, across 1 file
  • Implement backoff on 429 responsesin 8 of 123, across 1 file
  • Parse response data defensively with fallback patternsin 8 of 123, across 1 file
  • Use this skill only when the task clearly matches the scopein 8 of 123, across 1 file
  • Pass a JSON file as the positional argumentin 7 of 123, across 1 file
  • Specify output format with the --format flagin 7 of 123, across 1 file
  • Run health, churn, and expansion scripts togetherin 7 of 123, across 1 file
  • Verify output files contain expected records before continuingin 7 of 123, across 1 file

Said here and by no other author read

  • Create support_ltv.csv if it is missing
  • Read support_ltv.csv
  • Group customers by high and low support volume
  • Compare average LTV between groups
  • Save maintenance_cost_analysis.md

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.