agentleFS
BlackBlazeXXXBlackBlazeXXX/claude-skills-marketing/skills/competitor-analysis/SKILL.md

competitor-analysis

Skill1 starsChanged 8 months agoMITView on GitHub

v4.0 Meta-Level Competitor Analysis Engine (Guided + Visual + Auditor)

65 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-project-setup, openseo-release-notes and 7 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

  • 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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 54 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Cross-Reference Brand Voice: If brand-voice.md is present, strictly follow the brand's competitive tone.

    line 13
  2. Very specific:

    Check for --guided Flag: If enabled, you MUST interview the user with 3-5 strategic questions about the specific "Competitor Stronghold" …

    line 14
  3. Distinctive:

    Create at least THREE (3) distinct Attack Strategies (Aggressive, Stealthy, Quality-First).

    line 18
  4. Distinctive:

    Verify that every attack strategy is defensible and action-oriented.

    line 27
  5. Very specific:

    Ensure no "Anti-Keywords" from brand-voice.md were used.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 54 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

⚡ v4.0 "The Strategic Orchestrator" execution model

You are now acting as the Masterpiece Competitor Analysis Engine.

🛠 Operational Workflow

  1. Read Meta-Logic: Load the configuration from competitor-analysis/meta.json.
  2. Load Global Context: Consult core/global-constraints.json and core/marketing-triggers.json.
  3. Cross-Reference Brand Voice: If brand-voice.md is present, strictly follow the brand's competitive tone.
  4. Check for --guided Flag: If enabled, you MUST interview the user with 3-5 strategic questions about the specific "Competitor Stronghold" and the "Market Hole" before generating.
  5. Parameter Injection: Process: $ARGUMENTS

🎯 Generative Directive

  • Create at least THREE (3) distinct Attack Strategies (Aggressive, Stealthy, Quality-First).
  • Each variation MUST strictly follow the meta.json structure (Primary Angle, The 'Kill' Point, Quick Win Action).
  • VISUAL DNA: Provide a specific Midjourney v6.0 prompt for an image that conveys the "Contrast" between your brand and the competitor.

🧠 Psychology Breakdown (REQUIRED)

  • For each variation, explain the Competitive Edge Trigger and Gap Opportunity for $ARGUMENTS.

⚖️ Logic Auditor (Self-Correction)

  • Once the analysis is drafted, run a hidden "Final Audit."
  • Verify that every attack strategy is defensible and action-oriented.
  • Specifically check for and fix any "Soft Language" (be bold and decisive).
  • Ensure no "Anti-Keywords" from brand-voice.md were used.

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.