Ed3d Plugins plugin for Grok Build

Community Claude Code plugin, installs in GrokPluginResearch

Ed's repo of Claude Code plugins, centered around a research-plan-implement workflow. Only a tiny bit cursed. If you're lucky.

How to install Ed3d Plugins in Grok Build

1. Add this repo as a plugin marketplace in Grok Build (once per computer):

grok plugin marketplace add ed3dai/ed3d-plugins

2. Install the plugin:

grok plugin install ed3d-00-getting-started@ed3dai/ed3d-plugins --trust
✓ Install-checked in Grok Buildchecked Oct 18, 2026

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.

This repo's marketplace has 11 plugins; we checked ed3d-00-getting-started, ed3d-house-style, ed3d-plan-and-execute. Install another the same way: grok plugin install <name>@ed3dai/ed3d-plugins --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Inside Grok Build: type /plugins, open the Marketplace tab, press a and add ed3dai/ed3d-plugins, then select ed3d-00-getting-started and press i.

Command format: Grok Build's plugin guide

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

What it contains

Skills (30)

  • getting-started — Show the ed3d-plugins README and getting started information
  • asking-clarifying-questions — Use after initial design context is gathered, before brainstorming - resolves contradictions in requirements, disambiguates terminology, clarifies scope boundaries, and verifies assumptions to prevent building the wrong solution
  • brainstorming — Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
  • executing-an-implementation-plan — Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task, reviews once per phase, loads phases just-in-time to minimize context usage
  • finishing-a-development-branch — Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
  • requesting-code-review — Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches code-reviewer subagent, handles retries and timeouts, manages review-fix loop until zero issues
  • starting-a-design-plan — Use when beginning any design process - orchestrates gathering context, clarifying requirements, brainstorming solutions, and documenting validated designs to create implementation-ready design documents
  • starting-an-implementation-plan — Use when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary context
  • systematic-debugging — Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting
  • test-driven-development — Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
  • using-git-worktrees — Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
  • using-plan-and-execute — Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Read tool before announcing usage, following brainstorming before coding, and creating task todos for checklists
  • verification-before-completion — Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
  • writing-design-plans — Use after brainstorming completes - writes validated designs to docs/design-plans/ with structured format and discrete implementation phases required for creating detailed implementation plans
  • writing-implementation-plans — Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engi
  • execute-implementation-plan — Execute implementation plan task-by-task with subagents
  • flesh-it-out — Take a general idea and make it specific
  • how-to-customize — Explains how to customize design and implementation plans with project-specific guidance
  • start-design-plan — Start collaborative design process with brainstorming and planning
  • start-implementation-plan — Create implementation plan from design document
  • coding-effectively — ALWAYS use this skill when writing or refactoring code. Includes context-dependent sub-skills to empower different coding styles across languages and runtimes.
  • defense-in-depth — Use when invalid data causes failures deep in execution - validates at every layer data passes through to make bugs structurally impossible rather than temporarily fixed
  • howto-code-in-rust — Use when writing, reviewing, or modifying Rust code - covers error handling with thiserror+miette, type system patterns, async and serde conventions, testing crates, dependency pinning, and module organization
  • howto-code-in-typescript — Use when writing TypeScript code, reviewing TS implementations, or making decisions about type declarations, function styles, or naming conventions - comprehensive house style covering type vs interface rules, function declarations, FCIS in
  • howto-develop-with-postgres — Use when writing database access code, creating schemas, or managing transactions with PostgreSQL - enforces transaction safety with TX_ naming, read-write separation, type safety for UUIDs/JSONB, and snake_case conventions to prevent data
  • functional-core-imperative-shell — Use when writing or refactoring code, before creating files - enforces separation of pure business logic (Functional Core) from side effects (Imperative Shell) using FCIS pattern with mandatory file classification
  • programming-in-react — Use when writing or modifying React components, planning React features, or working with .jsx/.tsx files - provides modern React patterns with TypeScript, hooks usage, component composition, and common pitfalls to avoid
  • property-based-testing — Use when writing tests for serialization, validation, normalization, or pure functions - provides property catalog, pattern detection, and library reference for property-based testing
  • writing-for-a-technical-audience — Use when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns that signal inauthenticity
  • writing-good-tests — Use when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation

Subagents (4)

  • ed3d-plan-and-execute:code-reviewer — Reviews completed project steps against plans and enforces coding standards. Use when a numbered step from a plan is complete, a major feature is implemented, or before creating a PR. Validates plan a
  • ed3d-plan-and-execute:task-bug-fixer — Fixes issues identified by code-reviewer and triggers re-review. Use when code-reviewer returns any issues that need to be addressed before merge approval.
  • ed3d-plan-and-execute:task-implementor-fast — Implements individual tasks from plans with TDD, skill application, verification, and git commits. Use when executing a specific task that requires writing, modifying, or testing code as part of a lar
  • ed3d-plan-and-execute:test-analyst — Use after final code review passes to validate test coverage against acceptance criteria and generate human test plans - reads test-requirements.md, verifies automated tests exist, produces manual ver

Plugins in this marketplace (11)

  • ed3d-00-getting-started — Getting started guide and onboarding for ed3d-plugins
  • ed3d-plan-and-execute — Planning and execution workflows for Claude Code. Based on obra/superpowers.
  • ed3d-house-style — ed3d's house style for software development
  • ed3d-basic-agents — Core agents for general-purpose tasks. Other plugins expect this to exist.
  • ed3d-research-agents — Agents used for research across multiple data sources.
  • ed3d-extending-claude — Knowledge skills for extending Claude Code: creating plugins, commands, agents, skills, hooks, MCP servers, and marketplace management
  • ed3d-hook-skill-reinforcement — EXPERIMENTAL. A UserPromptSubmit hook that directs the model to consider and activate useful skills.
  • ed3d-hook-claudemd-reminder — A PostToolUse hook that reminds to invoke project-claude-librarian before committing when git status or git log reveals changes that may warrant CLAUDE.md updates.
  • ed3d-hook-security-hardening — PreToolUse and PostToolUse hooks that catch secrets leakage patterns: echoing env vars, reading secret files, tokens in URLs, and missing gitignore/permissions on sensitive files.
  • ed3d-playwright — Playwright automation toolkit with MCP integration, specialized agent for browser control, and best practice skills
  • ed3d-session-reflection — EXPERIMENTAL. Session awareness and conversation review tooling. Captures session metadata via SessionStart hook and provides conversation review agents and skills for analyzing prompting effectiveness, agent performance, and environment gaps.

About this listing

Ed3d Plugins is a community plugin on GitHub by ed3dai, 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 30 skills, 4 subagents, 11 plugins in this marketplaces. No license stated in the repo, so check with the author before reusing its code. We checked commit 0c90f4b5f039. It's one of 52 listings in the Research 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.

Ed3d Plugins FAQ

How do I install Ed3d Plugins in Grok Build?

Add the repo as a marketplace with grok plugin marketplace add ed3dai/ed3d-plugins, then run grok plugin install ed3d-00-getting-started@ed3dai/ed3d-plugins --trust. This repo's marketplace has 11 plugins; we checked ed3d-00-getting-started, ed3d-house-style, ed3d-plan-and-execute. Install another the same way: grok plugin install <name>@ed3dai/ed3d-plugins --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Is Ed3d Plugins an official Grok Build plugin?

No. Ed3d Plugins is a community plugin on GitHub by ed3dai, 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 Ed3d Plugins include?

According to what Grok loaded in our install check, Ed3d Plugins includes 30 skills, 4 subagents, 11 plugins in this marketplaces: getting-started, asking-clarifying-questions, brainstorming, executing-an-implementation-plan, finishing-a-development-branch, requesting-code-review….

Details

Type
Plugin
Category
Research
Source
Community Claude Code plugin, installs in Grok
License
No license stated
Author
ed3dai
Keywords
claude, claude-code, claude-code-plugin, claude-code-plugin-marketplace, skills
Source repo
https://github.com/ed3dai/ed3d-plugins
Checked commit
0c90f4b5f039
Homepage
https://ed3d.net
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 Ed3d Plugins? Add the badge; it links to this page.

Listed on GrokStacks

Markdown

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

HTML

<a href="https://grokstacks.com/p/ed3d-plugins/"><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/ed3d-plugins/" 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">Ed3d Plugins</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 30 skills, 4 subagents, 11 plugins in this marketplaces</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">Ed&#x27;s repo of Claude Code plugins, centered around a research-plan-implement workflow. Only a tiny bit cursed. If…</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[Ed3d Plugins on GrokStacks](https://grokstacks.com/p/ed3d-plugins/)**: Community plugin for Grok Build with 30 skills, 4 subagents, 11 plugins in this marketplaces. Install: `grok plugin install ed3d-00-getting-started@ed3dai/ed3d-plugins --trust` (after `grok plugin marketplace add ed3dai/ed3d-plugins`)

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

Also in Research

Academic Research Skills

Academic Research Skills for Claude Code: research → write → review → revise → finalize

Community Claude Code plugin, installs in GrokPluginResearch

AISafetyHot Hub

Safety News & Research Monitor. https://aisafetyhot.com

Community Claude Code plugin, installs in GrokPluginResearchNeeds sign-in

alirezarezvani/claude-skills

380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8 more coding agents — engineering, marketing, product, compliance, C-level advisory, research, business operations, commercial & finance, and your daily productivity skills.

Community Claude Code plugin, installs in GrokPluginResearch

Arbor

A generalist autonomous research agent — runs experiments, researches, and iteratively optimizes, autonomously.

Community Claude Code plugin, installs in GrokPluginResearch

Arxiv MCP Server

A local MCP server for agent literature work. Original-LaTeX section reads, BibTeX from arXiv metadata, and topic watches. Papers stay on disk. Search is optional.

Community Claude Code plugin, installs in GrokPluginResearch

Aso Skills

AI agent skills for App Store Optimization (ASO) and app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent Skills-compatible AI assistant to help with keyword research, metadata optimization, competitor analysis, and app growth.

Community Claude Code plugin, installs in GrokPluginResearch

All 52 research listings →