Interactive Bot

Interactive Bot

Gmail Commander Telegram bot — slash commands for email access + AI-powered free-text routing.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

Mandatory Preflight

Step 1: Check Bot Script Exists

ls -la "$HOME/.claude/plugins/marketplaces/cc-skills/plugins/gmail-commander/scripts/bot.ts" 2>/dev/null || echo "SCRIPT_NOT_FOUND"

Step 2: Verify Environment

echo "TELEGRAM_BOT_TOKEN: ${TELEGRAM_BOT_TOKEN:+SET}"
echo "TELEGRAM_CHAT_ID: ${TELEGRAM_CHAT_ID:-NOT_SET}"
echo "GMAIL_OP_UUID: ${GMAIL_OP_UUID:-NOT_SET}"
echo "HAIKU_MODEL: ${HAIKU_MODEL:-NOT_SET}"

Bot Commands (Sidebar Menu)

Two-Tier Command System

Tier 1 — Deterministic: Slash commands call Gmail CLI directly.

Tier 2 — Intelligent: Free-text messages route through Agent SDK (Haiku) with 4 Gmail MCP tools (list, search, read, draft).

Safety Controls

• Mutex: 1 agent query at a time
• Timeout: 2-minute maximum per query
• Circuit Breaker: 3 failures in a row disables agent for 10 minutes
• Anti-contamination: Skill contamination detection on all agent responses
• Auth Guard: Only responds to authorized TELEGRAM_CHAT_ID

Running Manually

cd ~/own/amonic && bun run "$HOME/.claude/plugins/marketplaces/cc-skills/plugins/gmail-commander/scripts/bot.ts"

References

• command-reference.md — All commands with examples
• compose-flow.md — Multi-step compose/reply state machine
• display-patterns.md — Email rendering rules

Post-Change Checklist

• [ ] YAML frontmatter valid (no colons in description)
• [ ] Trigger keywords current
• [ ] Path patterns use $HOME not hardcoded paths

Post-Execution Reflection

After this skill completes, reflect before closing the task:

0. Locate yourself. — Find this SKILL.md's canonical path before editing. 1. What failed? — Fix the instruction that caused it. 2. What worked better than expected? — Promote to recommended practice. 3. What drifted? — Fix any script, reference, or dependency that no longer matches reality. 4. Log it. — Evolution-log entry with trigger, fix, and evidence.

Do NOT defer. The next invocation inherits whatever you leave behind.

Evolution Log

Convention: Reverse chronological order (newest on top, oldest at bottom). Prepend new entries.

---

2026-02-26: Initial Evolution Log

Status: Skill is in use and maintained. Track improvements here.

Purpose

This evolution log tracks updates to the skill. Each entry should note:

• What changed (content, structure, tooling)
• Why it changed (bug fix, feature request, best practice)
• Files affected

How to Use

1. When updating SKILL.md or references, add an entry here with the date 2. Keep entries reverse-chronological (newest first) 3. Link to ADRs or GitHub issues when relevant 4. Reference specific line changes when helpful

---