القائمة
Send files to the user via Telegram. Use when the user asks you to send, share, or deliver a file to them.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | telegram-send |
| description | Send files to the user via Telegram. Use when the user asks you to send, share, or deliver a file to them. |
| ui | telegram |
When you need to send a file to the user, include this marker in your response:
[[telegram:send:/absolute/path/to/file]]
The Telegram frontend detects this pattern, strips it from the displayed message, and sends the file as a Telegram document attachment.
User: "Create a Python script and send it to me"
Here's the script I created.
[[telegram:send:/tmp/hello.py]]
User: "Send me my bashrc"
Here's your bashrc file:
[[telegram:send:/home/drew/.bashrc]]
[[telegram:send:...]] markersImplement a plan from a PR, or fix review findings / CI failures. Usage: mach6-implement 42 [finding-numbers] or mach6-implement 42 ci
Commit changes, push to remote, and post a progress comment on the associated PR or issue. Stages files by name (never git add -A), matches existing commit style, auto-detects PR from branch. Usage: mach6-push [optional commit message]
Run specialized review agents in parallel on a PR (code-reviewer, error-auditor, test-reviewer, completeness-checker, simplifier), post findings, then independently assess each finding to separate genuine issues from nitpicks and false positives. Usage: mach6-review 42 [aspects]
Assess an existing GitHub issue (explore codebase, identify scope/risks/ambiguities, post assessment) or create a new structured issue. Usage: mach6-issue 42 (assess) or mach6-issue (create) or mach6-issue <description> (create with context)
Explore codebase, create implementation plan, create feature branch with dummy commit, open draft PR, post plan as PR comment. Everything lives on the PR from this point forward. Usage: mach6-plan 42
Pre-merge checks, version bump, merge PR, git tag, GitHub release. Version bump happens BEFORE merge (on the feature branch) because master requires PRs. Usage: mach6-publish 42