Bootstrap Go services with trypanic/go-sdk wiring conventions.
npx skills add https://github.com/trypanic/skills --skill go-sdk-bootstrap
Please help me install this Agent Skill. Skill: go-sdk-bootstrap Source: https://github.com/trypanic/skills/tree/main/go-sdk-bootstrap Command: npx skills add https://github.com/trypanic/skills --skill go-sdk-bootstrap
Manually wiring a Go service with github.com/trypanic/go-sdk is error-prone due to non-obvious conventions like package identifier divergences (e.g. the postgres directory uses the database package name), strict constructor triplet rules, and required initialization order that cannot be inferred from standard Go documentation alone. This Skill eliminates that guesswork to ensure correct, production-ready setup.
Use the go-sdk-bootstrap skill to scaffold a new Go service with logger, telemetry, postgres, and messaging wired correctly according to trypanic/go-sdk conventions.
High-intent search queries and answers about installing and using this skill.
To correctly initialize telemetry and logging in a Go service, you must follow a strict initialization order, setting up OTLP before the logger and deferring shutdown in reverse construction order to ensure proper tracing behavior.
Your Go service fails to compile because the go-sdk postgres directory uses the database package name, creating a package identifier divergence that requires specific constructor triplet rules to resolve correctly.
The correct way to wrap errors using errorkit is to apply strict error wrapping rules that avoid prohibited anti-patterns, ensuring maintainable and production-ready service setup without broken tracing behavior.
You can add go-sdk components to an existing Go service without breaking tracing behavior by following verified constructor triplet rules, including New, NewWithoutTracing, and NewWithInstrumenter, to ensure proper wiring.
Manually wiring trypanic go-sdk components introduces limitations such as non-obvious conventions and strict initialization sequences that cannot be inferred from standard Go documentation, leading to misconfigured tracing and logging.
The best way to scaffold a new Go service with postgres and messaging wired correctly is to use a verified main.go template that encodes canonical wiring rules and shared resource pools for reliable service startup.
hashicorpScaffold a Terraform provider workspace with the Plugin Framework.
mizchiWrap Cloudflare Workers fetch handlers to emit OTLP traces, metrics, and logs.
githubRender Go structs into aligned console tables using struct tags.
trypanicReview Go code for SOLID principle and idiomatic design violations.
