# Customer Proof Development

> Use when a team needs to audit, develop, structure, verify, anonymize, approve, adapt, govern, refresh, or retire customer proof, case studies, testimonials, references, outcome stories, quotes, before-and-after evidence, customer metrics, proof libraries, or derivative sales and marketing claims without contacting customers or publishing assets.

- **Type:** Skill
- **Install:** `agentstack add skill-krillinai-growee-skills-customer-proof-development`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [krillinai](https://agentstack.voostack.com/s/krillinai)
- **Installs:** 0
- **Category:** [Data & Analytics](https://agentstack.voostack.com/c/data-and-analytics)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [krillinai](https://github.com/krillinai)
- **Source:** https://github.com/krillinai/growee-skills/tree/main/skills/content-strategy/references/modules/customer-proof-development
- **Website:** www.clawee.ai/

## Install

```sh
agentstack add skill-krillinai-growee-skills-customer-proof-development
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Customer Proof Development

Turn attributable, permissioned customer evidence into bounded proof that preserves who experienced what, under which conditions, over what period, and with what limitations. Optimize credibility, decision usefulness, and traceability, not dramatic narratives, logo count, largest metric, quote strength, asset volume, or conversion claims alone.

Read [proof-contract.md](references/proof-contract.md) before accepting a customer identity, relationship, source, quote, metric, outcome, permission, or usage right. Read [evidence-claims-and-metrics.md](references/evidence-claims-and-metrics.md) before verifying quotes, calculations, before-and-after evidence, prevalence, contribution, or causality. Read [story-formats-and-reuse.md](references/story-formats-and-reuse.md) before drafting narratives, anonymizing, adapting formats, or building a proof library. Read [consent-privacy-and-governance.md](references/consent-privacy-and-governance.md) before using private evidence, incentives, regulated claims, customer identity, approvals, or external actions. Read [output-contract.md](references/output-contract.md) before delivery. Use [playbook-sources.md](references/playbook-sources.md) to cite the pinned Growth Playbook basis.

## Select One Mode

| Mode | Use |
| --- | --- |
| `audit` | Inspect proof accuracy, evidence, lineage, consent, claims, freshness, channel use, risks, and gaps |
| `develop` | Turn supplied and authorized evidence into a bounded case, testimonial, reference brief, proof unit, or derivative draft |
| `library` | Design or govern proof taxonomy, source lineage, permissions, versions, usage, refresh, withdrawal, archive, and retirement |

Name one primary mode, decision, owner, customer and role, product and version, proof unit, audience, channel, market, language, locale, evidence cutoff, usage horizon, and external-action boundary. Public customer logos, review snippets, posts, partner pages, and testimonials can verify only what is visibly and attributably stated. They do not establish current customer status, implementation, adoption, outcomes, retention, revenue, ROI, endorsement scope, or permission for new uses.

## Freeze The Proof Contract

Record company, legal entity, brand, customer relationship, participant, speaker, role, title, account, user, buyer, payer, beneficiary, industry, market, language, locale, product, edition, plan, version, workflow, problem, prior alternative, selection, implementation, adoption, first and repeated value, outcome, metric, source, quote, paraphrase, translation, screenshot, logo, artifact, date, period, baseline, comparator, sample, calculation, currency, cost, limitation, concurrent change, counterevidence, incentive, consent, usage right, edit right, approval, channel, audience, market, duration, expiry, withdrawal, privacy, owner, and requested external action.

Use exactly `verified`, `inferred`, `unavailable`, or `not applicable` for evidence-bearing rows. A customer, employee, seller, partner, stakeholder, or vendor statement without inspectable support may be a `reported signal` with no evidence state. Keep customer statement, source fact, observed association, bounded contribution, causal effect, prediction, guarantee, and derivative claim separate.

## Build Atomic Proof Units

Every proof unit contains one customer and role, one scoped claim or quote, one product and version, one situation and period, one source lineage, one evidence state, material conditions and limitations, and one permission boundary. Keep source evidence immutable; derivatives point back to it.

Do not infer use or results from a logo. Do not combine several customers into an undisclosed composite, invent a company or quote, convert one report into population prevalence, or promise that future customers will obtain the same outcome. A clearly labeled hypothetical demonstration is not customer proof.

## Preserve Quote And Meaning Integrity

Keep direct quotes verbatim. Record speaker, role, company, source, date, context, prompt, surrounding qualifiers, language, translation, incentive, and approval. A shortened quote must not change scope, certainty, subject, timing, condition, or sentiment. Mark paraphrases and translations explicitly.

Do not remove setup difficulty, continued manual work, mixed adoption, uncertainty, or negative outcomes to create a stronger quote. Never attribute agent-written wording to the customer. Provide proposed wording separately for customer review when authorized.

## Verify Metrics Before Publishing Them

For every quantitative claim define metric, decision use, customer entity, baseline, comparator, numerator, denominator, unit, period, sample, eligibility, source system, calculation, exclusions, product version, market, currency, cost, maturity, uncertainty, and customer and internal approvals. Preserve exact source values and derived calculations separately.

An ambiguous statement such as `we saved 70%` remains a reported signal until its basis is verified. Do not convert it into cost, speed, money, annual value, ROI, or another metric. Do not select the highest metric while hiding denominator, timing, cost, or later reversal.

## Keep Contribution And Causality Bounded

Before-and-after movement, customer belief, product adoption timing, or attributed outcomes do not by themselves prove causal lift. Preserve changes in customer mix, headcount, process, pricing, channels, market, seasonality, other tools, implementation, and measurement. Use `reported by the customer`, `associated with`, `used in`, `supported`, or another bounded construction only when source meaning supports it.

For causal claims require a credible counterfactual, assignment or identification, exposure, compatible outcome, maturity, assumptions, and guardrails, then route method and interpretation to `growth-measurement`. Do not calculate incremental ROI from a simple before-and-after difference.

## Tell The Complete Decision-Relevant Story

Structure proof around the customer situation, prior alternative, decision criteria, product and implementation conditions, path to first and repeated value, evidence-supported outcomes, tradeoffs, costs, limitations, best-fit conditions, current status, and next step. Include material delays, failed workflows, uneven adoption, increased cost, reduced usage, or other counterevidence.

The story need not be negative, but it must not imply effortless, universal, permanent, or guaranteed success. Separate customer experience from company product claims and category conclusions.

## Acquire Rights Per Use

Research participation, private reference, quote use, logo use, screenshot use, metric use, case publication, sales use, ad use, press use, translation, localization, sublicensing, model training, and public reuse are different permissions. Define exact item, wording, edits, identity, channels, audiences, markets, languages, duration, effective date, expiry, withdrawal, correction, deletion, and approval owner.

Possession of CRM, calls, tickets, logs, contracts, invoices, emails, or product data is not publication permission. Use the minimum authorized evidence, protect confidential and security information, and preserve research, operations, customer reference, sales, marketing, press, and model purposes separately.

## Adapt Formats Through Lineage

Create atomic approved proof units before deriving a case page, short testimonial, sales slide, reference brief, ad, press quote, app listing, analyst response, social post, or localized asset. Every derivative records source units, exact edits, format, channel, audience, market, language, owner, version, approval, publication state, usage locations, expiry, withdrawal, and retirement.

Do not use one long interview unchanged across formats. Adapt length and structure without expanding the claim. Route final prose and edits to `copywriting`, content portfolio decisions to `content-strategy`, seller and buyer use to `sales-enablement`, and press use to the sibling [Public Relations](../public-relations/SKILL.md) module.

## Govern The Proof Library

Version customer role and relationship, product, claim, quote, metric, logo, screenshot, price, contract, market, permission, and outcome. Track active, review due, restricted, expired, withdrawn, corrected, superseded, archived, and retired states. Prevent expired or withdrawn proof from new use while preserving the audit history and removal obligations.

Refresh proof when the product, customer relationship, role, result, metric, market, claim, permission, regulation, or channel changes. The highest number is not automatically the most relevant proof.

## Deliver In Order

Return:

1. mode, decision, owner, customer, role, product, proof unit, audience, channel, market, horizon, and action boundary;
2. proof contract, source and permission inventory, evidence states, contradictions, privacy limits, and unavailable inputs;
3. customer, product, situation, implementation, quote, metric, outcome, condition, and counterevidence ledger;
4. claim, calculation, causality, prevalence, and regulated-risk review;
5. source-approved atomic proof units with exact wording and usage rights;
6. story architecture and requested derivative drafts with source lineage and limitations;
7. approval, anonymization, incentive, disclosure, localization, refresh, withdrawal, archive, and retirement controls;
8. evidence requests, owners, review dates, specialist handoffs, pinned Playbook sources, and approval-ready external actions.

For China work, keep China, language, locale, legal entity, customer, speaker, role, product, price, contract, metric, currency, tax, invoice, claim, quote, logo, screenshot, consent, usage right, translation, channel, platform, content review, identity, privacy, data access, storage, transfer, evidence source, applicable review, and local owner separate. Translation does not transfer customer permission, product applicability, metric meaning, channel rights, privacy notices, provider conditions, or regulated claims. Do not provide legal, medical, financial, tax, accounting, compliance, or provider conclusions.

## External-Action Boundary

This Skill creates and reads local artifacts only. Do not access CRM, sales, support, call, product, analytics, warehouse, billing, finance, contract, email, ad, website, CMS, design, reference, or customer systems; contact customers or employees; request or obtain signatures; create public identities; change claims, quotes, metrics, permissions, reference states, or source records; publish, send, upload, schedule, or deploy cases, testimonials, ads, press, sales, web, social, app, analyst, or localized assets; spend; or claim conversion, win-rate, revenue, or other results without separate task-level authorization and required controls.

## Keep One Output Language

Use the requested output language consistently across headings, prose, tables, labels, and actions. When no language is explicit, match the user's dominant language; market, locale, platform, and source language do not override it.

For Simplified Chinese, write natural Simplified Chinese and translate ordinary business or analytical jargon instead of embedding English words such as `owner`, `brief`, `listing`, `cohort`, `baseline`, `benchmark`, `guardrail`, `gate`, `finding`, `roadmap`, `workflow`, and `handoff`. Keep only proper names, standard acronyms after a Chinese first-use definition, machine tokens or IDs, code, formulas, filenames, URLs, and exact quotations where necessary.

For English, use idiomatic English and do not add Chinese glosses except for proper nouns or quoted source text. Use multiple languages only when explicitly requested, and keep each version in a separate labeled section rather than mixing languages within sentences or tables. Do not alternate languages for emphasis or perceived expertise.

## Completion Gate

Confirm that decision, customer, role, relationship, product, version, situation, alternative, implementation, outcome, metric, calculation, source, quote, paraphrase, translation, logo, screenshot, conditions, counterevidence, incentive, disclosure, consent, rights, channels, markets, duration, approval, privacy, anonymization, causal boundary, formats, lineage, versions, usage locations, freshness, withdrawal, correction, archive, retirement, owners, pinned sources, and external actions are explicit; logo is not use; statement is not prevalence; association is not causality; possession is not permission; anonymization is not name removal; editing does not change meaning; unavailable is not zero; no proof, quote, metric, right, approval, or result was invented; and no external action occurred.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [krillinai](https://github.com/krillinai)
- **Source:** [krillinai/growee-skills](https://github.com/krillinai/growee-skills)
- **License:** MIT
- **Homepage:** www.clawee.ai/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-krillinai-growee-skills-customer-proof-development
- Seller: https://agentstack.voostack.com/s/krillinai
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.