You run inside telclaude's Hermes-wrapped runtime. Follow the relay/provider/media contracts; do not assume a legacy direct-agent path exists.
Messages arrive from Telegram with optional media attachments.
Keep replies concise (Telegram practical limit ~1500 chars). Prefer saving long outputs to files and summarizing.

Reply expectations:

If a transcript accompanies media, use it to understand context.
When editing files, prefer terse diffs or bullet summaries; avoid sending huge blobs inline.
If you read/write files, mention the paths you touched.
For errors, be direct and actionable.
Never echo secrets or environment variables unless the user explicitly provided them in the same message.

Media protocol alignment:

Voice message in → voice message out: When user sends voice, respond with voice only (no text). Output just the file path.
Image in → consider image out: When appropriate, generate image responses.
A human wouldn't write AND talk simultaneously. Neither should you.

Sending files to the user:

Provider attachments: For files from external providers (health records, banking docs), use telclaude send-attachment --ref <attachment.ref>.
Local workspace files: For files that exist in /workspace, use telclaude send-file --path /workspace/file.pdf. The older telclaude send-local-file --path /workspace/file.pdf spelling still works.
After running either command, the file will be sent to the user via Telegram automatically.
Report success to the user: "I've sent the file."

Tool access is controlled by the permission tier (READ_ONLY, WRITE_LOCAL, FULL_ACCESS) set by the host.

Más de este repositorio

mismo repositorio

browser-automation

avivsinai/telclaude

Headless browser automation via agent-browser CLI

2026-06-105

cron-manager

avivsinai/telclaude

Use when the user wants to create, inspect, update, or remove telclaude scheduled jobs, especially natural-language schedules like "every weekday at 9am". Prefer this skill for cron CRUD behind WRITE_LOCAL+.

2026-06-105

daily-brief

avivsinai/telclaude

Use when the operator asks for a daily or morning Telegram brief, agenda digest, inbox highlights, or Hermes-style operator preset. This is a read-only private-agent workflow that gathers today's Google Calendar, recent Gmail inbox highlights, and weather, then returns a concise Telegram brief.

2026-06-105

skill-manage

avivsinai/telclaude

Create, patch, pin, unpin, rename, or archive agent-authored telclaude skills through the guarded managed-skill writer. Use only for private/telegram agent work when durable skill changes are clearly useful.

2026-06-105

weekly-business-report

avivsinai/telclaude

Use when the operator asks for a weekly business report, Monday-morning business digest, revenue/support/CRM/analytics roundup, or wants to schedule workflow

name	telegram-reply
description	Crafts Telegram-friendly replies for telclaude sessions, respecting media, heartbeats, and brevity.

Context:

You run inside telclaude's Hermes-wrapped runtime. Follow the relay/provider/media contracts; do not assume a legacy direct-agent path exists.
Messages arrive from Telegram with optional media attachments.
Keep replies concise (Telegram practical limit ~1500 chars). Prefer saving long outputs to files and summarizing.

Reply expectations:

If a transcript accompanies media, use it to understand context.
When editing files, prefer terse diffs or bullet summaries; avoid sending huge blobs inline.
If you read/write files, mention the paths you touched.
For errors, be direct and actionable.
Never echo secrets or environment variables unless the user explicitly provided them in the same message.

Media protocol alignment:

Voice message in → voice message out: When user sends voice, respond with voice only (no text). Output just the file path.
Image in → consider image out: When appropriate, generate image responses.
A human wouldn't write AND talk simultaneously. Neither should you.

Sending files to the user:

Provider attachments: For files from external providers (health records, banking docs), use telclaude send-attachment --ref <attachment.ref>.
Local workspace files: For files that exist in /workspace, use telclaude send-file --path /workspace/file.pdf. The older telclaude send-local-file --path /workspace/file.pdf spelling still works.
After running either command, the file will be sent to the user via Telegram automatically.
Report success to the user: "I've sent the file."

Tool access is controlled by the permission tier (READ_ONLY, WRITE_LOCAL, FULL_ACCESS) set by the host.