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 agentmods add skills/getcrew44/crew44/positioning-workshopnpx skills add getcrew44/crew44 --skill positioning-workshopgit clone --depth 1 https://github.com/getcrew44/crew44What 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 | $0.00038 | $0.03906 |
| Opus 5 | $0.00019 | $0.01953 |
| Sonnet 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 2d 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.
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.
- 2d ago First seen · 425 lines · 38 tokens per session scan A 8ffbcd672b4a
positioning-workshop is a skill published in the GitHub repository getcrew44/crew44 (359 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 3,906 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
test
Detect the project’s test stack, run the narrowest useful tests, create tests when authorized, and report coverage/gaps honestly.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the…