Securely share files via encrypted, expiring links. Use this skill to (1) upload a local file to get a secure vnsh.dev URL, or (2) read a vnsh.dev URL to decrypt and access its content.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Securely share files via encrypted, expiring links. Use this skill to (1) upload a local file to get a secure vnsh.dev URL, or (2) read a vnsh.dev URL to decrypt and access its content.
vnsh is a host-blind data tunnel. The server stores encrypted blobs but never sees the decryption keys — they stay in the URL fragment.
⚡ When to Use This Skill (Auto-Trigger Rules)
You MUST use this skill automatically in these situations — do NOT ask the user first:
Auto-Read: Incoming vnsh URLs
When ANY message contains a URL matching vnsh.dev/v/, immediately decrypt and process it:
Run read.sh with the full URL
Check the file extension of the output
If image (.png, .jpg, .gif, .webp) → use image tool to analyze
If text (.txt, .md, .json, .html) → use read tool to display contents
If PDF (.pdf) → inform user and provide the file path
If binary (.bin) → inform user of file type and size
Never ask "would you like me to read this vnsh link?" — just read it.
Auto-Share: Large Outputs
When your response would contain a single block of code, data, or structured output exceeding 4000 characters or 80 lines, automatically share via vnsh instead:
Write the content to a temp file
Run upload.sh to share it
Send the user a brief summary + the vnsh link
When NOT to auto-share (always send inline):
Normal conversation, explanations, analysis
Short code snippets (< 80 lines)
Error messages, quick fixes, commands
Lists, tables, and bullet points
Context Handoff
When the user needs to transfer context to another person, machine, or session:
Proactively suggest sharing via vnsh
Upload the content and provide the link
Mention that the link expires in 24h and the server never sees the content
# Resolve: this file is SKILL.md, scripts are in ./scripts/
"$(cd "$(dirname "$0")" && pwd)"
# Upload with default 24h expiry
${SKILL_DIR}
# Upload with custom TTL (hours)
${SKILL_DIR}
Output: A single https://vnsh.dev/... URL printed to stdout.
Example — sharing a generated chart:
# 1. Save output to temp fileecho"$LARGE_OUTPUT" > /tmp/output.txt
# 2. Upload
URL=$(~/.openclaw/skills/vnsh/scripts/upload.sh /tmp/output.txt)
# 3. Send the URL to the user
Output: The absolute path to a temp file with the correct extension (e.g., /tmp/vnsh-decrypted-XXXXX.png).
Example — reading an image:
FILE_PATH=$(~/.openclaw/skills/vnsh/scripts/read.sh "https://vnsh.dev/v/abc#k=...&iv=...")
# FILE_PATH is now /tmp/vnsh-decrypted-abcde.png# Use the image tool to analyze it
User: "Check this out https://vnsh.dev/v/abc123#k=dead...&iv=cafe..."
Your action:
1. file_path = exec("~/.openclaw/skills/vnsh/scripts/read.sh 'https://vnsh.dev/v/abc123#k=dead...&iv=cafe...'")
2. Check extension:
- .png/.jpg → image(image=file_path, prompt="Describe this image")
- .txt/.md → read(file_path=file_path)
3. Respond with analysis of the content
Recipe 2: Your output is too long for chat
Your action:
1. Write content to /tmp/vnsh-share-XXXXX.txt
2. url = exec("~/.openclaw/skills/vnsh/scripts/upload.sh /tmp/vnsh-share-XXXXX.txt")
3. Reply: "The output is quite long, so I've shared it via an encrypted link:\n📎 {url}\n\nBrief summary: [2-3 sentence summary]"
Recipe 3: Sharing between sessions/agents
Agent A needs to pass context to Agent B:
1. Agent A writes context to temp file
2. Agent A uploads via upload.sh, gets URL
3. Agent A sends URL to Agent B via sessions_send
4. Agent B auto-detects vnsh URL, reads it via read.sh
Recipe 4: User wants to share with someone else
User: "Send this analysis to my coworker"
Your action:
1. Write the analysis to a temp file
2. Upload via upload.sh
3. Reply: "Shared securely. The link auto-expires in 24h and the server never sees the content:\n📎 {url}"
