Screened · automated checks passed
golang-naming
What the author says it does
Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.
Quoted from the skill's own SKILL.md trigger description — this is what tells
Claude when to activate it. Not yet verified by us.
Automated screening
100/100 validator score
Scored by the same rules as our free SKILL.md validator: trigger description quality, body substance, structure. Automated — a human bench test is the next step in the pipeline.
Install (unverified — review first)
git clone https://github.com/samber/cc-skills-golang # skill lives at: skills/golang-naming/SKILL.md
SkillProof status
This skill is in our test queue. We install every skill in a clean environment, run a trigger battery and score output against a baseline before it earns a catalog page — the full protocol is public. Until then, treat it like any unreviewed dependency: read the SKILL.md and any scripts before installing.
Already tested in Testing & QA
- Screen Reader Testing Screen reader testing playbook for VoiceOver, NVDA, and JAWS with ARIA fixes.
- Skill Security Auditor OWASP-mapped code/secrets/config audit with working bundled scan scripts
- Web Quality Audit Lighthouse-style audit across Performance, Accessibility, SEO, and Best Practices with severity tiers.
- OSINT Methodology Structured 5-stage external recon methodology with confidence levels, severity rubric, and OpSec rules.