Stats
Actions
Tags
From lua-agent-builder
Search the lua-cli documentation at https://docs.heylua.ai. Uses WebFetch (does NOT shell out to `lua docs`, which only opens a browser).
How this command is triggered — by the user, by Claude, or both
Slash command
/lua-agent-builder:lua-docsThe summary Claude sees in its command listing — used to decide when to auto-load this command
You are `/lua-docs`. The user typed `/lua-docs $ARGUMENTS`. ## Step 1 — pick a starting URL If `$ARGUMENTS` clearly maps to a known section, fetch directly: - CLI command (`sync`, `compile`, `chat`, `push`, `deploy`, `init`, `auth`, `agents`, `logs`, `skills`, `webhooks`, `jobs`, `mcp`, `integrations`, …) → `https://docs.heylua.ai/cli/<command>` - Primitive (`tool`, `skill`, `webhook`, `job`, `preprocessor`, `postprocessor`, `mcp-server`) → `https://docs.heylua.ai/primitives/<primitive>` - Otherwise → `https://docs.heylua.ai/` and follow the most relevant link from the index. If `$ARGUM...
You are /lua-docs. The user typed /lua-docs $ARGUMENTS.
If $ARGUMENTS clearly maps to a known section, fetch directly:
sync, compile, chat, push, deploy, init, auth, agents, logs, skills, webhooks, jobs, mcp, integrations, …) → https://docs.heylua.ai/cli/<command>tool, skill, webhook, job, preprocessor, postprocessor, mcp-server) → https://docs.heylua.ai/primitives/<primitive>https://docs.heylua.ai/ and follow the most relevant link from the index.If $ARGUMENTS is empty, ask the user once for a topic.
Use WebFetch with the URL and a prompt like "summarize the key points for: ". Show the summary; if the page references related sub-pages, offer to fetch one.
Bash(lua docs) — that command only opens a browser, useless inside Claude Code.mcp__lua-docs__* tools — the MCP server they pointed at was never vendored, so the references were dead in shipped builds. WebFetch is the live source-of-truth replacement.npx claudepluginhub lua-ai-global/claude-code-lua-plugin --plugin lua-agent-builder