yokai
Reduces time-to-market for Go services by providing production-ready patterns for logging, metrics, and configuration.
A simple, modular, and observable Go framework for backend applications. Core modules preload logging, tracing, metrics, and health-check instrumentation; extension modules add public HTTP (Echo) and gRPC servers, workers, and ORM, wired through an Fx-based dependency injection system. Ready-to-use application templates cover HTTP, gRPC, MCP-server, and worker applications. This is a Go framework, not a Claude skill.
- Generate a new Go microservice with built-in logging and metrics observability
- Build modular backend services using pre-configured dependency injection patterns
- Add distributed tracing and monitoring to existing Go application code
Reduces time-to-market for Go services by providing production-ready patterns for logging, metrics, and configuration. Eliminates repeated infrastructure boilerplate across backend teams.
Go backend teams building microservices with observability and maintainability requirements.
https://github.com/ankorstore/yokai
By ankorstore
How to Get It
Start from a Yokai application template (HTTP, gRPC, MCP, or worker) — see the documentation at ankorstore.github.io/yokai
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
After installing, paste this into Claude:
Help me generate a new Go microservice with built-in logging and metrics observability
Trust Signals Auto-scanned
Community Pulse Quiet
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 834 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 834 GitHub stars; contributors unknown; last commit 0d ago; license MIT.