Borrowing it
Nothing to install: this file belongs to saski/arnesto. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saski/arnesto/main/.agents/skills/positioning-canvas/SKILL.mdgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/positioning-canvas)<a href="https://agentmods.dev/skills/saski/arnesto/positioning-canvas"><img src="https://agentmods.dev/badge/skills/saski/arnesto/positioning-canvas.svg" alt="Measured on agentmods" 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.00081 | $0.00672 |
| Opus 5 | $0.00041 | $0.00336 |
| Sonnet 5 | $0.00016 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
positioning-canvas 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 3d 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-canvas — 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Positioning Canvas
What It Is
Positioning defines how your product is the best in the world at delivering some value that a well-defined set of customers care a lot about.
The core insight: Positioning is not messaging. It's not your tagline. It's the fundamental strategic decision about how you win in the market — what you compete against, how you're different, what value only you can deliver, and who cares most about that value.
When positioning is weak:
- Prospects don't understand what you are on first contact
- Sales calls require 3+ meetings before "the light comes on"
- You win deals but customers churn because expectations didn't match reality
- Different teams (sales, marketing, product) tell different stories
When positioning is strong:
- It feels obvious — "of course that's what it is"
- Qualified prospects immediately understand why they should care
- Your differentiated value is clear against alternatives
- Everyone in the company tells the same story
Credit: This framework comes from April Dunford, author of Obviously Awesome and Sales Pitch, who has positioned over 200 B2B tech companies.
When to Use It
Use Positioning Canvas when you need to:
- Define or refine how you compete — who are the real alternatives?
- Articulate differentiated value — why pick you over everything else?
- Identify your best-fit customers — who cares most about your value?
- Choose or validate your market category — what context makes your value obvious?
- Align your team — get sales, marketing, product, and leadership on the same page
- Build a sales pitch — translate positioning into a story that wins deals
- Reposition after market changes — your product evolved, competition shifted, or customers changed
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.
- 3d ago First seen · 68 lines · 81 tokens per session scan A 04639ed4412a
positioning-canvas is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 81 tokens to every session and 672 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to positioning-canvas, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
repo-harness-assessment
Use when evaluating repository agent-readiness, mapping harness roles, choosing the next smallest improvement, or designing and reconciling agent entrypoints such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, or GitHub instructions.
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
validation-harness-design
Use when designing repository validation commands, doctor scripts, test matrices, JSON or JUnit outputs, CI gates, smoke checks, or harness command surfaces.