agentlas-core-engine-m…
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to…
Connect Agentlas agents or teams to Telegram.
$ npx -y skills add agentlas-ai/Agentlas-OS --skill hep-connect --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/hep-connectContext preview
The summary Claude sees to decide when to auto-load this skill.
Connect Agentlas agents or teams to Telegram.
name: hep-connect description: Connect Agentlas agents or teams to Telegram.
Update fallback: 자동 업데이트가 안 되면 `hephaestus update`를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다.
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:
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`.
Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
Repo: agentlas-ai/Agentlas-OS
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to…
Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.
Use when the user types /agentlas-graph, /agentlas graph, or /hep-graph to create, list, inspect, or run Agentlas automation graphs.
Use when the user types /agentlas-network, /agentlas network, $hephaestus-network, or /hep-network to staff a durable goal from registered Local, owner Cloud,…
Use when the user types /agentlas-storm, /agentlas storm, /hep-storm, or says @Hephaestus storm <goal> to drive a goal through the force-robust Stormbreaker…