dependency-selecting

Select direct Go dependencies using a formal decision table.

23|2|Updated Jun 9, 2025
One-click install
npx skills add https://github.com/kaptinlin/gozod --skill dependency-selecting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-selecting
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/dependency-selecting
Command: npx skills add https://github.com/kaptinlin/gozod --skill dependency-selecting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamlines selecting direct Go dependencies for projects by prioritizing kaptinlin/agentable libraries and vetted external options, reducing decision fatigue and risk.

Core Features & Use Cases

  • Direct-dependency guidance: Focuses on go.mod require entries, avoiding transitive-only recommendations.
  • Ecosystem-wide coverage: Applies to JSON, config, caching, messaging, resilience, i18n, docs, HTTP, query parsing, workflows, AI, health checks, testing, UUID, currency, and authorization.
  • Structured guidance: Includes a master decision table and references to established best practices for rapid, consistent choices.

Quick Start

Provide your project goals and I will propose a direct dependency list with rationale.

Frequently Asked Questions about dependency-selecting

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

FAQPage Schema
How do I choose the right Go dependencies for my project's JSON, caching, and messaging needs?

To choose Go dependencies, use a formal decision table that evaluates direct go.mod require entries for JSON, caching, and messaging. This approach prioritizes vetted libraries and standardized best practices to reduce decision fatigue and selection risk.

What is the best way to select direct Go modules without pulling in unnecessary transitive dependencies?

The best way to select direct Go modules is to enforce a direct-dependency scope that focuses strictly on go.mod require entries. This prevents transitive-only recommendations and standardizes choices using a master decision table for ecosystem-wide coverage.

Can I use this Go library selection process for both infrastructure and application level concerns?

Yes, you can use this Go library selection process for infrastructure and application concerns. It provides vetted direct-dependency choices across HTTP, resilience, health checks, workflows, AI, i18n, testing, UUID, currency, and authorization.

How do I standardize Go dependency choices across different categories like config, i18n, and query parsing?

You standardize Go dependency choices by applying a formal decision table that covers config, i18n, and query parsing. This structured guidance references established best practices and prioritizes dependable libraries for rapid, consistent project setup.

Does this dependency selection method apply to AI and workflow libraries in Go?

Yes, this dependency selection method applies to AI and workflow libraries in Go. It identifies and selects direct dependencies for projects needing dependable library choices across these specific domains using a structured decision table.

When should I not use automated Go dependency recommendations for my project?

You should not use automated Go dependency recommendations if your project requires transitive-only library inclusion or if you need to bypass the prioritization of specific vetted libraries and formal decision tables for custom architectural constraints.