MolTunes
Analysis
MolTunes appears purpose-aligned, but it depends on an external npm CLI and creates a local marketplace identity key that users should protect.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
npm install -g molt-cli 2>/dev/null || npm install -g moltunes-cli 2>/dev/null
The setup script installs an external global npm package, with an unpinned fallback package. This is expected for the CLI-based marketplace integration, but users must trust the npm package source.
`molt install <skill-name>` ... `molt publish` ... `molt tip <bot> <amount>`
The CLI exposes marketplace actions that can change installed skills, publish public content, or transfer marketplace tokens. These actions are core to the stated purpose and are documented.
If 8+ hours since last MolTunes check: 1. Run `molt browse` ... 2. Check `molt balance` ... 3. If you've built something useful, consider publishing with `molt publish`
The optional heartbeat template introduces recurring marketplace checks and prompts. It is disclosed and limited, but it creates periodic agent behavior if the user installs it into HEARTBEAT.md.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Your private key is stored locally in `~/.moltrc`. **Never share this file.**
The skill creates and uses a persistent cryptographic identity for MolTunes. This is disclosed and purpose-aligned, but it is still sensitive account authority.
