Agent skill

Backend Testing

by rhesis-ai in rhesis-ai/rhesis

Run the backend test suite correctly — working directory, Docker requirement, single-test vs full-suite commands.

Custom licenceAuto-check passedTesting & QA

Install Backend Testing

skills CLI
$ npx skills add rhesis-ai/rhesis --skill backend-testing -a claude-code

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

GitHub CLI
$ gh skill install rhesis-ai/rhesis backend-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/rhesis-ai/rhesis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/backend-testing .claude/skills/backend-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
backend-testing
GitHub stars
397
Token cost
~400 tokens
SKILL.md length
163 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
Custom licence

At a glance

Run the backend test suite correctly — working directory, Docker requirement, single-test vs full-suite commands.

  • Writing backend tests in apps/backend
  • Calls uv
  • Tasks that involve Test generation
  • Tasks that involve Containers

What it does

Backend Testing is an agent skill from rhesis-ai/rhesis. Run the backend test suite correctly — working directory, Docker requirement, single-test vs full-suite commands. Use when running or writing backend tests in apps/backend.

Its SKILL.md is about 400 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 Test generation and Containers. It works with Docker. The repository describes itself as: The collaboration layer for AI teams: domain experts annotate and review agent behavior, engineers improve the agent from what they find.

When your agent uses it

  • Writing backend tests in apps/backend
  • Tasks that involve Test generation
  • Tasks that involve Containers

Example prompts

  • “/backend-testing”

Requirements

  • Docker

What it can do on your machine

Read from SKILL.md and the folder at commit 1a2c578. 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:

    • uv

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

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    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

Backend Testing loads about 400 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 163 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
~400

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 163 words (~400 tokens).

“Ask the user before running the whole backend suite. It takes a very long time. Default to the narrowest selection that covers the change (single test, class, or file); only run ../../tests/backend/ in full once the user says to.”

— opening of SKILL.md by rhesis-ai, Custom licence
name
backend-testing

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/backend-testing of rhesis-ai/rhesis.

Open the folder on GitHubat commit 1a2c578

Compare with similar skills

Backend 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.

Backend Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Backend Testing this skillrhesis-ai/rhesis397—~400Automated safety check: PassCustom licence
Suite ConverterMargin-Lab/evals161—~3.7kAutomated safety check: PassAGPL-3.0
Run SDK Testsrestatedev/sdk-typescript125—~745Automated safety check: PassMIT
Corvus Bowtie Testingcorvus-dotnet/Corvus.JsonSchema199—~1.4kAutomated safety check: PassApache-2.0
PR TestElite588/AUTOGPT103—~9.4kAutomated safety check: NotesCustom licence
Dokan Automationgetdokan/dokan288—~6.1kAutomated safety check: NotesNone

Similar skills

  • Suite Converter

    Margin-Lab/evals

    Converts test suites from external eval frameworks into the Margin Eval suite format.

    161 GitHub stars~3.7k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Run SDK Tests

    restatedev/sdk-typescript

    Run the Restate SDK conformance test suite locally against this SDK's Docker image.

    125 GitHub stars~745 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Corvus Bowtie Testing

    corvus-dotnet/Corvus.JsonSchema

    Test Corvus.JsonSchema against the JSON Schema Test Suite using Bowtie, the cross-implementation meta-validator.

    199 GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed
  • PR Test

    Elite588/AUTOGPT

    E2E manual testing of PRs/branches using docker compose, agent-browser, and API calls.

    103 GitHub stars~9.4k tokensUpdated 5 mo ago
    Testing & QAAuto-check: notes
  • Dokan Automation

    getdokan/dokan

    Build, scaffold, and run the Dokan Lite/Pro Playwright suite.

    288 GitHub stars~6.1k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Model Download Dev

    open-edge-platform/edge-ai-libraries

    Extend, test, debug, or integrate the Model Download microservice codebase.

    169 GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed

More from rhesis-ai/rhesis

All 12 skills in this repo
  • Rhesis

    rhesis-ai/rhesis

    Design, run, and analyze AI test suites on Rhesis — explore endpoints, build test foundations from a spec, create requirements and metrics, execute tests, and analyze results.

    397 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Worktree

    rhesis-ai/rhesis

    Manage git worktrees with their own dev ports, symlinked .env files, playground, and simulations.

    397 GitHub stars~627 tokensUpdated today
    Auto-check: notes
  • Update Branch

    rhesis-ai/rhesis

    Rebase a feature branch onto main and force-push it safely. An agent skill from rhesis-ai/rhesis.

    397 GitHub stars~269 tokensUpdated today
    Auto-check passed
  • Docs Design Tokens

    rhesis-ai/rhesis

    Colour, font and design-token rules for the docs site — when hex is banned, when it is correct, and which surfaces ignore the theme.

    397 GitHub stars~658 tokensUpdated today
    Auto-check passed
  • Pull Request

    rhesis-ai/rhesis

    Open a pull request in this repo — branch naming, title format, and the required description sections.

    397 GitHub stars~371 tokensUpdated today
    Auto-check passed
  • Docs Social Images

    rhesis-ai/rhesis

    How the docs site generates per-page og:image cards, and the cache and font traps when changing them.

    397 GitHub stars~377 tokensUpdated today
    Auto-check passed

Works with

Questions about Backend Testing

What does Backend Testing do?

Run the backend test suite correctly — working directory, Docker requirement, single-test vs full-suite commands. Backend Testing is an agent skill from rhesis-ai/rhesis. Run the backend test suite correctly — working directory, Docker requirement, single-test vs full-suite commands.

When should I use Backend Testing?

Backend Testing fits situations like: writing backend tests in apps/backend; tasks that involve Test generation; tasks that involve Containers.

How do I install Backend Testing in Claude Code?

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

How do I install Backend Testing in Codex?

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

Can I use Backend 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 rhesis-ai/rhesis --skill backend-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/backend-testing, .gemini/skills/backend-testing, .github/skills/backend-testing and .opencode/skills/backend-testing in your project.

What does Backend Testing need to run?

Going by SKILL.md and its folder, Backend Testing needs the command-line tools its instructions call (uv). Our summary lists: Docker.

Does Backend Testing access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Backend 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 Backend Testing use?

Backend 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 Backend Testing use?

About 400 tokens (SKILL.md is roughly 1.6k 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 Backend Testing?

Skills that share tags, products or a category with Backend Testing: Suite Converter (Margin-Lab/evals, 161 stars), Run SDK Tests (restatedev/sdk-typescript, 125 stars), Corvus Bowtie Testing (corvus-dotnet/Corvus.JsonSchema, 199 stars) and PR Test (Elite588/AUTOGPT, 103 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Backend Testing?

rhesis-ai (a GitHub organization) maintains it in rhesis-ai/rhesis, which has 397 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

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