leak-publish

What This Skill Does

The leak-publish skill provides a secure, streamlined interface for agents to publish local files behind x402 payment gates. By leveraging the preinstalled 'leak' CLI, this skill enables creators and developers to monetize their digital assets directly from their local environment. It manages the entire lifecycle of a file publication, from validating the file structure and ensuring path security to handling the detached supervisor processes that keep the payment gate open across sessions. The skill strictly adheres to a safety-first architecture, requiring explicit user confirmation for sensitive operations like public exposure, and implementing a blocklist of restricted system paths to prevent accidental data leakage from configuration or system directories.

Installation

To add this capability to your agent environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/eucalyptus-viminalis/leak-publish

Ensure that the 'leak' binary is present on your system PATH before initialization. This skill is designed to operate on existing infrastructure and does not perform dynamic package installation at runtime, maintaining a lean and predictable execution environment.

Use Cases

• Monetizing Research Assets: Securely share proprietary datasets or model weights with verified buyers via x402 payment requirements.
• Digital Content Sales: Automate the sale of premium documents, artwork, or software binaries directly from your local storage.
• Access-Controlled Distribution: Host files that are only accessible for a specific duration or window, perfect for time-limited drops or exclusive content releases.

Example Prompts

1. "Publish my report at ./data/Q4_analysis.pdf for 0.05 USDC to 0x123...abc, keep it private, and use a 24-hour sale window."
2. "I want to list ./build/artifact.zip on the market for 0.1 USDC. Please use the public exposure option and set the payout to my wallet address 0xabc...123."
3. "Check the status of my active leak-publish sessions and provide me with the stop command for the latest file I uploaded."

Tips & Limitations

• Safety First: Always verify your file path before confirming. The skill will reject any symlinks, directories, or attempts to access system-sensitive folders like ~/.ssh or /etc.
• Persistence: The skill automatically attempts to use robust supervisors (systemd, launchd, tmux, or screen) to ensure the payment gate remains active. If these are unavailable, it falls back to nohup.
• Public Consent: Public exposure requires an additional layer of confirmation. Ensure you are ready for the asset to be indexed/discoverable when selecting the --public flag.
• Troubleshooting: If the 'leak' command is not found, install it via 'npm i -g leak-cli' to restore functionality.