Go API Playbook
Operational playbook for Go HTTP APIs — error wrapping, goroutine lifetimes, database/sql resource discipline, race-flagged verification. Read in full at the start of every task on this team.
Install
/plugin marketplace add toffyui/ccteamsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add toffyui/ccteams --skill go-api-playbookgit clone --depth 1 https://github.com/toffyui/ccteams.git /tmp/ccteams
mkdir -p ~/.claude/skills
cp -r /tmp/ccteams/teams/go-api/skills/go-api-playbook ~/.claude/skills/go-api-playbookPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Go API Playbook This is the literal procedure a frontier model follows when building or fixing Go HTTP services. Follow it step by step; the order is the point. Go's compiler catches type errors but is silent about the mistakes that actually ship bugs — dropped errors, leaked goroutines, unclosed rows — so those checks are yours. ## Operating loop 1. **Read `go.mod` before anything else.** Note (a) the `go` directive — you may not use language features newer than it (loop-var semantics changed in 1.22, `slices`/`maps` packages need 1.21, generics need 1.18); (b) the dependency list — if `chi`/`gin`/`echo`/`sqlx` is there, the project uses it; if not, you use `net/http` and `database/sql`, never a new dependency on your own authority. 2. **Find the local dialect and mirror it.** Before writing a handler, read two existing ones: `grep -rn "http.ResponseWriter" --include="*.go" .` — copy the project's routing registration, error-response shape (JSON envelope? plain `http.Error`?), and middleware chaining style exactly. A "better" pattern that differs from the neighbors is a defect here. 3. **Place code where the package layout says it goes.** Match existing package boundaries (`internal/`, `cmd/`, handler vs service vs store layers). Do not invent a new package for one function. 4. **Write the smallest coherent change**, then immediately run `go build ./...`. Build after every file, not at the end — Go's unused
Details
- Skill name
go-api-playbook- Repository
- toffyui/ccteams
- Path
teams/go-api/skills/go-api-playbook/SKILL.md- License
- MIT
- Repo updated
- 31 August 2026
FAQ
What does the Go API Playbook skill do?
Operational playbook for Go HTTP APIs — error wrapping, goroutine lifetimes, database/sql resource discipline, race-flagged verification. Read in full at the start of every task on this team.
How do I install the Go API Playbook skill?
Claude Code plugin: /plugin marketplace add toffyui/ccteams. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Go API Playbook popular?
It lives in toffyui/ccteams, which has 49 GitHub stars and 3 forks.
Related skills
Choose Team
49toffyui/ccteams
Pick and apply the best ccteams agent team for a described need using natural language — reads team metadata, selects the closest match, and applies it.
Debug Playbook
49toffyui/ccteams
Operational playbook for systematic debugging — hypothesis ledgers, discriminating experiments, mechanism sentences, minimal fixes, sibling hunts. Read in full at the start of every bug investigation.
Django Playbook
49toffyui/ccteams
Operational playbook for Django + DRF — settings/version detection, ORM loading strategy, migration discipline, serializer field hygiene, timezone rules, and exact verification commands. Read in full at the start of every task on this team.
Python Fastapi Playbook
49toffyui/ccteams
Operational playbook for FastAPI + Pydantic v2 async services — event-loop discipline, boundary validation, dependency lifetimes, response_model leaks, async ORM N+1s. Read in full at the start of every task on this team.
Rails Playbook
49toffyui/ccteams
Operational playbook for Ruby on Rails — version/test-framework detection, ActiveRecord loading strategy, callback boundaries, migration discipline, and exact verification commands. Read in full at the start of every task on this team.
Runtime Frameworks
49dynamics365ninja/d365fo-cli
Use the D365FO platform frameworks that decide behaviour at runtime — Feature Management, the SysExtension plug-in factory, telemetry and infolog, and the Global Address Book. Invoke when the user asks to add a feature flag, replace an if/switch chain with a registered strategy, log or capture infolog output, or read a party's address or contact details.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.