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

# 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 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

# 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