Competitor Monitoring

PassAudited by ClawScan on May 1, 2026.

Overview

This instruction-only skill is coherent for competitor tracking, with the main thing to notice being its persistent local business-intelligence memory and optional proactive alerts.

Before installing, decide whether you want regular competitor check-ins or only on-demand use, and be mindful that the local ~/competitor-monitoring/ folder can accumulate sensitive strategy notes, competitor dossiers, vulnerabilities, and priorities.

Findings (2)

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.

What this means

The local memory may contain sensitive competitive strategy or business vulnerabilities that future conversations can draw on.

Why it was flagged

The skill stores persistent user business context, including differentiation, vulnerabilities, and priorities, for reuse in future competitor-monitoring tasks.

Skill content
## Main Memory (~/competitor-monitoring/memory.md) ... ## User Context ... vulnerabilities: Where they're at risk ... priorities: What competitive signals matter most
Recommendation

Only store information you are comfortable keeping in local skill memory, and periodically review or delete ~/competitor-monitoring/ if the data becomes stale or too sensitive.

What this means

If enabled, the assistant may surface competitor updates proactively rather than only responding to direct requests.

Why it was flagged

The skill supports proactive check-ins and alerts, but the instructions frame this as a user preference to be chosen during setup.

Skill content
"Want me to check in on competitors regularly, or only when you ask?" ... "Should I alert you immediately when I spot important changes, or batch them?"
Recommendation

Choose on-demand or batched alerts during setup if you do not want proactive monitoring behavior.