marketing-positioning-tests
Skill0 starsChanged 41 days agoMITView on GitHub
Use when prospects misunderstand a product, messaging attracts poor-fit buyers, or a positioning or landing-page claim needs evidence before launch.
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- postgres-locking-joinsSkill
- ai-bug-patternsSkill
- compressed-ndjson-boundariesSkill
- http-resume-integritySkill
- linux-io-latency-triageSkill
- macos-disk-space-recoverySkill
- minimal-sufficient-evidenceSkill
- modularize-large-filesSkill
- patch-reproducer-validitySkill
- prompt-cache-boundariesSkill
- proton-drive-selective-backupSkill
- transactional-outbox-deliverySkill
- conventional-commitsSkill
- git-advanced-mergingSkill
- git-bisect-forensicsSkill
- git-data-recoverySkill
- git-hooksSkill
- git-rerereSkill
- git-reset-mechanicsSkill
- git-revisions-syntaxSkill
- git-rewriting-historySkill
- git-submodulesSkill
- git-worktreesSkill
- github-ssh-keysSkill
- npm-publish-ci-pitfallsSkill
- sapling-stacked-pr-workflowSkill
- go-concurrency-patternsSkill
- go-data-idiomsSkill
- go-error-handlingSkill
- go-interfaces-embeddingSkill
- go-pprof-profilingSkill
- marketing-funnel-diagnosisSkill
- marketing-geo-experimentsSkill
- marketing-incrementalitySkill
- python-descriptors-mroSkill
- python-logging-cookbookSkill
- python-scaling-regression-testsSkill
- python-unicode-gotchasSkill
- rust-compile-time-invariantsSkill
- rust-deterministic-concurrency-testsSkill
- rust-error-identity-boundariesSkill
- rust-regex-search-contractsSkill
- rust-runtime-bug-classesSkill
- rust-tokio-actor-deliverySkill
- rust-tokio-cancellation-safetySkill
- sales-discovery-qualificationSkill
- sales-mutual-action-plansSkill
- sales-pipeline-forecast-calibrationSkill
- sales-value-negotiationSkill
- ai-triage-evaluationSkill
- container-image-patchingSkill
- dependency-artifact-integritySkill
- dnssec-sentinel-diagnosticsSkill
- iam-policy-change-replaySkill
- rbvm-applicabilitySkill
- rbvm-asset-evidenceSkill
- rbvm-guarded-remediationSkill
- rbvm-priority-decisionsSkill
- rbvm-risk-exceptionsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Ask buyers to paraphrase the product, intended buyer, outcome, and difference.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Marketing Positioning Tests
Buyer alternatives determine differentiators; differentiators enable value; value identifies best-fit buyers; category supplies the comparison frame. Copy expresses this dependency chain.
Evidence before wording
Build a claim ledger from interviews, lost deals, and product evidence. Separate facts from assumptions; record source, date, customer context, and counterevidence. Missing evidence requires research, not invented quotes.
| Decision | Evidence required |
| Alternative | What buyers actually use or shortlist, including manual work |
| Differentiator | Capability demonstrably absent or weaker in that alternative |
| Value | Customer outcome enabled by that capability |
| Best-fit segment | Observable circumstances making that outcome important |
| Category | Familiar frame whose expectations the product can satisfy |
Feature comparisons may not resolve migration costs or uncertainty about making the wrong purchase.
Testable recipe
- Draft two genuinely different positioning hypotheses. Keep price, offer, and visuals stable when testing wording.
- Recruit relevant buyers by problem and purchase context. Show each version without explanation; counterbalance presentation order when people see both.
- Ask buyers to paraphrase the product, intended buyer, outcome, and difference. Ask which claim needs proof and what prevents consideration, not which slogan they like.
- Record comprehension errors, expectations, relevance, and credibility separately. Preserve disconfirming responses rather than creating one preference score.
- Revise the weakest link. Treat qualitative results as diagnostic; validate any claimed conversion lift with an appropriately designed experiment and downstream quality metric.
Example hypothesis: “Release approvals for distributed engineering teams” needs evidence that cross-time-zone handoffs matter and that asynchronous approval reduces them. “Save ten hours weekly” remains unusable until substantiated.
Sources and scope
- Dunford: positioning components: practitioner framework, especially B2B; not causal proof of demand.
- CXL: clarity testing: comprehension diagnostics; short exposure cannot establish purchase behavior.
Pitfalls
- Competitors found online may never enter buyers' consideration sets.
- A new category adds an education burden; novelty alone is not differentiation.
- Friendly existing customers can hide acquisition-stage confusion.
- Preference scores do not establish lift, and stronger wording cannot repair unsupported claims.
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.

