AI DevKit · Connect the current agent session to an available Telegram channel bridge.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Use this skill when the user wants to control or chat with the current session from Telegram.
Prefer the installed ai-devkit binary; if unavailable, use npx ai-devkit@latest. Run AI DevKit commands outside filesystem sandboxes because they inspect host-level agent and channel state.
Check readiness:
ai-devkit status --json
If AI DevKit is not ready, use ai-devkit-setup skill first. Stop if setup leaves manual actions.
Inspect channels and agents:
ai-devkit channel list
ai-devkit agent list --json
Identify the current agent by matching this session to an agent list --json entry. If unclear, ask for the agent name.
Find configured Telegram channels. If none exist, tell the user to run:
ai-devkit channel connect telegram
Stop after giving that action.
Choose a channel. Use the requested channel or the only available Telegram channel. If multiple Telegram channels are available, ask the user which one to use. Available means Telegram, enabled, configured with bot credentials, and not already running. Do not reject a Telegram channel only because it is not authorized yet; Telegram authorization cannot complete until after the bridge is started and the user sends a message to the bot.
If no Telegram channel is available because bridges are already running, ask before stopping one. After confirmation:
ai-devkit channel stop <channel>
Start the bridge in the background:
ai-devkit channel start <channel> --agent <agent-name> --daemon
Report the connected channel, agent name, and how to stop it: ai-devkit channel stop <channel>. If the channel was not authorized before start, explicitly tell the user the bridge is running and they must now send any message to the Telegram bot to authorize that chat before using it.
channel connect.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send. Use when an agent needs to find another active agent, read its recent context, send it information, or request information back.
The English summary is being prepared. Showing the original description.
AI DevKit · Manage running AI agents with ai-devkit agent commands. Use when an agent needs to identify itself, list agents, start workers, inspect agent detail, assign work, group agents, resume sessions, stop agents, or delegate work to other agents.
The English summary is being prepared. Showing the original description.
AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions.
The English summary is being prepared. Showing the original description.
AI DevKit · Check local AI DevKit readiness and run setup only when status shows onboarding or harness integration gaps.
The English summary is being prepared. Showing the original description.
AI DevKit · Use when the user asks to brainstorm, ideate, generate ideas, expand options, challenge ideas, pressure-test ideas, compare concepts, narrow choices, name something, plan content angles, explore strategy, evaluate product ideas, technical approaches, experiments, or decisions.
The English summary is being prepared. Showing the original description.
AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.
The English summary is being prepared. Showing the original description.