Agent skill

Integration Tests

by genlayerlabs in genlayerlabs/genlayer-studio

Setup Python virtual environment and run integration tests with gltest

MITAuto-check passedTesting & QA

Install Integration Tests

skills CLI

$ npx skills add genlayerlabs/genlayer-studio --skill integration-tests -a claude-code

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

GitHub CLI

$ gh skill install genlayerlabs/genlayer-studio integration-tests --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/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/integration-tests .claude/skills/integration-tests && 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/

Paste into Claude Code

Install the "integration-tests" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/integration-tests into .claude/skills/integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-tests", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/integration-tests

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add genlayerlabs/genlayer-studio --skill integration-tests -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install genlayerlabs/genlayer-studio integration-tests --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/integration-tests .agents/skills/integration-tests && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "integration-tests" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/integration-tests into .agents/skills/integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-tests", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add genlayerlabs/genlayer-studio --skill integration-tests -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install genlayerlabs/genlayer-studio integration-tests --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/integration-tests .cursor/skills/integration-tests && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "integration-tests" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/integration-tests into .cursor/skills/integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-tests", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/genlayerlabs/genlayer-studio.git --path .claude/skills/integration-tests

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add genlayerlabs/genlayer-studio --skill integration-tests -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install genlayerlabs/genlayer-studio integration-tests --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/integration-tests .gemini/skills/integration-tests && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "integration-tests" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/integration-tests into .gemini/skills/integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-tests", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install genlayerlabs/genlayer-studio integration-tests

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add genlayerlabs/genlayer-studio --skill integration-tests -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/integration-tests .github/skills/integration-tests && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "integration-tests" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/integration-tests into .github/skills/integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-tests", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add genlayerlabs/genlayer-studio --skill integration-tests -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install genlayerlabs/genlayer-studio integration-tests --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/genlayerlabs/genlayer-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/integration-tests .opencode/skills/integration-tests && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "integration-tests" agent skill from https://github.com/genlayerlabs/genlayer-studio/tree/main/.claude/skills/integration-tests into .opencode/skills/integration-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integration-tests", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: integration-tests
GitHub stars: 180
Token cost: ~1.1k tokens
SKILL.md length: 181 words
Files: 1
Skills in repo: 10
Repo updated: Sep 30, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Setup Python virtual environment and run integration tests with gltest

Works in 3 steps: Start the Studio → Setup Virtual Environment (first time or… → Run Integration Tests
Tasks that involve Integration testing
SKILL.md covers Prerequisites, Step 1: Start the Studio, Step 2: Setup Virtual… and Step 3: Run Integration Tests, plus 2 more sections
Calls pip, docker-compose and curl

What it does

Integration Tests is an agent skill from genlayerlabs/genlayer-studio. Setup Python virtual environment and run integration tests with gltest

Its SKILL.md is about 1.1k 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 Integration testing. It works with Python. The repository describes itself as: An interactive sandbox to explore the GenLayer Protocol. The licence is MIT.

When your agent uses it

Tasks that involve Integration testing

Example prompts

“/integration-tests”

Requirements

Python 3
Docker

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Start the Studio
Setup Virtual Environment (first time or reset)
Run Integration Tests

What it can do on your machine

Read from SKILL.md and the folder at commit c940729. 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:
- pip
- docker-compose
- curl
- brew
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pip and curl, 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

Integration Tests loads about 1.1k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 181 words of instructions outside code blocks.

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

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

The full file from genlayerlabs/genlayer-studio at commit c940729, republished under its MIT licence (© genlayerlabs). 181 words, ~1,132 tokens.

Download SKILL.mdSave it as .claude/skills/integration-tests/SKILL.md (or your agent's skills folder).

name: integration-tests
description: Setup Python virtual environment and run integration tests with gltest

Run Integration Tests

Setup the Python environment, start the studio, and run integration tests for GenLayer Studio.

Prerequisites

Python 3.12 installed
virtualenv installed (pip install virtualenv)
Docker and Docker Compose installed

Step 1: Start the Studio

The studio must be running before executing integration tests.

bash

# Stop any existing containers and rebuild
docker-compose down && docker-compose up --build

Wait for all services to be healthy before proceeding.

Step 2: Setup Virtual Environment (first time or reset)

In a separate terminal:

bash

# Remove existing venv if present
rm -rf .venv

# Create new venv with Python 3.12
virtualenv -p python3.12 .venv

# Activate
source .venv/bin/activate

# Upgrade pip
pip install --upgrade pip

# Install all dependencies
pip install -r requirements.txt
pip install -r requirements.test.txt
pip install -r backend/requirements.txt

# Set Python path
export PYTHONPATH="$(pwd)"

Step 3: Run Integration Tests

bash

# Activate venv (if not already)
source .venv/bin/activate
export PYTHONPATH="$(pwd)"

# Run all integration tests (serial)
gltest --contracts-dir . tests/integration

# Run tests in parallel (4 workers) - excludes test_validators.py
gltest --contracts-dir . tests/integration -n 4 --ignore=tests/integration/test_validators.py

# Run validator CRUD tests separately (must run serially)
gltest --contracts-dir . tests/integration/test_validators.py

# Run faster with leader-only mode (skips validator consensus)
gltest --contracts-dir . tests/integration --leader-only

# Run specific test file
gltest --contracts-dir . tests/integration/test_specific.py

# Run with verbose output
gltest --contracts-dir . tests/integration -v

# Run specific test function
gltest --contracts-dir . tests/integration/test_file.py::test_function_name

Parallel Execution Notes

Use -n 4 to run tests in parallel with 4 workers (pytest-xdist)
test_validators.py must be excluded from parallel runs (--ignore) because it tests validator CRUD operations and needs exclusive access to the validator state
Run test_validators.py separately after parallel tests complete

Quick Commands

Full Setup (first time)

bash

# Terminal 1: Start studio
docker-compose down && docker-compose up --build

# Terminal 2: Setup and run tests
rm -rf .venv && \
virtualenv -p python3.12 .venv && \
source .venv/bin/activate && \
pip install --upgrade pip && \
pip install -r requirements.txt && \
pip install -r requirements.test.txt && \
pip install -r backend/requirements.txt && \
export PYTHONPATH="$(pwd)" && \
gltest --contracts-dir . tests/integration

Quick Run (after initial setup, studio already running)

bash

source .venv/bin/activate && export PYTHONPATH="$(pwd)" && gltest --contracts-dir . tests/integration

Parallel Run (4 workers)

bash

source .venv/bin/activate && export PYTHONPATH="$(pwd)" && \
gltest --contracts-dir . tests/integration -n 4 --ignore=tests/integration/test_validators.py && \
gltest --contracts-dir . tests/integration/test_validators.py

Fast Run (leader-only mode)

bash

source .venv/bin/activate && export PYTHONPATH="$(pwd)" && gltest --contracts-dir . tests/integration --leader-only

Troubleshooting

Studio Not Running

bash

# Check if containers are up
docker-compose ps

# Check container logs
docker-compose logs -f backend

Connection Refused Errors

The studio needs time to initialize. Wait for all services to be healthy:

bash

# Watch container status
docker-compose ps

# Check backend health
curl http://localhost:4000/health

Python 3.12 Not Found

bash

# Check available Python versions
which python3.12

# On macOS with Homebrew
brew install python@3.12

gltest Command Not Found

bash

# Make sure venv is activated
source .venv/bin/activate

# Reinstall test dependencies
pip install -r requirements.test.txt

Import Errors

bash

# Ensure PYTHONPATH is set
export PYTHONPATH="$(pwd)"

# Verify from project root
pwd  # Should be genlayer-studio

Test Timeouts

Integration tests may timeout if the studio is under load. Try:

bash

# Run with leader-only for faster execution
gltest --contracts-dir . tests/integration --leader-only

# Run a single test file to isolate issues
gltest --contracts-dir . tests/integration/test_specific.py -v

Files

Just SKILL.md in .claude/skills/integration-tests of genlayerlabs/genlayer-studio.

Open the folder on GitHubat commit c940729

Compare with similar skills

Integration Tests 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.

Integration Tests compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Integration Tests this skillgenlayerlabs/genlayer-studio	180	—	~1.1k	Automated safety check: Pass	MIT	7 days ago
OpenHarness End-to-End EvalsHKUDS/OpenHarness	16k	1 repos	~2.1k	Automated safety check: Notes	MIT	4 mo ago
Create Flet Control Integration Testsflet-dev/flet	17k	—	~1.4k	Automated safety check: Pass	Apache-2.0	today
Godot E2ERandallLiuXin/GodotMaker	549	1 repos	~3.9k	Automated safety check: Pass	Custom licence	20 days ago
JS-in-HTML Testingliaohch3/claude-tap	3.3k	—	~924	Automated safety check: Pass	MIT	15 days ago
Run Integration Testsvalkey-io/valkey-search	145	—	~511	Automated safety check: Pass	BSD-3-Clause	today

Similar skills

OpenHarness End-to-End Evals
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
16k GitHub starsUsed in 1 repo~2.1k tokens
Testing & QAAuto-check: notes
Create Flet Control Integration Tests
flet-dev/flet
A skill your agent uses when asked to create or update integration tests for any Flet control in sdk/python/packages/flet/integrationtests, including visual goldens and interactive behavior tests.
17k GitHub stars~1.4k tokensUpdated today
Testing & QAAuto-check passed
Godot E2E
RandallLiuXin/GodotMaker
Write and run E2E (end-to-end) game tests using the godot-e2e framework.
549 GitHub starsUsed in 1 repo~3.9k tokens
Testing & QAAuto-check passed
JS-in-HTML Testing
liaohch3/claude-tap
Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.
3.3k GitHub stars~924 tokensUpdated 15 days ago
Testing & QAAuto-check passed
Run Integration Tests
valkey-io/valkey-search
Run or troubleshoot Valkey Search C++ and Python integration tests, including focused development runs, full-suite verification, and packaging/build or runtime failure classification.
145 GitHub stars~511 tokensUpdated today
Testing & QAAuto-check passed
Temporal Python Testing
wshobson/agents
Test Temporal workflows with pytest, time-skipping, and mocking strategies.
40k GitHub starsUsed in 11 repos~1.2k tokens
Testing & QAAuto-check passed

Questions about Integration Tests

What does Integration Tests do?

Setup Python virtual environment and run integration tests with gltest. Integration Tests is an agent skill from genlayerlabs/genlayer-studio.

When should I use Integration Tests?

Integration Tests fits situations like: tasks that involve Integration testing.

How do I install Integration Tests in Claude Code?

Run `npx skills add genlayerlabs/genlayer-studio --skill integration-tests -a claude-code`. Or copy the skill folder (.claude/skills/integration-tests in genlayerlabs/genlayer-studio) into .claude/skills/integration-tests in your project. Claude Code loads it when a task matches its description.

How do I install Integration Tests in Codex?

Run `npx skills add genlayerlabs/genlayer-studio --skill integration-tests -a codex`. Or copy the skill folder (.claude/skills/integration-tests in genlayerlabs/genlayer-studio) into .agents/skills/integration-tests in your project. Codex loads it when a task matches its description.

Can I use Integration Tests 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 genlayerlabs/genlayer-studio --skill integration-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/integration-tests, .gemini/skills/integration-tests, .github/skills/integration-tests and .opencode/skills/integration-tests in your project.

What does Integration Tests need to run?

Going by SKILL.md and its folder, Integration Tests needs the command-line tools its instructions call (pip, docker-compose, curl and brew). Our summary lists: Python 3; Docker.

Does Integration Tests access the network?

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

Is Integration Tests 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 Integration Tests use?

Integration Tests is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Integration Tests use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Integration Tests?

Skills that share tags, products or a category with Integration Tests: OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), Create Flet Control Integration Tests (flet-dev/flet, 17k stars), Godot E2E (RandallLiuXin/GodotMaker, 549 stars) and JS-in-HTML Testing (liaohch3/claude-tap, 3.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Integration Tests?

genlayerlabs (a GitHub organization) maintains it in genlayerlabs/genlayer-studio, which has 180 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 30, 2026.

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

Install Integration Tests

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Run Integration Tests

Prerequisites

Step 1: Start the Studio

Step 2: Setup Virtual Environment (first time or reset)

Step 3: Run Integration Tests

Parallel Execution Notes

Quick Commands

Full Setup (first time)

Quick Run (after initial setup, studio already running)

Parallel Run (4 workers)

Fast Run (leader-only mode)

Troubleshooting

Studio Not Running

Connection Refused Errors

Python 3.12 Not Found

gltest Command Not Found

Import Errors

Test Timeouts

Files

Compare with similar skills

Similar skills

More from genlayerlabs/genlayer-studio

Related

Questions about Integration Tests