From botster
Use when installing Botster for an agent, setting up the first Botster-managed agent, or checking whether Botster MCP and agent configuration are present.
How this skill is triggered — by the user, by Claude, or both
Slash command
/botster:botster-installThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to make a fresh agent usable inside Botster. The goal is a
Use this skill to make a fresh agent usable inside Botster. The goal is a single Botster MCP server, one working agent definition, and the core Botster plugins needed for coordination.
The agent plugin should provide this MCP server automatically:
[mcp_servers.botster]
command = "botster"
args = ["mcp-serve"]
env_vars = ["BOTSTER_SESSION_UUID"]
default_tools_approval_mode = "approve"
default_tools_enabled = true
Do not add duplicate Botster MCP aliases. botster mcp-serve resolves caller
identity from BOTSTER_SESSION_UUID; duplicate aliases make tool discovery
noisy without adding capability.
For a first useful agent setup, verify these exist:
agents/<name>/initialization.botster context worktree_path.botster context prompt.BOTSTER_SESSION_UUID.orchestrator and messaging are available if
the user wants multi-agent workflows.PATH.botster MCP server.whoami through MCP.whoami fails, check BOTSTER_SESSION_UUID propagation before changing
tools or plugin code.Botster is the hub and PTY orchestrator. Agent plugins configure agent-side integration; Botster Lua plugins provide runtime MCP tools. Keep those layers separate even when the user experience is one plugin install.
npx claudepluginhub tonksthebear/trybotster --plugin botsterGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.