hep-connect

SkillCommunication

Start the Agentlas Connect flow for Telegram.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the hep-connect skill

What this skill tells your AI

The instructions your AI receives, as published by agentlas-ai/agentlas-os in kimi/skills/hep-connect/SKILL.md and read by ahel’s review.

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

Hephaestus Connect

Raw arguments: everything the user typed after /skill:hep-connect.

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.

Signals

GitHub stars
1k
Forks
103
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
hep-connect
Source
github.com/agentlas-ai/agentlas-os