CapTP: Capability Transfer Protocol
**Trit**: 0 (ERGODIC - transports capabilities without amplification)
Best use case
CapTP: Capability Transfer Protocol is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
**Trit**: 0 (ERGODIC - transports capabilities without amplification)
Teams using CapTP: Capability Transfer Protocol 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/captp/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How CapTP: Capability Transfer Protocol Compares
| Feature / Agent | CapTP: Capability Transfer Protocol | 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?
**Trit**: 0 (ERGODIC - transports capabilities without amplification)
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
# CapTP: Capability Transfer Protocol
**Trit**: 0 (ERGODIC - transports capabilities without amplification)
**Color**: #46F27F (Coordinator stream)
**Source**: Spritely Goblins (codeberg.org/spritely/goblins)
---
## Overview
CapTP (Capability Transfer Protocol) enables distributed object programming with capability security. Objects can live anywhere on the network; CapTP abstracts location so programmers focus on object interaction, not protocol architecture.
**Core principle**: Capabilities are unforgeable references. You can only invoke what you've been given.
---
## Key Concepts
### Vats (Actor Containers)
```scheme
;; Guile Goblins
(define vat (spawn-vat))
(define greeter (vat-spawn vat ^greeter))
```
| Concept | Description | Trit Mapping |
|---------|-------------|--------------|
| **Vat** | Transactional actor container | 0 (ergodic boundary) |
| **Actor** | Encapsulated object with behavior | +1 (generative) |
| **Capability** | Unforgeable reference | -1 (constraining) |
### Promise Pipelining
```scheme
;; Don't wait for result - pipeline through promises
(<- (<- alice 'get-friend) 'greet "Hello")
```
Reduces round-trips: send message to promise, network resolves.
### Sturdy vs Live References
| Reference | Persistence | Use Case |
|-----------|-------------|----------|
| **Live** | Session only | Active communication |
| **Sturdy** | Survives restart | Reconnection, storage |
---
## CapTP Message Types
```
op:deliver-only → Fire-and-forget message
op:deliver → Message expecting response
op:pick → Select from multiple promises
op:abort → Cancel pending operation
op:listen → Subscribe to updates
op:gc → Garbage collection hint
```
---
## GF(3) Triads
```
# Core CapTP Bundle
keychain-secure (-1) ⊗ captp (0) ⊗ gay-mcp (+1) = 0 ✓ [Secure Transport]
shadow-goblin (-1) ⊗ captp (0) ⊗ agent-o-rama (+1) = 0 ✓ [Distributed Actors]
polyglot-spi (-1) ⊗ captp (0) ⊗ pulse-mcp-stream (+1) = 0 ✓ [Cross-Lang Objects]
temporal-coalgebra (-1) ⊗ captp (0) ⊗ koopman-generator (+1) = 0 ✓ [State Observation]
# Goblins Integration
three-match (-1) ⊗ captp (0) ⊗ gay-mcp (+1) = 0 ✓ [Colored Capabilities]
sheaf-cohomology (-1) ⊗ captp (0) ⊗ operad-compose (+1) = 0 ✓ [Compositional]
```
---
## Implementation Bridge
### Mapping to Our Goblins
| Spritely | Our System | Function |
|----------|------------|----------|
| `spawn-vat` | `SplitMixTernary.new(seed)` | Create isolated generator |
| `<-` (send) | `next_color!` | Advance state, get result |
| `$` (call) | `color_at(idx)` | Synchronous access |
| Sturdy ref | `(seed, index)` tuple | Reconstructable reference |
| Promise | Derivation chain | Future state determined by seed |
### Ruby Integration
```ruby
require 'captp'
# Create vat (generator with transactional boundary)
vat = CapTP::Vat.new(seed: 0x42D)
# Spawn actor (color stream)
actor = vat.spawn(:color_stream)
# Send message (advance stream)
promise = actor.send(:next_color)
# Pipeline (derive without waiting)
result = actor.send(:palette, 5).then { |colors| colors.map(&:hex) }
```
### Scheme Integration (Hoot target)
```scheme
(use-modules (goblins) (goblins actor-lib cell))
;; Define actor constructor
(define (^color-stream bcom seed)
(define idx (spawn ^cell 0))
(lambda (method . args)
(case method
((next-color)
(let ((i ($ idx)))
($ idx (+ i 1))
(color-at seed i)))
((palette)
(map (lambda (i) (color-at seed i))
(iota (car args)))))))
;; Spawn in vat
(define stream (spawn ^color-stream 1069))
(<- stream 'next-color) ;; => promise of color
```
---
## Netlayers
| Layer | Transport | Use Case |
|-------|-----------|----------|
| **Tor Onion** | .onion addresses | Anonymous, censorship-resistant |
| **TCP Direct** | IP:port | Local network, low latency |
| **WebSocket** | wss:// | Browser-based (Hoot target) |
| **NATS** | nats:// | High-throughput pub/sub |
| **Tailscale** | 100.x.y.z | Mesh VPN, zero-config |
---
## Security Model
### Principle of Least Authority (POLA)
```
You can only:
1. Use capabilities you were given
2. Create new objects (that you then have caps to)
3. Introduce objects you have caps to, to each other
```
### Attenuation
```ruby
# Full capability
full_stream = vat.spawn(:color_stream, seed: 0x42D)
# Attenuated: read-only, no advance
read_only = full_stream.attenuate(:color_at)
# Attenuated: limited palette size
limited = full_stream.attenuate(:palette, max: 10)
```
---
## Commands
```bash
just captp-vat seed=1069 # Create vat with seed
just captp-spawn actor_type # Spawn actor in vat
just captp-send actor method # Send message
just captp-pipeline expr # Pipeline expression
just captp-sturdy actor # Get sturdy reference
```
---
## Related Skills
| Skill | Relation |
|-------|----------|
| **localsend-mcp** | P2P file transfer via CapTP-like protocol |
| **tailscale-file-transfer** | Mesh VPN netlayer |
| **keychain-secure** | Credential capabilities |
| **shadow-goblin** | Validates capability boundaries |
| **agent-o-rama** | Generates actor proposals |
---
## References
- [Spritely Goblins](https://spritely.institute/goblins/)
- [Racket Goblins Docs](https://docs.racket-lang.org/goblins/)
- [Heart of Spritely Whitepaper](https://files.spritely.institute/papers/spritely-core.html)
- [Hoot: Scheme on WebAssembly](https://spritely.institute/hoot/)
- [E Language (historical)](http://erights.org/)
---
**Skill Name**: captp
**Type**: Distributed Object Protocol
**Trit**: 0 (ERGODIC)
**GF(3)**: Transports capabilities without amplification
**Invariant**: Capabilities unforgeable, only invoke what you're givenRelated Skills
universal-captp-derivation
Universal CapTP Derivation Skill
trifurcated-transfer
Trifurcated Transfer Skill
social-emergence-protocol
Minimal interaction patterns that bootstrap complex social behaviors in distributed systems
protocol-reverse-engineering
Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocols, or debugging network communication.
protocol-evolution-markets
Prediction markets for protocol standard evolution. Bet on which specs survive, fork, or merge using multiverse finance and GF(3) fitness signals.
protocol-acset
Model decentralized protocols as attributed C-sets for compositional analysis, interoperability design, and protocol evolution. Apply categorical mathematics to P2P infrastructure.
performing-s7comm-protocol-security-analysis
Perform security analysis of Siemens S7comm and S7CommPlus protocols used by SIMATIC S7 PLCs to identify vulnerabilities including replay attacks, integrity bypass, unauthorized CPU stop commands, and program download manipulation exploiting weaknesses in S7-300, S7-400, S7-1200, and S7-1500 controllers.
performing-dns-enumeration-and-zone-transfer
Enumerates DNS records, attempts zone transfers, brute-forces subdomains, and maps DNS infrastructure during authorized reconnaissance to identify attack surface, misconfigurations, and information disclosure in target domains.
detecting-modbus-protocol-anomalies
This skill covers detecting anomalies in Modbus/TCP and Modbus RTU communications in industrial control systems. It addresses function code monitoring, register range validation, timing analysis, unauthorized client detection, and deep packet inspection for malformed Modbus frames. The skill leverages Zeek with Modbus protocol analyzers, Suricata IDS with OT rules, and custom Python-based detection using Markov chain models for normal Modbus transaction sequences.
detecting-dnp3-protocol-anomalies
Detect anomalies in DNP3 (Distributed Network Protocol 3) communications used in SCADA systems by monitoring for unauthorized control commands, firmware update attempts, protocol violations, and deviations from baseline traffic patterns using deep packet inspection and machine learning approaches.
tailscale-file-transfer
Tailscale mesh VPN file transfer with open games semantics (play/coplay) and bidirectional lens optics
zx-calculus
Coecke's ZX-calculus for quantum circuit reasoning via string diagrams with Z-spiders (green) and X-spiders (red)