golang-documentationComprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.
Install via ClawdBot CLI:
clawdbot install samber/golang-documentationGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
Report → https://goreportcard.com/badge/github.com/{owner}/{repo}Calls external URL not in known-safe list
https://github.com/samber/cc-skills-golangAI Analysis
The skill's external calls (GoReportCard badge, GitHub repo) are consistent with its documentation purpose for generating project badges and referencing source material. No evidence of data exfiltration, credential harvesting, or hidden malicious instructions exists in the provided definition.
Audited Apr 18, 2026 · audit v1.0
Generated May 6, 2026
A developer maintains a Go library and needs to improve its documentation for better adoption. The skill guides them to add package comments, doc comments on exported functions, Example test functions, and a README with getting-started instructions. This ensures the library is discoverable on pkg.go.dev and users can immediately understand how to use it.
A team builds a new Go microservice and must produce documentation for internal developers. Using the skill, they create a CONTRIBUTING.md, CHANGELOG.md, and detailed doc comments for all exported APIs. This reduces onboarding time and helps team members understand the service's purpose, endpoints, and error cases without reading the entire codebase.
A developer creates a Go-based CLI tool and uses the skill to write a comprehensive README with installation steps, usage examples, and configuration docs. They also ensure the main package has clear doc comments. This improves user satisfaction and reduces support requests by making the tool self-documenting.
A company offers a Go-based API service and needs documentation for external developers. The skill helps them produce an API documentation site (using godoc or OpenAPI), add example test functions, and include a Playground link for key endpoints. This increases API adoption and reduces integration issues.
An engineering team inherits a large Go codebase with sparse documentation. They use the skill's review mode to audit doc comments, README, CONTRIBUTING, and CHANGELOG across multiple packages. Parallel sub-agents fix missing package comments and add examples, making the codebase maintainable and compliant with Go documentation standards.
By maintaining excellent documentation, open-source Go projects attract more contributors and users. Good docs reduce issues and increase stars, which leads to higher visibility and potential sponsorship or consulting revenue.
A CLI or API tool with polished documentation can be offered as a premium product or SaaS. Clear getting-started guides and examples lower the barrier to purchase, while comprehensive API docs reduce support costs.
Development teams that specialize in Go can use the skill to produce documentation for clients, charging for quality documentation as a service. This is particularly valuable for projects requiring high code quality and maintainability.
💬 Integration Tip
Combine this skill with a Go linter that enforces doc comments on exported symbols (e.g., golangci-lint with 'godot' and 'goerr113') to automate quality checks before review.
Scored Sep 28, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.