Agent skill

Testing

by golemcloud in golemcloud/golem

Running and debugging tests in the Golem workspace. An agent skill from golemcloud/golem.

Custom licenceAuto-check passedTesting & QA

Install Testing

skills CLI
$ npx skills add golemcloud/golem --skill testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install golemcloud/golem testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/testing .claude/skills/testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
testing
GitHub stars
1.5k
Token cost
~1.8k tokens
SKILL.md length
634 words
Files
1
Skills in repo
289
Repo updated
First seen
Licence
Custom licence

At a glance

Running and debugging tests in the Golem workspace. An agent skill from golemcloud/golem.

  • Works in 3 steps: Identify which tagged… → Build those components first by… → Only then run the Rust test command.
  • Running specific tests
  • SKILL.md covers Choosing the Right Test Command, External Process Ownership, Test Filtering Rules (test-r) and Debugging Test Failures, plus 2 more sections
  • Calls cargo and rg

What it does

Testing is an agent skill from golemcloud/golem. Running and debugging tests in the Golem workspace. Use when writing tests, running specific tests, filtering tests, debugging test failures, or understanding test infrastructure.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Failing and flaky tests and Debugging. The repository describes itself as: Golem Cloud is the agent-native platform for building AI agents and distributed applications that never lose state, never duplicate work, and never require you to build…

When your agent uses it

  • Running specific tests
  • Filtering tests
  • Debugging test failures
  • Understanding test infrastructure

Example prompts

  • “/testing”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Identify which tagged PrecompiledComponent or test component files the selected tests require.
  2. Build those components first by following their AGENTS.md, or run cargo make build-test-components if a broad rebuild is simpler.
  3. Only then run the Rust test command.

What it can do on your machine

Read from SKILL.md and the folder at commit 2dea6b9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo
    • rg

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • test-r.vigoo.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Testing loads about 1.8k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 634 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 634 words (~1,794 tokens).

“Root-workspace Rust tests use test-r. Each test crate or integration-test entry point using test-r must call test_r::enable!(), and test_r::test must be in lexical scope wherever #[test] is used. Separate workspaces may have their own harness setup.”

— opening of SKILL.md by golemcloud, Custom licence
name
testing

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/testing of golemcloud/golem.

Open the folder on GitHubat commit 2dea6b9

Compare with similar skills

Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing this skillgolemcloud/golem1.5k—~1.8kAutomated safety check: PassCustom licence
Pester Failure AnalysisPowerShell/PowerShell56k—~5.1kAutomated safety check: PassMIT
Testingkortix-ai/suna20k—~3.6kAutomated safety check: NotesCustom licence
OpenLogi Change VerificationAprilNEA/OpenLogi23k—~1.4kAutomated safety check: PassApache-2.0
RustPython Test Failure InvestigationRustPython/RustPython22k—~467Automated safety check: PassMIT
Issue To Regression Testbrunosabot/streamline-card269—~529Automated safety check: PassMIT

Similar skills

  • Pester Failure Analysis

    PowerShell/PowerShell

    Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.

    56k GitHub stars~5.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Testing

    kortix-ai/suna

    A skill your agent uses for every Kortix test task, behavior change, bug fix, refactor, API route change, CLI change, SDK change, browser journey, test failure, coverage question, local benchmark…

    20k GitHub stars~3.6k tokensUpdated today
    Testing & QAAuto-check: notes
  • Plans the smallest check that could disprove a code change in the OpenLogi project, then escalates through reproduction, focused tests and a final gate before a push.

    23k GitHub stars~1.4k tokensUpdated 4 days ago
    Testing & QAAuto-check passed
  • Investigates a failing RustPython test by comparing it with CPython, then either fixes it or gathers the details for an incompatibility report.

    22k GitHub stars~467 tokensUpdated today
    Testing & QAAuto-check passed
  • Issue To Regression Test

    brunosabot/streamline-card

    A skill your agent uses when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix.

    269 GitHub stars~529 tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Ue Test Authoring

    JasonMa0012/MooaToon

    A skill your agent uses when writing or modifying UE automated tests (Automation, CQTest, Functional, Gauntlet, LowLevel) with Rider MCP available.

    749 GitHub stars~2.1k tokensUpdated 19 days ago
    Testing & QAAuto-check: notes

More from golemcloud/golem

All 289 skills in this repo
  • Moonbit C Binding

    golemcloud/golem

    Guide for writing MoonBit bindings to C libraries using native FFI.

    1.5k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Adding Dependencies

    golemcloud/golem

    Adding or updating crate dependencies in the Golem workspace.

    1.5k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Analysing CI Failures

    golemcloud/golem

    Analysing GitHub Actions CI failures from a run URL. An agent skill from golemcloud/golem.

    1.5k GitHub stars~862 tokensUpdated today
    Auto-check passed
  • Adds a built-in WASM plugin that is externally released and provisioned by the registry service.

    1.5k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • DB Migration Scripts

    golemcloud/golem

    Writing database migration SQL scripts. An agent skill from golemcloud/golem.

    1.5k GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Debugging Hanging Tests

    golemcloud/golem

    Diagnosing and fixing hanging worker executor or integration tests.

    1.5k GitHub stars~879 tokensUpdated today
    Auto-check passed

Questions about Testing

What does Testing do?

Running and debugging tests in the Golem workspace. An agent skill from golemcloud/golem. Testing is an agent skill from golemcloud/golem. Running and debugging tests in the Golem workspace.

When should I use Testing?

Testing fits situations like: running specific tests; filtering tests; debugging test failures; understanding test infrastructure.

How do I install Testing in Claude Code?

Run `npx skills add golemcloud/golem --skill testing -a claude-code`. Or copy the skill folder (.agents/skills/testing in golemcloud/golem) into .claude/skills/testing in your project. Claude Code loads it when a task matches its description.

How do I install Testing in Codex?

Run `npx skills add golemcloud/golem --skill testing -a codex`. Or copy the skill folder (.agents/skills/testing in golemcloud/golem) into .agents/skills/testing in your project. Codex loads it when a task matches its description.

Can I use Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add golemcloud/golem --skill testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing, .gemini/skills/testing, .github/skills/testing and .opencode/skills/testing in your project.

What does Testing need to run?

Going by SKILL.md and its folder, Testing needs the command-line tools its instructions call (cargo and rg).

Does Testing access the network?

SKILL.md names 1 domain. As links in the text: test-r.vigoo.dev. This is read from the text; nothing was executed.

Is Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Testing use?

Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Testing use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Testing?

Skills that share tags, products or a category with Testing: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Testing (kortix-ai/suna, 20k stars), OpenLogi Change Verification (AprilNEA/OpenLogi, 23k stars) and RustPython Test Failure Investigation (RustPython/RustPython, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing?

golemcloud (a GitHub organization) maintains it in golemcloud/golem, which has 1,506 GitHub stars. The repository holds 289 skills in this directory. The repository was last updated on October 7, 2026.

Source: golemcloud/golem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.