Skill audit report
golang-code-style Audit report.
Golang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See `samber/cc-skills-golang@golang-naming` skill), linter configuration (→ See `samber/cc-skills-golang@golang-lint` skill), or doc comments (→ See `samber/cc-skills-golang@golang-documentation` skill).
OpenAgentSkill Trust Score
OpenAgentSkill Trust Score
The Trust Score helps an agent decide whether a skill is safe enough to shortlist before installation.
GitHub adoption
PASS86
3.0K GitHub stars
Stars/forks activity
INFO77
3.0K stars, 197 forks; issue activity unavailable in current metadata
Recent maintenance
PASS100
2d since push
License clarity
PASS86
MIT
README/SKILL.md completeness
PASS86
Metadata includes enough usage and workflow context
Dependency/runtime risk
WARN56
command execution surface, network or browser surface
Install availability
PASS92
npx skills add samber/cc-skills-golang --skill golang-code-style
Install command safety
PASS92
standard package or runtime install path
Permission surface
FAIL36
shell or command execution, filesystem or document access
Repository evidence
PASS86
https://github.com/samber/cc-skills-golang/tree/main/skills/golang-code-style
Review status
INFO66
AI review data available
Agent Proven outcomes
INFO54
No agent outcome data yet
Checks
Install and adoption review
Install path
92
npx skills add samber/cc-skills-golang --skill golang-code-style
Repository
88
https://github.com/samber/cc-skills-golang/tree/main/skills/golang-code-style
License
86
MIT
Maintenance
100
2d since push
AI review
55
The SKILL.md excerpt references a 'Parallelizing Code Style Reviews' section that is not visible in the provided excerpt; ensure it exists in the full file to avoid broken references.
README/SKILL.md completeness
86
Usable description available
Dependency risk
56
command execution surface, network or browser surface
Install command safety
92
standard package or runtime install path
Permission surface
36
shell or command execution, filesystem or document access
Stars/forks activity
77
3.0K stars, 197 forks; issue activity unavailable in current metadata
Adoption
88
3.0K GitHub stars
Financial decision safety
58
Research-only use: do not treat output as financial advice or execute a position without human approval.
Warnings
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- Financial research output is not financial advice; require human review before any live investment decision
- The SKILL.md excerpt references a 'Parallelizing Code Style Reviews' section that is not visible in the provided excerpt; ensure it exists in the full file to avoid broken references.
- The skill relies on external skills (naming, lint, documentation) for related concerns; this is fine but may require the user to install the full skill set for complete coverage.
- Financial research output is not financial advice; require human review before any live investment decision.
- Quality score needs review
- Permission surface needs review: shell or command execution, filesystem or document access
- Dependency/runtime risk: command execution surface, network or browser surface
- Permission surface: shell or command execution, filesystem or document access
Method
This report combines public metadata, AI review output, repository freshness, install readiness, OpenAgentSkill events, quality scoring, trust checks, and the agent safety gate. It is not a full source-code security review.
Compare nearby options
Related skills to audit next
Code Review
Review a branch or diff against repository standards and the originating spec in two independent analysis passes.
169K Stars · Audit report
Grill With Docs
A relentless interview that pressure-tests a plan against the codebase, sharpens domain language, and updates CONTEXT.md and ADRs when decisions become durable.
165K Stars · Audit report
To Spec
Turn the current conversation and codebase context into a structured implementation spec, then publish it to the configured project issue tracker.
165K Stars · Audit report