receive-secret

Receive P2P encrypted secrets from URLs and save them to files.

2|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/danwag06/send-secret --skill receive-secret
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receive-secret
Source: https://github.com/danwag06/send-secret/tree/main/skills/receive-secret
Command: npx skills add https://github.com/danwag06/send-secret --skill receive-secret

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Receive P2P encrypted secrets from send-secret links and save them to files, keeping sensitive content out of the agent's context.

Core Features & Use Cases

  • Secure reception: secrets decrypt and write to a local file on disk, never exposing content to the agent.
  • Controlled persistence: secrets are saved to a user-specified filename using the -o flag, not displayed or read back by the agent.
  • Workflow safety: ensures the filename is a real file path and uses dedicated storage rather than ephemeral stdout.

Quick Start

Save a received secret to a specific filename using the -o flag.

Frequently Asked Questions about receive-secret

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I receive an encrypted secret from a URL and save it to a file without exposing the content?

To receive an encrypted secret, use the -r flag to pass the URL and the -o flag to specify the output filename. This decrypts the P2P secret directly to disk, preventing any content disclosure to the agent context.

Why does the saved secret not appear in the agent's output when using a receive link?

The secret does not appear because the workflow enforces content safety by never printing secrets to stdout. It requires a dedicated file path for persistence, ensuring sensitive data is never read back into the agent's context.

Can I retrieve a P2P encrypted file and print the contents directly to the console?

No, you cannot print contents directly to the console. The process enforces workflow safety by requiring an explicit file path using the -o flag, preventing ephemeral stdout output and protecting sensitive content from exposure.

What is needed to decrypt a send-secret link and persist the data locally?

You need the specific send-secret URL provided via the -r input flag and a valid local file path designated by the -o output flag. This ensures the received encrypted secret is safely persisted to disk without agent disclosure.

Does receiving a secret over trycloudflare require specific filename arguments?

Yes, receiving a secret requires the -o flag to enforce a real file path for the saved data. This controlled persistence ensures secrets are written to a user-specified filename rather than being displayed or read back by the agent.