Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Positioning

ASecurity

Define what a product is, who it is for and why it wins — when asked for messaging, value proposition, "how do we describe this", target audience, competitor differentiation, or naming a category. Do this before writing copy or a deck.

2 stars
0 votes
0 copies
1 views
Added 10/3/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 10/3/2026

$npx -y skills add ivanvp91/TRCode --skill positioning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Positioning?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Positioning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ivanvp91-positioning/badge)](https://www.skillsdirectory.com/skills/ivanvp91-positioning)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: positioning
description: Define what a product is, who it is for and why it wins — when asked for messaging, value proposition, "how do we describe this", target audience, competitor differentiation, or naming a category. Do this before writing copy or a deck.
description_ru: Определить, что за продукт, для кого он и почему выигрывает — когда просят формулировки, ценностное предложение, «как это описать», целевую аудиторию, отличие от конкурентов или название категории. Делается до текстов и презентаций.
triggers: позиционирование, positioning, ценностное предложение, value proposition, оффер, целевая аудитория, target audience, сегмент, segment, конкуренты, competitors, отстройка, differentiation, месседж, messaging
---

# Positioning

## 1. Collect the raw material
- What the product actually does today (read the code/README if it is here — not the roadmap).
- Who already uses it and for what job.
- The alternatives, including the honest ones: a spreadsheet, a script, doing nothing.
- What it is *not* good at.

## 2. Fill the frame
Write each line explicitly:
- **For** [specific segment, narrow enough to recognise themselves]
- **who** [situation and pain, in their words]
- **X is a** [category the buyer already understands]
- **that** [the one capability that matters most]
- **unlike** [the real alternative, named]
- **because** [the structural reason it is better, not an adjective]

If "unlike" and "because" are weak, the problem is the product or the segment, not the wording. Say so.

## 3. Choose the segment deliberately
Narrow beats broad. "For everyone" produces copy that moves no one. Pick the group with the sharpest pain and the shortest path to value; you can widen later. Name what you are giving up by choosing it.

## 4. Rank the differentiators
List every claim, then mark each: **unique** (only we can say it), **shared** (true but competitors say it too), **table stakes** (must have, sells nothing). Lead with unique, mention table stakes only to defuse objections.

## 5. Produce the message hierarchy
- One-liner (≤ 12 words, outcome-first).
- Three pillars, each with a one-sentence proof.
- Objection → answer, for the top three objections.
- Vocabulary: the words to use, and the words to avoid (competitor terms, internal jargon).

## What not to do
- Do not invent a new category unless you can afford to teach it.
- Do not position against a competitor's weakness that they will fix next quarter.
- Do not confuse features with differentiation, or mission with positioning.
- Do not claim a segment you have no evidence for — flag it as a hypothesis to test.

## Answer format
The filled frame, the message hierarchy, and a short "risks" section: which claims need proof, which segment assumptions are untested.

Attribution

ivanvp91ivanvp91
View sourceSee grades on GitHubMore from ivanvp91 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →