mkt-positioning
Skill0 starsChanged 45 days agoMITView on GitHub
Find the angle that makes something sell. Use when launching a product, writing a landing page, crafting an offer, or when marketing feels flat. Searches competitor messaging to map the landscape, loads brand context, then generates 3-5 distinct positioning angles with a recommended pick. Writes chosen angle to brand_context/positioning.md. Optionally seeds an ad testing matrix. Triggers on: "find angles for", "how should I position", "what's the hook", "why isn't this selling", "make this stand out", "differentiate", "USP", "positioning". Foundation skill — run before execution skills that need an angle to write from. Does NOT trigger for voice extraction, audience research, or content writing.
In this repository96 other files it gives its agents.
- AGENTS.mdAGENTS.md
- team_context/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- fin-company-cfoSkill
- fin-invoice-reconciliationSkill
- fin-month-end-reportingSkill
- fin-personal-cfoSkill
- meta-find-skillsSkill
- meta-memory-recallSkill
- meta-memory-writeSkill
- meta-skill-creatorSkill
- meta-skillifySkill
- meta-synthesize-localsSkill
- meta-toolifySkill
- meta-wrap-upSkill
- mkt-ab-testingSkill
- mkt-ad-creativeSkill
- mkt-adsSkill
- mkt-asoSkill
- mkt-brand-voiceSkill
- mkt-churn-preventionSkill
- mkt-cold-emailSkill
- mkt-co-marketingSkill
- mkt-community-marketingSkill
- mkt-content-repurposingSkill
- mkt-copy-editingSkill
- mkt-copywritingSkill
- mkt-croSkill
- mkt-directory-submissionsSkill
- mkt-emailsSkill
- mkt-eventsSkill
- mkt-free-toolsSkill
- mkt-icpSkill
- mkt-influencer-marketingSkill
- mkt-jab-hookSkill
- mkt-launchSkill
- mkt-lead-magnetsSkill
- mkt-marketing-loopsSkill
- mkt-offersSkill
- mkt-onboardingSkill
- mkt-paywallsSkill
- mkt-popupsSkill
- mkt-programmatic-seoSkill
- mkt-prospectingSkill
- mkt-public-relationsSkill
- mkt-referralsSkill
- mkt-sales-enablementSkill
- mkt-schemaSkill
- mkt-signupSkill
- mkt-smsSkill
- mkt-socialSkill
- mkt-ugc-scriptsSkill
- mkt-visual-identitySkill
- ops-analyticsSkill
- ops-attributionSkill
- ops-cronSkill
- ops-ingestSkill
- ops-loopifySkill
- ops-project-managementSkill
- ops-revopsSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 11 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
If it doesn't exist → proceed to Step 1.
- Distinctive: line 50
Not the product. The transformation.
- Distinctive: line 52
Ask: "What does your customer's life look like after using this?
- Distinctive: line 61
Do nothing (live with the problem)
- Distinctive: line 73
Search the web for real competitor messaging.
- Very specific: line 75
Read references/competitive-search.md for the full search process and landscape map format.
- Very specific: line 83
Read references/market-sophistication.md for Schwartz's 5 stages.
- Very specific: line 91
Run the product through multiple angle frameworks.
- Distinctive: line 99
Before presenting, check each angle: specific, differentiated against the landscape map, believable given the available proof, relevant to …
- Distinctive: line 103
Ask: "Which angle resonates?
- Very specific: line 109
After the user selects an angle, write brand_context/positioning.md.
- Very specific: line 110
Read references/positioning-output.md for the exact format.
- Distinctive: line 112
If the file already existed, show what changed and confirm before overwriting.
- Distinctive: line 114
After saving, offer: "Want me to generate a 12-ad testing matrix for this angle?
- Very specific: line 120
Ask: "How did this angle perform once you used it?" Log feedback to context/learnings.md under ## mkt-positioning with date and context.
- Very specific: line 133
If the user flags an issue with the output, add a dated entry under ## Rules in this skill's SKILL.local.md (create it if missing) and log …
- Distinctive: line 139
User can't articulate the transformation: Ask what their best customers say about the product — the transformation is in their words, not …
- Distinctive: line 142
Positioning exists but feels stale: Run a fresh competitive search and compare — the market may have moved.
≈ “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
Positioning
The same product can sell dramatically better with a different angle. Not a different product — just a different way of framing what it already does. This skill finds those angles.
Outcome
brand_context/positioning.md containing: primary positioning angle, competitive landscape summary, market sophistication assessment, and all explored alternatives.
The structured data format is defined in references/positioning-output.md.
Context Needs
| File | Load level | How it shapes this skill |
brand_context/icp.md | Full | Audience segments, pain points, and language patterns inform angle generation |
brand_context/voice-profile.md | Tone only | Ensures angle language matches brand register |
context/learnings.md | ## mkt-positioning section | Apply previous feedback on what converted |
Load if they exist. Proceed without them if not.
Before You Start
Check if brand_context/positioning.md exists.
If it exists → Update mode. Read the file, show the current primary angle and statement, and ask: "Want to refine this with fresh competitive data, or start from scratch?" Refine mode runs a fresh competitive search and suggests adjustments. Start fresh runs the full process below.
If it doesn't exist → proceed to Step 1.
Step 1: Identify the Transformation
Not the product. The transformation. What does the customer's life look like after? What pain disappears? What capability appears?
Ask: "What does your customer's life look like after using this? What changes?"
A fitness program sells "fit into your old jeans." A SaaS tool sells "close your laptop at 5pm." The transformation is the raw material for angles.
Step 2: Map Alternatives
What would customers do if this didn't exist? Not just competitors — all alternatives:
- Do nothing (live with the problem)
- DIY (cobble together a solution)
- Hire someone (consultant, freelancer, agency)
- Buy a different category entirely
- Buy a direct competitor
Each alternative has weaknesses. Those weaknesses become angle opportunities.
Step 3: Competitive Messaging Search
Search the web for real competitor messaging. This grounds angles in current market reality.
Read references/competitive-search.md for the full search process and landscape map format.
Key output: a map showing saturated claims (everyone says it), partially claimed territory, and white space (nobody is talking about it). Angles built on white space outperform echoed claims.
Step 4: Assess Market Sophistication
Read references/market-sophistication.md for Schwartz's 5 stages.
The market stage determines which angle type will work. A new category needs simple announcement. A crowded market needs mechanism explanation. A jaded market needs identity framing.
Step 5: Generate Angles
Run the product through multiple angle frameworks. Read references/angle-frameworks.md for the full set (Contrarian, Unique Mechanism, Transformation, Enemy, Speed/Ease, Specificity, Social Proof, Risk Reversal).
Generate 3-5 distinct options. For each:
- Statement — one sentence positioning
- Psychology — why this works with this audience at this market stage
- Headline direction — how it would sound in copy
- Best for — market conditions and audience segments
Before presenting, check each angle: specific, differentiated against the landscape map, believable given the available proof, relevant to the ICP, and concrete enough to picture as a headline or ad. Sharpen or drop any that fail.
Mark one with a recommendation and explain why it's the strongest fit given their competitive white space and market stage.
Ask: "Which angle resonates? Pick a number, or tell me to combine elements from multiple."
Step 6: Save Output
After the user selects an angle, write brand_context/positioning.md.
Read references/positioning-output.md for the exact format.
If the file already existed, show what changed and confirm before overwriting.
After saving, offer: "Want me to generate a 12-ad testing matrix for this angle? I'll map 4 hooks across 3 formats."
Step 7: Collect Feedback
Ask: "How did this angle perform once you used it?"
Log feedback to context/learnings.md under ## mkt-positioning with date and context.
Rules
Updated automatically when the user flags issues. Read before every run.
Self-Update
If the user flags an issue with the output, add a dated entry under ## Rules in this skill's SKILL.local.md (create it if missing) and log it to context/learnings.md under ## mkt-positioning. Write the general rule the correction implies, not the one-off fix.
Troubleshooting
User can't articulate the transformation: Ask what their best customers say about the product — the transformation is in their words, not the founder's. No competitors found: The product may be category-creating (Stage 1). Lead with simple announcement angles. All angles feel similar: The mechanism isn't clear enough. Go back to Step 1 and dig deeper on what makes their approach different. Positioning exists but feels stale: Run a fresh competitive search and compare — the market may have moved.
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.

