Slash Command1.1k estrellas del repoactualizado today

agentlas-update

Update the installed Agentlas runtime and every host adapter on this machine.

Instalar en Claude Code

Copiar

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/agentlas-ai/Agentlas-OS/HEAD/.claude/commands/agentlas-update.md -o ~/.claude/commands/agentlas-update.md

Después abre una sesión nueva de Claude Code; el slash command carga automáticamente.

Definición

agentlas-update.md

# /agentlas-update

Identical to `/hep-update` and `/agentlas update <request>`. Locate the file named `hep-update.md` in the exact same directory this file was loaded from, read it, and follow its instructions exactly — treating everything typed after `/agentlas-update` as that command's request.

Do not improvise a separate workflow and do not summarize `hep-update.md` from memory; that file is the sole authority for this command's behavior.

Del mismo repositorio

agent-team-designSkill

Use when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.

agentlas-auto-activationSkill

Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.

agentlas-browserSlash Command

Use the Agentlas browser hardpoint for browser-required work.

agentlas-buildSkill

Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.

agentlas-callSlash Command

Prepare explicitly named Agentlas Hub or Cloud agents.

agentlas-cloudSkill

Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.

agentlas-connectSlash Command

Connect Agentlas agents or teams to Telegram.

agentlas-core-engine-meta-agentSkill

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 this for /meta-agent requests.