telegram-topic-teardown

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Managed Telegram Topic Teardown

Prefer the deterministic Telegram command:

```text
/teardown
```

It opens the confirmation card directly without invoking an LLM. If already
handling a natural-language teardown request inside an active managed turn,
request the same card with:

```bash
/usr/bin/python3 {{TELEGRAM_CONTROL_ROOT}}/agent_telegram.py topic-teardown
```

Use either path only from the managed topic being removed. Neither accepts a
chat ID, topic ID, or agent ID.

Tell the user to use the Telegram confirmation card. Do not claim the topic was
removed merely because the card was posted.

Confirmation performs the destructive work through the controller: it rejects
an active agent turn, stops an interactive console, blocks while originating
detached workers still exist, archives the managed agent and session pointer,
revokes routes and buttons, and durably queues deletion of the Telegram topic.

Do not call `deleteForumTopic`, edit the controller database, kill tmux, or
delete the topic by another path. If the helper reports that this is not the
agent's home topic, return to that topic and request teardown there.

From shantamg/telegram-control, Apache-2.0.

More from shantamg/telegram-control