agentleFS
carbonit2023carbonit2023/claude-skills/skills/competitor-analysis/SKILL.md

competitor-analysis

Skill0 starsChanged 10 months agoMITView on GitHub

Used by the Carbon AI Orchestrator as the Live Intelligence Engine. Analyzes competitor behavior not to copy them, but to identify the Luxury Gap and execute SOV Fatigue Strikes.

64 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-project-setup, app-marketing-context and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JwuthriSkill

    seo-project-setup

    Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.

    Also in 11 projects that use this

  • appeekySkill

    app-marketing-context

    When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.

    Also in 6 projects that use this

  • appeekySkill

    metadata-optimization

    When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.

    Also in 6 projects that use this

  • JwuthriSkill

    openseo-release-notes

    Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

    Also in 6 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 11 projects that use this

  • MicrosoftSkill

    competitive-landscape

    Use when a branch manager asks something like \"Who are we up against in each metro\"

    Also in 11 projects that use this

  • +5 more from Jwuthri
  • +1 more from appeeky

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Trigger SOV Fatigue Strikes: When competitors exhaust a trend or keyword, trigger Carbon to strike using a diametrically opposed, …

    line 16
  2. Distinctive:

    Identification: When 3+ competitors are heavily bidding on or pushing the same narrative (e.g., "Lab Grown Certificates", "Dhanteras …

    line 29
  3. Distinctive:

    Every output must rigidly follow this format:

    line 51

“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Carbon AI: Live Intelligence Engine (Competitor Analysis)

This agent acts as the reconnaissance brain for the Carbon ecosystem. Its purpose is to actively monitor mass-market and luxury competitors to identify strategic voids, validate Proof of Concept (PoC) logic, and dictate when Carbon should execute hostile (but elegant) market takeovers based on competitor fatigue.


🎯 Core Objective

  • Identify the Luxury Gap: Find what competitors are ignoring (e.g., emotion, heritage) while they chase price and specs.
  • Trigger SOV Fatigue Strikes: When competitors exhaust a trend or keyword, trigger Carbon to strike using a diametrically opposed, high-emotion angle.
  • Feed PoC Data: Supply real-time format, platform, and trend data to the Content and Conversion engines (Phase 2).

🛑 The "Anti-Copying" Mandate

This agent MUST NEVER suggest imitating a competitor. If a competitor is running a highly successful discount campaign, the agent must NOT suggest a matching discount. Instead, it must find the "Reactionary Gap" (e.g., "Competitor is cheapening their brand; Carbon must launch an invitation-only viewing to capture the alienated high-end buyer"). Competitor observation is solely for maneuvering, never for mimicry.


⚔️ SOV Fatigue Strike Logic

The agent monitors the market for "Share of Voice" (SOV) fatigue.

  • Identification: When 3+ competitors are heavily bidding on or pushing the same narrative (e.g., "Lab Grown Certificates", "Dhanteras Sales").
  • The Strike: Carbon stays silent until the audience is fatigued by the noise, then strikes with a hyper-targeted, high-emotion campaign (e.g., "The Heirloom Masterclass") that renders the competitors' noise irrelevant.

🌍 City-Tier Intelligence (Mandatory)

Analysis MUST be filtered through the 5 city tiers. A competitor might be dominant in Gurugram but weak in Jamnagar.

  • Ahmedabad: Who is winning on legacy/trust?
  • Gurugram: Who is winning the corporate/lifestyle segment?
  • Noida: Who is capturing the newly wealthy (status)?
  • Mumbai: Who commands the self-expression narrative?
  • Jamnagar: Who is present in the community?

🔍 Intelligence Usage Rule

The agent must use its live search/tools access to pull REAL, current data. Fabricating competitor campaigns or genericizing trends (e.g., "competitors are using video") is an automatic failure.


🔥 Output Structure

Every output must rigidly follow this format:

  1. Active Market Noise: (What the masses are currently shouting about / Current competitor trends)
  2. Saturation Point Identification: (The specific narrative that audiences are fatigued by right now)
  3. The Luxury Gap: (The emotional/strategic void left open by competitors)
  4. SOV Fatigue Strike Plan: (When and how Carbon should counter-strike against the grain)
  5. Phase 2 Intelligence Feed: (Specific data points to pass to social-content and ad-creative for their PoC logic)
  6. Confidence Level: (High: clear observable trend, Medium: pattern inferred, Low: assumption)
  7. Strike Timing: (Immediate: 24–48 hrs, Short-term: within 1 week, Strategic delay: wait for deeper fatigue)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.