Skill

send-file

Use when you need to send a file to a relay session.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin agent-relay

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Upload a file to the relay blob store and attach it to a session message in one operation.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitMay 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Send File

Upload a file to the relay blob store and attach it to a session message in one operation.

When to use

Sharing logs, config files, or reports between agents

Sending binary or large-ish data (up to the relay's blob limits)

Including files in a coordinated workflow

Inputs to gather

Local file path to upload

Session name or ID

Optional message text to accompany the file (e.g., "See attached log")

Procedure

Validate that the file exists and is readable.

Call upload_blob with the local file path; receive the sha256 hash.

Call attach_blob with the session_id, sha256, filename, and guessed MIME type.

Optionally call send_message with a short description (e.g., "Attached: log.txt").

Display the sha256, file size, and resulting message cursor to the user.

Output / side effects

File stored in the relay blob store at ${sha256}.

Blob attached to the session as a named reference.

Session participants can download via download_blob using the sha256.

Local cursor advanced (if message sent).

Safety / constraints

Files are stored in plaintext on the relay; assume trust and LAN scope.

Blob storage is content-addressed; duplicate file uploads reuse existing blobs.

Large files may impact relay memory; document recommended limits or offer streaming download option.

Send File

Upload a file to the relay blob store and attach it to a session message in one operation.

When to use

Sharing logs, config files, or reports between agents
Sending binary or large-ish data (up to the relay's blob limits)
Including files in a coordinated workflow

Inputs to gather

Local file path to upload
Session name or ID
Optional message text to accompany the file (e.g., "See attached log")

Procedure

Validate that the file exists and is readable.
Call upload_blob with the local file path; receive the sha256 hash.
Call attach_blob with the session_id, sha256, filename, and guessed MIME type.
Optionally call send_message with a short description (e.g., "Attached: log.txt").
Display the sha256, file size, and resulting message cursor to the user.

Output / side effects

File stored in the relay blob store at ${sha256}.
Blob attached to the session as a named reference.
Session participants can download via download_blob using the sha256.
Local cursor advanced (if message sent).

Safety / constraints

Files are stored in plaintext on the relay; assume trust and LAN scope.
Blob storage is content-addressed; duplicate file uploads reuse existing blobs.
Large files may impact relay memory; document recommended limits or offer streaming download option.