Larry — Autonomous TikTok Slideshow Agent

WarnAudited by ClawScan on May 10, 2026.

Overview

The TikTok automation mostly matches its stated purpose, but it is unsafe to trust as-is because it ships real-looking credentials, preconfigured affiliate destinations, and undeclared account/tool access.

Do not install or run this package as-is. First remove the bundled config.json, rotate any exposed credentials, create your own local config from the example, verify all portal URLs/account IDs are yours, and run only in dry-run mode until you have reviewed the generated drafts and provider calls.

Findings (6)

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

Anyone receiving the skill package could read or attempt to use these credentials, and the skill may run against unintended NVIDIA/Postiz accounts.

Why it was flagged

The distributed active config contains real-looking API keys and login credentials rather than only placeholders.

Skill content
"nvidia_api_key": "nvapi-[redacted]", "postiz_api_key": "[redacted]", "postiz_email": "alexander@[redacted]", "postiz_password": "[redacted]"
Recommendation

Remove config.json from the distributed package, rotate all exposed keys/passwords, ship only config.example.json, and require user-supplied local config or environment variables.

What this means

A compromised or mishandled config could expose full Postiz account access, not just permission to create a single draft.

Why it was flagged

The Postiz integration logs in with a full account email/password to obtain an auth cookie, which is broader and more sensitive than a scoped posting token.

Skill content
json={"email": config.get("postiz_email", ""), "password": config.get("postiz_password", ""), "provider": "LOCAL"}
Recommendation

Use a scoped API token/OAuth flow where possible, clearly declare the credential requirement, and avoid storing account passwords in the skill directory.

What this means

If a user runs or partially edits the included config, generated TikTok drafts may promote destinations that are not the user's own affiliate articles.

Why it was flagged

The bundled active configuration points generated content at specific existing sites and affiliate-style tags instead of neutral placeholders.

Skill content
"site_url": "https://saunamagie.de", "amazon_tag": "ak1337-snm-21" ... "site_url": "https://golfmagie.de", "amazon_tag": "ak1337-gm-21"
Recommendation

Distribute only placeholder portal entries, make the skill fail closed until the user supplies their own site/account values, and clearly label any example domains as examples.

What this means

The skill may unexpectedly use the user's Claude account or fail in environments without the CLI, and topic/site details may be sent through an undocumented provider path.

Why it was flagged

The code invokes an undeclared local Claude CLI dependency, likely relying on the user's local Claude session/account, even though the documented requirements focus on NVIDIA and Postiz.

Skill content
Generiert Hooks + Slide-Konzepte via Claude CLI (kein API-Key nötig) ... subprocess.run(["claude", "-p", prompt], capture_output=True, text=True, timeout=30)
Recommendation

Declare the Claude CLI as a required binary/credential if used, document what data is sent, or replace it with an explicitly configured provider call.

What this means

This is purpose-aligned, but it mutates a social-posting workspace and could create unwanted drafts if run with the wrong portal/account.

Why it was flagged

Non-dry-run mode uploads generated images and creates a Postiz/TikTok carousel draft under the configured account.

Skill content
"type": "carousel", "content": caption, "media": [{"id": mid} for mid in media_ids], "settings": {"account": account_id, "status": "draft"}
Recommendation

Use dry-run first, verify the configured account and destination URLs, and review each draft in Postiz before publishing.

What this means

Local log contents can bias future content generation if they are stale, incorrect, or manually altered.

Why it was flagged

Past performance logs are reused to influence future hook generation.

Skill content
log_file = LARRY_DIR / "logs" / "performance.json" ... return [p["hook"] for p in portal_posts[:5]]
Recommendation

Keep performance logs local, inspect them periodically, and reset or edit them if future generated hooks become inappropriate.