ocft_skill

This skill enables secure, chunked P2P file transfers between AI agents over chat channels with IPFS fallback for large files.

Python

2.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill ocft

_meta.json466 B
README.md5.0 KB
SKILL.md3.5 KB

Overview

This skill implements a peer-to-peer file transfer protocol for AI agents and bots operating over text message channels. It enables chunked, resumable transfers with integrity checks and a trusted-peer model, plus an IPFS fallback for very large files. The implementation is Python-friendly and designed to work over Telegram, Discord, Slack, or any text-based channel that can carry encoded messages.

How this skill works

The skill wraps file data into Base64-encoded JSON messages prefixed for easy detection, then sends 48KB chunks over the channel. Each chunk and the final file include SHA-256 hashes so receivers can verify integrity and resume interrupted transfers. Peers are managed with secrets and optional TTLs to enforce trust; when files exceed a configurable threshold, the skill can upload to IPFS via a configured provider and share the CID instead.

When to use it

Send files between autonomous agents over chat channels (Telegram, Discord, Slack, etc.)
Establish trusted, auditable P2P file sharing between bots
Transfer large files with chunking and automatic resume support
Fallback to IPFS when channel limits or size constraints block direct transfers
Share files where integrity verification and explicit acceptance is required

Best practices

Register and share peer connection URIs rather than raw secrets for safer onboarding
Set sensible max file size and IPFS threshold based on your channel’s message limits
Use short TTLs for temporary trusts and extend only for long-lived partnerships
Enable integrity checks and resume to handle flaky networks or rate limits
Configure an IPFS provider (Pinata, Filebase, or Kubo) if you expect many large transfers

Example use cases

A set of assistants exchanging datasets or model artifacts through a Slack workspace using trusted peers
A Telegram bot sending log archives to a maintenance agent, resuming after interruptions
Automated backup of agent-generated reports to IPFS when files exceed direct transfer limits
A research cluster sharing checkpoint files peer-to-peer with explicit accept/auto-accept policies

FAQ

Peers exchange a node ID and secret. Secrets can have a TTL and are stored in a trusted-peer whitelist; matching secrets establish trust before transfers begin.

What happens with very large files?

Files above the configured IPFS threshold are uploaded to a configured IPFS provider and the receiving peer gets a content identifier (CID) to fetch the file, avoiding excessive message chunking.