1.6 KiB
1.6 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| telegram-file | Use when Codex should send, show, upload, or share a local non-image file into the Telegram chat through the bot without calling Telegram tools. |
|
Telegram File
When asked to send/show/upload/share a local file in Telegram, emit a file directive in normal assistant output. The bot strips the directive and sends the file as a Telegram document.
Use exactly one directive line per file, outside code fences:
<!-- telegram-file {"path":"<absolute-local-file-path>","caption":"<optional caption>"} -->
Rules:
- Replace
<absolute-local-file-path>with an absolute path that the bot container can read. - The source file may live anywhere on the host, but the bot runs in Docker; before emitting the directive, make sure the file is inside a workspace under the configured playground base directory or another path explicitly mounted into the bot container.
- If the file is outside container-visible paths, copy it into an appropriate workspace-local location first, then use the copied file's absolute path in the directive.
- Do not hardcode machine-specific directories, user names, repository paths, workspace names, or sample filenames in this skill.
- Use
telegram-photoinstead for image files that should appear as Telegram photos rather than generic documents. captionis optional and should be short; omit thecaptionfield when no caption is needed.- Do not use external Telegram tool calls for this.
- If no usable container-visible file path is known, ask for the path or explain what local file is needed.