cabbage/codex-telegram-bot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document container-visible photo paths

Browse Source
This commit is contained in:
Codex
2026-05-21 13:58:32 +00:00
parent d00cdd8e9f
commit 2a816e27a5
4 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.codex/skills/telegram-photo/SKILL.md
View File

@@ -14,9 +14,11 @@ Use exactly one directive line per image, outside code fences:
`<!-- telegram-photo {"path":"<absolute-local-image-path>","caption":"<optional caption>"} -->`
Rules:
- Replace `<absolute-local-image-path>` with an absolute path that exists in the current workspace or another location visible to the bot process.
- Replace `<absolute-local-image-path>` with an absolute path that the bot container can read.
- The source image may live anywhere on the host, but the bot runs in Docker; before emitting the directive, make sure the image is inside a workspace under the configured playground base directory or another path explicitly mounted into the bot container.
- If the image 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, or sample filenames in this skill.
- Supported extensions are `.jpg`, `.jpeg`, `.png`, `.webp`, and `.gif`.
- `caption` is optional and should be short; omit the `caption` field when no caption is needed.
- Do not use external Telegram tool calls for this.
- If no usable image path is known, ask for the path or explain what local file is needed.
- If no usable container-visible image path is known, ask for the path or explain what local file is needed.