Larry

WarnAudited by ClawScan on May 10, 2026.

Overview

Larry is a coherent TikTok marketing automation skill, but it under-declares sensitive account credentials, public posting authority, persistent scheduled activity, and local storage of revenue/customer analytics.

Only install this if you are comfortable giving the agent access to your social posting workflow and optional RevenueCat business data. Use draft/manual approval for posts, store API keys carefully, avoid saving transaction-level customer data unless necessary, and do not create the daily cron job unless you know how to disable it.

Findings (7)

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

Installing users may not realize the skill needs credentials that can access social posting infrastructure and revenue/subscriber analytics.

Why it was flagged

The registry metadata declares no credential or config requirements, but the skill's scripts and references use Postiz API keys and RevenueCat secret keys. This under-declares account-level authority.

Skill content
Required env vars: none; Primary credential: none; Required config paths: none
Recommendation

Declare Postiz and RevenueCat credentials explicitly, document the minimum scopes needed, and tell users where credentials are stored and how to revoke them.

What this means

A RevenueCat secret key may allow access to business and customer subscription data beyond simple marketing metrics.

Why it was flagged

The skill asks for RevenueCat secret API credentials, which can expose sensitive subscriber, purchase, and revenue information. This is optional but high-impact and not declared in the registry metadata.

Skill content
"v1SecretKey": "sk_..." ... "Use the secret key (sk_), NOT the public key."
Recommendation

Use the least-privileged RevenueCat key available, avoid storing broad secret keys in plain local config when possible, and clearly separate optional RevenueCat access from required setup.

What this means

Customer purchase or transaction details could be retained locally in the marketing directory and reused in future reports.

Why it was flagged

The daily report fetches RevenueCat transactions and writes the returned metrics object, including transactions, into a local snapshot file. The artifacts do not show minimization, redaction, retention limits, or user review for this stored sensitive business/customer data.

Skill content
transactions: transactions.items || [] ... fs.writeFileSync(rcSnapshotPath, JSON.stringify({ date: dateStr, ...rcMetrics }, null, 2));
Recommendation

Store only aggregate metrics by default, redact customer identifiers, document retention, and require explicit opt-in before saving transaction-level RevenueCat data.

What this means

The skill could keep running daily and continue accessing Postiz and RevenueCat data after the initial setup unless the user knows how to stop it.

Why it was flagged

The skill recommends persistent scheduled execution. This is related to analytics, but the artifacts do not show clear approval, uninstall, retention, or disable instructions for the scheduled job.

Skill content
Set up a cron job to run every morning before the first post (e.g. 7:00 AM user's timezone): Task: node scripts/daily-report.js --config tiktok-marketing/config.json --days 3
Recommendation

Ask for explicit approval before creating a cron job, show the exact schedule and command, and provide a clear disable/removal command.

What this means

Mistakes in generated content, captions, schedules, or platform selection could be published or cross-posted to multiple public channels.

Why it was flagged

Posting and cross-posting to public social platforms is central to the skill's purpose and disclosed, but it is high-impact account mutation authority.

Skill content
posts via Postiz ... cross-posting to Instagram/YouTube/Threads ... analytics tracking
Recommendation

Use draft/manual-review mode by default, confirm each connected platform, and require user approval before publishing or cross-posting.

What this means

Setup may require installing packages and build tools that are not visible in the registry requirements.

Why it was flagged

The skill relies on local Node execution and an unpinned native npm dependency, but the registry says there is no install spec and no required binaries. This appears purpose-aligned, not hidden.

Skill content
This skill does NOT bundle any dependencies... Node.js (v18+) ... node-canvas (`npm install canvas`) ... Your agent should research the install requirements for your OS.
Recommendation

Pin dependency versions, document OS-specific install steps, and declare Node/canvas requirements in metadata.

What this means

Product details and prompts may be sent to selected image-generation providers, and generated files will be written locally.

Why it was flagged

The script executes local Node code, calls external image-generation APIs, downloads generated images, and writes them to the user-selected output directory. This is expected for the stated slideshow-generation purpose.

Skill content
fetch('https://api.openai.com/v1/images/generations' ...); ... fetch('https://api.replicate.com/v1/predictions' ...); ... fs.writeFileSync(outPath, buf);
Recommendation

Review prompts before sending them to providers and use a dedicated output directory.