YouTube Content Manager

YouTube内容管理后台，支持AI选题生成、脚本创作、标题优化、SEO描述生成、缩略图文案建议、发布记录管理和数据分析。集成SkillPay支付接口，每次调用收0.001USDT。

This skill implements the promised YouTube content features but shows several red flags you should address before running: - Do not run this on a machine with credentials you care about until you inspect and remove hardcoded secrets. The code contains hardcoded API keys (SkillPay and SiliconFlow) and a fixed Flask SECRET_KEY. These keys may be valid and could be used by the skill owner to receive payments or process AI requests — or they could be stolen keys. Replace them with your own credentials stored in environment variables. - The SKILL.md instructs you to configure OpenAI, but the code calls a different AI provider (api.siliconflow.cn). Confirm which provider you trust, remove unused dependencies, and update the documentation. - The payment flow is odd (charge endpoint with amount 0 in some calls, pay route uses amount 8), and the SKILL.md exposes a SkillPay API key. If you plan to accept or pay money, review the billing endpoints and test in TEST_MODE first. Keep TEST_MODE = True until you fully audit the billing code. - The app transmits user prompts and generated content to external endpoints. If your prompts or stored video scripts contain sensitive information, understand that data will be sent to the configured AI/payment services. - Suggested safe actions: run the code in an isolated environment, remove or rotate the hardcoded API keys, set SECRET_KEY and API keys via environment variables, verify the skill owner's identity (homepage is missing and source is unknown), and consider using your own paid AI account. If you cannot verify or remove the embedded keys, treat this skill as untrusted.

Type: OpenClaw Skill Name: youtube-content-manager Version: 1.0.1 The skill bundle contains hardcoded sensitive API keys for both a payment service (SkillPay) and an AI provider (SiliconFlow) within `scripts/app.py` and `SKILL.md`. It implements a mandatory third-party payment gateway (skillpay.me) that requires users to pay USDT to access functionality, which is an atypical and risky monetization method for an agent skill. Furthermore, there are technical discrepancies between the documentation and implementation, such as the code using SiliconFlow while the documentation specifies OpenAI, and the payment logic in `scripts/app.py` inconsistently passing an amount of 0 to the billing endpoint.