How do I install the Kasia skill?

Run npx skillmds@latest add johnalbertini14-glitch/kasia in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kasia safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kasia?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kasia free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

johnalbertini14-glitch (@johnalbertini14-glitch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kasia by johnalbertini14-glitch — Agent Skill

Name: Kasia
Rating: 4.2 (5 reviews)
Author: johnalbertini14-glitch

Kasia

Send and receive encrypted on-chain messages on the Kaspa blockchain using the Kasia protocol. Use when a user asks to message someone on Kaspa/Kasia, check Kasia conversations, read encrypted messages, send payments with messages, or manage Kasia handshakes. Requires kasia-mcp and kaspa-mcp servers configured in mcporter.

johnalbertini14-glitch Updated Sep 21, 2026 1 repo stars

File contents

Kasia — Encrypted Messaging on Kaspa

Send and receive encrypted messages on the Kaspa blockchain via the Kasia protocol. Uses mcporter to call kasia-mcp tools.

Prerequisites

mcporter installed (npm install -g mcporter)
kasia-mcp built and configured in config/mcporter.json
kaspa-mcp configured (same wallet) — needed to broadcast transactions
Wallet mnemonic or private key set in mcporter config

Run scripts/setup.sh to configure automatically:

scripts/setup.sh /path/to/kasia-mcp --mnemonic "your twelve word phrase" --network mainnet

Verify: mcporter list kasia (should show 8 tools)

Tools

Call via mcporter call kasia.<tool> from the workspace directory.

Read Operations (no transaction needed)

Tool	Purpose	Example
`kasia_get_conversations`	List all conversations + status	`mcporter call kasia.kasia_get_conversations`
`kasia_get_requests`	Pending incoming handshakes	`mcporter call kasia.kasia_get_requests`
`kasia_get_messages`	Read decrypted messages	`mcporter call kasia.kasia_get_messages address="kaspa:q..."`
`kasia_read_self_stash`	Read encrypted private data	`mcporter call kasia.kasia_read_self_stash scope="notes"`

Write Operations (two-step: generate payload → broadcast)

Write tools return a payload and instructions. Broadcast with kaspa.send_kaspa:

# Step 1: Generate payload
mcporter call kasia.kasia_send_handshake address="kaspa:q..."
# Returns: { action, to, amount, payload, instructions }

# Step 2: Broadcast (use the returned values)
mcporter call 'kaspa.send_kaspa(to: "kaspa:q...", amount: "0.2", payload: "<hex>")'

Tool	Purpose
`kasia_send_handshake`	Start a conversation with someone
`kasia_accept_handshake`	Accept an incoming handshake request
`kasia_send_message`	Send an encrypted message in an active conversation
`kasia_write_self_stash`	Store encrypted private data on-chain

Conversation Flow

Check requests: kasia_get_requests — see pending incoming handshakes
Start or accept: kasia_send_handshake or kasia_accept_handshake → broadcast with kaspa.send_kaspa
Chat: kasia_send_message → broadcast. Read replies with kasia_get_messages
Pay: Use kaspa.send_kaspa directly for payments (no Kasia-specific tool needed)

Conversation Status

pending_outgoing — You sent a handshake, waiting for acceptance
pending_incoming — Someone sent you a handshake, needs acceptance
active — Both sides completed handshake, can exchange messages

Background Polling

For real-time message relay, set up a background poller:

Create a polling script that calls kasia_get_messages every N seconds
Track seen transaction IDs to avoid duplicates
Write new messages to a file (e.g., memory/kasia-new-messages.jsonl)
Use a cron job or heartbeat check to relay new messages to the user

See references/protocol.md for the full protocol specification and indexer API details.

Important

Mainnet only — kasia-mcp enforces mainnet (messaging isn't available on testnet)
Two-step writes — Write tools generate payloads; you must broadcast with kaspa.send_kaspa
Same wallet — kasia-mcp and kaspa-mcp must use the same mnemonic/key
Costs KAS — Every message is a transaction (~0.2 KAS minimum per tx)

---name: kasiadescription: Send and receive encrypted on-chain messages on the Kaspa blockchain using the Kasia protocol. Use when a user asks to message someone on Kaspa/Kasia, check Kasia conversations, read encrypted messages, send payments with messages, or manage Kasia handshakes. Requires kasia-mcp and kaspa-mcp servers configured in mcporter.---# Kasia — Encrypted Messaging on KaspaSend and receive encrypted messages on the Kaspa blockchain via the Kasia protocol. Uses `mcporter` to call kasia-mcp tools.## Prerequisites- `mcporter` installed (`npm install -g mcporter`)- `kasia-mcp` built and configured in `config/mcporter.json`- `kaspa-mcp` configured (same wallet) — needed to broadcast transactions- Wallet mnemonic or private key set in mcporter configRun `scripts/setup.sh` to configure automatically:```bashscripts/setup.sh /path/to/kasia-mcp --mnemonic "your twelve word phrase" --network mainnet```Verify: `mcporter list kasia` (should show 8 tools)## ToolsCall via `mcporter call kasia.<tool>` from the workspace directory.### Read Operations (no transaction needed)| Tool | Purpose | Example ||------|---------|---------|| `kasia_get_conversations` | List all conversations + status | `mcporter call kasia.kasia_get_conversations` || `kasia_get_requests` | Pending incoming handshakes | `mcporter call kasia.kasia_get_requests` || `kasia_get_messages` | Read decrypted messages | `mcporter call kasia.kasia_get_messages address="kaspa:q..."` || `kasia_read_self_stash` | Read encrypted private data | `mcporter call kasia.kasia_read_self_stash scope="notes"` |### Write Operations (two-step: generate payload → broadcast)Write tools return a payload and instructions. Broadcast with `kaspa.send_kaspa`:```bash# Step 1: Generate payloadmcporter call kasia.kasia_send_handshake address="kaspa:q..."# Returns: { action, to, amount, payload, instructions }# Step 2: Broadcast (use the returned values)mcporter call 'kaspa.send_kaspa(to: "kaspa:q...", amount: "0.2", payload: "<hex>")'```| Tool | Purpose ||------|---------|| `kasia_send_handshake` | Start a conversation with someone || `kasia_accept_handshake` | Accept an incoming handshake request || `kasia_send_message` | Send an encrypted message in an active conversation || `kasia_write_self_stash` | Store encrypted private data on-chain |## Conversation Flow1. **Check requests**: `kasia_get_requests` — see pending incoming handshakes2. **Start or accept**: `kasia_send_handshake` or `kasia_accept_handshake` → broadcast with `kaspa.send_kaspa`3. **Chat**: `kasia_send_message` → broadcast. Read replies with `kasia_get_messages`4. **Pay**: Use `kaspa.send_kaspa` directly for payments (no Kasia-specific tool needed)## Conversation Status- `pending_outgoing` — You sent a handshake, waiting for acceptance- `pending_incoming` — Someone sent you a handshake, needs acceptance- `active` — Both sides completed handshake, can exchange messages## Background PollingFor real-time message relay, set up a background poller:1. Create a polling script that calls `kasia_get_messages` every N seconds2. Track seen transaction IDs to avoid duplicates3. Write new messages to a file (e.g., `memory/kasia-new-messages.jsonl`)4. Use a cron job or heartbeat check to relay new messages to the userSee `references/protocol.md` for the full protocol specification and indexer API details.## Important- **Mainnet only** — kasia-mcp enforces mainnet (messaging isn't available on testnet)- **Two-step writes** — Write tools generate payloads; you must broadcast with `kaspa.send_kaspa`- **Same wallet** — kasia-mcp and kaspa-mcp must use the same mnemonic/key- **Costs KAS** — Every message is a transaction (~0.2 KAS minimum per tx)

Frequently asked questions