acpbot ships two operator skills for coding agents (Grok, Claude, Codex, …):
| Skill | Package path | Purpose |
|---|---|---|
| telegram | skills/telegram/SKILL.md | Progress pings, mid-turn text, photos, files, voice via host MCP acpbot |
| schedules | skills/schedules/SKILL.md | Create / list / cancel / fire delayed or recurring jobs |
Skills are embedded in the release binary. Telegram /skills discovers them automatically. Install globally so agent CLIs also see them in every workspace.
Install
acpbot skills installRun after setup or skill upgrades. The worker does not install skills on boot.
Install targets (symlink preferred, copy fallback). Never overwrites a real directory that is not already an acpbot skill symlink:
~/.agents/skills/{telegram,schedules}~/.grok/skills/{telegram,schedules}~/.claude/skills/{telegram,schedules}
Binary installs materialise skills under ~/.local/share/acpbot/bundled-skills/ when the package tree is not on disk.
Discovery
| Path | Who uses it |
|---|---|
| Bundled root (package or materialised) | Always on skillRoots for Telegram /skills |
~/.agents/skills, ~/.grok/skills, ~/.claude/skills | Global agent CLIs after acpbot skills install |
Session cwd .agents/skills (etc.) | Per-repo overrides |
Extra roots: [skills].roots in config.toml, or env ACPBOT_SKILL_ROOTS (colon / semicolon / comma separated). See Configuration.
Telegram /skills
In a topic, /skills lists skills from config roots + session cwd, then composes a prompt for the agent with the chosen skill body.
Related
- MCP — host tools those skills describe
- Schedules — how host fire works
- Worker API — how outbound Telegram is delivered