mcpField
C
customer-reference-program-review

customer-reference-program-review

github.com/sylphxaiMarketing & growth137 installsUpdated today
Repository

About customer-reference-program-review

customer-reference-program-review is a skill for turning customer advocacy and reference-program questions into operational plans. It defines proof formats, consent and eligibility controls, ownership, metrics, and recovery paths for marketing and sales teams.

Key features

  1. 01Classifies customer proof formats
  2. 02Defines consent and eligibility rules
  3. 03Sets reference matching and request intake
  4. 04Specifies usage and renewal guardrails
  5. 05Creates plans, decision tables, and workflows

Use cases

  1. 01Designing a customer reference program
  2. 02Setting approval rules for quotes and case studies
  3. 03Matching references to buyer segments
  4. 04Managing advocacy fatigue and reference retirement

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill customer-reference-program-review

After installing, type/customer-reference-program-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/customer-reference-program-patterns.md

Details

From the project README

Customer Reference Program Review

Use this skill to convert customer reference, case study, quote, logo, consent, sales proof, and advocacy governance questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify target buyers, proof gaps, customer health, consent status, legal constraints, reference formats, sales request volume, segment matching, and advocacy fatigue risk.
  2. Read references/customer-reference-program-patterns.md.
  3. Classify proof as anonymous evidence, approved quote, logo, case study, reference call, webinar, analyst reference, procurement proof, or executive sponsor.
  4. Define eligibility, consent, approval, matching, request intake, usage limits, incentives, renewal/health guardrails, refresh cadence, and retirement rules.
  5. Produce reference program plan, state machine, decision table, event schema, advocacy checklist, and sales enablement workflow.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not use logos, quotes, metrics, recordings, or case studies without explicit approval and scope.
  • Do not pressure unhealthy, renewing, escalated, or overused customers into advocacy.
  • Do not let sales invent reference claims, confidential outcomes, or segment fit.
  • Do not treat references as a substitute for product proof, security evidence, or implementation quality.

Output format

Reference context:
Audience / source of truth / risk boundary:

Customer advocacy plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Eligibility, consent, matching, and fatigue controls:
- <trigger> -> <policy, metric, edge case, support note>

Comments

Markdown supported