fadnote

What This Skill Does

The FadNote skill for OpenClaw provides a robust mechanism for creating secure, self-destructing, and end-to-end encrypted notes. Designed for developers, privacy advocates, and team leads, this utility ensures that sensitive information—such as API keys, passwords, or confidential snippets—is never stored in plaintext on the server. When you invoke FadNote, the content is encrypted locally before being transmitted to the FadNote endpoint. Once the generated link is accessed, the note is immediately deleted from the host, ensuring that the information has a single "life cycle" and preventing unauthorized access through data breaches or log exposure.

Installation

Installation is streamlined through the ClawHub system. Simply execute claw install fadnote in your terminal to initialize the skill. For those requiring a manual configuration, clone the repository from the provided GitHub link, navigate to the openclaw-skill directory, and create a symbolic link from the fadnote.js script to your ~/.claw/bin/ folder. Ensure your system meets the Node.js 18+ runtime requirement to leverage the latest cryptographic libraries included in the build.

Use Cases

FadNote is ideal for secure credentials sharing during CI/CD setups, ephemeral configuration management, and ad-hoc collaboration where persistence is a security liability. It excels in environments where you need to share a token with a colleague but want to guarantee that the data cannot be recycled or re-accessed later. It is a vital tool for preventing "secret leakage" in collaborative chat environments like Slack or Discord.

Example Prompts

1. "Secure this API key for the staging server: sk-live-98765"
2. "FadNote this database password so I can share it with the backend team: pass123-admin"
3. "Create a secure link for these credentials: username=admin, password=secret!"

Tips & Limitations

By default, notes expire after 24 hours (86,400 seconds) if not read, but you can customize this duration using the --ttl flag. Note that since the encryption key is part of the URL fragment, you should be careful about where the link is pasted, as it remains visible in browser history until visited. Use the --json flag when building automated pipelines to parse the noteId and decryptionUrl programmatically.