メニュー
Work with messaging-channel bots (Telegram / Slack) — register a bot, route inbound messages through the AI agent, handle webhooks vs polling, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Add a new tool/function the AI agent can call (e.g. look something up, hit an external API, perform an action). Use when extending the assistant's capabilities, wiring a new function into the agent, or when the model needs a new action. This project uses {{ cookiecutter.ai_framework }}.
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.background_tasks }}.
Work with Stripe billing — subscriptions, plans/prices, the Customer Portal, credits, usage metering, invoices, and webhook events. Use when changing plans, handling a new Stripe webhook, debugging a payment/subscription flow, or touching credit balances and usage.
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
| name | channel-bot |
| description | Work with messaging-channel bots (Telegram / Slack) — register a bot, route inbound messages through the AI agent, handle webhooks vs polling, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery. |
Channels are a thick service at backend/app/services/channels/: per-platform adapters plus a router that funnels inbound messages into the same agent pipeline as the web chat.
| File | Responsibility |
|---|---|
base.py | Shared channel adapter interface |
telegram.py | Telegram adapter (aiogram v3) |
slack.py | Slack adapter (Events API + Socket Mode) |
router.py | Maps an inbound platform message → conversation/session → agent run → reply |
chart_render.py | Renders chart tool output as PNG for channels |
Bots are stored in the DB (channel_bot), with per-user identity (channel_identity) and per-thread session (channel_session) tables. Bot tokens are encrypted at rest with CHANNEL_ENCRYPTION_KEY (Fernet).
uv run {{ cookiecutter.project_slug }} cmd channel ... # see `cmd channel --help`
POST /api/v1/telegram/{bot_id}/webhook / the Slack events endpoint. Verify the signature/secret (HMAC for Telegram, signing secret for Slack) before processing.services/channels/<platform>.py against the base.py interface (parse inbound → normalized message; send outbound).router.py so inbound messages reach the agent and replies stream back.api/routes/v1/ (signature-verified) and/or a polling entrypoint.router.py into the same agent/session pipeline as web chat — don't duplicate agent logic per platform.CHANNEL_ENCRYPTION_KEY); never log or echo them.