Apify Competitor Intelligence
PassAudited by ClawScan on May 10, 2026.
Overview
The skill is coherent for Apify-based competitor research, but it uses your Apify token to launch remote scraper actors, so you should confirm the actor, inputs, costs, and outputs before running it.
This skill appears safe to install for its stated purpose if you trust Apify and intend to run these competitor-intelligence actors. Before using it, verify the selected actor, keep result limits reasonable, avoid putting confidential information into actor inputs, and watch your Apify account for costs or long-running jobs.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone using the skill is allowing it to act through their Apify account, which may access datasets and consume Apify credits.
The script sends the user's Apify token in authenticated API requests to start actor runs and download results.
'Authorization': `Bearer ${token}`Use an Apify token with only the permissions you intend, review the selected actor and input before running, and monitor usage/costs.
The skill can trigger remote scraping jobs and produce downloaded datasets; a wrong actor or overly broad input could create unwanted cost or data collection.
The helper can launch a selected Apify Actor with user-provided JSON input, which is central to the skill but is a real external action.
const url = `https://api.apify.com/v2/acts/${apiActorId}/runs`; ... method: 'POST' ... body: JSON.stringify(parsedInput)Confirm the actor ID, result limit, and input JSON before execution, especially when using actors outside the documented table.
Installing the skill adds an external CLI dependency to the environment.
The skill installs an external npm package to provide the mcpc binary used for Apify MCP calls.
install:
- kind: node
package: "@apify/mcpc"
bins: [mcpc]Install only from the expected source and keep normal package-management safeguards in place.
If a run exceeds the local timeout, it may continue in Apify and keep consuming resources until it finishes or is stopped elsewhere.
The local polling timeout does not necessarily stop the remote Apify actor run.
Warning: Timeout after ${timeout}s, actor still runningCheck the Apify console for long-running jobs and stop any run that should not continue.