Skip to content
TrustedSkillsbeta
Back to all skills

Golang Testing

Checked
peopleforrester·vlatest·backend·MIT

Helps with Go, testing as part of developing backend services and APIs workflows.

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 peopleforrester/claude-dotfiles --skill golang-testing -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

peopleforrester

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 peopleforrester/claude-dotfiles at db7caa0374.

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

Scanned
1 file, 161 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 allows AI agents to execute Go testing commands. It can run tests, benchmarks, and code coverage analysis for Go projects. The agent can then report on test results or integrate them into CI/CD pipelines.

When to use it

  • Automated Testing: Run unit tests automatically as part of a development workflow.
  • Benchmark Performance: Execute benchmark tests to identify performance bottlenecks in Go code.
  • Code Coverage Analysis: Generate reports showing the percentage of code covered by existing tests.
  • CI/CD Integration: Integrate testing into continuous integration and deployment pipelines for automated quality checks.

Key capabilities

  • Executes go test commands
  • Runs benchmark tests using go test -bench=.
  • Generates code coverage reports with go test -coverprofile=coverage.out

Example prompts

  • "Run all Go tests in the current directory."
  • "Execute benchmarks for package 'my_package'."
  • "Generate a code coverage report named 'coverage.txt'."

Tips & gotchas

  • Requires a Go environment to be set up and accessible within the agent's execution context.
  • The skill assumes familiarity with standard Go testing practices and command-line arguments.