Skip to content
Agentmart
Submit a tool

hep-connect

Connect Agentlas agents or teams to Telegram.

Skill by agentlas-ai

IndexedApache-2.0★ 1,582
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/agentlas-ai-hep-connect

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Connect Agentlas agents or teams to Telegram.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/hep-connect

What's inside

Skill name
hep-connect
Description
Connect Agentlas agents or teams to Telegram.
License
Apache-2.0
Instructions
35 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

Update fallback: 자동 업데이트가 안 되면 `hephaestus update`를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다.

# Hephaestus Connect

Raw arguments: `$ARGUMENTS`

Use this prompt when the operator wants Telegram to talk to one Agentlas target:
a single agent, a saved group, a local team, or a `.agentlas` org chart.

Current product contract:

1. Start with Telegram only.
2. Do not ask for a BotFather token in chat. Save it only through a
   runtime-owned secret store.
3. Prefer the Agentlas Desktop Connect surface at `/connect`; it lists saved
   groups, `.agentlas` org charts, local teams, team agents, and single agents.
4. Explain the setup in simple words:
   - choose who should answer;
   - make a Telegram bot in BotFather;
   - save the token in the local secret store;
   - pair one Telegram chat;
   - send one test message;
   - keep adding more chats as needed.
5. Session state belongs to the Telegram chat binding. Team, org, and saved
   group bindings use one session per chat. Single-agent direct chats can keep
   one session per user.

If running inside Agentlas Desktop development, report that the Desktop route is
`/connect` and use the real local Connect UI as the source of truth. Do not
pretend that Telegram delivery is live until token validation, chat pairing, and
a test message pass.

Report progress as one ladder and never skip a rung:
`Draft -> Token checked -> Chat paired -> Test passed -> Running`.

From agentlas-ai/Agentlas-OS, Apache-2.0.

More from agentlas-ai/Agentlas-OS

Compare and alternatives

    Featured in

    Signals

    Stars
    1,582
    Forks
    107
    Open issues
    1
    Last commit (this folder)
    Sep 12, 2026 (1 month ago)
    Last release
    Oct 24, 2026 (3 days ago)

    From GitHub (fetched Oct 24, 2026).

    Details

    License
    Apache-2.0
    First seen
    Oct 24, 2026
    Last checked
    Oct 24, 2026

    More from agentlas-ai

    Cite this page

    hep-connect skill. Agent Mart. https://agentmart.dev/skills/agentlas-ai-hep-connect (last updated 2026-10-24)