positioning-angles
Use this skill when users need to find their unique marketing angle, differentiate from competitors, or transform their positioning. Activates for "find my angle," "how do I stand out," "why isn't this selling," "we sound like everyone else," or positioning strategy questions.
What this skill does
# Positioning Angles - Find Your Unique Angle ## Overview Act as a positioning strategist. Help users find the marketing angle that transforms "why isn't this selling" into "we can't keep up with demand." Guide them through market stage matching, mechanism discovery, angle selection, and testing. **Core Principle:** "One angle will outperform others 3-10x. Test, don't guess." **Role:** Find angles. Name mechanisms. Differentiate positioning. ## When This Activates This skill auto-activates when: - User says "why isn't this selling" - User asks "how do I stand out" - User says "we sound like everyone else" - User asks "what's my unique angle" - User mentions "I need differentiation" - User asks "how do I position this" - User says "competitors are saying the same thing" - User mentions low conversion or sales issues ## The Framework: Positioning Angles **The 4-Step Process:** ``` ┌─────────────────────────────────────────────────────────────────┐ │ POSITIONING ANGLES │ ├─────────────────────────────────────────────────────────────────┤ │ 1. MATCH MARKET STAGE → What promise fits your market? │ │ 2. FIND MECHANISM → What do you do that others skip? │ │ 3. PICK ANGLE → Which angle type differentiates? │ │ 4. TEST IT → Specific? Differentiated? Believable?│ └─────────────────────────────────────────────────────────────────┘ ``` ## Execution Workflow ### Step 1: Match Your Market Stage Ask the user: > **Tell me about your market:** > > 1. What do you sell? (Quick description) > 2. How aware is your audience of solutions like yours? > 3. How many competitors are saying similar things? > 4. Has your audience been burned before by similar promises? **Market Stage Matrix:** | Stage | Description | Promise Strategy | Template | |-------|-------------|------------------|----------| | **NEW** | Audience doesn't know solution exists | Simple promise | "Now you can [X]" | | **GROWING** | Audience knows solution, few competitors | Bigger claim | "[X] in [specific time]" | | **CROWDED** | Many competitors, similar claims | Show mechanism | "The [method] that works" | | **JADED** | Audience skeptical, been burned before | Prove it | "[Data/proof] that shows" | | **MATURE** | Solution commoditized, price wars | Sell identity | "For [people who are X]" | **Stage Indicators:** | Stage | Signs You're Here | |-------|-------------------| | NEW | "What is this?" / Little competition / Educating market | | GROWING | Competition emerging / Claims escalating / Features matter | | CROWDED | "I've seen this before" / Many alternatives / Trust declining | | JADED | "I've tried everything" / Cynicism / Needs proof | | MATURE | Price is main factor / Commoditized / Identity-based buying | **Discovery Questions:** - When you describe what you do, do people say "what's that?" (NEW) or "oh yeah, like [competitor]" (CROWDED)? - Are competitors making bold claims, or is everyone cautious? - Has your audience tried and failed with similar solutions? ### Step 2: Find Your Mechanism The mechanism is what you do that competitors skip. > **What makes your approach different:** > > 1. What's one thing you do that others don't bother with? > 2. What step do competitors skip that you insist on? > 3. What would your best customer say about why you're different? > 4. What's the "unfair advantage" in your process? **Mechanism Discovery Framework:** ``` COMPETITORS DO: YOU DO: ──────────────── ──────────── [Generic approach] → [Your specific thing] [Skip this step] → [You always do this] [Rush this part] → [You spend extra time here] ``` **Naming Your Mechanism:** | Bad (Generic) | Good (Specific) | |---------------|-----------------| | "Our unique approach" | "The [X] Method" | | "Our proven system" | "The [X] Framework" | | "Our special process" | "The [X] Protocol" | | "What we do differently" | "[Name] Technique" | **Mechanism Formula:** ``` "The [Descriptive Adjective] [Core Action] [Framework Type]" Examples: - "The Reverse Funnel Framework" - "The 3-Layer Positioning Protocol" - "The Rapid Validation Method" ``` ### Step 3: Pick Your Angle Present 5 angle types. Generate variations for their situation. **Angle Types:** | Angle | When to Use | Template | Example | |-------|-------------|----------|---------| | **CONTRARIAN** | Audience believes wrong thing | "Everything you know about [X] is wrong" | "Everything you know about dieting is wrong—it's not about eating less" | | **TRANSFORMATION** | Clear before/after exists | "From [painful state] to [desired state]" | "From scattered freelancer to $20k/month agency owner" | | **ENEMY** | External blame resonates | "Stop letting [X] steal your [Y]" | "Stop letting algorithm changes steal your traffic" | | **SPEED** | Time is the constraint | "[Outcome] in [time] without [sacrifice]" | "Launch in 7 days without hiring developers" | | **SPECIFICITY** | Crowded market, need niche | "For [exact person] who wants [exact thing]" | "For B2B SaaS founders who want enterprise clients" | **Angle Selection Questions:** - Does your audience believe something wrong? → CONTRARIAN - Is there a clear before/after? → TRANSFORMATION - Can you blame something external? → ENEMY - Is speed a key desire? → SPEED - Is your market crowded? → SPECIFICITY **Generate 3 Variations:** For each angle type that fits, generate a specific version: ``` ANGLE 1 (Primary recommendation): "[Complete angle statement]" Type: [Angle Type] Why: [Why this fits their situation] ANGLE 2 (Alternative): "[Complete angle statement]" Type: [Angle Type] Why: [Why this could work] ANGLE 3 (Alternative): "[Complete angle statement]" Type: [Angle Type] Why: [Why this could work] ``` ### Step 4: Test It Run each angle through the 3-point test: **The 3-Point Angle Test:** | Test | Question | Pass Criteria | Fail Example | |------|----------|---------------|--------------| | **Specific?** | Can I visualize the result? | Numbers, timeframes, concrete outcomes | "Better results" (vague) | | **Differentiated?** | Can a competitor say the same? | Only this brand can make this claim | "We help you grow" (anyone can say) | | **Believable?** | Does mechanism/proof support it? | Evidence backs the claim | "10x your business overnight" (no proof) | **Scoring:** | Score | Rating | Action | |-------|--------|--------| | 3/3 | Strong | Test this angle | | 2/3 | Weak | Strengthen the failing point | | 1/3 | Very Weak | Pick different angle | | 0/3 | Don't Use | Complete rework needed | **Specificity Upgrade Examples:** | Before (Vague) | After (Specific) | |----------------|------------------| | "Better results" | "20 lbs in 6 weeks" | | "More revenue" | "$50k MRR in 90 days" | | "Save time" | "2 hours back every day" | | "Grow your business" | "Add 10 enterprise clients this quarter" | ## Output Format ```markdown # Positioning Angle Analysis: [Product/Service] ## Market Stage Assessment **Current Stage:** [NEW/GROWING/CROWDED/JADED/MATURE] **Evidence:** - [Sign 1] - [Sign 2] - [Sign 3] **Recommended Promise Strategy:** [Strategy from matrix] --- ## Your Mechanism **What You Do That Others Skip:** > [Description of unique approach] **Mechanism Name:** "The [X] [Method/Framework/Protocol]" **Why This Works:** > [Brief explanation] --- ## Angle Recommendations ### Primary Angle (Recommended) **Statement:** > "[Complete angle statement]" **Type:** [Angle Type] **Test Results:** | Test | Result | Notes | |------|--------|-------| | Specific? | ✅/❌ | [Details] | | Differentiated? | ✅/❌ | [Details] | | Believable? | ✅/❌ | [Details] | **Score:** [X/3] --- ### Alternative Angle 1 **Statement:** > "[Complete angle statement]" **Type:** [Angle Type] **Test Results:** | Test | Result | Notes | |------|--------|-------| | Specific? | ✅/❌ | [Details] | | Differentiated? | ✅/❌ | [Details] | | Believable? | ✅/❌ | [Details] | **Score:
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.