FradSer/dotclaude plugin for Grok Build

Community Claude Code plugin, installs in GrokPluginSecurityMCP: manual setup

A comprehensive development environment with specialized AI agents for code review, security analysis, and technical leadership.

How to install FradSer/dotclaude in Grok Build

grok plugin install FradSer/dotclaude --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.

We install this repo directly: Grok Build 1.0.62 can't install it through its own marketplace file. This repo's marketplace has 23 plugins; we checked git. Install another the same way: grok plugin install <name>@FradSer/dotclaude --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Command format: Grok Build's plugin guide

Skills work, MCP part needs manual setup. Grok loads FradSer/dotclaude's skills and commands, but not its MCP server: it needs settings that Claude Code asks for when you install it (userConfig), and Grok doesn't ask for them. Add the server yourself:

grok mcp add deepwiki-code-context https://mcp.deepwiki.com/mcp
grok mcp add context7-code-context https://mcp.context7.com/mcp
grok mcp add exa-code-context 'https://mcp.exa.ai/mcp?tools=get_code_context_exa' -H 'x-api-key: ${EXA_API_KEY}'

Set the variable shown in ${…} in your shell before starting Grok (Grok fills it in when it loads the server).

Then start a new session or press r in /mcps. If it asks you to sign in, select it in /mcps and press i.

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

What it contains

Skills (40)

  • lark — Lark/Feishu CLI router: match intent, then Read the Entry file under lark-*/ (e.g. lark-doc/lark-doc.md). Covers docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, conta
  • commit — Creates clean, conventional git commits using standard git. Use when the user asks to "commit", "git commit", "create commit", or wants to commit staged or unstaged changes.
  • commit-and-push — Creates clean conventional git commits using standard git and pushes changes to the remote repository. Use when the user asks to "commit and push", "push changes", or complete a commit followed by git push.
  • finish-feature — Finalizes and merges a feature branch into develop using git-flow, then prunes stale branches and worktrees. This skill should be used when the user asks to "finish a feature", "merge feature branch", "complete feature", "git flow feature f
  • finish-hotfix — Finalizes a hotfix and merges it into main and develop using git-flow, then prunes stale branches and worktrees. This skill should be used when the user asks to "finish a hotfix", "merge hotfix branch", "complete hotfix", "git flow hotfix f
  • finish-release — Finalizes a release and merges it into main and develop with a tag using git-flow, then prunes stale branches and worktrees. This skill should be used when the user asks to "finish a release", "merge release branch", "complete release", "gi
  • start-feature — Starts working on a new feature branch using git-flow. This skill should be used when the user asks to "start a feature", "create feature branch", "begin new feature", "git flow feature start", or wants to start a new feature. Accepts eithe
  • start-hotfix — Begins a hotfix for a production issue using git-flow. This skill should be used when the user asks to "start a hotfix", "create hotfix branch", "fix a critical bug", "git flow hotfix start", or wants to begin a hotfix. Accepts either an ex
  • start-release — Begins a new version release using git-flow. This skill should be used when the user asks to "start a release", "create release branch", "prepare a release", "git flow release start", or wants to begin a new version release. Accepts either
  • storm-engine — Provides the shared STORM methodology, artifact layout, stage-gating contract, citation hygiene, and retrieval fallback. Use when executing any /storm:* skill (generate, research, outline, write, polish). Internal knowledge; never user-invo
  • storm-generate — Run the full STORM pipeline end-to-end. This skill should be used when the user asks to "generate a storm article", "write a wikipedia-style article about X", "research and write a long-form piece on X", or invokes /storm:generate. Orchestr
  • storm-research — Run STORM phase 1 — multi-perspective research. This skill should be used when the user asks to "research a topic for an article", "find sources on X from multiple perspectives", "do storm research on X", or invokes /storm:research. Discove
  • storm-outline — Run STORM phase 2 — outline generation. This skill should be used when the user asks to "generate an outline for a storm article", "draft a wikipedia-style outline", or invokes /storm:outline. Produces a draft outline from parametric knowle
  • storm-write — Run STORM phase 3 — per-section article writing. This skill should be used when the user asks to "write the article sections", "draft the storm article", or invokes /storm:write. Writes each outline section in parallel with inline citations
  • storm-polish — Run STORM phase 4 — article polishing. This skill should be used when the user asks to "polish the storm article", "finalize the article", or invokes /storm:polish. Adds a summary section, removes duplicate content, and verifies citation in
  • better-interface — User-invoked, cross-discipline interface review that coordinates six domain references: accessibility, layout, writing, typography, colors, and ui. Use when explicitly invoked for a holistic review of a screen, flow, feature, or product int
  • plugin-best-practices — This skill should be used when the user asks to "validate plugin structure", "review manifest files", "check frontmatter compliance", "verify tool invocation patterns", "explain plugin component types", or needs Claude Code plugin architect
  • optimize-plugin — This skill should be used when the user asks to "validate a plugin", "optimize plugin", "check plugin quality", "review plugin structure", or "run plugin optimizer".
  • ask-matt — Recommends the skill or flow that fits the user's situation. A router over the skills in this repo. Use when the user asks which skill to use, is unsure what fits, or needs a pointer to the right workflow.
  • diagnosing-bugs — Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
  • grill-with-docs — Runs a relentless interview that sharpens a plan or design and creates docs (ADRs and glossary) along the way. Use when the user wants to stress-test a plan or design, or produce decision records.
  • triage — Moves issues and external PRs through a state machine of triage roles — categorise, verify, grill, and write agent-ready briefs. Use when the user says "triage this issue" or wants agent-ready issue briefs.
  • improve-codebase-architecture — Scans a codebase for deepening opportunities, presents them as a visual HTML report, then grills through the chosen one. Use when the user wants to improve codebase architecture or find refactoring opportunities.
  • setup-matt-pocock-skills — Configures a repo for the engineering skills: issue tracker, triage label vocabulary, and domain doc layout. Use once before first use of the other engineering skills, when the user says "set up the skills" or "initialize repo config".
  • bdd — Behavior-driven development: Discovery → Formulation → Automation. Use when the user wants to build features or fix bugs via Gherkin scenarios and the BDD lifecycle, or mentions BDD/Gherkin/Executable Specifications. Delegates test implemen
  • tdd — BDD-driven test implementation: red-green loop mechanics, seams, mocking, and test quality under BDD Automation. Use when the user wants to write or improve tests during BDD implementation, needs guidance on test structure, or asks about te
  • to-spec — Turns the current conversation into a spec and publishes it to the project issue tracker, with no interview. Use when the user says "write a spec", "create a PRD", or wants the discussion captured as a spec.
  • to-tickets — Breaks a plan, spec, or conversation into tracer-bullet tickets that declare their blocking edges, published to the configured tracker. Use when the user says "break this into tickets" or wants a plan decomposed into vertical slices.
  • wayfinder — Plans a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on the issue tracker, resolved one at a time. Use when the user has a large ambiguous goal and wants the route charted.
  • implement — Implements a piece of work from a spec or ticket set. Use when the user says "implement this spec", "work the tickets", or wants code written from an existing plan.
  • prototype — Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
  • research — Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
  • domain-modeling — Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
  • codebase-design — Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs th
  • code-review — Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?).
  • resolving-merge-conflicts — Use when you need to resolve an in-progress git merge/rebase conflict.
  • wizard — Generates an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, running a one-off migratio
  • grill-me — Runs a relentless interview that sharpens a plan or design. Use when the user wants to be grilled on an idea, pressure-test a plan, or refine a design through questioning.
  • grilling — Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
  • handoff — Compacts the current conversation into a handoff document for another agent to pick up. Use when the user says "hand this off" or wants the work continued by a fresh session.

Subagents (2)

  • plugin-optimizer:plugin-optimizer — Use this agent when validating plugin structure, analyzing documentation redundancy, or executing optimization workflows. Trigger when user asks to "validate plugin", "check for redundancy", "optimize
  • git-agent:git-agent — Thin wrapper around git-agent CLI. Routes the user's intent to the right git-agent CLI subcommand. By default, any input is treated as a commit intent and passed to `git-agent commit --intent`. Runs w

Hooks (1)

  • hooks — PreToolUse

Plugins in this marketplace (23)

  • git — Conventional Git automation, advanced repository management, and GitFlow workflow automation for feature, hotfix, and release branches with post-finish cleanup
  • git-agent — AI-first Git CLI automation — atomic AI commits, co-change relations, autonomous git health agent, pre-tool hook safety, and workspace initialization
  • github — GitHub project operations with quality gates
  • swiftui — SwiftUI code review with modern API best practices
  • office — Office productivity skills for patent applications, PRD generation, video generation, Remotion programmatic video authoring, and AI writing trope detection
  • generate-image — Generate or edit images via two backends: Google Gemini (gemini-3-pro-image) or any OpenAI-compatible endpoint (gpt-image-2, dall-e-3)
  • lark — Feishu/Lark CLI skills, mirrored from larksuite/cli — docs, sheets, IM, calendar, approval, drive, wiki, contacts, and more
  • marketing — Marketing skills for AI agents, mirrored from coreyhaines31/marketingskills — CRO, copywriting, SEO, paid ads, ad creative, analytics, and growth
  • hyperframes — HyperFrames HTML-based video authoring skills, mirrored from heygen-com/hyperframes — keyframes, animation, captions, motion graphics, and remotion-to-hyperframes conversion
  • refactor — Agent and skills for code simplification and refactoring to improve code quality while preserving functionality
  • mattpocock — BDD-first engineering skills forked from mattpocock/skills (synced 2026-09-23)
  • superpowers — Advanced development workflow orchestration with BDD support and self-improving skills
  • plugin-optimizer — Validates and optimizes Claude Code plugins against official best practices and file patterns
  • acpx — Knowledge base for acpx - a headless ACP CLI for agent-to-agent communication
  • code-context — Retrieve code context for any repo, library, or natural-language query via DeepWiki, Context7, Exa, git clone, and web search+fetch
  • utils — General-purpose utility skills for documentation, writing, and project maintenance
  • autoresearch — Autonomous research loop inspired by karpathy/autoresearch — give it a plain-language goal; it infers a recommended contract, then grills each decision with you (goal measurability, artifact, evaluator, bounds) before iterating: cheap sequential rounds that escalate to a parallel GAN tournament when
  • antigravity — Delegate tasks and deep research to Google Gemini Managed Agents (Antigravity) running in a remote sandbox, then read the results back
  • storm — Wikipedia-style long-form article generation via multi-perspective question asking and retrieval — a Claude-native port of Stanford STORM's two-stage research-to-article pipeline
  • hardware — Hardware and EDA toolkit. Drives the KiCad CLI for schematic/PCB export and checks, and OpenSCAD for parametric 3D/2D part design and STL/DXF/PNG output.
  • memory — Active memory writing during conversation, plus manual /memory:consolidate with theme clustering, ground-truth prune, adversarial pass, and machine validator — no auto-consolidation
  • pi — Bridges to pi (dev/pi), a minimal terminal coding harness. Delegates coding tasks to the pi CLI for execution with full file and git context.
  • interfaces — Agent skills for building great product interfaces, from typography and color to accessibility and UX writing

About this listing

FradSer/dotclaude is a community plugin on GitHub by FradSer, 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 40 skills, 2 subagents, 1 hook, 23 plugins in this marketplaces. Its license is MIT. We checked commit f55ac1cea492. It's one of 79 listings in the Security 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.

FradSer/dotclaude FAQ

How do I install FradSer/dotclaude in Grok Build?

Run grok plugin install FradSer/dotclaude --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. This repo's marketplace has 23 plugins; we checked git. Install another the same way: grok plugin install <name>@FradSer/dotclaude --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Is FradSer/dotclaude an official Grok Build plugin?

No. FradSer/dotclaude is a community plugin on GitHub by FradSer, 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 FradSer/dotclaude include?

According to what Grok loaded in our install check, FradSer/dotclaude includes 40 skills, 2 subagents, 1 hook, 23 plugins in this marketplaces: lark, commit, commit-and-push, finish-feature, finish-hotfix, finish-release….

Details

Type
Plugin
Category
Security
Source
Community Claude Code plugin, installs in Grok
License
MIT
Author
FradSer
Keywords
claude
Source repo
https://github.com/FradSer/dotclaude
Checked commit
f55ac1cea492
Homepage
https://dotclaude.frad.me
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 FradSer/dotclaude? Add the badge; it links to this page.

Listed on GrokStacks

Markdown

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

HTML

<a href="https://grokstacks.com/p/fradser-dotclaude/"><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:

FradSer/dotclaudeCommunity plugin for Grok Build · 40 skills, 2 subagents, 1 hook, 23 plugins in this marketplacesA comprehensive development environment with specialized AI agents for code review, security analysis, and technical…View on GrokStacks →
<a href="https://grokstacks.com/p/fradser-dotclaude/" 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">FradSer/dotclaude</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 40 skills, 2 subagents, 1 hook, 23 plugins in this marketplaces</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">A comprehensive development environment with specialized AI agents for code review, security analysis, and technical…</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[FradSer/dotclaude on GrokStacks](https://grokstacks.com/p/fradser-dotclaude/)**: Community plugin for Grok Build with 40 skills, 2 subagents, 1 hook, 23 plugins in this marketplaces. Install: `grok plugin install FradSer/dotclaude --trust`

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

Also in Security

Aaron Marketing Skills

120 marketing skills as an AI marketing staff — plugin, portable skills, or an 8-bot team across 7 disciplines (narrative, SEO/GEO, social, email, paid, influencer, launch) on one contract, with 8 auditor gates: TALE · CORE-EEAT · CITE · ECHO · SEND · ROAS · STAR · RAMP.

Community Claude Code plugin, installs in GrokPluginSecurity

Adrian

Open-source runtime AI agent security tool - monitors and controls AI agents, catching malicious tool use, prompt injection, and policy drift in real time, before the agent acts.

Community Claude Code plugin, installs in GrokPluginSecurity

Agent Beacon

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

Community Claude Code plugin, installs in GrokPluginSecurity

Agent Governance Toolkit

AI Agent Governance Toolkit — Policy enforcement, zero-trust identity, execution sandboxing, and reliability engineering for autonomous AI agents. Covers 10/10 OWASP Agentic Top 10.

Community Claude Code plugin, installs in GrokPluginSecurity

Agentguard

Security guard for AI agents — blocks malicious skills, prevents data leaks, protects secrets. 24 detection rules, runtime action evaluation, trust registry.

Community Claude Code plugin, installs in GrokPluginSecurity

Android Reverse Engineering Skill

Claude Code skill to support Android app's reverse engineering

Community Claude Code plugin, installs in GrokPluginSecuritySecurity tool

All 79 security listings →