Menu
Handles inbound Telegram messages as orchestrator commands when running with --channels plugin:telegram@claude-plugins-official
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Schedules and runs cron jobs and the nanika publishing pipeline via scheduler CLI. Use when scheduling jobs, managing cron tasks, running the daemon, checking job history, or setting up the daily publishing pipeline.
Obsidian vault CLI — read, write, search, capture, triage, enrich, and ingest into the vault at ~/.alluka/vault/. Prefer this CLI over the Write tool for vault paths so the search index, frontmatter schema, and triage hooks stay in sync — plain Write still works and the memory system reads any valid markdown at the canonical paths regardless of how it was produced. Use when user asks about notes, vault, captures, inbox triage, note search, or importing scout/learnings data.
Full article pipeline — from topic research to Substack draft. Scouts trending intel, writes or selects an article, generates intaglio art via Google Flow, creates manifest, and cross-posts to Substack. Use when creating, illustrating, or publishing articles.
Telegram and Discord channel integration for the orchestrator. Handles inbound messages as orchestrator commands and pushes mission lifecycle events back.
Send native voice messages and text to Discord channels via the discord CLI. Use when sending audio as a Discord voice message or checking channel config.
Send voice messages and text to Telegram chats via the telegram CLI. Use when sending audio as a Telegram voice message or checking chat config.
| name | telegram-channel |
| description | Handles inbound Telegram messages as orchestrator commands when running with --channels plugin:telegram@claude-plugins-official |
| license | MIT |
| metadata | {"author":"joey","version":"0.1.0"} |
When running as a Telegram channel session, this skill teaches you how to handle inbound messages from Telegram and route them to orchestrator commands.
You are running as a long-lived Claude Code session with
--channels plugin:telegram@claude-plugins-official. Messages arrive as
<channel source="telegram" ...> events. You have access to the reply tool
to send responses back to Telegram.
Interpret inbound messages and map them to orchestrator actions:
| User Intent | Action |
|---|---|
| Task-like request ("research X", "build Y", "compare A vs B") | Confirm with user, then orchestrator run "<task>" |
| "status" or "what's running" | orchestrator status |
| "metrics" or "how did it go" | orchestrator metrics --last 5 |
| "cancel " or "stop" | orchestrator cancel <id> |
| Question about codebase | Answer directly, no orchestrator call |
| Unclear intent | Ask for clarification |
orchestrator run — always confirm the task with the user first.orchestrator run, reply with the mission ID and phase plan. Don't wait for completion — the daemon notifier handles progress updates.User: research the best practices for Go error handling
You: I'll create a mission for that. Running:
orchestrator run "research Go error handling best practices" --no-review
Mission 20260322-abc123 started
3 phases: research → synthesize → write-report
User: status
You: Active missions:
`20260322-abc123` — research Go error handling (phase 2/3: synthesize)
`20260322-def456` — completed 5m ago
When a voice message arrives (attachment with audio MIME type like audio/ogg, audio/mpeg, audio/mp4, audio/wav):
download_attachment(chat_id, message_id)elevenlabs transcribe --input <downloaded_path>Example:
[Voice message arrives]
→ download_attachment(chat_id, message_id) → /tmp/voice_123.ogg
→ elevenlabs transcribe --input /tmp/voice_123.ogg → "check the status of my running missions"
→ Reply: "Got it — checking mission status..."
→ orchestrator status
→ Reply with results
If elevenlabs CLI is not available, reply: "Voice transcription unavailable. Please send a text message instead."