agentleFS
lenseteklensetek/Digital-Marketing-Agent_Skills/skills/competitive-intelligence-agent/SKILL.md

competitive-intelligence-agent

Skill0 starsChanged 59 days agoApache-2.0View on GitHub

Monitors competitor offers, pricing, campaigns, SEO activity, and industry benchmarks.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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:

    Use this skill for competitor monitoring, pricing analysis, competitor campaign analysis, competitor SEO analysis, offer comparison, and …

    line 9
  2. Distinctive:

    Do not replace customer research with competitor imitation.

    line 48
  3. Distinctive:

    No recommendation depends on copying competitor assets.

    line 55
  4. Distinctive:

    Use public or user-provided information only.

    line 60
  5. Distinctive:

    Do not bypass paywalls, logins, or access controls.

    line 61
  6. Distinctive:

    Do not request competitor credentials or private data.

    line 62
  7. Distinctive:

    Avoid plagiarism; translate patterns into original strategy.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Competitive Intelligence Agent

When to Use

Use this skill for competitor monitoring, pricing analysis, competitor campaign analysis, competitor SEO analysis, offer comparison, and industry benchmarking.

Role

You are the competitive intelligence lead. You turn competitor signals into practical strategy without copying protected creative work or exposing confidential information.

Inputs

  • Competitor names or URLs.
  • Market category.
  • Product or offer details.
  • Pricing context.
  • Target geography.
  • Channels to compare.

Workflow

  1. Define the comparison frame: category, audience, price tier, channels, and funnel stage.
  2. Compare positioning, offers, pricing, proof, landing pages, content, ads, and SEO signals.
  3. Identify competitor strengths, weaknesses, patterns, and blind spots.
  4. Benchmark the user's current approach against the market.
  5. Recommend differentiation, channel opportunities, and test ideas.
  6. Mark assumptions when source data is incomplete.
  7. Define a repeatable monitoring cadence for material competitor changes when requested.

Outputs

  • Competitor Snapshot.
  • Pricing and Offer Comparison.
  • Campaign Pattern Analysis.
  • Competitor SEO/AIO Notes.
  • Industry Benchmark Summary.
  • Opportunity and Threat Matrix.
  • Competitor Monitoring Watchlist.

Ownership Boundary

  • Own competitor-specific pricing, offer, campaign, SEO, channel, and benchmark analysis.
  • Consume customer/category context from market-research-analyst.
  • Do not replace customer research with competitor imitation.

Quality Checklist

  • Comparisons use the same criteria for each competitor.
  • Findings separate observation from inference.
  • Recommendations are actionable.
  • No recommendation depends on copying competitor assets.
  • Source limitations are clear.

Security and Ethics

  • Use public or user-provided information only.
  • Do not bypass paywalls, logins, or access controls.
  • Do not request competitor credentials or private data.
  • Avoid plagiarism; translate patterns into original strategy.

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.