メニュー
Send messages, inspect group rosters, and pin messages via the Telegram Bot API through `telegram-agent`. Writes are dry-run by default; --apply is required to commit.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/agentculture/telegram-agent --skill telegramコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of vector+keyword, the default) — each hit carrying its text, full metadata, a relevance `score`, and a freshness `signal`. Recall passively reinforces matched records (bumps last_recall + recall_count). Shadowed and archived records are excluded by default; use --include-shadowed / --include-archived to retrieve them. The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree); the wrapper defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope telegram-agent --visibility private`, suffix read from culture.yaml) — matching where /remember writes — so a no-flag recall returns this agent's own private records plus the shared public pool, and Claude and the colleague backend recall each other's memories because both resolve the same suffix via
Ingest records into the shared eidetic memory store so they can be recalled later. Drives `eidetic remember`: accepts one record as a JSON object, or a batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and dedups by content hash) — re-remembering updates in place, never duplicates. Stamps a `created` date on every record at ingest time. Accepts `supersedes` (id of the record this one replaces, for within-scope shadowing via `sweep`) and `links` (list of related-memory ids). The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree), and the wrapper defaults records to this agent's PERSONAL, PRIVATE scope (`--scope telegram-agent --visibility private`, suffix read from culture.yaml) so they don't leak to a default/other-scope recall — Claude and the colleague backend still share them because both resolve the same suffix via this skill. Pass `--visibility public` to contribute to the shared public pool instead. Use when the user says "remember this", "store this", "save
SOC 職業分類に基づく
SKILL.md を表示中
| name | telegram |
| description | Send messages, inspect group rosters, and pin messages via the Telegram Bot API through `telegram-agent`. Writes are dry-run by default; --apply is required to commit. |
Thin wrapper around telegram-agent bot send / telegram-agent group roster / telegram-agent group pin.
Scripts default to --json so agents get structured output without
remembering the flag.
message_id from the
send response and pass it to pin).uv sync in the telegram-agent repo root — installs the package and entry point.
Alternatively, pip install 'telegram-agent[telegram]' for a global install.
Scripts invoke uv run telegram-agent so telegram-agent does not need to be on $PATH.TELEGRAM_AGENT_BOT_TOKEN in environment or a local .env (cwd or repo root).
Get a token by creating a bot with @BotFather on Telegram.can_pin_messages, can_post_messages).| Script | Wraps | Side effect | Default |
|---|---|---|---|
send.sh | telegram-agent bot send | sends a message | dry-run — pass --apply to actually send |
roster.sh | telegram-agent group roster | read-only | runs |
pin.sh | telegram-agent group pin | pins / unpins | dry-run — pass --apply to actually pin |
MSG_ID=$(./scripts/send.sh --chat @announcements --text "Release v0.2 is out" \
--parse-mode markdown --apply | jq -r .message_id)
./scripts/pin.sh --chat @announcements --message "$MSG_ID" --apply
./scripts/roster.sh --chat @announcements | jq '.intent.administrators'
TELEGRAM_AGENT_BOT_TOKEN or .env. The .gitignore covers
.env; keep it that way.--apply. The validated
plan tells you if the bot has the right permissions; --apply skipping
that check defeats the purpose.- telegram-agent (Claude)
trailer applies to GitHub posts, not Telegram chat messages.