All authors
Claude Skills by bearlike
github.com/bearlike15 skills2 installs34 views
- Mewbo Cli SmoketestEnd-to-end smoke testing of the Mewbo CLI via tmux. Use this skill when asked to test the CLI, verify CLI behavior after changes, smoke-test the agent loop, check for regressions, or validate MCP/plugin/session features work correctly through the terminal interface. Also use when debugging CLI crashes, MCP connection issues, or session lifecycle problems that need live reproduction.Votes: 0GitHub stars: 41
- St Widget BuilderUse when the user asks to render, build, visualise, mock up, or show a widget (chart, dashboard, card, table, graph) in the Mewbo Console. Teaches how to delegate the work to the st-widget-builder sub-agent instead of writing HTML or inline code yourself.Votes: 0GitHub stars: 41
- App BuilderUse when the user asks to build, create, or set up an app (a durable data app with a dashboard and background pipelines) — not a one-off widget or chart. Teaches how to delegate app-building to the app-builder sub-agent.Votes: 0GitHub stars: 41
- Claude Md ImproverAudit and improve CLAUDE.md files in repositories. Use when asked to check, audit, update, improve, or fix CLAUDE.md files, or when someone mentions project memory optimization.Votes: 0GitHub stars: 41
- BrainstormingExplore intent, requirements and design before implementation. Use before any creative work such as creating features, building components, adding functionality, or modifying behavior.Votes: 0GitHub stars: 41
- Device ControlUse when driving the user's Android device through device_control_start, device_ui and device_action — opening apps, navigating screens, filling fields, or any multi-step flow through another app's UI.Votes: 0GitHub stars: 41
- Generative UiUse when presenting information already in hand as a small, static structured panel in the conversation — status, results, comparisons, or a compact summary — rather than prose, a markdown table, a widget, or an app.Votes: 0GitHub stars: 41
- Mewbo HarnessUse when you need to know how this harness itself behaves rather than what a tool's arguments are — why a tool result was truncated and how to page past it, what a tool timeout does and does not mean, which directory a relative path resolves against, how to reach a tool whose schema was not bound, how spawned sub-agents finish, and how to present a structured UI panel. Read this before reading the harness implementation source.Votes: 0GitHub stars: 41
- Working In GroveUse when working inside a Grove workspace, including reporting task phase, updating a workspace or its ticket links, using GROVE_PHASE_FILE, writing to another Grove agent through the mailbox, or waiting on slow work like CI by registering a watch instead of sleeping. Also use when a worktree has a phase file, when asked for progress, or when an attached issue or pull request needs updating. For fleet operation from outside use using-grove. For setup use configuring-grove.Votes: 0GitHub stars: 9
- Configuring GroveUse when configuring Grove for a user or project, including agent rosters, init scripts, containers, private credentials, daemon or MCP setup, or the native-versus-terminal launch of a Claude Code or Codex agent. Also use when resolving config layers, validating a config schema, or explaining why a workspace starts with unexpected runtime behavior. For fleet operation use using-grove. For an agent inside a workspace use working-in-grove.Votes: 0GitHub stars: 8
- Reinstalling GroveUse when a user wants to reinstall, update, or upgrade Grove after pulling new code, or when they report seeing the OLD UI / stale behavior after an update ("I still see the old dashboard", "the redesign isn't showing", "I reinstalled but nothing changed"). Covers the editable uv-tool install model, the independently-updated surfaces (package/CLI/TUI, daemon, webapp, plus the opt-in grove-mcp server in either its stdio or networked transport), the reinstall-vs-restart decision, a required ver...Votes: 0GitHub stars: 8
- Using GroveUse when orchestrating Grove workspaces from outside, including creating or supervising host or container agents, steering a fleet, using Grove CLI or MCP tools, or having agents write to each other through the mailbox. Also use when splitting work across workspaces, reviewing a diff from several angles, managing ticket links, or checking who needs attention. For a worker reporting from inside a workspace use working-in-grove. For setup use configuring-grove.Votes: 0GitHub stars: 8
- Collaborating On DiagramsUse when working with an existing .drawio diagram through Grove collaboration. Triggers on opening, reading, editing, updating, stopping, or recovering a diagram in a Grove workspace. Covers revisioned managed writes, XML-preserving edits, collaboration state, conflicts, read-only stop, and container/editor limits.Votes: 0GitHub stars: 8
- Mocking Up In GroveUse when a visual or frontend task in a Grove workspace needs a mockup approved before code — a new control, a redesigned surface, a layout change. Covers drawing a draw.io mockup through Grove's diagram tools, previewing it in the browser, getting sign-off, filing the approved image on the tracker issue, and handing the issue to implementation. For the raw diagram tool contract use collaborating-on-diagrams.Votes: 0GitHub stars: 8
- Leading In GroveUse when you lead a fleet of Grove teammates toward one deliverable, including deciding how many to spawn and how to split the work, writing their onboarding prompt, getting acknowledgment, running scheduled check-ins, answering their mailbox questions, keeping tickets and your own status compaction-proof, reviewing and deploying what lands on main, and tearing the fleet down. Also use when a teammate stalls, overbuilds, goes quiet, or when the user asks where everything stands. For the Grove...Votes: 0GitHub stars: 8