New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Go Rig

by mudrii in mudrii/openclaw-dashboard

A skill your agent uses when building, reviewing, or refactoring Go code in this repository.

MITAuto-check passedDevelopment

Install Go Rig

skills CLI
$ npx skills add mudrii/openclaw-dashboard --skill go-rig -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mudrii/openclaw-dashboard go-rig --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mudrii/openclaw-dashboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/go-rig .claude/skills/go-rig && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
go-rig
GitHub stars
458
Token cost
~682 tokens
SKILL.md length
327 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when building, reviewing, or refactoring Go code in this repository.

  • Works in 5 steps: Define the boundary behavior first. → Add the smallest failing test at the… → Implement the minimum code to pass. → …
  • Refactoring Go code in this repository
  • SKILL.md covers When To Use, Workflow, Testing Expectations and Design Discipline, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Go Rig is an agent skill from mudrii/openclaw-dashboard. Use this skill when building, reviewing, or refactoring Go code in this repository. It adds process discipline for TDD/ATDD, package boundaries, dependency injection, and review quality, and complements the always-on rules in AGENTS.md.

Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Design patterns, Test-driven development and Refactoring. The repository describes itself as: A beautiful, zero-dependency command center for OpenClaw AI agents. The licence is MIT.

When your agent uses it

  • Refactoring Go code in this repository
  • Tasks that involve Design patterns
  • Tasks that involve Test-driven development

Example prompts

  • “/go-rig”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Define the boundary behavior first.
  2. Add the smallest failing test at the closest useful layer.
  3. Implement the minimum code to pass.
  4. Refactor back to clarity.
  5. Repeat in small increments.

What it can do on your machine

Read from SKILL.md and the folder at commit b63ac25. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Go Rig loads about 682 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 327 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~682

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mudrii/openclaw-dashboard at commit b63ac25, republished under its MIT licence (© mudrii). 327 words, ~682 tokens.

Download SKILL.mdSave it as .claude/skills/go-rig/SKILL.md (or your agent's skills folder).
name
go-rig
description
Use this skill when building, reviewing, or refactoring Go code in this repository. It adds process discipline for TDD/ATDD, package boundaries, dependency injection, and review quality, and complements the always-on rules in AGENTS.md.

Go Rig

This is the native Codex Go workflow skill for this repository.

AGENTS.md owns:

  • always-on project constraints
  • Go version and toolchain expectations
  • compatibility, dependency, testing, and command policy

This skill owns:

  • TDD/ATDD workflow
  • design and abstraction discipline
  • dependency injection discipline
  • package-boundary judgment
  • review checklist for Go changes

When To Use

Use this skill when:

  • implementing a new behavior
  • refactoring Go code
  • changing package boundaries
  • changing exported APIs or JSON behavior
  • adding test seams, DI, or acceptance coverage

Workflow

  1. Define the boundary behavior first.
  2. Add the smallest failing test at the closest useful layer.
  3. Implement the minimum code to pass.
  4. Refactor back to clarity.
  5. Repeat in small increments.

If tests are not being run in the current turn, still design the change test-first.

Testing Expectations

Each meaningful change should consider:

  • happy path
  • invalid input and validation failure
  • edge and boundary cases
  • error paths
  • concurrency behavior when relevant

Use acceptance-style tests for user-visible behavior and unit tests for domain rules.

Design Discipline

  • Start with concrete types.
  • Add interfaces only when a real consumer needs substitution.
  • Keep packages domain-focused.
  • Avoid speculative abstractions.
  • Inject collaborators at boundaries instead of constructing them deep in domain code.
  • Prefer option structs over long positional parameter lists.

Package And API Discipline

  • Keep exported APIs stable unless compatibility work is intentional.
  • Keep root facade wrappers as zero-logic forwarding.
  • Translate weakly typed edge data into strict domain types quickly.
  • Avoid transport or persistence concerns leaking into core domain behavior.

Review Checklist

  • Boundaries are coherent.
  • Dependencies are explicit.
  • Functions are readable in one pass.
  • Tests cover behavior, not just implementation details.
  • JSON and API compatibility changes were reviewed intentionally.
  • Nil vs empty behavior is intentional.
  • Concurrency changes have shutdown and ownership semantics.

Repository Notes

  • The repository uses a root facade package over internal/app<domain>/.
  • New functionality belongs in internal/ first, with root wrappers added only for compatibility.
  • This repo has a zero-dependency bias; do not assume external helper libraries for tests or comparisons.

© mudrii, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/go-rig of mudrii/openclaw-dashboard.

Open the folder on GitHubat commit b63ac25

Compare with similar skills

Go Rig next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Go Rig compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Go Rig this skillmudrii/openclaw-dashboard458—~682Automated safety check: PassMIT
Py Rigmudrii/hermesd118—~6.3kAutomated safety check: PassMIT
Solidramziddin/solid-skills606—~2.7kAutomated safety check: PassNone
Effect TSmattiacerutti/supernova186—~2.8kAutomated safety check: PassMIT
Skill Writingmillionco/expect3.6k—~1.8kAutomated safety check: PassCustom licence
Happier Implementhappier-dev/happier1.9k—~4.2kAutomated safety check: PassMIT

Similar skills

  • Py Rig

    mudrii/hermesd

    A skill your agent uses when building, reviewing, or refactoring Python code that requires strong maintainability discipline: SRP, DRY, OCP, explicit dependency injection, TDD/ATDD workflow, strict…

    118 GitHub stars~6.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Solid

    ramziddin/solid-skills

    A skill your agent uses when writing code, implementing features, refactoring, planning architecture, designing systems, reviewing code, or debugging.

    606 GitHub stars~2.7k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Effect TS

    mattiacerutti/supernova

    Write idiomatic Effect v4 TypeScript following official best practices from effect-solutions and the Effect source.

    186 GitHub stars~2.8k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Skill Writing

    millionco/expect

    Write and improve agent skills (SKILL.md files). An agent skill from millionco/expect.

    3.6k GitHub stars~1.8k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • Happier Implement

    happier-dev/happier

    Implement, change, build, fix, refactor, migrate, or apply accepted review findings in the Happier repositories with canonical-owner discovery, scope-preserving solution economy, TDD, efficient…

    1.9k GitHub stars~4.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Omk Coding

    KaimingWan/oh-my-kiro

    Enforces coding best practices: deep-read before modify, LSP-first navigation, TDD red-green-refactor, minimal changes, self-review, verification.

    107 GitHub stars~2.4k tokensUpdated 6 mo ago
    DevelopmentAuto-check passed

More from mudrii/openclaw-dashboard

  • Go Rig

    mudrii/openclaw-dashboard

    A skill your agent uses when building, reviewing, or refactoring Go code that must follow strict design discipline — ATDD/TDD workflow, explicit dependency injection, package-boundary discipline…

    458 GitHub stars~2.8k tokensUpdated 16 days ago
    Auto-check passed

  • Frontend Dashboard

    mudrii/openclaw-dashboard

    A skill your agent uses when editing the embedded dashboard frontend in this repository.

    458 GitHub stars~361 tokensUpdated 16 days ago
    Auto-check passed

  • Go Review

    mudrii/openclaw-dashboard

    A skill your agent uses when the task is to review Go code in this repository.

    458 GitHub stars~325 tokensUpdated 16 days ago
    Auto-check passed

  • Project Ops

    mudrii/openclaw-dashboard

    A skill your agent uses when working on repository operations in this project, including build, test, lint, release, CI alignment, Makefile-driven checks, and operational packaging constraints.

    458 GitHub stars~387 tokensUpdated 16 days ago
    Auto-check passed

Categories

Questions about Go Rig

What does Go Rig do?

A skill your agent uses when building, reviewing, or refactoring Go code in this repository. Go Rig is an agent skill from mudrii/openclaw-dashboard. Use this skill when building, reviewing, or refactoring Go code in this repository.

When should I use Go Rig?

Go Rig fits situations like: refactoring Go code in this repository; tasks that involve Design patterns; tasks that involve Test-driven development.

How do I install Go Rig in Claude Code?

Run `npx skills add mudrii/openclaw-dashboard --skill go-rig -a claude-code`. Or copy the skill folder (.codex/skills/go-rig in mudrii/openclaw-dashboard) into .claude/skills/go-rig in your project. Claude Code loads it when a task matches its description.

How do I install Go Rig in Codex?

Run `npx skills add mudrii/openclaw-dashboard --skill go-rig -a codex`. Or copy the skill folder (.codex/skills/go-rig in mudrii/openclaw-dashboard) into .agents/skills/go-rig in your project. Codex loads it when a task matches its description.

Can I use Go Rig in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mudrii/openclaw-dashboard --skill go-rig -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/go-rig, .gemini/skills/go-rig, .github/skills/go-rig and .opencode/skills/go-rig in your project.

What does Go Rig need to run?

SKILL.md names no scripts, command-line tools or credentials: Go Rig is instructions for the agent only.

Does Go Rig access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Go Rig safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Go Rig use?

Go Rig is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Go Rig use?

About 682 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Go Rig?

Skills that share tags, products or a category with Go Rig: Py Rig (mudrii/hermesd, 118 stars), Solid (ramziddin/solid-skills, 606 stars), Effect TS (mattiacerutti/supernova, 186 stars) and Skill Writing (millionco/expect, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Go Rig?

mudrii (a GitHub user) maintains it in mudrii/openclaw-dashboard, which has 458 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 23, 2026.

Source: mudrii/openclaw-dashboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.