Skills competitor-analysis

📦

competitor-analysis

Name: competitor-analysis
Author: aaron-he-zhu

v17.0.0 Content revision r1 Safe ⚙️ External commands🌐 Network access📁 Filesystem access

Analyze Competitors and Prioritize Market Opportunities

Competitor strategy is difficult to compare when evidence comes from different tools and formats. This skill organizes SEO, content, backlink, technical, and AI citation evidence into prioritized opportunities and a phased action plan.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "competitor-analysis" from https://skillstore.io/skills/aaron-he-zhu-competitor-analysis.md and its manifest at https://skillstore.io/api/skills/aaron-he-zhu-competitor-analysis/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/aaron-he-zhu-competitor-analysis.md Signed manifest GET /api/skills/aaron-he-zhu-competitor-analysis/manifest Signed lockfile GET /api/skills/aaron-he-zhu-competitor-analysis/lockfile

Test it

Using "competitor-analysis". Compare our analytics platform with three named competitors and prioritize SEO opportunities.

Expected outcome:

Executive summary: Competitor A leads on authority and backlinks, while Competitor B has stronger publishing velocity.
Priority opportunity: Build evidence-rich comparison pages for commercial terms where competitors rank and your site does not.
Action plan: Validate keyword volumes now, publish two pages this month, and review ranking movement after eight weeks.

Using "competitor-analysis". Create a battlecard for one enterprise competitor using current public evidence.

Expected outcome:

Battlecard finding: The competitor emphasizes integrations, but public pricing and onboarding evidence remain incomplete.
Recommended response: Lead with faster implementation and transparent cost only after validating both claims with current sources.

Using "competitor-analysis". Assess a video-heavy competitor and identify SEO and AI citation openings.

Expected outcome:

Observed strength: Video outliers cluster around beginner questions and use consistent outcome-led titles.
Opening: Publish cited definitions and supporting videos for high-intent questions that lack complete competitor coverage.

Security Audit

Safe

v4 • 7/12/2026 Open versioned report

Two findings are confirmed: line 48 instructs execution of a local Firecrawl connector that performs network requests against a supplied target. The remaining 27 findings are Markdown code fences, inline identifiers, repository links, or scoped output paths and do not demonstrate shell execution or path traversal.

Files scanned

537

Lines analyzed

Review items

False positives ignored

Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

SKILL.md:48

Ruby/shell backtick execution

**Zero-dependency competitor fetch (keyless)**: `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/f

Line 48 explicitly instructs the agent to run python3 with a repository connector and a supplied target. This is real external command execution, even though it supports the stated workflow.

Low

SKILL.md:48

Fetch API call

**Zero-dependency competitor fetch (keyless)**: `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/f

Line 48 documents a Firecrawl connector that scrapes, maps, or searches remote sites using a supplied target. This is intentional outbound network access.

Risk Factors

⚙️ External commands (16)

references/analysis-templates.md:117-139 SKILL.md:22-24 SKILL.md:24-26 SKILL.md:26-28 SKILL.md:28-32 SKILL.md:32-36 SKILL.md:36 SKILL.md:48 SKILL.md:54-93 SKILL.md:93-95 SKILL.md:95-99 SKILL.md:99-101 SKILL.md:101-105 SKILL.md:105-107 SKILL.md:107-111 SKILL.md:111

🌐 Network access (3)

SKILL.md:48 SKILL.md:10 SKILL.md:13

📁 Filesystem access (10)

SKILL.md:38 SKILL.md:42 SKILL.md:46 SKILL.md:48 SKILL.md:54 SKILL.md:85 SKILL.md:89 SKILL.md:111 SKILL.md:119 SKILL.md:123

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/aaron-he-zhu-competitor-analysis/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/aaron-he-zhu-competitor-analysis/security.svg)](https://skillstore.io/skills/aaron-he-zhu-competitor-analysis?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/aaron-he-zhu-competitor-analysis?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/aaron-he-zhu-competitor-analysis/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/aaron-he-zhu-competitor-analysis.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

aaron-he-zhu. (2026). competitor-analysis security audit report (audit version 4) [Author version 17.0.0]. Skillstore. https://skillstore.io/skills/aaron-he-zhu-competitor-analysis/audits/4

BibTeX citation

@techreport{aaron-he-zhu-aaron-he-zhu-competitor-analysis-2026,
  author = {aaron-he-zhu},
  title = {competitor-analysis security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/aaron-he-zhu-competitor-analysis/audits/4},
  note = {Author version 17.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "competitor-analysis security audit report (audit version 4)"
version: "17.0.0"
type: report
authors:
  - name: "aaron-he-zhu"
date-released: "2026-07-12"
url: "https://skillstore.io/skills/aaron-he-zhu-competitor-analysis/audits/4"
identifiers:
  - type: other
    value: "skillstore:aaron-he-zhu-competitor-analysis:audit:4"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Stronger evidence confidence

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

CleanExpo Recommended

cleanexpo-competitor-analysis

Skillstore Score 78

Evidence Confidence High

Skillstore usage 8

Updated

2026-08-21

aaron-he-zhu Current

aaron-he-zhu-competitor-analysis

Skillstore Score 78

Evidence Confidence Medium

Skillstore usage 5

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Set quarterly SEO priorities

Benchmark three to five domains across rankings, content, backlinks, technical SEO, and AI citations before setting quarterly priorities.

Build an evidence-based battlecard

Convert competitor positioning, pricing, strengths, and weaknesses into an evidence-based battlecard for sales and messaging teams.

Assess a new market

Identify direct and indirect competitors, evaluate the market, and choose immediate, short-term, and long-term opportunities.

Try These Prompts

Review one competitor

Analyze the SEO strategy for [competitor URL]. Label each metric as Measured, User-provided, Estimated, or N/A. Cite the source for every claim.

Compare several domains

Compare [my site] with [competitor 1], [competitor 2], and [competitor 3]. Build one table covering traffic, authority, rankings, backlinks, and content cadence. Prioritize five opportunities.

Evaluate multichannel strengths

Evaluate [competitor] across content, technical SEO, backlink assets, YouTube outliers, and AI citations. Explain each repeatable strength and exploitable weakness using labeled evidence.

Create a strategic landscape

Create a competitive landscape for [market] using [competitors] and [our data]. Separate direct, indirect, and content competitors. Apply a positioning framework, quantify confidence, and produce a phased action plan with owners and evidence gaps.

Best Practices

Provide target domains, your site, market, audience, and available exports before analysis.
Keep metric labels, source links, and source dates visible in every comparison.
Validate estimated claims before using them in sales, investment, or publishing decisions.

Avoid

Do not present model estimates as measured data.
Do not compare unrelated companies without separating direct, indirect, and content competitors.
Do not scrape restricted pages or bypass access controls.

Frequently Asked Questions

How many competitors should I include?

Use three to five close competitors for the main benchmark. Record additional companies for later review.

Do I need an SEO platform?

No. Without tools or exports, unavailable metrics must be labeled Estimated or N/A.

Can the skill retrieve competitor pages?

It can use an optional Firecrawl connector when the host provides it. Network access and connector execution should require user approval.

Does it replace content-gap analysis?

No. Use the dedicated content-gap workflow for a pairwise map of missing topics sorted by traffic potential.

What does the final report contain?

It contains an executive summary, comparison table, evidence-based findings, priority opportunities, and an immediate, short-term, and long-term action plan.

How does it prevent unsupported claims?

Every metric receives an evidence label. Missing required data is marked N/A instead of being invented.