Skip to content
TrustedSkillsbeta
Back to all skills

Go Performance

Checked
caarlos0·vlatest·testing·MIT

Helps with Go, performance optimization as part of agent workflows 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 caarlos0/dotfiles --skill go-performance -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

caarlos0

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 caarlos0/dotfiles at a3a8c16459.

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

Scanned
1 file, 146 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, caarlos0-go-performance, provides access to performance optimization techniques and tools specifically tailored for Go applications. It allows users to analyze, profile, and improve the speed and efficiency of their Go code. The skill leverages caarlos0's dotfiles configuration for a standardized approach to Go performance tuning.

When to use it

  • Debugging slow Go programs: Identify bottlenecks in your application’s execution.
  • Optimizing resource usage: Reduce memory consumption or CPU load during program operation.
  • Benchmarking code changes: Accurately measure the impact of optimizations on performance metrics.
  • Preparing for production deployment: Ensure your Go applications meet performance requirements before release.

Key capabilities

  • Go Performance Profiling
  • Code Optimization Techniques
  • Standardized Configuration (caarlos0's dotfiles)
  • Benchmarking Tools

Example prompts

  • "Analyze the performance of my main.go file and identify any bottlenecks."
  • "Can you suggest optimizations for this Go code snippet to reduce memory usage?"
  • "Benchmark this function against its previous version after I made these changes."

Tips & gotchas

This skill assumes a working Go development environment is already set up. The effectiveness of the optimization suggestions depends on the complexity and structure of your specific Go application.