Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add The-Utopia-Studio/skills --skill positioning-workshopgit clone --depth 1 https://github.com/The-Utopia-Studio/skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/the-utopia-studio/skills/positioning-workshop)<a href="https://agentmods.dev/skills/the-utopia-studio/skills/positioning-workshop"><img src="https://agentmods.dev/badge/skills/the-utopia-studio/skills/positioning-workshop/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/the-utopia-studio/skills/positioning-workshop"><img src="https://agentmods.dev/badge/skills/the-utopia-studio/skills/positioning-workshop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.03906 |
| Opus 5.5 | $0.00015 | $0.01562 |
| Sonnet 5.5 | $0.00008 | $0.00781 |
| Haiku 4.5 | $0.00004 | $0.00391 |
Grade A, and why
positioning-workshop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to positioning-workshop — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Guide product managers through discovering and articulating product positioning by asking adaptive questions about target customers, unmet needs, product category, benefits, and competitive differentiation. Use this to align stakeholders on strategic positioning before writing PRDs, launch plans, or marketing materials—ensuring you've made deliberate choices about who you serve, what need you address, and how you differ from alternatives.
This is not a brainstorming session—it's a structured discovery process that outputs a Geoffrey Moore positioning statement backed by evidence and strategic choices.
Key Concepts
The Positioning Workshop Flow
An interactive discovery process that:
- Gathers product context (marketing materials, competitor intel)
- Identifies target customer segment through questioning
- Uncovers underserved needs via Jobs-to-be-Done lens
- Defines product category and benefits
- Establishes competitive differentiation
- Outputs a complete positioning statement (uses
positioning-statement.md)
Why This Works
- Structured discovery: Prevents "positioning by committee" (too vague)
- Evidence-based: Uses real marketing materials, customer feedback, competitive intel
- Adaptive: Questions adjust based on B2B vs. B2C, new product vs. repositioning, etc.
- Actionable output: Generates a Geoffrey Moore positioning statement ready for stakeholder review
Anti-Patterns (What This Is NOT)
- Not a tagline generator: Positioning ≠ marketing copy
- Not feature-first: Starts with customer problems, not product capabilities
- Not consensus-driven: Forces hard choices (can't be "for everyone")
When to Use This
- Defining positioning for a new product
- Repositioning an existing product (pivot, market shift)
- Aligning stakeholders on product strategy
- Preparing for launch or major release
- Before writing positioning-dependent artifacts (PRD, press release, sales deck)
When NOT to Use This
- Before customer research (positioning requires validated insights)
- For internal tools with captive users (no market positioning needed)
- When positioning is already clear and validated
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 425 lines · 38 tokens per session scan A 8ffbcd672b4a
positioning-workshop is a skill published in the GitHub repository The-Utopia-Studio/skills (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 3,906 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to positioning-workshop, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
github
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending,"…
xml-sitemap
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate…
robots-txt
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine…
google-ads
When the user wants to set up, optimize, or manage Google Ads campaigns. Also use when the user mentions "Google Ads," "Google Search Ads," "PPC," "SEM," "PMF testing with ads," "test product-market fit," "Responsive Search Ads," "RSA," "Performance Max," "Quality Score," "keyword bidding," or "Google Display/YouTube…
content-strategy
When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic…
canonical-tag
When the user wants to configure canonical URLs, fix duplicate content, or consolidate URL signals. Also use when the user mentions "canonical," "canonical URL," "duplicate content," "duplicate content fix," "preferred URL," or "URL consolidation." For GSC duplicates, use google-search-console.