Skip to content
TrustedSkillsbeta
Back to all skills

Go Interfaces

Checked
cxuu·vlatest·backend·Apache-2.0

Automates Go interface implementation generation based on specified methods, reducing boilerplate code and ensuring consistency.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add cxuu/golang-skills --skill go-interfaces -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

cxuu

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned cxuu/golang-skills at 91f0c2eef5.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
91f0c2eef5
Manifest
skills/go-interfaces/SKILL.md
Scanned
5 files, 923 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps Go developers automate and improve their use of interfaces. It provides scripts to ensure compliance with interface contracts, promotes best practices for defining interfaces in consuming packages rather than implementing ones, and encourages returning concrete types from constructors. The goal is to reduce boilerplate code, maintain consistency, and enhance the flexibility of Go projects by hiding implementation details.

When to use it

  • When you need to verify that your Go code correctly implements exported interfaces.
  • To enforce a design pattern where consuming packages define interfaces rather than implementing ones.
  • When refactoring existing Go code to improve modularity and reduce dependencies.
  • To ensure safe type assertions using the comma-ok idiom, preventing runtime panics.

Key capabilities

  • Interface Compliance Checking: The check-interface-compliance.sh script identifies exported interfaces that lack compile-time compliance checks (using var _ I = (*T)(nil)).
  • Interface Placement Guidance: Provides recommendations on defining interfaces in consuming packages, not implementing ones.
  • Concrete Type Return Encouragement: Promotes returning concrete types (structs or pointers) from constructors to allow for future method additions without refactoring.
  • Implementation Hiding: Suggests returning interfaces from constructors to hide implementation details and enable algorithm substitution.
  • Safe Type Assertions: Emphasizes the use of the comma-ok idiom (value.(string), ok) to safely check type assertions and avoid runtime panics.

Example prompts

Since this is a code generation/analysis skill, there are no direct user prompts. However, you would invoke it via command line:

  • bash scripts/check-interface-compliance.sh --help (to see options for the compliance check script)
  • (During development) Reviewing the recommendations on interface placement and concrete type return when designing Go packages.

Tips & gotchas

  • This skill focuses on code analysis and guidance, not automatic generation of interfaces or implementations.
  • The check-interface-compliance.sh script requires a working Bash environment.
  • Follow the provided guidelines regarding interface placement to avoid unnecessary complexity and improve maintainability.