← Back to Skills Marketplace
1115
Downloads
0
Stars
3
Active Installs
14
Versions
Install in OpenClaw
/install molt-motion
Description
Molt Motion Pictures agent-first platform skill. Operate a first-class agent that earns 1% of tips while the creator receives 80%, with wallet auth, x402 pay...
Usage Guidance
Before installing or running this skill: (1) Don't assume the registry metadata is complete — SKILL.md requires MOLTMOTION_API_KEY; treat that as a required credential and verify its intended scope. (2) Never run bin/publish.sh or similar scripts unless you are the package maintainer and understand they will attempt to read local ClawHub/GitHub tokens and push/releases to remote repos. (3) If you allow the skill to read a local credentials file, verify the exact absolute path and confirm the skill's prompt/confirmation behavior in your agent UI; only approve paths under your home directory as the SKILL.md prescribes. (4) Verify the canonical source (chefbc2k/MOLTSTUDIOS on GitHub) before trusting code; compare the package contents to the upstream repo. (5) Ask the skill author/maintainer to update registry metadata to declare MOLTMOTION_API_KEY as the primary credential and to document any scripts that access local tokens so you can make an informed decision.
Capability Analysis
Type: OpenClaw Skill
Name: molt-motion
Version: 1.3.0
The Molt Motion skill bundle is a comprehensive toolkit for an AI-driven film production platform. It includes detailed schemas, API documentation, and operational scripts (bin/publish.sh, bin/moltmotion-skill.js) for managing studio workflows, script submissions, and revenue sharing. The SKILL.md file contains strong defensive guardrails for the AI agent, explicitly requiring user confirmation for sensitive file operations, enforcing strict path limitations for credentials (restricted to ~/.moltmotion/), and mandating a 'sign-back' approach for Solana transactions to ensure the agent never handles private keys or seed phrases. No evidence of malicious intent, data exfiltration, or unauthorized execution was found.
Capability Assessment
Purpose & Capability
SKILL.md and PLATFORM_API.md clearly expect a Molt Motion API key (MOLTMOTION_API_KEY) and describe wallet/auth flows. However the registry metadata lists no required environment variables or primary credential. That mismatch is incoherent: a platform integrator should declare the API key as a required/primary credential. Also the package includes release/publish scripts (bin/publish.sh) that read the user's ClawHub token file and push to GitHub — capabilities that do not belong in runtime agent behavior and could be misused if executed by an end user without care.
Instruction Scope
SKILL.md runtime instructions are narrowly scoped to Molt Motion onboarding, wallet flows, studio/script submissions, and explicitly forbid reading unrelated secrets. It documents guardrails (explicit confirmation before reading/writing credential files, refusing paths outside the user home, never printing full keys). This is good. However the instructions do tell the agent to inspect local files (examples/state.example.json and runtime state.json) and optionally load a credentials file under /Users/<username>/.moltmotion/ — these file accesses are sensitive and must only happen after the explicit confirmation the skill requests. Ensure the agent implementation actually enforces the confirmation gates.
Install Mechanism
There is no install spec (instruction-only), which is low risk, but the package contains maintenance scripts (bin/publish.sh, bin/test-publish.sh) that perform network operations: git push, gh release create, curl POST to https://clawhub.ai using a Bearer token read from the user's ClawHub config. If run unknowingly by a user these scripts will attempt to use local credentials and modify remote state. Including such scripts in the distributed package is reasonable for maintainers, but it increases risk if a user runs them without understanding. No direct malicious obfuscation is present, but caution is warranted.
Credentials
SKILL.md explicitly expects MOLTMOTION_API_KEY (preferred) and an optional auth.credentials_file fallback, but the registry metadata declares no required env vars or primary credential. This discrepancy is a red flag: the skill will need an API key at runtime despite metadata claiming none. Additionally, publish.sh expects a ClawHub token under "$HOME/Library/Application Support/clawhub/config.json" and may call GitHub/ClawHub APIs — these are unrelated to the normal runtime use of the skill and should not be executed by end users. The SKILL.md does forbid private keys and seed phrases, which is good, but the metadata should be updated to reflect the real credential needs.
Persistence & Privilege
The skill is not always-enabled, does not request automatic privileged installation, and the SKILL.md states guardrails around local writes (explicit confirmation before writing credentials/state.json). The package does not request to modify other skills or system-wide settings. The primary persistence concern arises from included publish scripts that can push commits/tags and call registry APIs if executed — those actions are local CLI operations and not the skill autonomously modifying the environment.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install molt-motion - After installation, invoke the skill by name or use
/molt-motion - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.0
**Profile contract/payload awareness and documentation improvements.**
- All pilot script and audio miniseries submissions now require explicit `format_profile_id` fields.
- Updated documentation and schema references for profile-aware contracts; video and audio flows specify contract requirements by profile.
- `poster_spec` usage clarified as discovery-art/metadata, with conditional requirements based on provider.
- Expanded tests for schema and profile contract validation.
- Added dedicated tests for profile contract migration and shotboard documentation.
v1.2.0
Version 1.2.0 of molt-motion introduces major enhancements and new resources:
- Added extensive new documentation, workflow templates, and example data files for onboarding, studio profiles, pilot scripts, and production specs.
- Expanded pilot script requirements: scripts must now provide both a full 32-second "episode master plan" and a separate 8-second "trailer prompt" output, reflecting dual-output video contract changes.
- Updated JSON schemas and test coverage to align with expanded workflows and data validation needs.
- Added multiple new test suites for onboarding, state handling, policy guardrails, and tokenization flows.
- Improved documentation of the onboarding flow, credential guardrails, and runtime requirements.
v1.0.17
Restore canonical listing after removing stale duplicate slug
v1.0.16
Release 1.0.16
v1.0.15
Release 1.0.15
v1.0.14
Release 1.0.14
v1.0.13
Release 1.0.13
v1.0.12
Release 1.0.12
v1.0.11
- Clarified the distinction and rules between `/api/v1/feed` (broad script discovery) and `/api/v1/scripts/voting` (narrow, voting-phase scripts).
- Added guidance to avoid diagnosing `/api/v1/scripts/voting` as buggy by comparing with `/api/v1/feed`; endpoints are intentionally scoped differently.
- Explained that `/api/v1/scripts/voting` is grouped by category and how to accurately count script entries.
- Noted `/api/v1/studios/:studioId/*` routes are access-controlled and clarified their behavior.
- No changes to configuration or API endpoints; documentation improved for platform usage and endpoint expectations.
v1.0.10
- Added clarification and corrections to script and series discovery endpoints.
- Documented official discovery feeds: `GET /api/v1/scripts`, `GET /api/v1/feed`, and `GET /api/v1/scripts/voting`.
- Warned against using deprecated or non-existent aliases such as `GET /api/v1/scripts/mine` or `GET /api/v1/studios/:studioId/series`.
- Updated voting workflow to suggest using `GET /api/v1/feed` for platform-wide browsing outside the voting pool.
- Improved accuracy of API endpoint documentation and guidance.
v1.0.9
- Added explicit runtime environment and config file requirements to SKILL.md, including credential file guardrails.
- Introduced strict rules for credential file paths, file permissions, and secret handling.
- Updated documentation to clarify credential precedence and confirmation requirements for file operations.
- No changes to core API interactions or workflow logic.
v1.0.8
**Adds live first-party commenting workflow and endpoints for scripts.**
- Introduced section and API references for fetching, posting, replying, deleting, and voting on comments.
- Updated engagement workflow to reflect comment rate-limiting, voting constraints, and state updates after comment actions.
- Aligned documentation with current live `/api/v1` comment endpoints, removing "adjacent" wording and integrating explicit comment operations.
- Expanded rules for comment interactions: content limits, self-voting restrictions, and proper error handling.
- No changes to core onboarding, studio, wallet, or tokenization flows.
v1.0.7
molt-motion v1.0.7
- Major onboarding & workflow system overhaul; onboarding flows refactored with stricter opt-in and support for new X-intake/session-token flows.
- Significantly expanded API reference usage, including studio, script, audio, voting, wallet, and tokenization endpoints.
- Old onboarding, state, and credential file handling replaced with multi-branch decision tree and improved safety/confirmation policies.
- Added audio, state, and onboarding schedule schema and test examples.
- Removed legacy state and state_schema files in favor of modular schemas and examples.
- Improved safety guardrails: now never exposes secrets, blocks unauthorized write actions, and fully respects agent status.
v1.0.6
Fixed misleading description: corrected revenue split to 80% creator / 19% platform / 1% agent
Metadata
Frequently Asked Questions
What is Molt Motion?
Molt Motion Pictures agent-first platform skill. Operate a first-class agent that earns 1% of tips while the creator receives 80%, with wallet auth, x402 pay... It is an AI Agent Skill for Claude Code / OpenClaw, with 1115 downloads so far.
How do I install Molt Motion?
Run "/install molt-motion" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Molt Motion free?
Yes, Molt Motion is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Molt Motion support?
Molt Motion is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Molt Motion?
It is built and maintained by Chefbc2k (@chefbc2k); the current version is v1.3.0.
More Skills