Apex Microsoft Docs
jonathan-vella/apex
ANALYSIS SKILL — Query official Microsoft documentation to understand concepts, find tutorials, and learn how services work.
Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces…
Install Go Spec Reviewer
$ npx skills add inference-gateway/inference-gateway --skill go-spec-reviewer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install inference-gateway/inference-gateway go-spec-reviewer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/inference-gateway/inference-gateway.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/go-spec-reviewer .claude/skills/go-spec-reviewer && rm -rf skills-srcUse ~/.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/
Install the "go-spec-reviewer" agent skill from https://github.com/inference-gateway/inference-gateway/tree/main/.agents/skills/go-spec-reviewer into .claude/skills/go-spec-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-spec-reviewer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/inference-gateway/inference-gateway/tree/main/.agents/skills/go-spec-reviewerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add inference-gateway/inference-gateway --skill go-spec-reviewer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install inference-gateway/inference-gateway go-spec-reviewer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inference-gateway/inference-gateway.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/go-spec-reviewer .agents/skills/go-spec-reviewer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "go-spec-reviewer" agent skill from https://github.com/inference-gateway/inference-gateway/tree/main/.agents/skills/go-spec-reviewer into .agents/skills/go-spec-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-spec-reviewer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add inference-gateway/inference-gateway --skill go-spec-reviewer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install inference-gateway/inference-gateway go-spec-reviewer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inference-gateway/inference-gateway.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/go-spec-reviewer .cursor/skills/go-spec-reviewer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "go-spec-reviewer" agent skill from https://github.com/inference-gateway/inference-gateway/tree/main/.agents/skills/go-spec-reviewer into .cursor/skills/go-spec-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-spec-reviewer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/inference-gateway/inference-gateway.git --path .agents/skills/go-spec-reviewer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add inference-gateway/inference-gateway --skill go-spec-reviewer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install inference-gateway/inference-gateway go-spec-reviewer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inference-gateway/inference-gateway.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/go-spec-reviewer .gemini/skills/go-spec-reviewer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "go-spec-reviewer" agent skill from https://github.com/inference-gateway/inference-gateway/tree/main/.agents/skills/go-spec-reviewer into .gemini/skills/go-spec-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-spec-reviewer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install inference-gateway/inference-gateway go-spec-reviewerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add inference-gateway/inference-gateway --skill go-spec-reviewer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/inference-gateway/inference-gateway.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/go-spec-reviewer .github/skills/go-spec-reviewer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "go-spec-reviewer" agent skill from https://github.com/inference-gateway/inference-gateway/tree/main/.agents/skills/go-spec-reviewer into .github/skills/go-spec-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-spec-reviewer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add inference-gateway/inference-gateway --skill go-spec-reviewer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install inference-gateway/inference-gateway go-spec-reviewer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inference-gateway/inference-gateway.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/go-spec-reviewer .opencode/skills/go-spec-reviewer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "go-spec-reviewer" agent skill from https://github.com/inference-gateway/inference-gateway/tree/main/.agents/skills/go-spec-reviewer into .opencode/skills/go-spec-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-spec-reviewer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
go-spec-reviewer- GitHub stars
- 214
- Token cost
- ~1.2k tokens
- SKILL.md length
- 148 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces…
- A user has a Go spec to review
- SKILL.md covers When to use and How to dispatch
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Asks is this spec ready?
What it does
Go Spec Reviewer is an agent skill from inference-gateway/inference-gateway. Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces, explicit wrapped errors, context propagation) plus Cobra/Viper conventions where applicable. Use when a user has a Go spec to review, asks "is this spec ready?", or is about to implement from a written design. Distilled from spf13/go-skills and adapted to this repo's conventions.
Its SKILL.md is about 1.2k 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 DevOps & Cloud, covering Architecture decision records and Subagents. It works with DeepSeek, Model Context Protocol, OpenAI and Kubernetes. The repository describes itself as: An open-source, cloud-native, high-performance gateway unifying multiple LLM providers, from local solutions like Ollama to major cloud providers such as OpenAI, Groq, Cohere… The licence is Apache-2.0.
When your agent uses it
- A user has a Go spec to review
- Asks is this spec ready?
- Is about to implement from a written design
Example prompts
- “is this spec ready?”
- “/go-spec-reviewer”
What it can do on your machine
Read from SKILL.md and the folder at commit 14ec752. 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
Links to these hosts (documentation or services it may open):
github.com
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 Spec Reviewer loads about 1.2k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 148 words of instructions outside code blocks.
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 inference-gateway/inference-gateway at commit 14ec752, republished under its Apache-2.0 licence (© inference-gateway). 148 words, ~1,179 tokens.
Download SKILL.mdSave it as
.claude/skills/go-spec-reviewer/SKILL.md (or your agent's skills folder).- name
- go-spec-reviewer
- description
- Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces, explicit wrapped errors, context propagation) plus Cobra/Viper conventions where applicable. Use when a user has a Go spec to review, asks "is this spec ready?", or is about to implement from a written design. Distilled from spf13/go-skills and adapted to this repo's conventions.
- license
- Apache-2.0
Go Spec Reviewer
Dispatch a subagent to verify a Go design spec is complete, consistent, and idiomatic before implementation begins - the cheapest place to catch a flawed design. The reviewer channels Rob Pike, the stdlib authors, and spf13: reject needless abstraction, demand explicit error handling and context propagation, expect the simplest design that works. It complements plan mode with a focused spec gate.
When to use
- A spec or design doc to review, or the question "is this spec ready?"
- About to implement from a written spec
- A technical review of a planned feature before any code is written
How to dispatch
Spawn a general-purpose subagent (the Agent tool) pointed at the spec file,
with the prompt below. It returns Status / Issues / Recommendations - it does
not edit code.
You are a Go spec reviewer. Verify this spec is complete and ready for
implementation, through the lens of idiomatic Go.
Think like Rob Pike: is it simple, doing one thing well?
Think like the stdlib authors: small interfaces, defined at the point of use?
Think like spf13: if it's a CLI, does it follow Cobra/Viper conventions?
Spec to review: <SPEC_FILE_PATH>
Step 1 - Codebase context. Before reviewing, explore the repo for conventions and
conflicts: list packages under internal/ and cmd/; for a Cobra CLI, scan cmd/ for
package-level flag vars (all cmd files share one package -> name collisions); check
cmd/root.go for command registration; note existing types/interfaces the spec
should reuse rather than reinvent.
Step 2 - Go philosophy:
| Concern | Look for |
| ----------- | -------- |
| Simplicity | layers/abstractions with one implementation; over-engineering |
| Interfaces | consumer-defined? small (1-3 methods)? real polymorphism? |
| Errors | returned explicitly, wrapped with %w, never silently swallowed? |
| Context | ctx threaded through I/O and long calls? timeouts set? |
| Concurrency | goroutines with clear ownership and a stop condition? races? |
| Packages | one clear purpose each? new package justified vs extending one? |
| Naming | short, no stutter (pkg.PkgThing)? |
| YAGNI | driven by stated requirements, not speculative futures? |
Step 3 - Cobra/Viper (skip if not a CLI):
| Concern | Look for |
| ------------ | -------- |
| Flag naming | package-level flag vars unique across cmd/ (one shared package) |
| Registration | new subcommands added in cmd/root.go via AddCommand? |
| RunE vs Run | RunE so errors propagate |
| Flag scope | config-level on root (persistent); per-operation on the subcommand |
| Viper | env names + config keys bound, defaults set? |
Step 4 - Completeness:
| Category | Look for |
| ------------ | -------- |
| Completeness | TODO/TBD/placeholders, missing error paths |
| Consistency | contradictions, types named differently across sections |
| Clarity | ambiguity that would make two implementors build different things |
| Scope | one focused implementation, not several subsystems |
| Security | user input sanitized before shell/path/external use? |
Calibration: only flag issues that would cause real implementation problems - a
missing error path, a flag collision that won't compile, an abstraction that adds
complexity without enabling anything. Skip wording and formatting nits. Respect
THIS repo's established conventions (the internal/ domain-infra-services split, the
DI container, counterfeiter-generated mocks, the per-mode bash allow-list,
pluggable storage backends) - judge idiomaticity within them; do not flag the
chosen architecture itself as a defect. Approve unless gaps would lead to a flawed
or incomplete implementation.
Output:
## Go Spec Review
Status: Approved | Issues Found
Issues (if any):
- [Section X]: [specific issue] - [why it matters for implementation]
Recommendations (advisory, non-blocking):
- [correctness / idiomaticity / clarity suggestions]Adapted from spf13/go-skills (MIT, by Steve Francia) for this repo's local subagent tooling and conventions. Pairs with go and cobra-viper.
© inference-gateway, Apache-2.0. 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 .agents/skills/go-spec-reviewer of inference-gateway/inference-gateway.
Open the folder on GitHubat commit 14ec752
Compare with similar skills
Go Spec Reviewer 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Go Spec Reviewer this skillinference-gateway/inference-gateway | 214 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Apex Microsoft Docsjonathan-vella/apex | 217 | — | ~966 | Automated safety check: Pass | MIT | |
| NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress | 5.1k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| K8s Agent Sandbox MCPkubernetes-sigs/agent-sandbox | 4.2k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Devsydevsy-org/devsy | 113 | — | ~1.7k | Automated safety check: Pass | MPL-2.0 | |
| Openai Docsaafqaq/codex-lb-enhanced | 103 | 2 repos | ~861 | Automated safety check: Pass | Apache-2.0 |
Similar skills
NGINX Ingress Controller Feature Checklists
nginx/kubernetes-ingress
Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.
- Official
K8s Agent Sandbox MCP
kubernetes-sigs/agent-sandbox
An MCP server skill for managing Kubernetes sandboxes. An agent skill from kubernetes-sigs/agent-sandbox.
Devsy
devsy-org/devsy
Operate Devsy workspaces and providers for end users. An agent skill from devsy-org/devsy.
Openai Docs
aafqaq/codex-lb-enhanced
A skill your agent uses when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions…
Deploy
noskillish/bankmcp
Deploy BankMCP™ to a small server so it works in claude.ai and on the phone: Railway or Fly.io, volume, domain, setup page, connector.
More from inference-gateway/inference-gateway
Go
inference-gateway/inference-gateway
Idiomatic Go - package and interface design, error wrapping, table-driven tests, generics, the modern standard library (slices/maps/cmp/errors.Join), current syntax, and logging discipline.
Go Concurrency
inference-gateway/inference-gateway
Idiomatic Go concurrency - sync primitives, channel semantics, the select statement, and the standard channel patterns (cancellation/done-channel, fan-out/fan-in, pipeline, or-done, context…
Related
Categories
Questions about Go Spec Reviewer
What does Go Spec Reviewer do?
Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces…. Go Spec Reviewer is an agent skill from inference-gateway/inference-gateway. Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces, explicit wrapped errors, context propagation) plus Cobra/Viper conventions where applicable.
When should I use Go Spec Reviewer?
Go Spec Reviewer fits situations like: A user has a Go spec to review; asks is this spec ready?; is about to implement from a written design.
How do I install Go Spec Reviewer in Claude Code?
Run `npx skills add inference-gateway/inference-gateway --skill go-spec-reviewer -a claude-code`. Or copy the skill folder (.agents/skills/go-spec-reviewer in inference-gateway/inference-gateway) into .claude/skills/go-spec-reviewer in your project. Claude Code loads it when a task matches its description.
How do I install Go Spec Reviewer in Codex?
Run `npx skills add inference-gateway/inference-gateway --skill go-spec-reviewer -a codex`. Or copy the skill folder (.agents/skills/go-spec-reviewer in inference-gateway/inference-gateway) into .agents/skills/go-spec-reviewer in your project. Codex loads it when a task matches its description.
Can I use Go Spec Reviewer 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 inference-gateway/inference-gateway --skill go-spec-reviewer -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-spec-reviewer, .gemini/skills/go-spec-reviewer, .github/skills/go-spec-reviewer and .opencode/skills/go-spec-reviewer in your project.
What does Go Spec Reviewer need to run?
SKILL.md names no scripts, command-line tools or credentials: Go Spec Reviewer is instructions for the agent only.
Does Go Spec Reviewer access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Go Spec Reviewer 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 Spec Reviewer use?
Go Spec Reviewer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Go Spec Reviewer use?
About 1.2k tokens (SKILL.md is roughly 4.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 Spec Reviewer?
Skills that share tags, products or a category with Go Spec Reviewer: Apex Microsoft Docs (jonathan-vella/apex, 217 stars), NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k stars), K8s Agent Sandbox MCP (kubernetes-sigs/agent-sandbox, 4.2k stars) and Devsy (devsy-org/devsy, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Go Spec Reviewer?
inference-gateway (a GitHub organization) maintains it in inference-gateway/inference-gateway, which has 214 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 10, 2026.
Source: inference-gateway/inference-gateway on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.