Skill
agent-communication
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…
@codeaholicguyView SkillDevelopment
Skill
/remote-from-telegram
AI DevKit · Connect the current agent session to an available Telegram channel bridge.
Install
$ npx -y skills add codeaholicguy/ai-devkit --skill remote-from-telegram --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/remote-from-telegram
Context preview
The summary Claude sees to decide when to auto-load this skill.
AI DevKit · Connect the current agent session to an available Telegram channel bridge.
SKILL.md
remote-from-telegram.SKILL.mdname: remote-from-telegram
description: AI DevKit · Connect the current agent session to an available Telegram channel bridge.
Remote From Telegram
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.
Workflow
1. Check readiness:
ai-devkit status --json
If AI DevKit is not ready, use `ai-devkit-setup` skill first. Stop if setup leaves manual actions.
2. Inspect channels and agents:
ai-devkit channel list
ai-devkit agent list --json
3. Identify the current agent by matching this session to an `agent list --json` entry. If unclear, ask for the agent name.
4. Find configured Telegram channels. If none exist, tell the user to run:
ai-devkit channel connect telegram
Stop after giving that action.
5. 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.
6. If no Telegram channel is available because bridges are already running, ask before stopping one. After confirmation:
ai-devkit channel stop <channel>
7. Start the bridge in the background:
ai-devkit channel start <channel> --agent <agent-name> --daemon
8. 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.
Boundaries
- Do not create or connect a Telegram channel for the user; only point them to `channel connect`.
- Do not stop a running bridge without explicit confirmation.
- Do not guess when both agent or channel selection are ambiguous.
Read more
name: remote-from-telegram description: AI DevKit · Connect the current agent session to an available Telegram channel bridge.
Remote From Telegram
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.
Workflow
1. Check readiness:
ai-devkit status --json
If AI DevKit is not ready, use `ai-devkit-setup` skill first. Stop if setup leaves manual actions.
2. Inspect channels and agents:
ai-devkit channel list ai-devkit agent list --json
3. Identify the current agent by matching this session to an `agent list --json` entry. If unclear, ask for the agent name.
4. Find configured Telegram channels. If none exist, tell the user to run:
ai-devkit channel connect telegram
Stop after giving that action.
5. 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.
6. If no Telegram channel is available because bridges are already running, ask before stopping one. After confirmation:
ai-devkit channel stop <channel>
7. Start the bridge in the background:
ai-devkit channel start <channel> --agent <agent-name> --daemon
8. 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.
Boundaries
- Do not create or connect a Telegram channel for the user; only point them to `channel connect`.
- Do not stop a running bridge without explicit confirmation.
- Do not guess when both agent or channel selection are ambiguous.
Ships withai-devkit
The control plane for AI coding agents. AI DevKit gives Claude Code, Codex CLI, Gemini CLI, opencode, Pi, Cursor, GitHub Copilot, Devin, and other coding agents one local-first operating layer: one config, one console, local memory retrieval, cross-agent
Get the whole plugin
Stats
1,629
Stars
251
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
3d ago
Last commit
11mo ago
Created
Repo: codeaholicguy/ai-devkit
Other skills on ai-devkit.
@codeaholicguyView SkillSkill
agent-management
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…
@codeaholicguyView SkillSkill
agent-orchestration
AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve…
@codeaholicguyView SkillSkill
ai-devkit-setup
AI DevKit · Check local AI DevKit readiness and run setup only when status shows onboarding or harness integration gaps.
@codeaholicguyView SkillSkill
brainstorm
AI DevKit · Use when the user asks to brainstorm, ideate, generate ideas, expand options, challenge ideas, pressure-test ideas, compare concepts, narrow…
@codeaholicguyView SkillSkill
changelog
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…
@codeaholicguyView Skill