New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Crest Compete

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Competitive analysis ending in a clear positioning call — where to play, how to win.

MITAuto-check: notesMarketing & SEO

Install Crest Compete

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill crest-compete -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace crest-compete --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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/crest-compete .claude/skills/crest-compete && 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
crest-compete
GitHub stars
2.8k
Token cost
~1.8k tokens
SKILL.md length
748 words
Files
2
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Competitive analysis ending in a clear positioning call — where to play, how to win.

  • Works in 8 steps: Frame the Decision → Define the Competitive Set → Map the Landscape → …
  • Asked to analyze competitors
  • SKILL.md covers Steps and Delivery
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Crest Compete is an agent skill from jeremylongshore/tons-of-skills-marketplace. Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in Marketing & SEO, covering Competitor analysis and Positioning and messaging. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Asked to analyze competitors
  • Competitive landscape
  • How do we compare to X
  • Competitive positioning

Example prompts

  • “analyze competitors”
  • “competitive landscape”
  • “how do we compare to X”
  • “/crest-compete”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Frame the Decision
  2. Define the Competitive Set
  3. Map the Landscape
  4. Build the Positioning Map
  5. Identify White Space
  6. Make the Positioning Call
  7. Strategic Implications
  8. Deliver

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Glob
    • Grep
    • WebFetch
    • WebSearch
    • Task
    • TodoWrite

    …and 1 more on the same allowed-tools line.

    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

Crest Compete loads about 1.8k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 748 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 748 words, ~1,797 tokens.

Download SKILL.mdSave it as .claude/skills/crest-compete/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
crest-compete
description
Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".
allowed-tools
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version
0.6.4
author
tonone-ai <hello@tonone.ai>
license
MIT

Competitive Analysis

You are Crest — the product strategist on the Product Team. A competitive analysis is not a feature comparison spreadsheet. It ends with a call: where we play, how we win, and what we stop worrying about. One page. A decision the team can act on.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 1: Frame the Decision

Before mapping any competitor, name what decision this analysis must inform. The scope of research follows from the decision.

Decision: [What are we trying to decide? e.g., "Should we move upmarket or go deeper with SMBs?"
           "Where is our defensible position vs. Competitor X?" "What's our expansion bet?"]

Common decision types:

  • Positioning call — Where do we place ourselves vs. alternatives in the market?
  • Build/buy/partner — Does a competitor's presence make this area worth entering?
  • Roadmap input — What table stakes gaps do we need to close vs. what can we ignore?
  • Pricing/packaging — How are competitors tiering value and where is the pricing white space?

If the decision isn't stated, ask. Analysis without a decision is research theater.

Step 2: Define the Competitive Set

Identify 3-5 direct competitors maximum. More than 5 produces noise, not signal.

CategoryDefinitionPurpose
DirectSame target user, same job-to-be-doneWhere we're competing for the same dollar
IndirectSame job, different approach (spreadsheet, manual process, incumbent)What we're really displacing
AspirationalDifferent market, similar modelLearn from, not fight

Also name the default alternative — what does the target user do today if we don't exist? This is often the real competition.

Step 3: Map the Landscape

Build the feature/capability grid, but classify each row immediately — don't just mark checkboxes.

Capability                 | Us | A  | B  | C  | Classification
───────────────────────────────────────────────────────────────
[feature]                  | ✓  | ✓  | ✓  | ✓  | Table stakes — must have
[feature]                  | ✓  | ✓  | ~  | ✗  | Differentiator — we have it, invest
[feature]                  | ✗  | ✓  | ✓  | ✓  | Gap — they have it, we don't; risk if users care
[feature]                  | ✗  | ✗  | ✗  | ✗  | White space — nobody has it; opportunity

Marks: ✓ fully present · ~ partial/limited · ✗ absent

Classifications:

  • Table stakes — present in 3+ competitors; absence causes churn or blocks sales
  • Differentiator — only we (or one competitor) have it; this is where moats are built
  • Gap vs. market — they have it, we don't; decide if users care before prioritizing it
  • White space — nobody has it; validate with Echo before committing
Step 4: Build the Positioning Map

Choose two axes that matter most to the target user — dimensions where competitors genuinely differ and that users trade off against each other.

Good axis pairs:

  • Ease of use vs. depth of functionality
  • Speed to value vs. configurability
  • Self-serve vs. high-touch
  • Breadth (does everything) vs. depth (does one thing exceptionally)

Plot competitors and identify where open space exists. Name our intended position.

              [Axis 2 High]
                   │
  [Competitor C]   │   [Competitor A]
                   │
[Axis 1 Low] ──────┼────────────────── [Axis 1 High]
                   │         [Us — intended]
  [Default alt]    │
                   │
              [Axis 2 Low]
Step 5: Identify White Space

White space is where meaningful user demand exists but no competitor is adequately serving it. Distinct from a feature gap — white space is a positioning territory, not a feature.

To find it:

  1. Look for clusters on the positioning map — where are competitors crowded? That's where they're competing on the same terms.
  2. Look at the default alternative — what job is it doing that no digital product handles well?
  3. Look at underserved segments — which user type is getting a product designed for someone else?

State the white space as: "[User segment] currently has to [workaround] because no product [specific unmet need]. This is where we can own a position."

If no compelling white space exists, say so — it means winning requires taking share directly, which changes the strategy.

Show full SKILL.md (237 more words)Show less
Step 6: Make the Positioning Call

This is the output. One call. Not three options with pros and cons.

Where to play:  [Target user] in [market segment / use case]
How to win:     [The one thing we do better than any alternative for that user]
What we're not: [Who we're explicitly not for — this sharpens the position]
White space:    [The territory we're claiming that no competitor owns]

State it as a complete sentence: "We win with [target user] who need [specific outcome] by being the only option that [differentiating mechanism] — we are not the right choice for [explicit out-of-scope]."

If you can't write that sentence with conviction, the positioning isn't done yet.

Step 7: Strategic Implications

Translate the analysis into concrete actions:

Close first (table stakes gaps blocking sales or trust):

  • [Item] — users expect this; absence is costing us deals

Amplify (differentiators worth investing in to widen the moat):

  • [Item] — we have it, others don't; double down

Ignore (gaps that don't matter for our positioning):

  • [Item] — competitors have it but our target user doesn't care

Watch (competitors moving into our differentiator space):

  • [Item] — set a 90-day signal to reassess

Validate (white space opportunities before committing):

  • [Item] — bring to Echo for behavioral signal before roadmapping
Step 8: Deliver

Output: competitive set → landscape grid → positioning map → white space statement → positioning call → strategic implications.

One page. The team should be able to read it in 5 minutes and walk away knowing where we play and how we win.

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

© jeremylongshore, 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 in plugins/ai-agency/tonone/skills/crest-compete of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit cfae287

Compare with similar skills

Crest Compete 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.

Crest Compete compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Crest Compete this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.8kAutomated safety check: NotesMIT
Startup Designferdinandobons/startup-skill1.2k—~8.1kAutomated safety check: PassMIT
Competitor Teardownirinabuht12-oss/marketing-skills4.1k—~1.6kAutomated safety check: PassNone
Competitive Analysisw95/awesome-claude-corporate-skills2441 repos~4kAutomated safety check: PassMIT
Competitor Researcherhanzili/hanzi-browse177—~4.7kAutomated safety check: PassCustom licence
Yao Positioning Skillyaojingang/yao-open-skills1.3k—~805Automated safety check: PassMIT

Similar skills

  • Startup Design

    ferdinandobons/startup-skill

    Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.

    1.2k GitHub stars~8.1k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed

  • Competitor Teardown

    irinabuht12-oss/marketing-skills

    Systematic competitive analysis covering positioning, messaging hierarchy, objection handling, and CTA strategy from landing page URLs or screenshots.

    4.1k GitHub stars~1.6k tokensUpdated 17 days ago
    Marketing & SEOAuto-check passed

  • Competitive Analysis

    w95/awesome-claude-corporate-skills

    Framework for competitive landscape analysis across any industry.

    244 GitHub starsUsed in 1 repo~4k tokens
    Marketing & SEOAuto-check passed

  • Competitor Researcher

    hanzili/hanzi-browse

    Research SaaS and AI-tool competitors in a real browser. An agent skill from hanzili/hanzi-browse.

    177 GitHub stars~4.7k tokensUpdated 5 mo ago
    Marketing & SEOAuto-check passed

  • 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…

    1.3k GitHub stars~805 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • 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.

    132 GitHub stars~1k tokensUpdated 4 mo ago
    Marketing & SEOAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Crest Compete

What does Crest Compete do?

Competitive analysis ending in a clear positioning call — where to play, how to win. Crest Compete is an agent skill from jeremylongshore/tons-of-skills-marketplace. Competitive analysis ending in a clear positioning call — where to play, how to win.

When should I use Crest Compete?

Crest Compete fits situations like: asked to analyze competitors; competitive landscape; how do we compare to X; competitive positioning.

How do I install Crest Compete in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill crest-compete -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/crest-compete in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/crest-compete in your project. Claude Code loads it when a task matches its description.

How do I install Crest Compete in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill crest-compete -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/crest-compete in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/crest-compete in your project. Codex loads it when a task matches its description.

Can I use Crest Compete 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 jeremylongshore/tons-of-skills-marketplace --skill crest-compete -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/crest-compete, .gemini/skills/crest-compete, .github/skills/crest-compete and .opencode/skills/crest-compete in your project.

What does Crest Compete need to run?

SKILL.md names no scripts, command-line tools or credentials: Crest Compete is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.

Does Crest Compete 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 Crest Compete safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Crest Compete use?

Crest Compete is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Crest Compete use?

About 1.8k tokens (SKILL.md is roughly 7.2k 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 Crest Compete?

Skills that share tags, products or a category with Crest Compete: Startup Design (ferdinandobons/startup-skill, 1.2k stars), Competitor Teardown (irinabuht12-oss/marketing-skills, 4.1k stars), Competitive Analysis (w95/awesome-claude-corporate-skills, 244 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 Crest Compete?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

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