Agent Skills for production-ready Golang projects

AI agent skills are reusable instruction sets that extend your coding assistant with domain-specific expertise, loaded on demand so they don't bloat your context. This repository covers Go-specific skills only (language, testing, security, observability, etc.); for dev workflow skills (git conventions, CI/CD, PR reviews) you'll want to add a separate skills plugin.

For generic skills, please visit cc-skills.

[!IMPORTANT]
Bootstrapped with Claude Code by distilling my Go project commits. Edited, tested, reviewed and reworked by a human.

No AI slop here. AI-made skills are useless.

🚀 How to use

Install with skills CLI (universal, works with any Agent Skills-compatible tool):

npx skills add https://github.com/samber/cc-skills-golang --all
# or a single skill:
npx skills add https://github.com/samber/cc-skills-golang --skill golang-performance

/plugin marketplace add samber/cc
/plugin install cc-skills-golang@samber

git clone https://github.com/samber/cc-skills-golang.git ~/.openclaw/skills/cc-skills-golang
# or in workspace:
git clone https://github.com/samber/cc-skills-golang.git ~/.openclaw/workspace/skills/cc-skills-golang

gemini extensions install https://github.com/samber/cc-skills-golang

git clone https://github.com/samber/cc-skills-golang.git  ~/.cursor/skills/cc-skills-golang

/plugin install https://github.com/samber/cc-skills-golang
# or
git clone https://github.com/samber/cc-skills-golang.git ~/.copilot/skills/cc-skills-golang

git clone https://github.com/samber/cc-skills-golang.git ~/.agents/skills/cc-skills-golang

git clone https://github.com/samber/cc-skills-golang.git ~/.agents/skills/cc-skills-golang

git clone https://github.com/samber/cc-skills-golang.git ~/.antigravity/skills/cc-skills-golang

🧩 Skills

These skills are designed as atomic, cross-referencing units. A skill may reference conventions defined in another (e.g. error-handling rules that affect logging live in golang-error-handling, not golang-observability). Installing only a subset will give you a partial and potentially inconsistent view of the guidelines. For best results, install all general-purpose skills together.

• ⭐️ Recommended
• ✅ Published
• 👷 Work in progress
• ❌ To-do
• ⚡ Command available
• 🧠 Ultrathink automatically
• ⚙️ Overridable (see doc below)
• Description (tok): weight of the description field from YAML frontmatter, always loaded into Claude's context for skill triggering
• SKILL.md (tok): weight of the full SKILL.md file loaded when the skill triggers
• Directory (tok): weight of all files in the skill directory (SKILL.md + referenced markdown files)

General purpose:

Tools:

🧪 Skill evaluations

See EVALUATIONS.md for the full per-skill breakdown.

🎯 Tuning Skill Triggers

If a skill triggers too often or not often enough, please open an issue suggesting a description change. The description field in SKILL.md frontmatter is the primary triggering mechanism — small wording adjustments can significantly improve trigger accuracy. Some SKILL.md files might have a When to use section which is another level of exclusion. Finally, SKILL.md files are an entrypoint for lazy loading references with deep knowledge located in references/.

🔄 Overlap

Claude reports very little overlap between skills in this repo, thanks to cross-reference. I suggest enabling most of the skills and leveraging lazy loading. The recommended ⭐️ skills load ~1,100 tokens of descriptions at startup; full skill content is only pulled in when relevant. Note:

• I estimate that 50% of golang-naming and golang-code-style overlap with linters (golangci-lint).
• A large part of the security rules in golang-security have been distilled from the Bearer (SAST) checklist. The skill is still useful for methodology.
• If your team has its own conventions, create a company skill and declare the override explicitly near the top of its body: This skill supersedes samber/cc-skills-golang@golang-naming skill for [company] projects. Skills marked ⚙️ in the table above support this mechanism.

✍️ Contribute

• 100 tokens per skill description - what? when to use this skill?
• 1.000–2.500 tokens per SKILL.md — keep the main file focused on essentials
• Use secondary markdown files for depth — reference them from SKILL.md with relative links (e.g., [Logging](./logging.md)). Claude reads these on demand when the topic is relevant, so they don't count against the context budget until needed
• Up to 10.000 tokens for full skill and secondary files
• 2–4 skills loaded simultaneously in a typical session — design skills to coexist
• Stay below ~10k tokens of total loaded SKILL.md anytime to avoid degrading response quality

For more guidelines, please check CLAUDE.md.

💫 Fuel the Revolution

• ⭐️ Star this repo - Your star powers the caffeine engine!
• ☕️ Buy me a coffee - I'll literally use it to build more skills while drinking actual coffee

📝 License

Copyright © 2026 Samuel Berthe.

This project is under MIT license.