golang-documentationComprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and...
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 Jun 29, 2026
YouTube Data API integration with managed OAuth. Search videos, manage playlists, access channel data, and interact with comments. Use this skill when users want to interact with YouTube. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
Trello API integration with managed OAuth. Manage boards, lists, cards, members, and labels. Use this skill when users want to interact with Trello for project management. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
Fetch up-to-date library documentation via Context7 API. Use PROACTIVELY when: (1) Working with ANY external library (React, Next.js, Supabase, etc.) (2) User asks about library APIs, patterns, or best practices (3) Implementing features that rely on third-party packages (4) Debugging library-specific issues (5) Need current documentation beyond training data cutoff Always prefer this over guessing library APIs or using outdated knowledge.
API reference for CoinMarketCap DEX endpoints including token lookup, pools, transactions, trending, and security analysis. Use this skill whenever the user...
Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.
Lightweight API mock server for prototyping and testing, supporting JSON/JSON Schema responses, dynamic data, validation, latency, and webhook simulation.