Updated: Jul 19, 2026
Version: v1.1
Sources: 1 source
Status: Published

competitor-profiling

Competitor profiling

Corey Haines / Marketing Skills

Researches and synthesizes public evidence to compare competitors without turning assumptions into facts.

License: MIT
Risk: Risk level: high

Risk profile

This is a risk profile, not a certification or a safety guarantee.

What can it read? Present: It can read public competitor and review pages, plus product notes you add.
What can it create or change? Present: It can create research reports and saved data files in your project.
Can it use the internet or send data? Present: It can use the internet to open public pages and send data to online research services.
Can it use saved logins or a paid quota? Present: It can use saved research-service logins and consume a paid usage quota.
Which action needs your approval? Present: Every Firecrawl or DataForSEO call that sends data, uses configured credentials, or consumes paid quota needs your explicit approval first.
When was the source verified, and has the snapshot changed since? Present: The source was last verified on 2026-07-19. The published snapshot still matches that verification. This is not a live check of the upstream source.

Canonical source: https://github.com/coreyhaines31/marketingskills/blob/67264763cb107d61749f418d081c56e5bcbc0209/skills/competitor-profiling/SKILL.md(opens in a new tab)
Source revision: 67264763cb107d61749f418d081c56e5bcbc0209
License: MIT
Verification date: 2026-07-19
Source status: Verified
Change status: Snapshot consistent; The published snapshot still matches the last verification. This is not a live check of the upstream source.

Understand

Covered goals

research competitors
compare positioning
synthesize market evidence

Inputs → outputs

competitor website URLs
the user's product context
quick-scan or deep-profile depth
optional focus areas such as pricing, positioning, SEO, or content

one Markdown competitor profile per competitor
raw scrape, SEO, and optional review data organized by competitor and date
a cross-competitor Markdown summary when multiple competitors are profiled

Recognize

Verbatim from the English source

Triggers

competitor research
competitive landscape
positioning comparison

Non-triggers

legal clearance
private intelligence gathering
automatic market monitoring

Choose

Verbatim from the English source

Permissions

read public competitor and review pages
read user-provided product context files when present
use configured Firecrawl and DataForSEO credentials and quota
create dated raw-data directories and Markdown profiles in the scoped project
require explicit authorization before any Firecrawl or DataForSEO call that sends data, uses configured credentials, or consumes paid quota

External effects

network requests to competitor, review, Firecrawl, and DataForSEO services
Firecrawl and DataForSEO calls can consume paid API quota
raw scrape, SEO, review, profile, and summary files are created on disk

Compatibility

an Agent Skills runtime with filesystem access and configured Firecrawl and DataForSEO MCP tools

Required tools

Firecrawl Map, Scrape, and optional Search MCP tools
DataForSEO MCP tools and configured credentials
filesystem tools for the competitor-profiles directory

Check permissions and confirm every external effect before using this skill.

Compare

None declared

Understand → Recognize → Choose → Compare

Pack for your agent

Pre-written instruction by SkillCodex — your request is neither sent nor used to adapt this text; no content is generated, and copying executes nothing.

Use in your agent

Complete the task with Competitor profiling

# Use Competitor profiling in your agent

## Objective
Use the existing competitor-profiling skill only when it directly covers the requested task.

## Prerequisites
- competitor website URLs
- the user's product context
- quick-scan or deep-profile depth
- optional focus areas such as pricing, positioning, SEO, or content
- Firecrawl Map, Scrape, and optional Search MCP tools
- DataForSEO MCP tools and configured credentials
- filesystem tools for the competitor-profiles directory

## Permissions
- read public competitor and review pages
- read user-provided product context files when present
- use configured Firecrawl and DataForSEO credentials and quota
- create dated raw-data directories and Markdown profiles in the scoped project
- require explicit authorization before any Firecrawl or DataForSEO call that sends data, uses configured credentials, or consumes paid quota

## External effects
- network requests to competitor, review, Firecrawl, and DataForSEO services
- Firecrawl and DataForSEO calls can consume paid API quota
- raw scrape, SEO, review, profile, and summary files are created on disk

## Procedure
- Open the canonical source pinned to revision 67264763cb107d61749f418d081c56e5bcbc0209.
- Read the skill instructions before calling its tools.
- Ask for confirmation before any paid, destructive, or remote effect not already authorized.
- Run the procedure within the requested scope and retain useful evidence.

## When not to use
- legal clearance
- private intelligence gathering
- automatic market monitoring

## Expected result
- one Markdown competitor profile per competitor
- raw scrape, SEO, and optional review data organized by competitor and date
- a cross-competitor Markdown summary when multiple competitors are profiled

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

Requires · Firecrawl Map, Scrape, and optional Search MCP tools
Requires · DataForSEO MCP tools and configured credentials
Requires · filesystem tools for the competitor-profiles directory

Why it works

Activation is limited to tasks the skill actually covers.
Permissions, tools, and external effects are visible before execution.
Confirmation and the output format keep actions controllable.

Try next

Check the Competitor profiling result

# Verify the Competitor profiling outcome

## Objective
Check that the competitor-profiling skill was used within scope and that its effects match the authorized request.

## Checks
- Compare the source and revision with the manifest.
- Separate local, browser, and external evidence.
- Report any permission or effect that was not disclosed.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

sha256:a644a3497caff2c9a2d591e59b43e06c9f82e296a1352e3ea869290fb8f33a13

Verify in your agent

Confirm that Competitor profiling produced the right outcome

# Verify Competitor profiling in your agent

## Result to check
Verify the use of competitor-profiling for the current bounded task.

## Failure signals
- The source or revision does not match the manifest.
- A permission or external effect was not disclosed.
- The output does not match the expected artifacts.
- The skill activated for a declared non-trigger.

## Checks
- Compare the SHA-256 of SKILL.md with sha256:ea7b5b7feb79ead8df038653c33aae96d38890784018a2b0afae9b2a1e21b3af.
- Confirm the permissions actually used and the observed effects.
- Verify artifacts with the narrowest available test.
- Separate local, browser, and external evidence in the report.

## Expected result
- one Markdown competitor profile per competitor
- raw scrape, SEO, and optional review data organized by competitor and date
- a cross-competitor Markdown summary when multiple competitors are profiled

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

Requires · Firecrawl Map, Scrape, and optional Search MCP tools
Requires · DataForSEO MCP tools and configured credentials
Requires · filesystem tools for the competitor-profiles directory

Why it works

The check starts from the manifest and expected artifacts, not a general impression.
Observed permissions and effects are compared with what was disclosed.
Local, browser, and external evidence stay separate in the verdict.

Try next

Prepare the next Competitor profiling check

# Make the Competitor profiling check reusable

## Objective
Turn the successful checks into a bounded checklist for the next use of competitor-profiling.

## Checks
- Keep only observable signals.
- Tie each permission to its expected effect.
- Add an explicit stop if the source or revision changes.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

sha256:375c0934a6fff7df374fd8d6f160ac3dd08b571a5c09e2af2737494b6ff92a62

Pack digest: sha256:365f1ca60e3b80c14562b1f8346916c1158825717605e86d9be0172cbbfb29fb

Source provenance

Open the canonical source

Source revision: 67264763cb107d61749f418d081c56e5bcbc0209
Digest: sha256:ea7b5b7feb79ead8df038653c33aae96d38890784018a2b0afae9b2a1e21b3af

Risk profile

This is a risk profile, not a certification or a safety guarantee.

What can it read?

Present

It can read public competitor and review pages, plus product notes you add.

What can it create or change?

Present

It can create research reports and saved data files in your project.

Can it use the internet or send data?

Present

It can use the internet to open public pages and send data to online research services.

Can it use saved logins or a paid quota?

Present

It can use saved research-service logins and consume a paid usage quota.

Which action needs your approval?

Present

Every Firecrawl or DataForSEO call that sends data, uses configured credentials, or consumes paid quota needs your explicit approval first.

When was the source verified, and has the snapshot changed since?

Present

The source was last verified on 2026-07-19. The published snapshot still matches that verification. This is not a live check of the upstream source.

Canonical source

https://github.com/coreyhaines31/marketingskills/blob/67264763cb107d61749f418d081c56e5bcbc0209/skills/competitor-profiling/SKILL.md

Source revision

67264763cb107d61749f418d081c56e5bcbc0209

License

MIT

Verification date

2026-07-19

Source status

Verified

Change status

Snapshot consistent

The published snapshot still matches the last verification. This is not a live check of the upstream source.

Understand

Covered goals

research competitors
compare positioning
synthesize market evidence

Inputs → outputs

competitor website URLs
the user's product context
quick-scan or deep-profile depth
optional focus areas such as pricing, positioning, SEO, or content

one Markdown competitor profile per competitor
raw scrape, SEO, and optional review data organized by competitor and date
a cross-competitor Markdown summary when multiple competitors are profiled

Choose

Verbatim from the English source

Permissions

read public competitor and review pages
read user-provided product context files when present
use configured Firecrawl and DataForSEO credentials and quota
create dated raw-data directories and Markdown profiles in the scoped project
require explicit authorization before any Firecrawl or DataForSEO call that sends data, uses configured credentials, or consumes paid quota

External effects

network requests to competitor, review, Firecrawl, and DataForSEO services
Firecrawl and DataForSEO calls can consume paid API quota
raw scrape, SEO, review, profile, and summary files are created on disk

Compatibility

an Agent Skills runtime with filesystem access and configured Firecrawl and DataForSEO MCP tools

Required tools

Firecrawl Map, Scrape, and optional Search MCP tools
DataForSEO MCP tools and configured credentials
filesystem tools for the competitor-profiles directory

Check permissions and confirm every external effect before using this skill.

# Use Competitor profiling in your agent ## Objective Use the existing competitor-profiling skill only when it directly covers the requested task. ## Prerequisites - competitor website URLs - the user's product context - quick-scan or deep-profile depth - optional focus areas such as pricing, positioning, SEO, or content - Firecrawl Map, Scrape, and optional Search MCP tools - DataForSEO MCP tools and configured credentials - filesystem tools for the competitor-profiles directory ## Permissions - read public competitor and review pages - read user-provided product context files when present - use configured Firecrawl and DataForSEO credentials and quota - create dated raw-data directories and Markdown profiles in the scoped project - require explicit authorization before any Firecrawl or DataForSEO call that sends data, uses configured credentials, or consumes paid quota ## External effects - network requests to competitor, review, Firecrawl, and DataForSEO services - Firecrawl and DataForSEO calls can consume paid API quota - raw scrape, SEO, review, profile, and summary files are created on disk ## Procedure - Open the canonical source pinned to revision 67264763cb107d61749f418d081c56e5bcbc0209. - Read the skill instructions before calling its tools. - Ask for confirmation before any paid, destructive, or remote effect not already authorized. - Run the procedure within the requested scope and retain useful evidence. ## When not to use - legal clearance - private intelligence gathering - automatic market monitoring ## Expected result - one Markdown competitor profile per competitor - raw scrape, SEO, and optional review data organized by competitor and date - a cross-competitor Markdown summary when multiple competitors are profiled ## Guardrails - Show the proposed changes before any external action. - Do not publish, send, delete, pay for, or change remote state without explicit authorization. - Preserve unrelated changes and stop if the scope becomes ambiguous. ## Output format - Outcome or verdict. - Files or actions involved. - Checks run and observable evidence. - Remaining blockers or limitations.

# Verify the Competitor profiling outcome ## Objective Check that the competitor-profiling skill was used within scope and that its effects match the authorized request. ## Checks - Compare the source and revision with the manifest. - Separate local, browser, and external evidence. - Report any permission or effect that was not disclosed. ## Guardrails - Show the proposed changes before any external action. - Do not publish, send, delete, pay for, or change remote state without explicit authorization. - Preserve unrelated changes and stop if the scope becomes ambiguous. ## Output format - Outcome or verdict. - Files or actions involved. - Checks run and observable evidence. - Remaining blockers or limitations.

# Verify Competitor profiling in your agent ## Result to check Verify the use of competitor-profiling for the current bounded task. ## Failure signals - The source or revision does not match the manifest. - A permission or external effect was not disclosed. - The output does not match the expected artifacts. - The skill activated for a declared non-trigger. ## Checks - Compare the SHA-256 of SKILL.md with sha256:ea7b5b7feb79ead8df038653c33aae96d38890784018a2b0afae9b2a1e21b3af. - Confirm the permissions actually used and the observed effects. - Verify artifacts with the narrowest available test. - Separate local, browser, and external evidence in the report. ## Expected result - one Markdown competitor profile per competitor - raw scrape, SEO, and optional review data organized by competitor and date - a cross-competitor Markdown summary when multiple competitors are profiled ## Guardrails - Show the proposed changes before any external action. - Do not publish, send, delete, pay for, or change remote state without explicit authorization. - Preserve unrelated changes and stop if the scope becomes ambiguous. ## Output format - Outcome or verdict. - Files or actions involved. - Checks run and observable evidence. - Remaining blockers or limitations.

# Make the Competitor profiling check reusable ## Objective Turn the successful checks into a bounded checklist for the next use of competitor-profiling. ## Checks - Keep only observable signals. - Tie each permission to its expected effect. - Add an explicit stop if the source or revision changes. ## Guardrails - Show the proposed changes before any external action. - Do not publish, send, delete, pay for, or change remote state without explicit authorization. - Preserve unrelated changes and stop if the scope becomes ambiguous. ## Output format - Outcome or verdict. - Files or actions involved. - Checks run and observable evidence. - Remaining blockers or limitations.