buyer-resources · v2.0.0 · 2026-09-30 · sha256 24adb14cec64ad16

buyer-resources v2.0.0A

Immutable. This exact content never changes and is served at /api/v1/blob/24adb14cec64ad16.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_q3v7bszcqdazj7t2/24adb14cec64ad167dfa3256ab671b58eecfdfadaa885d996d51f4a8d9c69b91.json

Then /plugin install buyer-resources@markdownregistry-q3v7bszcqdazj7t2 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: buyer-resources
description: "Evaluate downloadable and interactive buyer resources, lead magnets and free tools for buyer value, qualified acquisition and product progression. Use for gating, ungated utility, resource investment, build/buy/embed decisions and engineering briefs."
metadata:
  version: 2.0.0
---

# Buyer Resources

## Approved context and evidence

Read `../_shared/evidence-gaps.md` and `../_shared/ssot-consumption.md`.
Load only relevant approved manifest context and record sources in Inputs and assumptions.
Read `../_shared/segment-selection.md` when an audience decision is needed; inherit accepted segments and ICP.
Separate sources, interpretation, and proposals. Missing evidence remains Assumed or Gap.
Do not edit SSOT. Route proposed canon changes to `ssot-context-loop` for human review and approval.

## Modes

- **Downloadable resource:** Read [downloadable strategy](references/downloadable.md). Assess audience fit, promised value, format, value exchange, gating, distribution and nurture progression.
- **Interactive resource or free tool:** Read [interactive strategy](references/interactive.md). Assess utility, feasibility, build/buy/embed, data needs, ungated value, investment case and maintenance economics.

## Workflow and outputs

Start with the accepted buyer problem and objective, not a desired format. Compare resource options, including no build. State assumptions about usage, acquisition cost, qualified demand and ongoing ownership; do not fabricate ROI.
Decide gating versus ungated access from buyer value, friction, consent, distribution and progression. Separate resource success from product activation.
Deliver Inputs and assumptions; buyer need; resource concept and unique value; investment/maintenance case; feasibility and risks; gating and consent decision; distribution brief; product progression; measurement and stop/review conditions; owner handoffs; ranked Evidence gaps.
Engineering owns building, security, data access and maintenance of tools. Brief scope, acceptance criteria, data provenance and support owner. Content and final copy route to `content-strategy` and `marketing-copy`; capture and nurture to `acquisition-conversion` and `email-sequence`; search opportunity to `search-discoverability`; paid distribution to `paid-ads`.

## Related skills

`content-strategy`, `marketing-copy`, `acquisition-conversion`, `email-sequence`, `search-discoverability`, `paid-ads`, `product-activation`, `analytics-tracking`.