buyer-resources
Skill2 starsChanged 29 days agoMITView on GitHub
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.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- account-based-marketingSkill
- acquisition-conversionSkill
- ad-creativeSkill
- analytics-trackingSkill
- aso-auditSkill
- cold-emailSkill
- community-marketingSkill
- competitor-alternativesSkill
- competitor-profilingSkill
- content-strategySkill
- customer-marketingSkill
- customer-researchSkill
- email-sequenceSkill
- eventsSkill
- go-to-market-strategySkill
- icp-and-buyer-personasSkill
- launch-readiness-checkSkill
- launch-strategySkill
- localization-claimsSkill
- market-entry-briefSkill
- market-entry-orchestrationSkill
- marketing-copySkill
- marketing-experimentationSkill
- market-intelligenceSkill
- messaging-consistency-auditSkill
- messaging-frameworkSkill
- objection-intelligenceSkill
- output-quality-checkSkill
- paid-adsSkill
- partner-marketingSkill
- positioning-strategySkill
- pricing-strategySkill
- product-activationSkill
- product-communicationsSkill
- product-marketing-contextSkill
- referral-programSkill
- revopsSkill
- sales-enablementSkill
- search-discoverabilitySkill
- social-contentSkill
- ssot-context-loopSkill
- upgrade-conversionSkill
- website-buyer-journeySkill
- win-loss-intelligenceSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read ../_shared/evidence-gaps.md and ../_shared/ssot-consumption.md.
- Very specific: line 14
Read ../_shared/segment-selection.md when an audience decision is needed.
- Very specific: line 16
Do not edit SSOT. Route proposed canon changes to ssot-context-loop for human review and approval.
- Distinctive: line 20
Downloadable resource: Read downloadable strategy.
- Very specific: line 21
Interactive resource or free tool: Read interactive strategy.
- Distinctive: line 25
Start with the accepted buyer problem and objective, not a desired format.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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. Assess audience fit, promised value, format, value exchange, gating, distribution and nurture progression.
- Interactive resource or free tool: Read interactive strategy. 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.
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
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.