Competitor Radar
v1.0.0Structure competitor booth observations from a trade show into a field-intel note and battlecard-ready summary.
⭐ 1· 74·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and SKILL.md consistently describe taking raw show-floor notes and producing structured competitor intel and internal action notes. There are no unexpected binaries, credentials, or config paths requested that would be inconsistent with that purpose.
Instruction Scope
The runtime instructions stay narrowly focused on parsing user-provided observations, tagging evidence vs. inference, and producing structured outputs. One user-facing guidance item asks the user to 'flag' contacts and check badge/LinkedIn data for outreach — that references personally identifiable information (PII) and follow-up actions, but the skill does not instruct the agent to fetch external badge systems or automatically exfiltrate data. Users should be aware that outputs may prompt manual PII lookups that must follow privacy policies.
Install Mechanism
No install spec and no code files — instruction-only skill. No downloads, package installs, or archive extraction are present.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. Nothing requests unrelated secrets or credentials.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request permanent presence or system-wide changes; autonomous invocation remains at platform default but is not combined with other red flags.
Assessment
This skill appears internally consistent and lightweight — it only needs the user's raw notes and produces a tagged intel summary. Before installing or using it: (1) avoid pasting sensitive PII or corporate credentials into observations; the skill will encourage you to flag contacts but will not access badge systems itself, so any follow-up PII lookups should follow your privacy/legal policies; (2) verify any high-impact claims (prices, quantified performance) with primary sources before acting — the skill deliberately tags unverified overheard or inferred items but downstream teams may treat outputs as actionable; (3) because it is instruction-only, review the SKILL.md locally and confirm you are comfortable with the implied workflow (manual badge/LinkedIn lookups, sharing battlecards internally). If you want the agent to automatically query CRM or badge systems, require a separate, explicit integration with appropriate credentials and governance — the current skill does not and should not have that capability.Like a lobster shell, security has layers — review code before you run it.
latestvk977sz5gz00cy4nfmxmtgkr0k583hg5k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.