What problem does it solve? When brain files are created or modified, recipients often receive only file paths or links instead of the actual document. This Skill enforces a mandatory rule: every brain file write is followed by delivering the real file as an attachment to both Telegram and Slack, eliminating broken links and missed deliveries. ## Core Features & Use Cases - Telegram attachment delivery: Include a MEDIA:/absolute/path line in the response so the Telegram gateway sends the file as a native attachment (supports .md, .png, .pdf, .csv, and more). - Slack 3-step upload flow: Uses files.getUploadURLExternal, raw byte upload, and files.completeUploadExternal since the legacy files.upload API is deprecated. - Edge case handling: Skips Slack for files over 20MB (offers a GDrive link instead), falls back to Telegram-only delivery when the Slack token is missing, and supports multiple files per operation. - Use Case: After writing a new person page via mcp_gbrain_put_page, the agent automatically attaches the Markdown file to the Telegram chat and uploads it to the Slack Admin DM, confirming both deliveries. ## Quick Start After writing any brain file, attach it to Telegram with a MEDIA: line and upload it to Slack using the slack-upload-brain-file.py script with the file path and channel ID.