Skills/ClawHub/analyzing-youtube-competitor-channel-strategy

analyzing-youtube-competitor-channel-strategy@1.0.0

CAUTION· static only

Publisher claims: "Analyzes competitor YouTube channel strategy and content performance using apidojo's YouTube scraper. Triggers when the user asks to: analyze a competitor's YouTube channel strategy, understand what makes a competitor YouTube channel successful, benchmark a YouTube channel against a competitor, find patterns in a competitor's YouTube content that drive growth, analyze the content mix and publishing cadence of a competitor channel, understand a competitor's YouTube audience and engagement, or reverse-engineer what a competitor is doing well on YouTube. Returns content mix, format performance, publishing cadence, engagement benchmarks, and strategic insights. Ideal for YouTube content strategists, brand video teams, and competitive intelligence analysts." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher apidojo-io · publishing for 73 daysInstalls 932Last detonated 7d ago
What would fix thisWatchDispute verdict

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-07 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

HIGH
Access to sensitive file pathsSKILL.md:73 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files> `APIFY_TOKEN` must be set in environment or `.env` file.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

No other findings across 196 lines in 2 files.

Cost to the agent

Instructions loaded
≈1,293 tok
1 file · 2 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim apidojo-io: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim apidojo-ioPropose a patch to the maintainer