clawdlink
Encrypted Clawdbot-to-Clawdbot messaging. Send messages to friends' Clawdbots with end-to-end encryption.
Best use case
clawdlink is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Encrypted Clawdbot-to-Clawdbot messaging. Send messages to friends' Clawdbots with end-to-end encryption.
Teams using clawdlink should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/clawdlink/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clawdlink Compares
| Feature / Agent | clawdlink | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Encrypted Clawdbot-to-Clawdbot messaging. Send messages to friends' Clawdbots with end-to-end encryption.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ClawdLink
Encrypted peer-to-peer messaging between Clawdbots via central relay.
## Installation
```bash
cd ~/clawd/skills/clawdlink
npm install
node scripts/install.js # Adds to HEARTBEAT.md
node cli.js setup "Your Name"
```
## Quick Start for Clawdbot
Use the handler for JSON output:
```bash
node handler.js <action> [args...]
```
### Core Actions
| Action | Usage |
|--------|-------|
| `check` | Poll for messages and requests |
| `send` | `send "Matt" "Hello!" [--urgent] [--context=work]` |
| `add` | `add "clawdlink://..."` |
| `accept` | `accept "Matt"` |
| `link` | Get your friend link |
| `friends` | List friends |
| `status` | Get status |
### Preference Actions
| Action | Usage |
|--------|-------|
| `preferences` | Show all preferences |
| `quiet-hours` | `quiet-hours on` / `quiet-hours 22:00 08:00` |
| `batch` | `batch on` / `batch off` |
| `tone` | `tone casual` / `tone formal` / `tone brief` |
## Delivery Preferences
Users control how they receive messages:
### Quiet Hours
```bash
node handler.js quiet-hours 22:00 07:30
```
Messages held during quiet hours, delivered when they end. Urgent messages still come through.
### Batch Delivery
```bash
node handler.js batch on
node handler.js preferences set schedule.batchDelivery.times '["09:00","18:00"]'
```
Non-urgent messages batched and delivered at set times.
### Communication Tone
```bash
node handler.js tone casual
```
Options: `natural`, `casual`, `formal`, `brief`
### Per-Friend Settings
```bash
node handler.js preferences set friends."Sophie Bakalar".priority high
node handler.js preferences set friends."Sophie Bakalar".alwaysDeliver true
```
## Message Metadata
When sending, include context:
```bash
node handler.js send "Sophie" "Need to discuss budget" --urgent --context=work
```
Options:
- `--urgent` — Bypasses quiet hours and batching
- `--fyi` — Low priority, always batchable
- `--context=work|personal|social` — Helps with batching decisions
## Conversation Patterns
### Setting preferences
**User:** "Set quiet hours from 10pm to 8am"
**Action:** `node handler.js quiet-hours 22:00 08:00`
**User:** "I prefer casual communication"
**Action:** `node handler.js tone casual`
**User:** "Batch my ClawdLink messages and deliver at 9am and 6pm"
**Action:**
```bash
node handler.js batch on
node handler.js preferences set schedule.batchDelivery.times '["09:00","18:00"]'
```
**User:** "Always let messages from Sophie through"
**Action:** `node handler.js preferences set friends."Sophie".alwaysDeliver true`
### Sending with context
**User:** "Tell Matt I need the files urgently"
**Action:** `node handler.js send "Matt" "I need the files" --urgent --context=work`
## Preferences Schema
```json
{
"schedule": {
"quietHours": { "enabled": true, "start": "22:00", "end": "08:00" },
"batchDelivery": { "enabled": false, "times": ["09:00", "18:00"] },
"timezone": "America/Los_Angeles"
},
"delivery": {
"allowUrgentDuringQuiet": true,
"summarizeFirst": true,
"includeContext": true
},
"style": {
"tone": "natural",
"greetingStyle": "friendly"
},
"friends": {
"Sophie Bakalar": { "priority": "high", "alwaysDeliver": true }
}
}
```
## Data Storage
`~/.clawdbot/clawdlink/`
- `identity.json` — Keypair
- `config.json` — Display name
- `friends.json` — Friends with shared secrets
- `preferences.json` — Delivery preferences
- `held_messages.json` — Messages waiting for delivery
- `pending_requests.json` — Friend requests
## Auto-Polling
`heartbeat.js` runs on each Clawdbot heartbeat:
- Polls relay for messages/requests
- Applies delivery preferences
- Holds messages during quiet hours
- Delivers batched messages at scheduled times
- Outputs formatted text when there's something to deliver
## Security
- **E2E encrypted** — XChaCha20-Poly1305
- **Ed25519 signatures** — Sender verification
- **X25519 key exchange** — Shared secrets
- **7-day TTL** — Messages auto-expireRelated Skills
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names
polymarket
Trade prediction markets on Polymarket. Analyze odds, place bets, track positions, automate alerts, and maximize returns from event outcomes. Covers sports, politics, entertainment, and more.
polymarket-traiding-bot
No description provided.
polymarket-analysis
Analyze Polymarket prediction markets for trading edges. Pair Cost arbitrage, whale tracking, sentiment analysis, momentum signals, user profile tracking. No execution.
polymarket-agent
Autonomous prediction market agent - analyzes markets, researches news, and identifies trading opportunities
polymarket-5
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-4
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-3
Query Polymarket prediction market odds and events via CLI. Search for markets, get current prices, list events by category. Supports sports betting (NFL, NBA, soccer/EPL, Champions League), politics, crypto, elections, geopolitics. Real money markets = more accurate than polls. No API key required. Use when asked about odds, probabilities, predictions, or "what are the chances of X".
polymarket-2
Query Polymarket prediction markets - check odds, trending markets, search events, track prices.
pollinations
Pollinations.ai API for AI generation - text, images, videos, audio, and analysis. Use when user requests AI-powered generation (text completion, images, videos, audio, vision/analysis, transcription) or mentions Pollinations. Supports 25+ models (OpenAI, Claude, Gemini, Flux, Veo, etc.) with OpenAI-compatible chat endpoint and specialized generation endpoints.