public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS /tmp/public-plugin-packaging && cp -r /tmp/public-plugin-packaging/.agents/skills/public-plugin-packaging ~/.claude/skills/public-plugin-packagingSKILL.md
# Public Plugin Packaging ## Checklist - `codex/marketplace.json` exists. - Codex plugin has `.codex-plugin/plugin.json`. - Codex plugin includes at least one `SKILL.md`. - Codex plugin includes `commands/<slug>.md` for the package command. - `.claude/commands/meta-agent.md` exists. - `.claude/commands/<slug>.md` exists for the package command. - `.claude/agents/agentlas-core-engine-meta-agent.md` exists. - `.claude/skills/agentlas-core-engine-meta-agent/SKILL.md` exists. - `.gemini/commands/<slug>.toml` exists for Gemini CLI custom commands. - `.agentlas/global-commands.json` exists and final handoff includes `global_commands`. - `scripts/install.sh` supports one-line installation. - `scripts/verify-package.sh` passes. - `scripts/public_safety_check.sh` passes. ## Public Boundary Publish schemas, templates, prompts, and adapters. Do not publish hosted service secrets, private research notes, raw logs, or local machine paths.
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.
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
Use the Agentlas browser hardpoint for browser-required work.
Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
Prepare explicitly named Agentlas Hub or Cloud agents.
Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.
Connect Agentlas agents or teams to Telegram.
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.