- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jdubois/boot-ui --skill bootui-rubber-duck -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jdubois/boot-ui --skill bootui-rubber-duck -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jdubois/boot-ui --skill bootui-rubber-duck -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jdubois/boot-ui --skill bootui-rubber-duck -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/jdubois/boot-ui/tree/HEAD/.github/skills/bootui-rubber-duckFrom the publisher
Get three independent, high-signal critiques of a proposal from three different powerful models, then reconcile them. This develops BootUI itself and supplements repository instructions and the relevant path-scoped instructions.
Pick one target and state it precisely:
git status, git diff, plus the intent behind it).git diff against the base (or gh pr diff), changed tests,
and CI state.Collect only what a reviewer needs: goal, constraints, files changed, tests run, and open doubts. Read the docs
that govern the area (docs/SPECIFICATION.md, docs/features/, docs/WEBFLUX-SUPPORT.md,
docs/QUARKUS-SUPPORT.md, PRODUCT.md/DESIGN.md for UI) so the brief names the invariants at stake.
Reviewers are stateless and must not see each other's output. The brief contains:
Launch three rubber-duck agents (use the task tool, agent_type: rubber-duck, background mode) at the same time,
each with a different model from the strongest available. Prefer one per model family, for example:
gpt-6-sol (or gpt-6.1-sol)claude-sonnet-5.5 (or claude-sonnet-5 at high/max effort)gemini-4-argon (or grok-4.7)Use the highest reasoning effort offered, and fall back to the next-best model if one is unavailable. Keep the same brief for all three. Respect the repository's limit on parallel sub-agents (3 fits within it). While they run, do independent work such as reproducing the riskiest claim yourself; do not poll.
Read all three results, then produce a single list:
Classify accepted items as blocking or follow-up. Do not accept a claim you have not verified.
Finish by telling the user which models were used, what was accepted, rejected, and still open.
Use to rubber duck a proposed BootUI design, plan, or implementation, either in the current agent session or in a pull request, by getting independent critiques from three different powerful models an
---name: bootui-rubber-duckdescription: Use to rubber duck a proposed BootUI design, plan, or implementation, either in the current agent session or…---# .github/skills/bootui-rubber-duck/SKILL.mdOverview
Use to rubber duck a proposed BootUI design, plan, or implementation, either in the current agent session or in a pull request, by getting independent critiques from three different powerful models and synthesizing them. Not for routine reviews of trivial changes.
FAQ
Download .github/skills/bootui-rubber-duck/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/jdubois/boot-ui.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.