BuilderIO/skills plugin for Grok Build

Community Claude Code plugin, installs in GrokPluginDevelopmentNeeds sign-in

Skills for agents

How to install BuilderIO/skills in Grok Build

grok plugin install BuilderIO/skills --trust
✓ Install-checked in Grok Buildchecked Oct 18, 2026

Needs your own API key or sign-in to work fully. We check that it installs and loads, not your account.

Review before you trust it. --trust lets this plugin's hooks, MCP servers and scripts run code on your computer. It's a community repo that neither xAI nor GrokStacks has reviewed, so read its code first.

We install this repo directly: Grok Build 1.0.62 can't install it through its own marketplace file. Then start a new Grok session, or press r in /plugins, to load it.

Command format: Grok Build's plugin guide

Needs a sign-in. Its MCP server is hosted by the vendor, and most hosted MCP servers ask you to sign in the first time. In Grok, open /mcps, select the server and press i to sign in.

What we checked: on Oct 18, 2026 it installed with grok 1.0.62 and Grok found 24 skills, 1 slash command. That's an install check only: we haven't run it in a live Grok session.

What it contains

Skills (24)

  • agent-watchdog — Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done o
  • an — Open and operate Agent-Native workspace apps through Dispatch MCP, with inline app surfaces, browser-session authentication, and current screen state.
  • efficient-fable — Use when running Claude Fable on codebase-heavy or token-heavy work and the user wants Fable to orchestrate research, coding, and testing while cheaper subagents do bounded heavy lifting.
  • efficient-frontier — Apply the same orchestration as `/efficient-fable` to any high-cost frontier model: delegate research, coding, and testing to cheaper subagents while keeping planning, synthesis, and final review with the expensive model.
  • factory — Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.
  • factory-babysit-pr — Experimental workflow for babysitting one explicitly authorized pull or merge request. Use to monitor its live review state and checks, fix actionable in-scope findings, and apply separate reply, approval, merge, and soak gates.
  • factory-collect — Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports. Use when scanning configured signal sources and applying separate fix, reply, or close rules.
  • factory-human-digest — Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.
  • factory-lookback — Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.
  • factory-recover — Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.
  • factory-review-prs — Experimental workflow for reviewing configured repositories' pull requests. Use for manual or scheduled PR triage, approval, or merge decisions.
  • factory-ship — Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
  • factory-watchdog — Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work. Use for scheduled ship follow-through.
  • plan-arbiter — Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions
  • plow-ahead — Use when the user explicitly wants autonomous progress without routine clarification stops: "plow ahead", "do not stop", "use your best judgment", "keep going until done", "finish while I am away", "do not ask questions unless truly blocked
  • quick-recap — Use when adding or following the red/yellow/green final status block convention for agent responses, especially by installing managed AGENTS.md or CLAUDE.md instructions.
  • read-the-damn-docs — Use when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/off
  • rewind — Retrieve recent local Clips Rewind context when the user says "Look at Rewind," asks what just happened, or refers to something they recently said or saw.
  • stay-within-limits — Use when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.
  • turn-into-app — Turns a thread, skill, spreadsheet, or Claude/ChatGPT project into a polished, visual Agent-Native app: populated domain screens with the in-app agent working behind contextual controls. Use when a user invokes `/turn-into-app`, or asks to
  • visual-edit — Open and collaboratively edit a running local app in Design, with shared fallback previews and source handoff. Use when the user asks to inspect, share, or edit a real local app in Design.
  • visual-plan — Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.
  • visual-recap — Turn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes.
  • webmcp — Open a user-provided URL in the host's built-in browser and use the page's MCP or WebMCP tools before browser UI automation for app communication or edits.

MCP servers (1)

  • agent-native-dispatch — http server

About this listing

BuilderIO/skills is a community plugin on GitHub by BuilderIO, written as a Claude Code plugin that Grok Build installs. We install-checked it in Grok; we haven't run it in a live session or reviewed its code. When we installed it, Grok found 24 skills, 1 MCP server. Its license is MIT. We checked commit 20ff8a101fe8. It's one of 409 listings in the Development category on GrokStacks.

Stacks Weekly: every new Grok Build and Codex plugin, every Tuesday.

One short email for GrokStacks and CodexStacks readers, with each new plugin's install line and what it ships. Subscribe and get the free starter list: 20 Grok Build plugins worth installing first.

You'll get a confirmation email first. Unsubscribe anytime.

BuilderIO/skills FAQ

How do I install BuilderIO/skills in Grok Build?

Run grok plugin install BuilderIO/skills --trust. We install-checked this command in Grok Build. We install this repo directly: Grok Build 1.0.62 can't install it through its own marketplace file. Then start a new Grok session, or press r in /plugins, to load it.

Is BuilderIO/skills an official Grok Build plugin?

No. BuilderIO/skills is a community plugin on GitHub by BuilderIO, not in xAI's official Grok Build marketplace. We checked that it installs and what Grok loads from it, but haven't run it in a live Grok session or reviewed its code.

What does BuilderIO/skills include?

According to what Grok loaded in our install check, BuilderIO/skills includes 24 skills, 1 MCP server: agent-watchdog, an, efficient-fable, efficient-frontier, factory, factory-babysit-pr….

Details

Type
Plugin
Category
Development
Source
Community Claude Code plugin, installs in Grok
License
MIT
Author
BuilderIO
Source repo
https://github.com/BuilderIO/skills
Checked commit
20ff8a101fe8
Homepage
https://www.agent-native.com/
Checked by GrokStacks
Install-checked in Grok Build on Oct 18, 2026; not run in a live session

Something wrong or missing? Submit or improve this listing. Marketplace listings also refresh automatically every night.

For maintainers: badge and embeds

Maintain BuilderIO/skills? Add the badge; it links to this page.

Listed on GrokStacks

Markdown

[![Listed on GrokStacks](https://grokstacks.com/badge.svg)](https://grokstacks.com/p/builderio-skills/)

HTML

<a href="https://grokstacks.com/p/builderio-skills/"><img src="https://grokstacks.com/badge.svg" alt="Listed on GrokStacks" width="164" height="28"></a>

Embed card (static HTML and inline CSS, no JavaScript). Preview:

<a href="https://grokstacks.com/p/builderio-skills/" style="display:block;max-width:380px;box-sizing:border-box;padding:14px 16px;border:1px solid #2a2e3c;border-radius:12px;background:#0a0b0f;color:#e8eaf0;font:14px/1.45 -apple-system,Segoe UI,Roboto,Helvetica,Arial,sans-serif;text-decoration:none"><span style="display:block;font-size:16px;font-weight:700;color:#e8eaf0">BuilderIO/skills</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 24 skills, 1 MCP server</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">Skills for agents</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[BuilderIO/skills on GrokStacks](https://grokstacks.com/p/builderio-skills/)**: Community plugin for Grok Build with 24 skills, 1 MCP server. Install: `grok plugin install BuilderIO/skills --trust`

More on badges, embeds and keeping your listing up to date: GrokStacks for plugin authors.

Also in Development

All 409 development listings →