Index of every page on this site: llms.txt
All skills
salikshah avatar

/category-positioning-sop

@7cbc184
Run it yourself

How to turn a thin AI wrapper startup into a category leader. Positioning SOP for AI-native startups. Use when the user mentions category positioning, turning an AI wrapper into a category leader, a positioning SOP, category design, or startup positioning.

  • 2 files
  • 6.8 KB
  • Updated last month
  • GitHub
Use this Skill: https://skilld.dev/gh/salikshah/startup-agent-skills/category-positioning-sop

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈71 tokens for metadata: the name and description. ≈1.3k when used: this file. ≈372 more on demand in 1 file.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈283 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Category Positioning SOP

Intent

Turn a thin AI wrapper startup into a category leader. Most AI startups sound like wrappers over rented models. This SOP shows how to design a category narrative that makes a product the unavoidable answer in its category.

Inputs

  • Product name and description
  • Current positioning (how the company describes itself)
  • Top 3 competitors and their positioning
  • Target customer (who buys, who uses)
  • Unique technical or workflow advantage

Process (SOP)

  1. Run the Wrapper Test and decide whether the product is a wrapper.
  2. Find the constraint outside the model: vertical, infrastructure, security, workflow, or data.
  3. Design the category narrative: enemy, new category, core idea, and proof.
  4. Write the one-liner: target customer, outcome, unique mechanism, proof metric.
  5. Build the proof stack with a receipt for every claim.
  6. Distribute the narrative through the channels where the audience already gathers.

If the product fails two or more Wrapper Test questions, position it as a feature or workflow layer until the constraint is real. When to stop: do not publish a category claim without at least one verifiable receipt.

Step 1: The Wrapper Test

Run the 10-minute test:

  1. Can a technical user get 80% of the output by pasting the core prompt into a general AI model directly? (If yes, it is a wrapper.)
  2. Can a competitor clone the UI in a weekend? (If yes, no moat.)
  3. Does a frontier-model vendor shipping the feature next quarter kill the business? (If yes, no defensibility.)

If the product fails 2+ tests, it is a wrapper. That is OK — most start here.

Step 2: Find the Constraint Outside the Model

Companies that survive pick a narrow surface where they have an unfair edge:

  • Vertical: regulated industries (healthcare, legal, finance)
  • Infrastructure: agent memory, reward models, cold starts, latency
  • Security: securing AI agents
  • Workflow: owning the workflow end to end
  • Data: proprietary data loops, network effects

Step 3: Design the Category Narrative

Answer these questions:

  • What enemy are you against? (e.g., "AI wrappers with broken onboarding")
  • What new category are you creating? (e.g., "DevEx for AI startups")
  • What's the one idea that defines you? (e.g., "Developer adoption is the byproduct, not the product")
  • What proof do you have? (e.g., "1,000 paid customers, $0 ad spend")

Step 4: Write the One-Liner

"I help [target customer] [do outcome] by [unique mechanism]. Proof: [metric]."

Step 5: Build the Proof Stack

Every claim needs a receipt. Typical receipts:

  • Adoption → GitHub stars, package downloads, active users
  • Revenue → closed proposals, customer logos (with permission)
  • Authority → awards, press, original research
  • Content → assets produced, publishing cadence, measured reach

Step 6: Distribute the Narrative

  • X (daily): Technical insights, build logs, positioning teardowns
  • LinkedIn (weekly): Long-form articles, teardown analyses, and operating notes
  • YouTube: Short explainers and demos
  • Website: The hub — product pages, proof, and contact

Outputs

  • Category narrative document
  • One-liner positioning statement
  • Proof stack (receipts for every claim)
  • Distribution plan (X, LinkedIn, YouTube, website)
  • Competitor positioning map

Pre-flight checklist:

  • Wrapper Test completed
  • Constraint outside the model named
  • One-liner includes a proof metric
  • Every claim has a receipt
  • Distribution plan names an owner and cadence

Evidence

Category design is a well-established positioning discipline: name the enemy, define a new category, and attach a proof stack so the category claim is verifiable. The Wrapper Test operationalizes the common "thin wrapper" critique of AI startups.

Examples

Before: "We use AI to help teams work better." — generic, no category, no proof. After: "We make AI agents safe to deploy in regulated healthcare workflows. 3 enterprise design partners, SOC 2 certified." — names the category, states the constraint, attaches a receipt.

The shift: move from describing capabilities to naming a category and proving you own it.

Metrics

  • Category named (Y/N). Target: one category name used consistently for 90 days.
  • One-liner published (Y/N). Target: live on the homepage and in the founder bio.
  • Proof stack complete (Y/N). Target: 3+ receipts.
  • Distribution channels active (count). Target: 2+ channels with weekly cadence.
  • Inbound conversations attributed to positioning (monthly). Target: 3+ per month by day 90.

Anti-Patterns

  • Listing capabilities instead of naming a category — "AI + analytics + automation" is a feature list, not a position
  • Leading with company age or team size instead of the customer outcome
  • Claiming "interdisciplinary" or "full-stack" without specifying the constraint you own
  • Skipping the Wrapper Test — if the product is a wrapper, admit it and fix the constraint before claiming a category

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 7cbc184. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
disable-model-invocation
false
Other metadata
triggers
[
  "category positioning",
  "AI wrapper to category leader",
  "positioning SOP",
  "category design",
  "startup positioning"
]

README badge

README badge for salikshah/startup-agent-skills/category-positioning-sop