pkg-go-dev

Queries the pkg.go.dev v1beta REST API for Go module metadata, docs, and vulnerabilities.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/missdeer/skills --skill pkg-go-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pkg-go-dev
Source: https://github.com/missdeer/skills/tree/main/pkg-go-dev
Command: npx skills add https://github.com/missdeer/skills --skill pkg-go-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) components.

What problem does it solve?

This skill eliminates the need for manual web browsing or unreliable scraping when researching Go packages, providing direct access to official module metadata, documentation, and security data.

Core Features & Use Cases

  • Comprehensive Metadata: Retrieve authoritative details on Go modules, including versions, exported symbols, and import graphs.
  • Security & Search: Instantly query the Go vulnerability database for CVEs affecting specific modules or perform full-text searches across the Go ecosystem.
  • Use Case: When evaluating a new dependency, use this skill to verify its latest version, check for known vulnerabilities, and inspect its exported symbols without leaving your development environment.

Quick Start

Use the pkg-go-dev skill to fetch the latest documentation and exported symbols for the github.com/google/go-cmp/cmp package.

Frequently Asked Questions about pkg-go-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check a Go package for known vulnerabilities before adding it as a dependency?

To check Go package vulnerabilities, you can query the Go vulnerability database via the pkg.go.dev v1beta REST API to retrieve specific CVEs affecting a module. This provides direct access to security data without manual web browsing.

What's the best way to retrieve exported symbols and version history for a Golang module?

Retrieving exported symbols and version history for a Golang module is done by querying the pkg.go.dev REST API for authoritative metadata. This approach facilitates deep inspection of package symbols and version data programmatically.

Can I perform full-text search across the Go ecosystem from my development environment?

Yes, you can perform full-text search across the Go ecosystem from your development environment. This skill queries the official pkg.go.dev API, enabling ecosystem-wide search for modules and documentation without leaving your terminal.

Do I need curl and jq installed to query Go module documentation programmatically?

Yes, you need curl and jq installed to query Go module documentation programmatically. These dependencies handle executing the API requests to pkg.go.dev and parsing the returned JSON metadata respectively.

How does pkg-go-dev compare to web scraping for analyzing Go import dependencies?

Querying the pkg.go.dev API eliminates unreliable web scraping for analyzing Go import dependencies. It provides direct, authoritative access to module metadata and import graphs, ensuring accurate dependency analysis and security auditing.

What limitations exist when using the pkg.go.dev API for package metadata retrieval?

Limitations when using the pkg.go.dev API for package metadata retrieval include reliance on the v1beta REST API endpoint stability and the availability of the external pkg.go.dev service for fetching documentation and vulnerability information.