Loading...
Loading...
Found 123 Skills
Idiomatic Go patterns for errors, interfaces, concurrency, and packages. Use when: - Writing or reviewing Go code - Designing interfaces or package structure - Implementing concurrency patterns - Handling errors and context propagation - Structuring Go projects Keywords: Go, golang, error wrapping, interface design, goroutine, channel, context, package design, dependency injection, race condition
Use this skill to build, run, deploy, evaluate, and troubleshoot Go agents with Google's Agent Development Kit (`google.golang.org/adk`), including llmagent config, tools/integrations, callbacks/plugins, sessions/state/memory, workflows, streaming, MCP/A2A, and runtime/deployment patterns.
Enable developers to learn and use Chainlink Runtime Environment (CRE) quickly by referencing filtered CRE docs. Trigger when user wants onboarding, CRE workflow generation (in TypeScript or Golang or other supported languages), workflow guidance, CRE CLI and/or SDK help, runtime operations advice, or capability selection
Expert Guide to Indie Game Development with Go (Golang) and its game engines (such as Ebitengine or Raylib-go). Covers core areas including memory management, concurrency-safe game loops, asset embedding (go:embed), and cross-platform cross-compilation. Suitable for scenarios where high-performance 2D/3D games are built using the Go ecosystem.
Go programming language. Covers goroutines, channels, interfaces, error handling, and modules. Use for building concurrent, high-performance backend services. USE WHEN: user mentions "go", "golang", "goroutines", "channels", asks about "concurrency", "select statement", "interfaces", "error handling", "go modules" DO NOT USE FOR: Gin/Fiber/Echo frameworks - use framework-specific skills DO NOT USE FOR: GORM - use ORM-specific skill DO NOT USE FOR: gRPC - use API design skills
Go-specific code review with 6-phase methodology: Context, Automated Checks, Quality Analysis, Specific Analysis, Line-by-Line, Documentation. Use when reviewing Go code, PRs, or auditing Go codebases for quality and best practices. Use for "review Go", "Go PR", "check Go code", "Go quality", "review .go". Do NOT use for writing new Go code, debugging Go bugs, or refactoring -- use golang-general-engineer, systematic-debugging, or systematic-refactoring for those tasks.
Go testing patterns and methodology: table-driven tests, t.Run subtests, t.Helper helpers, mocking interfaces, benchmarks, race detection, and synctest. Use when writing new Go tests, modifying existing tests, adding coverage, fixing failing tests, writing benchmarks, or creating mocks. Triggered by "go test", "_test.go", "table-driven", "t.Run", "benchmark", "mock", "race detection", "test coverage". Do NOT use for non-Go testing (use test-driven-development instead), debugging test failures (use systematic-debugging), or general Go development without test focus (use golang-general-engineer directly).
Go/Golang backend expert. PROACTIVELY use when working with Go, Gin, Echo, Fiber frameworks. Triggers: golang, go, gin, echo, fiber
Maintain Go repositories with high-quality standards, adhering to CI/CD, linting, and agent-friendly best practices.
Eino orchestration with Graph, Chain, and Workflow. Use when a user needs to build multi-step pipelines, compose components into executable graphs, handle streaming between nodes, use branching or parallel execution, manage state with checkpoints, or understand the Runnable abstraction. Covers Graph (directed graph with cycles), Chain (linear sequential), and Workflow (DAG with field mapping).
Review Go code for language and runtime conventions: concurrency, context usage, error handling, resource management, API stability, type semantics, and testability. Language-only atomic skill; output is a findings list.
Build voice applications using TeXML markup language (TwiML-compatible). Manage applications, calls, conferences, recordings, queues, and streams. This skill provides Go SDK examples.