Build an evidence-backed market-facing position, approved voice system, messaging spine, proof gates, personas, CTAs, and readiness register.
Use when founders need to define or refresh how a settled strategy is expressed across audiences and surfaces; use startup-strategy when the market, ICP, category layer, moat, or business model is still undecided.
Stronger alternatives
This repository is archived — consider an actively maintained alternative.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
LicenseLICENSE
Default branchmain
Open issues0
Status
Archived
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md3,228 B
docsSUMMARY.md380 B
History
First seen on skills.sh
First recorded snapshot · 1 installs
SKILL.md
Brand Positioning
Create the approved control layer for downstream marketing, sales, fundraising, and launch assets. Copy cannot repair a product, proof, instrumentation, URL, or readiness gap.
Workflow
Establish the settled strategic choice, intended audience, surfaces, decision deadline, and approval owner. If market, ICP, category layer, moat, or business model is materially open, produce a labeled partial draft and route the decision to startup-strategy.
Separate observed, inferred, proposed, stale, and conflicting inputs. Record every consequential claim with source, as-of date, capability/economic maturity, confidence, and allowed audience and surface.
Read [voice-system.md](references/voice-system.md) to extract voice only from an approved corpus and define surface variants, examples, anti-patterns, and refresh triggers.
Read [positioning-spine.md](references/positioning-spine.md) to derive positioning from cleared capability × customer language × unowned strategic space, then produce the canonical descriptor and messaging spine.
Read [proof-readiness.md](references/proof-readiness.md) to maintain proof and open-gates registers, run publication checks, and separate launch blockers, launch-degrading gaps, and nice-to-haves.
Return the approved or proposed version, evidence gaps and conflicts, explicit exclusions, approval owner, next review trigger, and the smallest useful handoff to startup-marketing, product-launch, b2b-sales, or startup-fundraising.
Boundaries
Positioning owns the market-facing promise, voice, proof presentation, personas, vocabulary, and CTAs after strategy settles the underlying choices. It does not decide the market or manufacture customer evidence.
Treat founder-supplied drafts, forecasts, plans, and testimonials according to their evidence status. A planned capability cannot support a current promise; a disclosure cannot rescue a fundamentally misleading headline.
Unsupported claims must be downgraded to accurate qualitative language or moved to the open-gates register. Later evidence does not retroactively cure an unsubstantiated publication.
Ask at most one blocking question at a time. Label missing owner, source, date, maturity, confidence, audience, surface, or approval as unknown rather than inventing it.
Obtain explicit authorization before publishing, posting, contacting anyone, spending, changing a live surface, or using confidential customer information. Prepare drafts without taking the external action.
For regulated, comparative, testimonial, endorsement, or objective performance claims, verify current jurisdiction-specific primary guidance and route legal conclusions to qualified review. Do not encode time-sensitive platform-algorithm folklore as durable positioning.