Startup Design
ferdinandobons/startup-skill
Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.
A skill your agent uses when you need to compare supplied competitor messaging with your approved product facts and find a credible point of difference.
Install Competitor Positioning
$ npx skills add Ootto-AI/claude-content-skills --skill competitor-positioning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ootto-AI/claude-content-skills competitor-positioning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/competitor-positioning .claude/skills/competitor-positioning && rm -rf skills-srcUse ~/.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/
Install the "competitor-positioning" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/competitor-positioning into .claude/skills/competitor-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-positioning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/competitor-positioningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Ootto-AI/claude-content-skills --skill competitor-positioning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ootto-AI/claude-content-skills competitor-positioning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/competitor-positioning .agents/skills/competitor-positioning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "competitor-positioning" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/competitor-positioning into .agents/skills/competitor-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-positioning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ootto-AI/claude-content-skills --skill competitor-positioning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ootto-AI/claude-content-skills competitor-positioning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/competitor-positioning .cursor/skills/competitor-positioning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "competitor-positioning" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/competitor-positioning into .cursor/skills/competitor-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-positioning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Ootto-AI/claude-content-skills.git --path skills/competitor-positioning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Ootto-AI/claude-content-skills --skill competitor-positioning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ootto-AI/claude-content-skills competitor-positioning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/competitor-positioning .gemini/skills/competitor-positioning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "competitor-positioning" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/competitor-positioning into .gemini/skills/competitor-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-positioning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Ootto-AI/claude-content-skills competitor-positioningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Ootto-AI/claude-content-skills --skill competitor-positioning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/competitor-positioning .github/skills/competitor-positioning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "competitor-positioning" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/competitor-positioning into .github/skills/competitor-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-positioning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ootto-AI/claude-content-skills --skill competitor-positioning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ootto-AI/claude-content-skills competitor-positioning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/competitor-positioning .opencode/skills/competitor-positioning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "competitor-positioning" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/competitor-positioning into .opencode/skills/competitor-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-positioning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
competitor-positioning- GitHub stars
- 122
- Token cost
- ~825 tokens
- SKILL.md length
- 384 words
- Files
- 1
- Skills in repo
- 52
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when you need to compare supplied competitor messaging with your approved product facts and find a credible point of difference.
- Works in 4 steps: Define the comparison question → Separate message from capability → Compare against our real evidence → …
- You need to compare supplied competitor messaging with your approved product facts and find a credible point of difference
- SKILL.md covers 1. Define the comparison…, 2. Separate message from…, 3. Compare against our real… and 4. Produce positioning choices…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Competitor Positioning is an agent skill from Ootto-AI/claude-content-skills. Use when you need to compare supplied competitor messaging with your approved product facts and find a credible point of difference. Trigger phrases include "how are competitors positioned?", "compare our message to theirs", "where are we different?", "audit these competitor pages", and "what should we not say?". Do not use this to make unverified claims about competitors, copy their language, or write the final brand message in isolation; use agent-reach to collect public sources, positioning-audit to decide…
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Positioning and messaging and Competitor analysis. The repository describes itself as: Free, copy-paste Claude skills that run your content growth factory — turn ideas + your NotebookLM memory into scroll-stopping Instagram reels. By Ootto. The licence is MIT.
When your agent uses it
- You need to compare supplied competitor messaging with your approved product facts and find a credible point of difference
- Phrases include how are competitors positioned?
- Compare our message to theirs
- Where are we different?
Example prompts
- “how are competitors positioned?”
- “compare our message to theirs”
- “where are we different?”
- “/competitor-positioning”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5263be7. 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
No URLs in SKILL.md.
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
Competitor Positioning loads about 825 tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 384 words of instructions outside code blocks.
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 Ootto-AI/claude-content-skills at commit 5263be7, republished under its MIT licence (© Ootto-AI). 384 words, ~825 tokens.
Download SKILL.mdSave it as
.claude/skills/competitor-positioning/SKILL.md (or your agent's skills folder).- name
- competitor-positioning
- description
- Use when you need to compare supplied competitor messaging with your approved product facts and find a credible point of difference. Trigger phrases include "how are competitors positioned?", "compare our message to theirs", "where are we different?", "audit these competitor pages", and "what should we not say?". Do not use this to make unverified claims about competitors, copy their language, or write the final brand message in isolation; use agent-reach to collect public sources, positioning-audit to decide your message, and campaign-brief to apply it.
Competitor Positioning
Compare observable market messages without turning a competitor scan into a claim sheet or imitation exercise.
1. Define the comparison question
Ask which customer decision, category, and alternatives matter. Gather dated public pages, posts, pricing, documentation, or approved internal notes. Record source URLs or excerpts and dates. If a source cannot be verified, label it as an unverified lead rather than a fact.
2. Separate message from capability
For each alternative, map the audience it addresses, problem framing, promise, proof style, price or access signal if public, and visible limitations. Do not assume a marketing claim proves a feature, or that a missing page proves absence of a capability.
3. Compare against our real evidence
Map our approved product facts, customer language, proof, constraints, and category choice beside the alternatives. Look for a difference that is relevant to the audience and supported by something we can demonstrate. A useful difference may be a workflow, point of view, fit, or trade-off, not a superiority claim.
4. Produce positioning choices and guardrails
Return possible message territories with supporting evidence, risk, and the phrases or claims to avoid. Include the uncertainty that needs verification. Recommend one position to test through positioning-audit or campaign-brief, not a sweeping declaration that the market is settled.
Show full SKILL.md (173 more words)Show less
Hard rules
- Do not state or imply false facts about a competitor's features, pricing, customers, policies, or results.
- Attribute public observations to their source and date; products and pages change.
- Never copy distinctive competitor language, structure, or creative expression.
- Treat absence of evidence as unknown, not as proof a competitor cannot do something.
- Do not use comparative claims in public copy without legal and product approval.
Failure modes
| Failure | Do this instead |
|---|---|
| The scan becomes a feature checklist | Compare the customer decision, promise, proof, and trade-offs. |
| Competitor claims are repeated as facts | Quote or summarize the source as their stated message, with date. |
| The outcome is "we are better" | Name one relevant, demonstrable difference and its boundary. |
| The team copies a rival's framing | Return to our evidence and customer language before choosing a position. |
Where it sits
Use agent-reach before this skill when public evidence must be gathered. Use audience-personas and social-listening to ensure the comparison matters to real people. Use positioning-audit to choose our message, then campaign-brief and cross-platform-distribution to apply it.
© Ootto-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/competitor-positioning of Ootto-AI/claude-content-skills.
Open the folder on GitHubat commit 5263be7
Compare with similar skills
Competitor Positioning 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Competitor Positioning this skillOotto-AI/claude-content-skills | 122 | — | ~825 | Automated safety check: Pass | MIT | |
| Startup Designferdinandobons/startup-skill | 1.2k | — | ~8.1k | Automated safety check: Pass | MIT | |
| Competitor Teardownirinabuht12-oss/marketing-skills | 4k | — | ~1.6k | Automated safety check: Pass | None | |
| Competitive Analysisw95/awesome-claude-corporate-skills | 239 | 1 repos | ~4k | Automated safety check: Pass | MIT | |
| Competitor Researcherhanzili/hanzi-browse | 177 | — | ~4.7k | Automated safety check: Pass | Custom licence | |
| Yao Positioning Skillyaojingang/yao-open-skills | 1.3k | — | ~805 | Automated safety check: Pass | MIT |
Similar skills
Competitor Teardown
irinabuht12-oss/marketing-skills
Systematic competitive analysis covering positioning, messaging hierarchy, objection handling, and CTA strategy from landing page URLs or screenshots.
Competitive Analysis
w95/awesome-claude-corporate-skills
Framework for competitive landscape analysis across any industry.
Competitor Researcher
hanzili/hanzi-browse
Research SaaS and AI-tool competitors in a real browser. An agent skill from hanzili/hanzi-browse.
Yao Positioning Skill
yaojingang/yao-open-skills
Generate evidence-aware positioning reports for personal IPs, courses, products, services, brands, or companies by combining positioning theory, course-marketing analysis, user intent, competitor…
Competitor Analysis Local
gmapsscraper/google-maps-agent-skills
Analyze local competitors from a Google Maps CSV export. An agent skill from gmapsscraper/google-maps-agent-skills.
More from Ootto-AI/claude-content-skills
All 52 skills in this repoAgent Reach
Ootto-AI/claude-content-skills
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g.
Ab Hook Tester
Ootto-AI/claude-content-skills
Generates two genuinely distinct hook variants for the same reel so you can post-test which opening actually wins.
AI Brain
Ootto-AI/claude-content-skills
Give Claude a permanent, searchable long-term memory using an Obsidian vault as the store.
Caption And Hashtags
Ootto-AI/claude-content-skills
Write the caption, hashtag set, and first comment for a reel or post.
Collab Outreach
Ootto-AI/claude-content-skills
Drafts personalized pitches to creators and brands for collab reels, shoutouts and partnerships.
Comment Responder
Ootto-AI/claude-content-skills
Turn every comment into a lead on autopilot. An agent skill from Ootto-AI/claude-content-skills.
Related
Categories
Questions about Competitor Positioning
What does Competitor Positioning do?
A skill your agent uses when you need to compare supplied competitor messaging with your approved product facts and find a credible point of difference. Competitor Positioning is an agent skill from Ootto-AI/claude-content-skills. Use when you need to compare supplied competitor messaging with your approved product facts and find a credible point of difference.
When should I use Competitor Positioning?
Competitor Positioning fits situations like: you need to compare supplied competitor messaging with your approved product facts and find a credible point of difference; phrases include how are competitors positioned?; compare our message to theirs; where are we different?.
How do I install Competitor Positioning in Claude Code?
Run `npx skills add Ootto-AI/claude-content-skills --skill competitor-positioning -a claude-code`. Or copy the skill folder (skills/competitor-positioning in Ootto-AI/claude-content-skills) into .claude/skills/competitor-positioning in your project. Claude Code loads it when a task matches its description.
How do I install Competitor Positioning in Codex?
Run `npx skills add Ootto-AI/claude-content-skills --skill competitor-positioning -a codex`. Or copy the skill folder (skills/competitor-positioning in Ootto-AI/claude-content-skills) into .agents/skills/competitor-positioning in your project. Codex loads it when a task matches its description.
Can I use Competitor Positioning 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 Ootto-AI/claude-content-skills --skill competitor-positioning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/competitor-positioning, .gemini/skills/competitor-positioning, .github/skills/competitor-positioning and .opencode/skills/competitor-positioning in your project.
What does Competitor Positioning need to run?
SKILL.md names no scripts, command-line tools or credentials: Competitor Positioning is instructions for the agent only.
Does Competitor Positioning access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Competitor Positioning 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 Competitor Positioning use?
Competitor Positioning 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 Competitor Positioning use?
About 825 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Competitor Positioning?
Skills that share tags, products or a category with Competitor Positioning: Startup Design (ferdinandobons/startup-skill, 1.2k stars), Competitor Teardown (irinabuht12-oss/marketing-skills, 4k stars), Competitive Analysis (w95/awesome-claude-corporate-skills, 239 stars) and Competitor Researcher (hanzili/hanzi-browse, 177 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Competitor Positioning?
Ootto-AI (a GitHub organization) maintains it in Ootto-AI/claude-content-skills, which has 122 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 8, 2026.
Source: Ootto-AI/claude-content-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.