Agent skill
positioning
Generate positioning systems and messaging frameworks — full visual HTML positioning documents, messaging frameworks, matrices, elevator pitches, positioning statements, narrative arcs, and value prop hierarchies.
Filed under Positioning and messaging.
From octavehq/lfgtm · 27 skill entries · 11 · pushed 2026-09-21
What it does when it runs
Generate positioning systems and messaging frameworks — full visual HTML positioning documents, messaging frameworks, matrices, elevator pitches, positioning statements, narrative arcs, and value prop hierarchies. Use when user says "positioning system", "positioning exercise", "message framework", "messaging framework", "positioning anchors", "positioning document", "visual messaging framework", "elevator pitch", "messaging matrix", "narrative arc", "positioning statement", "value prop hierarchy", "build messaging", or asks for a comprehensive positioning or messaging deliverable.
Automated analysis of the skill and the 10 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- fonts.googleapis.com
- fonts.gstatic.com
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/octavehq/lfgtm.git /tmp/lfgtm git -C /tmp/lfgtm sparse-checkout set "skills/positioning" mkdir -p ~/.claude/skills/positioning cp -R "/tmp/lfgtm/skills/positioning/." ~/.claude/skills/positioning/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 27 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add octavehq/lfgtm /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from octavehq/lfgtm/blob/6facb2c00d93c48e29a370d3d93d52e4380f3b45/skills/positioning/SKILL.md, which is licensed MIT (repository). 365 words, 5 headings.
/octave:positioning - Positioning & Messaging System
Run the task
Read the task method before selecting context, claims, or output. It is the execution method for this skill. Supporting templates supply structure and styling; populate them from the task method and current evidence, not their illustrative figures or assertions.
Full system is the default when no focus is supplied. Support focused persona, messaging, homepage, or other requested lenses from the same strategy rows. Use supplied style or the inherited brand; ask only about unresolved choices. A narrow edit does not authorize rewriting every cell.
Use GTM context for strategic tasks and evidence and inputs for material claims and missing facts. A narrow list/get or a render-only handoff does not require unrelated research. Read host runtime for available tools, portable resource paths, routing, and review fallback.
Resolve current tool schemas before execution; use returned IDs and pagination. Inventory rows locate records; hydrate selected entities/resources before relying on their contents. Reuse supplied or inherited context and authorization. Ask grouped questions only for material unresolved inputs, continue independent work, incorporate replies, and recheck affected output.
Usage
/octave:positioning [mode] [--product <name>] [--persona <name>] [--competitor <name>] [--style <preset>]
References by task
- elevator pitches
- html scaffold
- messaging framework
- messaging matrix
- narrative arc
- positioning statement
- section layouts
- section templates
- value prop hierarchy
Read only the reference for the selected mode, then the format/layout references when rendering. Do not repeat intake or change approved claims when routing to a renderer.
Delivery and changes
Apply output readiness to text and artifacts. HTML also uses the review protocol and the matching format checks. A working preview can be shared with its status; unrun checks are NOT RUN. Reviewers return findings on an immutable version; one author applies edits and rechecks the final version.
For visual output, inherit the selected sender/workspace brand through brand kit usage; honor an explicit override and avoid repeated brand extraction. Public hosting requires the approved audience and publish manifest, followed by URL/access/link verification.
For comparisons, trends or rates, use the analytics contract. Only requested persistence loads workspace mutations; report changes as applied only after scoped readback.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- positioning-basics by BrianRWagner · 422
- positioning-and-story by AIDevGTM · 298
- crafting-positioning by GTM-Strategist · 259
- competitive-positioning by louisblythe · 159
- brand-messaging-and-positioning by manojbajaj95 · 101
- positioning-icp by chadboyda · 77
- positioning-map by pmalliance · 69
- portfolio-positioning by realjaymes · 63
Need help setting it up?
This page tells you what positioning does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.