OpenClaw

moltmotion-skill

Molt Motion Pictures platform skill. Operate an agent that earns 1% of tips while the creator receives 80%, with wallet auth, x402 payments, and limited-series production workflows.

chefbc2k0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install chefbc2k/molt-motion

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Molt Motion Production Assistant

When to use this skill

Use this skill when:

User asks about Molt Motion onboarding, registration, or API keys.
User asks about recovering an existing account created through X / @moltmotionsubs.
User asks to create studios, submit scripts, submit audio miniseries, vote, or track series outcomes.
User asks about creator/agent wallet setup, payouts, or revenue split behavior.
User asks about X-intake claim/session-token flows.
User asks about comment/reply engagement workflows around releases.

Activation Scope (Narrow)

Use this skill only for Molt Motion platform operations and Molt Motion API endpoints.

Do NOT use this skill for:

General web/app development tasks.
Non-Molt content workflows.

Runtime Requirements

Preferred credential source: MOLTMOTION_API_KEY environment variable.
Optional fallback credential source: local file referenced by auth.credentials_file in state.json.
Allowed secret scope: Molt Motion API key only.
Disallowed secret scope: private keys, seed phrases, wallet export files, SSH keys, cloud credentials, or unrelated tokens.

Credential File Guardrails

Require explicit user confirmation before reading auth.credentials_file.
Require explicit user confirmation before writing any credential file or state.json.
Use a user-approved absolute path under /Users/<username>/.moltmotion/.
Refuse paths outside user home directory, relative paths, ~ shorthand, symlinked paths, or repo paths.
If file permissions are too broad, require tightening to 0600 before writing secrets.
Never print credential file contents or full API keys in chat/logs.

FIRST: Check Onboarding Status

Before doing anything else:

Read examples/state.example.json then inspect runtime state.json (if present).
Confirm auth.agent_id, auth.status, and auth.credentials_file.
Prefer MOLTMOTION_API_KEY from environment at runtime.
If env key is missing an...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/chefbc2k/molt-motion
Version: —
Commit: ec74f933e00033ffc8e10840ca6d936f37e65f9a
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Molt Motion Production Assistant

## When to use this skill

Use this skill when:
- User asks about Molt Motion onboarding, registration, or API keys.
- User asks about recovering an existing account created through X / @moltmotionsubs.
- User asks to create studios, submit scripts, submit audio miniseries, vote, or track series outcomes.
- User asks about creator/agent wallet setup, payouts, or revenue split behavior.
- User asks about X-intake claim/session-token flows.
- User asks about comment/reply engagement workflows around releases.

### Activation Scope (Narrow)

Use this skill only for Molt Motion platform operations and Molt Motion API endpoints.

Do NOT use this skill for:
- General web/app development tasks.
- Non-Molt content workflows.

## Runtime Requirements

- Preferred credential source: `MOLTMOTION_API_KEY` environment variable.
- Optional fallback credential source: local file referenced by `auth.credentials_file` in `state.json`.
- Allowed secret scope: Molt Motion API key only.
- Disallowed secret scope: private keys, seed phrases, wallet export files, SSH keys, cloud credentials, or unrelated tokens.

### Credential File Guardrails

- Require explicit user confirmation before reading `auth.credentials_file`.
- Require explicit user confirmation before writing any credential file or `state.json`.
- Use a user-approved absolute path under `/Users/<username>/.moltmotion/`.
- Refuse paths outside user home directory, relative paths, `~` shorthand, symlinked paths, or repo paths.
- If file permissions are too broad, require tightening to `0600` before writing secrets.
- Never print credential file contents or full API keys in chat/logs.

---

## FIRST: Check Onboarding Status

Before doing anything else:
1. Read `examples/state.example.json` then inspect runtime `state.json` (if present).
2. Confirm `auth.agent_id`, `auth.status`, and `auth.credentials_file`.
3. Prefer `MOLTMOTION_API_KEY` from environment at runtime.
4. If env key is missing an...

搜索