Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Tiktok Auto Reply
v1.0.0自动监控指定关键词的TikTok热门视频评论并定时发送配置的自动回复，支持频率限制和多模板切换。
⭐ 0· 136·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description match the code: it monitors keywords and replies to comments using TikTok API credentials placed in config.json. However, the registry metadata declares no required credentials while the SKILL.md and config.example.json require accessToken/clientKey/clientSecret — a mismatch. Also, the TikTok client methods in index.js are placeholders that return mock results rather than performing real HTTP calls, while node-fetch is declared as a dependency but not actually used.
Instruction Scope
Runtime instructions are limited to copying/editing config.json and running the script (check/watch). They do not request unrelated system files or hidden network endpoints. Inconsistencies: SKILL.md and README reference running watch.js in one place though no watch.js exists (the script is invoked as node index.js watch or npm run watch). The instructions do instruct storing API credentials in a local JSON file (plaintext), which increases risk if the workspace is shared.
Install Mechanism
There is no formal install spec in registry (instruction-only), but SKILL.md/README instruct npm install and package.json lists node-fetch. Installing via npm is expected for a Node.js skill; the dependency is from the public npm registry (traceable). No high-risk external binaries or downloads are used.
Credentials
The skill legitimately needs TikTok API credentials, but the registry metadata does not declare required credentials or a primaryEnv. Instead, users are instructed to put secrets into config.json — storing sensitive tokens in a plaintext file in the skill directory is potentially unsafe. The number of secrets (accessToken, clientKey, clientSecret) is reasonable for the claimed purpose, but the storage mechanism and lack of explicit registry declaration are disproportionate/misleading.
Persistence & Privilege
The skill does not request always:true and does not modify system or other skills' configs. It runs as a normal user-space Node.js program and does not persist additional privileges beyond its workspace files.
What to consider before installing
This skill appears to be a simple TikTok auto-reply tool but has several warning signs: (1) it expects TikTok API credentials but those are stored in a local config.json (plaintext) rather than declared as secure env vars — avoid committing that file and keep credentials out of shared/workspace repos; (2) index.js currently contains placeholder/mock API methods (no real HTTP calls), so the published package may be incomplete or a template — review/replace the API calls before giving it real credentials; (3) documentation/script mismatches (references to watch.js) indicate sloppy maintenance — verify the correct run command (npm run watch or node index.js watch); (4) installing runs npm install which will fetch node-fetch from the public registry — inspect package.json and the installed node_modules before running; (5) automated posting can violate TikTok terms and risk account suspension — test in dryRun mode and use a throwaway/test account first. Recommended next steps: review index.js for any real network endpoints, confirm where/when credentials are used, move secrets to a secure location (env vars or a secrets manager), run in an isolated environment, and verify the upstream repository before trusting it.Like a lobster shell, security has layers — review code before you run it.
latestvk97awdxzp2gaqp0ejkrdb5tced839862
License
MIT-0
Free to use, modify, and redistribute. No attribution required.