harry0703/MoneyPrinterTurbo

Selection

Select when

• You need a finished narrated short video from a topic or script.
• You want stock-footage and AI-generated-footage options in one workflow.
• You need configurable TTS, subtitles, music, and video dimensions.
• You want WebUI, API, CLI, and agent-driven access to the same application.
• You need sequential batch generation with per-task overrides.
• You want to reuse local assets or existing provider configuration.
• You need optional automatic publishing to TikTok, Instagram, or YouTube Shorts.
• You have a terminal-capable Claude Code environment and want the supplied skill to operate the application.

Boundaries

Avoid when

• You need a native Claude Code marketplace plugin, hook, or MCP integration.
• You cannot review and trust a skill that downloads and executes an adjacent helper.
• You require a fully offline pipeline without external model or media services.
• You cannot provide or manage the API credentials required by your selected providers.
• You need guaranteed rights clearance for every stock, music, font, or generated asset.
• You require mobile-native video editing or a manual timeline editor.
• You need the agent skill on Linux, which its supplied compatibility statement does not support.
• You cannot accommodate long-running media processing or substantial disk use.

Strengths

Capabilities

Risk profile

Risks and limitations

• Uncertainty: only selected first-party files were supplied, so the main application, agent helper, Docker files, CI workflows, tests, lockfile, and provider implementations were not directly inspected.
• Uncertainty: supplied metadata and documentation include 2026 dates relative to this analysis context, so recency, release state, and adoption figures cannot be independently reconciled.
• Uncertainty: Claude Code is not named in the skill compatibility field, so Claude Code applicability is inferred from its terminal, network, filesystem, and long-running-command requirements.
• The agent skill can download and execute a Python helper and then install or update a sizable application under the user's home directory.
• The application depends on numerous third-party providers whose pricing, limits, privacy, availability, and API compatibility can change.
• Many workflows require API keys, and automatic social publishing adds high-impact external side effects when enabled.
• Local Whisper can download multi-gigabyte models, while video processing and the repository itself can require substantial disk, memory, and time.
• The README notes that bundled background music includes tracks sourced from YouTube and advises deletion if infringing, so asset licensing requires review.
• Stock-footage, music, fonts, generated media, scripts, and published outputs still require rights, policy, factual, and quality review.
• The supplied agent workflow is limited to macOS and Windows even though the underlying application also documents Linux support.
• Repository-reported generated examples, coverage levels, cross-platform behavior, and provider support were not independently reproduced.
• No independent security audit, privacy assessment, provider data-retention analysis, or end-to-end quality benchmark was supplied.

The project stores or reuses provider credentials in local configuration, can back up and restore API keys, downloads dependencies or models, calls many external services, and can publish publicly to social platforms. The skill says not to print secrets and requires explicit confirmation for paid Seedance tasks. API CORS defaults to same-origin, with trusted origins configurable. Security fixes are best-effort for latest main and the newest release line, with private vulnerability reporting preferred. Implementations were not audited.