leak-publish_skill

Overview

This skill publishes a local file behind an x402 payment gate using a preinstalled leak CLI. It supports local-only or explicit public exposure, runs the publish workflow in the background by default, and reports supervisor control details after launch. Safety checks and explicit confirmations protect sensitive paths and accidental public releases.

How this skill works

The skill validates the provided file path, price, sale window, and payout address, then invokes the leak CLI with appropriate flags. By default it uses an automatic detached run mode and prefers available supervisors (systemd --user, launchd, tmux, screen, or nohup) to keep the process alive. If the user opts into public exposure, the skill requires an additional explicit confirmation before adding --public.

When to use it

• You need to sell a local file behind an x402 payment gate with a timed sale window.
• You want the publish process to persist after logout or terminal exit.
• You need to decide between local-only distribution and explicit public exposure.
• You require a background supervisor to manage a long-running leak CLI process.
• You want automatic safety checks to prevent exposing sensitive system paths.

Best practices

• Confirm the exact file path when prompted and avoid symlinks or directories.
• Choose public exposure only after typing the explicit confirmation phrase.
• Provide a valid USDC price, sale window, and a correct --pay-to payout address.
• Ensure the leak binary is installed and on PATH before running the workflow.
• Prefer systemd --user on Linux or launchd on macOS for robust background supervision.

Example use cases

• Publish a single binary to sell for 0.01 USDC for a 15-minute sale window while keeping the process running under systemd --user.
• Run a local-only sale for a confidential asset with the process detached via tmux or screen.
• Expose an asset publicly after team approval by re-running with explicit --public consent.
• Smoke-check the persistent runner to verify supervisor selection and logging before a real sale.
• Back up and archive previously published sale metadata while the leak process runs in the background.