Managing Test Environments

What it does

When your agent uses it

• Performing specialized testing
• With phrases like manage test environment
• Provision test env
• Setup test infrastructure

Example prompts

• “manage test environment”
• “provision test env”
• “setup test infrastructure”
• “/managing-test-environments”

Requirements

• Python 3
• Docker
• Compatibility (from SKILL.md): Designed for Claude Code
• Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(test:env-*)

Workflow steps

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

1. 1Read the project's existing configuration files (docker-compose.yml, .env.test, jest.config.*, pytest.ini) to understand current…
2. 2Inventory all external dependencies the test suite requires (databases, message queues, cache servers, third-party API stubs).
3. 3Create or update a docker-compose.test.yml defining isolated service containers
4. 4Write seed data scripts that populate databases with baseline test data
5. 5Generate environment configuration files (.env.test) with connection strings, API keys, and feature flags appropriate for testing.
6. 6Create a startup script that orchestrates the full environment lifecycle
7. 7Validate the environment by running a small smoke test suite against the provisioned services.

What it can do on your machine

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

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Edit
  • Grep
  • Glob
  • Bash(test:env-*)

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 3 files in scripts/ (Python), which the agent can run.

  Shell commands in SKILL.md call:

  • docker-compose

  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):

  • docs.docker.com
  • testcontainers.com
  • github.com
  • 12factor.net

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

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • POSTGRES_PASSWORD

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

• Compatibility

  Designed for Claude Code

  From compatibility in the SKILL.md frontmatter.

Context cost

Managing Test Environments loads about 1.3k tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 435 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~64

When it runs · the whole SKILL.md, loaded when a task matches

~1.3k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~1.3k

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

• NoteMentions a .env fileSKILL.md:32

  - Environment variable management via `.env` files or secrets manager

• NoteMentions a .env fileSKILL.md:37

  figuration files (`docker-compose.yml`, `.env.test`, `jest.config.*`, `pytest.ini`) to understand current environment se

• NoteMentions a .env fileSKILL.md:47

  nerate environment configuration files (`.env.test`) with connection strings, API keys, and feature flags appropriate fo

• NoteMentions a .env fileSKILL.md:59

  - `.env.test` with test-specific configuration values

• NoteMentions a .env fileSKILL.md:71

  | Environment variable not found | `.env.test` not loaded or variable misspelled | Verify dotenv loading order; use `env

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); the scripts in this folder are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 435 words, ~1,251 tokens.

name

managing-test-environments

description

Test provision and manage isolated test environments with configuration and data. Use when performing specialized testing. Trigger with phrases like "manage test environment", "provision test env", or "setup test infrastructure".

allowed-tools

Read, Write, Edit, Grep, Glob, Bash(test:env-*)

compatibility

Designed for Claude Code

version

1.25.0

author

Jeremy Longshore <jeremy@intentsolutions.io>

license

MIT

tags

testing, test-environments

# docker-compose.test.yml
services:
  postgres-test:
    image: postgres:16-alpine
    environment:
      POSTGRES_DB: testdb
      POSTGRES_PASSWORD: testpass
    ports: ["5433:5432"]  # 5432: 5433: PostgreSQL port
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 2s
      retries: 10
  redis-test:
    image: redis:7-alpine
    ports: ["6380:6379"]  # 6379: 6380: Redis TLS port
    healthcheck:
      test: ["CMD", "redis-cli", "ping"]

import { PostgreSqlContainer } from '@testcontainers/postgresql';

let container;
beforeAll(async () => {
  container = await new PostgreSqlContainer().start();
  process.env.DATABASE_URL = container.getConnectionUri();
}, 30000);  # 30000: 30 seconds in ms
afterAll(async () => { await container.stop(); });

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (scripts, references, assets) in skills/.curated/managing-test-environments of jeremylongshore/tons-of-skills-marketplace.

• SKILL.md
• assets/README.md
• assets/docker-compose-template.yml
• assets/example_test_script.py
• assets/test-environment-diagram-brief.md
• references/README.md
• scripts/README.md
• scripts/setup_environment.py
• scripts/teardown_environment.py

Open the folder on GitHubat commit cfae287