From Lubby
Show the current Lubby connection status, including server, login state, share level, and whether presence sharing is paused.
How this skill is triggered — by the user, by Claude, or both
Slash command
/lubby:statusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read `~/.lubby/config.json` and report to the user:
Read ~/.lubby/config.json and report to the user:
cat ~/.lubby/config.json 2>/dev/null || echo "not configured"
Report concisely:
api_url valuetoken is set (show only the first 8 characters, e.g. lub_AB12...), no otherwiseshare_level (explain: presence_only means only "waiting + agent + stack" is shared, never code, files, or prompts)paused flagIf not configured, suggest /lubby:login.
npx claudepluginhub aliwesome/lubby-plugin --plugin lubbyProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.