Agent skill

Positioning Messaging Designer

by swan-gtm in swan-gtm/gtm-skills

Design positioning and messaging frameworks for your company using the Use Case Messaging Canvas and Opposites method.

MITAuto-check passedMarketing & SEO

Install Positioning Messaging Designer

skills CLI
$ npx skills add swan-gtm/gtm-skills --skill positioning-messaging-designer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install swan-gtm/gtm-skills positioning-messaging-designer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/rutger-katz/positioning-messaging-designer .claude/skills/positioning-messaging-designer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
positioning-messaging-designer
GitHub stars
172
Token cost
~5.2k tokens
SKILL.md length
2,735 words
Files
2 (incl. references)
Skills in repo
32
Repo updated
First seen
Licence
MIT

At a glance

Design positioning and messaging frameworks for your company using the Use Case Messaging Canvas and Opposites method.

  • Works in 6 steps: Category: What market do you play in? → Alternative: What do they compare you… → Differentiation: What makes you… → …
  • You need to define your positioning
  • SKILL.md covers When This Skill Activates, The Chain, Part 1: Positioning: The 12… and Part 2: The Use Case Messaging…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Positioning Messaging Designer is an agent skill from swan-gtm/gtm-skills. Design positioning and messaging frameworks for your company using the Use Case Messaging Canvas and Opposites method. Use whenever you need to define your positioning, build a messaging framework, create a Use Case Canvas, or bridge the gap between ICP and copy. Triggers include 'position yourself,' 'messaging framework,' 'Use Case Canvas,' 'how should we position,' 'our messaging is all over the place,' 'we skip straight to copy,' 'Opposites method,' 'Old Way vs New Way,' 'positioning workshop,' 'value prop,'…

Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/positioning-messaging-reference.md`).

It sits in Marketing & SEO, covering Positioning and messaging. It works with LinkedIn. The repository describes itself as: Open, production-grade GTM skills for AI agents. The licence is MIT.

When your agent uses it

  • You need to define your positioning
  • Build a messaging framework
  • Create a Use Case Canvas
  • Bridge the gap between ICP and copy

Example prompts

  • “position yourself,”
  • “messaging framework,”
  • “Use Case Canvas,”
  • “/positioning-messaging-designer”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Category: What market do you play in?
  2. Alternative: What do they compare you to? (Competitors, doing nothing, building in-house)
  3. Differentiation: What makes you meaningfully different?
  4. Capabilities: What can they DO with you that they can't elsewhere?
  5. Benefits: What results do they get?
  6. Features: What powers those capabilities?

What it can do on your machine

Read from SKILL.md and the folder at commit 67abd04. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • neontriforce.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Positioning Messaging Designer loads about 5.2k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 229 tokens; SKILL.md has 2,735 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~229
When it runs · the whole SKILL.md, loaded when a task matches
~5.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~10k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from swan-gtm/gtm-skills at commit 67abd04, republished under its MIT licence (© swan-gtm). 2,735 words, ~5,150 tokens.

Download SKILL.mdSave it as .claude/skills/positioning-messaging-designer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
positioning-messaging-designer
description
Design positioning and messaging frameworks for your company using the Use Case Messaging Canvas and Opposites method. Use whenever you need to define your positioning, build a messaging framework, create a Use Case Canvas, or bridge the gap between ICP and copy. Triggers include 'position yourself,' 'messaging framework,' 'Use Case Canvas,' 'how should we position,' 'our messaging is all over the place,' 'we skip straight to copy,' 'Opposites method,' 'Old Way vs New Way,' 'positioning workshop,' 'value prop,' 'one-liner,' 'elevator pitch,' 'positioning line,' or any situation where you have an ICP but your messaging is missing or inconsistent. BOUNDARY: This skill designs POSITIONING and MESSAGING frameworks. For ICP building (the step BEFORE), see icp-builder. For writing actual LinkedIn copy, see a LinkedIn posting skill. For proposals, see a proposal generator skill.
title
Positioning and messaging designer
category
Positioning

Positioning & Messaging Designer

You are designing positioning and messaging for your company. This is the bridge between knowing WHO to sell to (ICP) and knowing WHAT to say (copy). Most companies skip this step. They go from ICP straight to copy and wonder why everything needs rewriting.

The core insight: you don't invent messaging. You extract it from the contrast between your customer's current reality and what becomes possible. The Use Case Messaging Canvas and the Opposites method make this systematic.


When This Skill Activates

Situation 1: Copy Skip. You have an ICP but went straight to writing copy. Your messaging is inconsistent across channels: LinkedIn says one thing, the website says another, sales pitches a third. The symptom is constant rewriting.

Situation 2: Positioning is vague. You can't articulate what makes your company different in one sentence. "We're an AI-powered platform that helps companies..." is generic, category-stuffed, and says nothing. No clear alternative, no contrast.

Situation 3: Post-ICP work. You just completed ICP building with icp-builder and the next step is translating those insights into a positioning framework and messaging architecture.

Before starting: Confirm you have SPICED data. If you don't have customer interviews or at least deal analysis with pain language, the positioning will be fiction. Go back to ICP work first.


The Chain

This is the sequence. Every step feeds the next:

ICP + SPICED → Positioning → Messaging Framework → Copy (every channel)

Skip a step and everything downstream breaks. This skill covers the middle two.


Part 1: Positioning: The 12 Elements

Positioning answers: "Why should I choose you over the alternative?" It's not a tagline. It's the structure that makes the solution visible in a crowded market.

Primary Elements (answer "Why choose you?")

Work through these six elements for your company. Every one should be grounded in SPICED data, not aspiration:

  1. Category: What market do you play in?
  2. Alternative: What do they compare you to? (Competitors, doing nothing, building in-house)
  3. Differentiation: What makes you meaningfully different?
  4. Capabilities: What can they DO with you that they can't elsewhere?
  5. Benefits: What results do they get?
  6. Features: What powers those capabilities?
Secondary Elements (add specificity)
  1. Personas: Who specifically benefits most?
  2. Use Case: What job are they hiring you for?
  3. Overarching Problem: What big-picture struggle ties it together?
  4. Sub-Problems (1, 2, 3): Specific blockers (these come from SPICED Pain)

For the full element definitions with examples, read references/positioning-messaging-reference.md Section 1.

The Positioning Line

Once the 12 elements are mapped, write ONE repeatable positioning line. Six formulas to choose from:

FormulaStructureBest when...
Problem/Outcome"We help [who] reduce [pain] so they achieve [result]"Main value is solving a costly pain
Job-to-be-Done"When you need to [job], use [us] instead of [old way]"Job is clear, you're the obvious alternative
Category + Competitor"Unlike [alternative], we're [difference]"Competing for budget against a specific rival
Segment/Niche"[Category] built for [niche], not generic [everyone]"You own a specific niche
Primary Value Vector"The most [value] way for [who] to [result]"Differentiator is speed, cost, or simplicity
Strategic Archetype"The [archetype] in [category] for [who] who need [job]"Positioning as a platform, not a tool

Pick ONE. Make it repeatable. Back it with proof. Keep it consistent across all channels.

For full formula details with examples, read references/positioning-messaging-reference.md Section 2.


Part 2: The Use Case Messaging Canvas

The canvas is the core deliverable. Two sides: Old Way (their current reality) and New Way (what becomes possible), connected by a Use Case and Persona.

How to Build It

Step 1: Fill the Left Side First (Their Reality)

This is THEIR world, not your narrative. Use their words from SPICED interviews:

  • Overarching Problem: Big picture struggle, in their words
  • 3 Specific Problems: Pain 1, 2, 3 from SPICED (exact customer language)
  • Limitation of Current Way: What's broken about how they do it now (anti-feature)
  • Current Way: What they actually do today (anti-capability)

If it doesn't come from SPICED data, it's not positioning. It's fiction.

Step 2: Fill the Center (Job & Persona)

  • Use Case: The specific job or outcome being done
  • Persona: Who specifically benefits (name, title, context)

Step 3: Flip Each Row to the Right (The Opposites Method)

Every New Way element is the OPPOSITE of an Old Way element:

  • Problem → Benefit (directly solves the pain)
  • Anti-feature → Product Feature (what was broken → what's now possible)
  • Anti-capability → Capability (what they did manually → what the system does)
  • Overarching Problem → Desired Outcome (the aspirational end state)

The Opposites write the messaging. You don't invent it: you extract it from the contrast.

For the full canvas template and detailed instructions, read references/positioning-messaging-reference.md Sections 3-4.

Pain language enrichment: Reference your own collection of raw customer pain language. The left side of the canvas should sound like real customer quotes: specific, emotional, concrete.


Part 3: From Framework to Copy

The messaging framework is not a document you write once and file. It's the operating system for everything your company says. Three tools working together:

ToolPurposeFeeds into
SPICEDWHAT to say (substance)Use Case Canvas
Use Case CanvasWHERE to put it (structure)Copy outlines
OppositesHOW to say it (contrast)Every headline, email, post

The canvas produces messaging that flows directly into LinkedIn posts (Old Way vs New Way is high-engagement), website copy, sales decks, email sequences, and proposal templates.


Part 4: Validation and Measurement

Post-Launch Measurement Framework

Positioning is not validated by opinion. Test it against real market signals:

Immediate signals (Week 1-2):

  • BDR call-opening rate: Do prospects engage when the new positioning is used? Track by message version.
  • Sales call discovery time: How quickly do prospects "get it"? Target: under 3 minutes to clear understanding. Longer discovery time signals positioning needs tightening.
  • Win/loss analysis: Are you winning against the right competitors? Positioning should make your competitive set clear.

Medium-term signals (Month 1-3):

  • Website conversion lift: Does traffic from the new positioning convert at higher rates? Compare landing pages by message variant.
  • Proposal acceptance: Fewer iterations needed per proposal suggests messaging clarity is working.
  • Competitive win rate: Positioning focused on a clear alternative should lift win rates against that competitor specifically.
  • Sales team adoption: Can reps repeat the positioning naturally? If not, it's too complex.

Leading indicators to track:

  • Call-to-discovery velocity: Time from first touch to meaningful conversation (target: same-day response for inbound, same-call for discovery)
  • Prospect objection patterns: Do objections shift? (New positioning should eliminate old objections, create room for new, more product-focused ones)
  • Customer interview resonance: Does the positioning resonate with existing customers during reference calls or case study interviews?
Measurement Integration with RevOps

The three metrics that matter for RevOps accountability:

  1. Sales efficiency: Deals closing faster with clearer positioning (shorter sales cycle = lower CAC amortization)
  2. Pipeline quality: Deals won against the intended competitor at higher rates (indicating positioning clarity is filtering for right-fit prospects)
  3. AE productivity: Reps need fewer pitch iterations to win (measurable through deal record audit: how many versions of the deck per deal)

Positioning success is indistinguishable from GTM execution efficiency.


LLM-Assisted Positioning (2026)

For rapid iteration and testing, use LLMs to scale positioning validation:

Rapid Variant Generation

Claude or similar LLMs can generate positioning line variants in seconds:

  • Provide the 12 positioning elements (filled in from SPICED)
  • Ask the model to generate 10 positioning lines using each of the 6 formulas
  • BDRs test the top 5 variants in calls within 24 hours
  • Retain the variants with highest call-open or conversion impact
Competitive White-Space Mapping

Use LLM analysis to identify positioning gaps:

  • Feed the model your top 10 competitor positioning lines
  • Ask it to identify white-space (positions competitors are NOT taking)
  • Map your SPICED differentiation against that white-space
  • Result: positioning that is not a direct competitor clone
Messaging Variant Testing

Generate message variants at scale for A/B testing:

  • Provide the Use Case Canvas and a outreach template
  • Ask the LLM to create 3-5 message variants using different problem framings
  • Run variants through outreach or email sequences
  • Measure conversion by variant to identify which problem resonates fastest
Customer Research Synthesis

LLMs can synthesis qualitative research into positioning angles:

  • Load call transcripts or interview notes (anonymized SPICED data)
  • Ask the model to identify recurring phrases, pain patterns, and ideal outcomes
  • Extract direct customer language for the left side of the canvas
  • Reduces manual synthesis time significantly (practice-based)

AI Sales Platform Integration

Positioning connects to AI-driven sales execution through intent signals and deal patterns:

Signal Validation

Modern AI sales platforms (Outreach, Salesloft, Seamless, Chorus) track real-world message resonance:

  • Positioning clarity shows up in first-call discovery speed
  • Chorus (or similar conversation intelligence) can measure how quickly prospects shift from problem exploration to solution discussion when the new positioning is used
  • Compare call outcomes (deal progression rate) by positioning variant if running parallel approaches
  • Outreach and Salesloft sequences can measure open and reply rates by message version; clearer positioning lifts engagement
Win/Loss Pattern Recognition

AI platforms can identify if positioning is working in real deals:

  • Chorus and Salesloft can flag deals where the correct competitor is mentioned vs. wrong competitors
  • Winning deals should reference the intended competitor; losing deals against the wrong competitor indicate positioning miss
  • Use this feedback to refine the alternative your positioning defines
Post-Deal Feedback Loop

Use deal data to validate positioning was the reason for the win:

  • In win calls with new customers, play back their initial objection from the discovery call
  • Ask them why it shifted; if the answer aligns with your positioning, the framework is working
  • Likewise for losses: position misses will show up as "we didn't realize you did X" or "we thought you were more like Y"

Delivery Formats

Within a 90-day program (full build): Run the weekly GTM sequence: Tuesday ICP, Wednesday Positioning, Thursday Messaging. Iterate over 2-3 weeks. Canvas becomes the living source of truth.

As a standalone positioning workshop: Pre-gather SPICED data. Work through 12 elements and one positioning line in the morning. Build the canvas in the afternoon. You'll have a complete messaging framework to deploy.

As follow-on to ICP work: Natural handoff from icp-builder. SPICED data from the ICP process feeds directly into the left side of the canvas.

For the weekly GTM sequence (Tuesday/Wednesday/Thursday workflow), read references/positioning-messaging-reference.md Section 6.


Show full SKILL.md (1,049 more words)Show less

Framework Additions

Radical Clarity in Noisy Markets

The 30-Second Clarity Test: if a stranger can't say who you are after 30 seconds, the positioning has failed. Use this as a validation gate before finalizing any positioning work.

How to apply:

  1. Read the positioning line to someone unfamiliar with the company
  2. After 30 seconds, ask them to repeat back what the company does and for whom
  3. If they can't → the positioning needs more iteration
  4. If they can → test with 5 more people to confirm

Time-to-aha as diagnostic metric:

  • Before-state to diagnose: 20 minutes for customers to get the aha moment
  • Target: much faster (ideally within 30 seconds of reading/hearing the positioning)
  • Track this during sales calls: how long before the prospect "gets it"?
Iterative Refinement Process

Positioning is not a one-shot exercise. Five pitch decks in six months is a normal iteration count for a team doing it properly.

Validation velocity:

  • Test messaging with BDRs doing 400 calls/day = real-world message validation at speed
  • Run past existing customers (pricing complexity is the classic thing they surface first)
  • Outside consultants (mixed results: internal iteration often more effective)
  • Real-time positioning workshops with the sales team

Implication for Use Case Canvas: After completing the Opposites method and Canvas, don't treat it as finished. Build a 30-day validation sprint:

  1. Week 1: BDR testing (volume calls using new messaging)
  2. Week 2: AE testing (discovery calls using new framing)
  3. Week 3: Customer validation (existing customers react to new positioning)
  4. Week 4: Iterate and lock: or start another cycle
Three-Priority Clarity

An organizational messaging clarity test: can everyone in the org repeat the three things they're doing this quarter?

If they can't: The messaging is too complex, there are too many priorities, or communication is broken.

Use in positioning work: After finalizing positioning, test whether the sales team can articulate the top 3 value propositions without notes. If not, simplify further.

Buyer journey context: B2B buyers spend two-thirds of any buying journey gathering, processing, and de-conflicting information (Gartner, August 2018, "Gartner Says B2B Buyers Want More Simplicity in Accessing the Right Information"). Your positioning either reduces that work or adds to it.


Part 5: Sales Enablement and Rollout

Positioning is only useful if the sales team uses it consistently. Rolling out across a team of 10-100 people requires intentional change management:

Readiness Check (Before Rollout)

Before announcing positioning to sales, verify the sales leadership actually believes it:

  • Sales leader alignment: The VP/Director of Sales should be able to repeat the positioning line without notes. If not, they won't enforce it.
  • Competitive reality check: Play back positioning against recent lost deals. Do reps think this positioning would have changed the outcome? If not, positioning needs refining or adoption is false.
  • Ease-of-use test: Can a rep use the positioning in a discovery call without sounding scripted? If it feels unnatural, sales will ignore it.
Structured Rollout

Week 1: Positioning Workshop

  • Full team call (sales, success, marketing, product)
  • Present the 12 elements and the chosen positioning line
  • Show the Use Case Canvas and explain the Opposites method
  • Play a call recording where the old messaging was confused; replay the same call scenario using new positioning
  • Purpose: Build belief that positioning is better

Week 2-3: Enablement

  • All messaging artifacts (positioning line, elevator pitches, email templates, deck slides, LinkedIn version) in Slack or sales wiki
  • Do 3 breakout practices: (1) cold discovery call, (2) warm inbound handling, (3) objection handling using positioning
  • Measure: Can reps run a mock discovery call using the positioning? Record and review 3 calls

Week 4: Soft rollout

  • AE-led calls (not BDR) use new positioning with prospects already in the deal
  • Track call progression: Are prospects reaching deeper stages faster?
  • Collect AE feedback: What works? What's confusing?
  • Iterate on messaging for one more week based on feedback

Week 5+: Full rollout

  • All outbound and discovery calls use new positioning
  • BDR messaging aligns with AE positioning
  • Add to pipeline qualification criteria: "Is this prospect aware of the alternative we're positioning against?"
Measuring Adoption

Three simple metrics:

  1. Message consistency: Pull 10 random call recordings. Do reps mention the core positioning? (Target: 8/10 minimum)
  2. Time-to-aha: Track discovery call recordings. When does the prospect shift from problem exploration to solution interest? (Target: within 3 minutes of the positioning frame)
  3. Objection shift: Do objections change? Positioning should eliminate old objections ("Aren't you like competitor X?") and create room for product objections ("Does it work with Salesforce?"). Track by keyword in deal records and call notes.
Handling Pushback

"I don't think this positioning works."

  • Ask which specific competitor or deal it didn't work on
  • Look at the call recording together
  • Most likely: positioning was right, but the rep didn't lead with it (AE didn't position in opening)
  • Solution: more practice, not new positioning

"Our customers don't care about this alternative."

  • They might not yet
  • Positioning's job is not to reflect what customers already believe; it's to frame the decision in your favour
  • Play back the SPICED interviews that led to this alternative
  • If still unconvinced, run a small test with 5 prospects and measure call progression

Common Mistakes to Flag

When building positioning, watch for these patterns:

  1. Writing positioning before SPICED: Guessing instead of listening. Go back to customer interviews first.
  2. Filling the right side before the left: Their narrative overwrites customer reality. Always start with the Old Way.
  3. Using "nice" words instead of customer words: Messaging won't resonate. Use the exact language from interviews.
  4. Forgetting the Opposites: New Way doesn't clearly contrast with Old Way. Every right-side element should be a direct flip.
  5. Creating a document instead of a system: The canvas should be a living reference that everyone uses, not a slide deck that collects dust.

Reference Files

FileWhen to readWhat's inside
references/positioning-messaging-reference.mdAlways: the full methodology12 positioning elements, 6 positioning formulas, Use Case Canvas structure, Opposites method, weekly GTM sequence, blank canvas template
  • icp-builder: The step BEFORE this skill: builds, validates, and expands the ICP that feeds positioning
  • sales-methodology: Discovery calls produce SPICED data that feeds the canvas
  • marketing-operations: Uses messaging framework outputs for campaign execution

Cross-References

  • icp-builder: Input: the ICP and SPICED data that feeds positioning
  • gtm-planning: Positioning line feeds into GTM collateral and territory messaging

Built by Neon Triforce

© swan-gtm, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/rutger-katz/positioning-messaging-designer of swan-gtm/gtm-skills.

  • SKILL.md
  • references/positioning-messaging-reference.md

Open the folder on GitHubat commit 67abd04

Compare with similar skills

Positioning Messaging Designer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Positioning Messaging Designer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Positioning Messaging Designer this skillswan-gtm/gtm-skills172—~5.2kAutomated safety check: PassMIT
Marketing OsYuzzyuk/marketing-os540—~2.5kAutomated safety check: PassMIT
Content Idea GeneratorBrianRWagner/ai-marketing-claude-code-skills441—~1.7kAutomated safety check: PassNone
LinkedIn Authority BuilderBrianRWagner/ai-marketing-claude-code-skills441—~1.9kAutomated safety check: PassNone
B2b Brand Marketingarnabbagxd/Brand-building-skills729—~2.4kAutomated safety check: PassMIT
Running MarketingGTM-Strategist/gtm-strategist-skills264—~7.8kAutomated safety check: PassMIT

Similar skills

  • Marketing Os

    Yuzzyuk/marketing-os

    A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.

    540 GitHub stars~2.5k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Content Idea Generator

    BrianRWagner/ai-marketing-claude-code-skills

    Produces content ideas for LinkedIn, X, newsletters or short video from your positioning statement, in quick, standard or deep planning modes.

    441 GitHub stars~1.7k tokensUpdated 6 mo ago
    Marketing & SEOAuto-check passed
  • LinkedIn Authority Builder

    BrianRWagner/ai-marketing-claude-code-skills

    Builds a LinkedIn thought-leadership content system, from positioning check and content pillars to formats and posting rhythm, in quick, standard or deep modes.

    441 GitHub stars~1.9k tokensUpdated 6 mo ago
    Marketing & SEOAuto-check passed
  • B2b Brand Marketing

    arnabbagxd/Brand-building-skills

    Build and execute brand marketing strategy for B2B companies — thought leadership, ABM brand layer, trust signals, LinkedIn presence, long sales cycle brand touchpoints, and enterprise credibility.

    729 GitHub stars~2.4k tokensUpdated 4 mo ago
    Marketing & SEOAuto-check passed
  • Running Marketing

    GTM-Strategist/gtm-strategist-skills

    A skill your agent uses when the user wants to build an ongoing marketing engine, create a content strategy, set up social media publishing, plan influencer partnerships, or run email and paid ad…

    264 GitHub stars~7.8k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed
  • Competitor Intel

    gooseworks-ai/goose-skills

    Competitor intelligence system. An agent skill from gooseworks-ai/goose-skills.

    1.2k GitHub starsUsed in 1 repo~1.8k tokens
    Marketing & SEOAuto-check passed

More from swan-gtm/gtm-skills

All 32 skills in this repo
  • Revops Revenue Planning

    swan-gtm/gtm-skills

    Annual and quarterly revenue plan construction, top-down vs bottoms-up reconciliation, plan versioning, stretch goal handling, and FP&A-RevOps collaboration for B2B revenue teams.

    172 GitHub stars~7.2k tokensUpdated 3 days ago
    Auto-check passed
  • AI Personalization Prompts

    swan-gtm/gtm-skills

    A skill your agent uses when setting up AI-powered personalization, building Clay or lemlist workflows, or automating prospect research — 6 AI personalization prompts (lemlist style) plus 2 email…

    172 GitHub stars~653 tokensUpdated 3 days ago
    Auto-check passed
  • Audience Icp Filter

    swan-gtm/gtm-skills

    A skill your agent uses when a list of people already exists and someone needs to know who on it is worth contacting — event or webinar attendees, registrants, a prospecting export, a CRM segment, a…

    172 GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed
  • Brand Mention Monitor

    swan-gtm/gtm-skills

    A skill your agent uses when you need to know what people are saying about a brand across the web and social — "monitor brand mentions", "what are people saying about [brand] this week", "run a…

    172 GitHub stars~2.1k tokensUpdated 3 days ago
    Auto-check passed
  • Bridge Before Cold

    swan-gtm/gtm-skills

    Use this skill before staging a prospect and before drafting any first touch, when a segment has gone silent, and when deciding whether an account is genuinely cold.

    172 GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check passed
  • Champion Move Detection

    swan-gtm/gtm-skills

    Use this skill on a monthly cadence to detect champions and heavy users of your paying customers who changed jobs, verify the move against live LinkedIn data, score the new company, and surface…

    172 GitHub stars~5k tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Positioning Messaging Designer

What does Positioning Messaging Designer do?

Design positioning and messaging frameworks for your company using the Use Case Messaging Canvas and Opposites method. Positioning Messaging Designer is an agent skill from swan-gtm/gtm-skills. Design positioning and messaging frameworks for your company using the Use Case Messaging Canvas and Opposites method.

When should I use Positioning Messaging Designer?

Positioning Messaging Designer fits situations like: you need to define your positioning; build a messaging framework; create a Use Case Canvas; bridge the gap between ICP and copy.

How do I install Positioning Messaging Designer in Claude Code?

Run `npx skills add swan-gtm/gtm-skills --skill positioning-messaging-designer -a claude-code`. Or copy the skill folder (skills/rutger-katz/positioning-messaging-designer in swan-gtm/gtm-skills) into .claude/skills/positioning-messaging-designer in your project. Claude Code loads it when a task matches its description.

How do I install Positioning Messaging Designer in Codex?

Run `npx skills add swan-gtm/gtm-skills --skill positioning-messaging-designer -a codex`. Or copy the skill folder (skills/rutger-katz/positioning-messaging-designer in swan-gtm/gtm-skills) into .agents/skills/positioning-messaging-designer in your project. Codex loads it when a task matches its description.

Can I use Positioning Messaging Designer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add swan-gtm/gtm-skills --skill positioning-messaging-designer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/positioning-messaging-designer, .gemini/skills/positioning-messaging-designer, .github/skills/positioning-messaging-designer and .opencode/skills/positioning-messaging-designer in your project.

What does Positioning Messaging Designer need to run?

SKILL.md names no scripts, command-line tools or credentials: Positioning Messaging Designer is instructions for the agent only.

Does Positioning Messaging Designer access the network?

SKILL.md names 1 domain. As links in the text: neontriforce.com. This is read from the text; nothing was executed.

Is Positioning Messaging Designer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Positioning Messaging Designer use?

Positioning Messaging Designer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Positioning Messaging Designer use?

About 5.2k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5k tokens, read only when the agent opens those files.

What are the alternatives to Positioning Messaging Designer?

Skills that share tags, products or a category with Positioning Messaging Designer: Marketing Os (Yuzzyuk/marketing-os, 540 stars), Content Idea Generator (BrianRWagner/ai-marketing-claude-code-skills, 441 stars), LinkedIn Authority Builder (BrianRWagner/ai-marketing-claude-code-skills, 441 stars) and B2b Brand Marketing (arnabbagxd/Brand-building-skills, 729 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Positioning Messaging Designer?

swan-gtm (a GitHub organization) maintains it in swan-gtm/gtm-skills, which has 172 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 8, 2026.

Source: swan-gtm/gtm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.