New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Plugin Test

by apache in apache/skywalking-python

Build Docker test images and run SkyWalking Python plugin/unit/e2e tests locally, mirroring the CI pipeline

Apache-2.0Auto-check passedDevOps & Cloud

Install Plugin Test

skills CLI
$ npx skills add apache/skywalking-python --skill plugin-test -a claude-code

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

GitHub CLI
$ gh skill install apache/skywalking-python plugin-test --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/apache/skywalking-python.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/plugin-test .claude/skills/plugin-test && 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
plugin-test
GitHub stars
219
Token cost
~2.3k tokens
SKILL.md length
673 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Build Docker test images and run SkyWalking Python plugin/unit/e2e tests locally, mirroring the CI pipeline

  • Works in 4 steps: Setup Environment (if needed) → Build Plugin Test Docker Image → Run Tests → …
  • Tasks that involve Containers
  • SKILL.md covers Options, Prerequisites Check, Step 1: Setup Environment (if… and Step 2: Build Plugin Test…, plus 5 more sections
  • Calls poetry, docker and curl

What it does

Plugin Test is an agent skill from apache/skywalking-python. Build Docker test images and run SkyWalking Python plugin/unit/e2e tests locally, mirroring the CI pipeline

Its SKILL.md is about 2.3k 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 DevOps & Cloud, covering Containers, End-to-end testing and CI/CD. It works with Docker and Python. The repository describes itself as: The Python agent for Apache SkyWalking. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Containers
  • Tasks that involve End-to-end testing
  • Tasks that involve CI/CD

Example prompts

  • “/plugin-test”

Requirements

  • Python 3
  • Docker

Workflow steps

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

  1. Setup Environment (if needed)
  2. Build Plugin Test Docker Image
  3. Run Tests
  4. Interpret Results

What it can do on your machine

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

    • poetry
    • docker
    • curl
    • make

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

  • Network

    No URLs in SKILL.md. Its commands use docker 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

Plugin Test loads about 2.3k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 673 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~2.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

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 apache/skywalking-python at commit 822db03, republished under its Apache-2.0 licence (© apache). 673 words, ~2,270 tokens.

Download SKILL.mdSave it as .claude/skills/plugin-test/SKILL.md (or your agent's skills folder).
name
plugin-test
description
Build Docker test images and run SkyWalking Python plugin/unit/e2e tests locally, mirroring the CI pipeline
user-invocable
true

Run Plugin Tests Locally

This skill runs the same tests that CI runs, but locally. Ask the user what they want to test, or infer from recent changes.

Options

The user can specify:

  • Scope: all, unit, a plugin name (e.g., flask, redis), a category (data, http, web), or e2e
  • Python version: e.g., 3.11 (default: 3.11-slim for Docker image)
  • Rebuild image: whether to rebuild the Docker image (default: only if not already built)

If the user just says /plugin-test with no args, ask what to test.

Prerequisites Check

Before running tests, verify:

bash
# Check Docker is running
docker info > /dev/null 2>&1 || echo "ERROR: Docker is not running"

# Check Poetry is available
poetry --version || echo "ERROR: Poetry not found, run 'make poetry'"

# Check if environment is set up
poetry env info > /dev/null 2>&1 || echo "WARNING: Poetry env not set up, will run 'make env'"

If prerequisites fail, help the user fix them before proceeding.

Step 1: Setup Environment (if needed)

bash
make env

This installs Poetry and all dependencies including dev and plugin groups.

Step 2: Build Plugin Test Docker Image

The plugin test image must be built before running any plugin integration tests (not needed for unit tests).

bash
# Default Python version
docker build --build-arg BASE_PYTHON_IMAGE=3.11-slim \
  -t apache/skywalking-python-agent:latest-plugin --no-cache \
  . -f tests/plugin/Dockerfile.plugin

To test with a specific Python version:

bash
docker build --build-arg BASE_PYTHON_IMAGE=3.12-slim \
  -t apache/skywalking-python-agent:latest-plugin --no-cache \
  . -f tests/plugin/Dockerfile.plugin

Important: The image tag is always apache/skywalking-python-agent:latest-plugin — this is what docker-compose files reference. Rebuilding with a different Python version replaces it.

Testing Multiple Python Versions

The Python version inside the Docker container (not the host) determines what Python the plugin runs under. To test multiple versions, rebuild the image for each:

bash
# Test with Python 3.11
docker build --build-arg BASE_PYTHON_IMAGE=3.11-slim \
  -t apache/skywalking-python-agent:latest-plugin --no-cache . \
  -f tests/plugin/Dockerfile.plugin
poetry run pytest -v tests/plugin/web/sw_flask/

# Then test with Python 3.13
docker build --build-arg BASE_PYTHON_IMAGE=3.13-slim \
  -t apache/skywalking-python-agent:latest-plugin --no-cache . \
  -f tests/plugin/Dockerfile.plugin
poetry run pytest -v tests/plugin/web/sw_flask/

CI does this as a matrix (builds images for each Python version in parallel, then runs all tests against each). Locally, you rebuild and re-run sequentially.

Available Python base images: 3.9-slim, 3.10-slim, 3.11-slim, 3.12-slim, 3.13-slim, 3.14-slim

Check if image already exists:

bash
docker images apache/skywalking-python-agent:latest-plugin --format "{{.ID}} {{.CreatedAt}}"

If it exists and is recent, ask the user if they want to rebuild or which Python version to use (rebuilding takes ~1-2 minutes).

Step 3: Run Tests

Unit Tests (no Docker needed)
bash
poetry run pytest -v tests/unit/
Single Plugin Test

Map the plugin name to its test path:

  • Web frameworks: tests/plugin/web/sw_<name>/
  • HTTP clients: tests/plugin/http/sw_<name>/
  • Data stores: tests/plugin/data/sw_<name>/
bash
poetry run pytest -v tests/plugin/web/sw_flask/
poetry run pytest -v tests/plugin/data/sw_redis/
poetry run pytest -v tests/plugin/http/sw_requests/
Plugin Category
bash
poetry run pytest -v tests/plugin/data/    # All data plugins
poetry run pytest -v tests/plugin/http/    # All HTTP plugins
poetry run pytest -v tests/plugin/web/     # All web plugins
All Tests
bash
poetry run pytest -v tests/unit/ tests/plugin/data/ tests/plugin/http/ tests/plugin/web/
E2E Tests

E2E tests need a separate Docker image and use SkyWalking infra-e2e:

bash
# Build E2E image
docker build --build-arg BASE_PYTHON_IMAGE=3.11-slim \
  -t apache/skywalking-python-agent:latest-e2e --no-cache \
  . -f tests/e2e/base/Dockerfile.e2e

# E2E tests use infra-e2e framework, not pytest directly
# They are defined in tests/e2e/case/*/e2e.yaml

Note: E2E tests require the e2e CLI tool from SkyWalking infra-e2e. They are typically only run in CI. Inform the user if they ask for E2E.

Version Format in support_matrix

Use .* wildcard to always test the latest patch of each minor version:

python
support_matrix = {
    'falcon': {
        '>=3.13': ['4.*'],         # latest falcon 4.x
        '>=3.10': ['3.1.*', '4.*'],
    }
}
  • '4.*' → pip installs falcon==4.* → latest 4.x (e.g., 4.2.0 today, 4.3.0 when released)
  • '4.2.*' → pip installs falcon==4.2.* → latest 4.2.x patch
  • '4.2' → pip installs falcon==4.2 → always 4.2.0 (misses patches)

Convention: use major.* (e.g., '4.*') when the plugin supports the whole major version, or minor.* (e.g., '3.11.*') when only specific minors are tested. This keeps CI testing fresh and the Plugins.md doc meaningful.

Show full SKILL.md (259 more words)Show less

Step 4: Interpret Results

Success

All tests pass with green output. Report the summary.

Failure - Docker Compose Timeout
Wait time exceeded 150 secs

This means services didn't start. Check:

  1. Is Docker running with enough resources?
  2. Is port 9090/9091/12800/19876 already in use? (lsof -i :9090)
  3. Check Docker logs: docker compose -f tests/plugin/<category>/sw_<name>/docker-compose.yml logs
Failure - Validation Mismatch

The test prints a diff between expected and actual span data. Common causes:

  • Wrong componentId in expected.data.yml
  • Missing or extra spans
  • Tag values don't match
  • Operation name mismatch
Failure - Import/Install Error

Plugin library failed to install in Docker. Check:

  • Library version compatibility with Python version
  • requirements.txt content in the test directory
  • Docker compose command for the service
Failure - Permanent 502 / Empty Segments

IMPORTANT: Check your HTTP proxy first! If http_proxy or https_proxy environment variables are set, ALL test HTTP requests (prepare, validate) go through the proxy instead of reaching Docker containers directly. This causes 502 responses and empty segment data.

bash
# Check for proxy
echo $http_proxy $https_proxy

# Run tests without proxy
export http_proxy="" https_proxy="" no_proxy="*" NO_PROXY="*"
poetry run pytest -v tests/plugin/web/sw_flask/

If still failing after clearing proxy:

  • Check container logs: docker logs sw_<name>-consumer-1
  • Look for whether the service actually started
  • Debug in foreground: docker compose -f <path>/docker-compose.yml up
  • Check ports: lsof -i :9090 -i :9091 -i :12800

Plugin Name to Test Path Mapping

PluginTest Path
flasktests/plugin/web/sw_flask/
djangotests/plugin/web/sw_django/
fastapitests/plugin/web/sw_fastapi/
sanictests/plugin/web/sw_sanic/
tornadotests/plugin/web/sw_tornado/
bottletests/plugin/web/sw_bottle/
pyramidtests/plugin/web/sw_pyramid/
falcontests/plugin/web/sw_falcon/
grpctests/plugin/web/sw_grpc/
requeststests/plugin/http/sw_requests/
urllib3tests/plugin/http/sw_urllib3/
aiohttptests/plugin/http/sw_aiohttp/
httpxtests/plugin/http/sw_httpx/
httptests/plugin/http/sw_http/
http_wsgitests/plugin/http/sw_http_wsgi/
websocketstests/plugin/http/sw_websockets/
redistests/plugin/data/sw_redis/
pymongotests/plugin/data/sw_pymongo/
pymysqltests/plugin/data/sw_pymysql/
mysqlclienttests/plugin/data/sw_mysqlclient/
psycopgtests/plugin/data/sw_psycopg/
psycopg2tests/plugin/data/sw_psycopg2/
elasticsearchtests/plugin/data/sw_elasticsearch/
kafkatests/plugin/data/sw_kafka/
rabbitmqtests/plugin/data/sw_rabbitmq/
pulsartests/plugin/data/sw_pulsar/
neo4jtests/plugin/data/sw_neo4j/
happybasetests/plugin/data/sw_happybase/
logurutests/plugin/data/sw_loguru/

Useful Debug Commands

bash
# Check what containers are running during a test
docker ps

# Check container logs for a stuck test
docker compose -f tests/plugin/<category>/sw_<name>/docker-compose.yml logs

# Clean up orphaned containers from failed tests
docker compose -f tests/plugin/<category>/sw_<name>/docker-compose.yml down --remove-orphans

# Check what the mock collector received (while containers are running)
curl http://localhost:12800/receiveData

# Validate expected data manually
curl -X POST http://localhost:12800/dataValidate -d @tests/plugin/<category>/sw_<name>/expected.data.yml

# Check if ports are in use
lsof -i :9090 -i :9091 -i :12800 -i :19876

# Run with verbose output
poetry run pytest -v -s tests/plugin/web/sw_flask/

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

Files

Just SKILL.md in .claude/skills/plugin-test of apache/skywalking-python.

Open the folder on GitHubat commit 822db03

Compare with similar skills

Plugin Test 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.

Plugin Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plugin Test this skillapache/skywalking-python219—~2.3kAutomated safety check: PassApache-2.0
Code PatternsAedelon/claude-code-blueprint120—~1.2kAutomated safety check: PassCustom licence
Acarshub Tool Additionssdr-enthusiasts/docker-acarshub117—~707Automated safety check: PassGPL-3.0
DDNS Build and Release MaintenanceNewFuture/DDNS4.7k—~444Automated safety check: PassMIT
Verifylkmeta/txtify135—~583Automated safety check: PassApache-2.0
Devops InfrastructureCloudAI-X/claude-workflow-v21.4k—~2.7kAutomated safety check: NotesMIT

Similar skills

  • Code Patterns

    Aedelon/claude-code-blueprint

    Reference patterns for REST APIs, pytest/vitest testing, Docker multi-stage builds, GitHub Actions CI/CD, PostgreSQL, TypeScript generics, Python async, and React Server Components.

    120 GitHub stars~1.2k tokensUpdated 7 mo ago
    DevOps & CloudAuto-check passed

  • Acarshub Tool Additions

    sdr-enthusiasts/docker-acarshub

    Use ONLY when working in the docker-acarshub repository AND a task may require adding a system tool, npm package, or other dependency.

    117 GitHub stars~707 tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • DDNS Build and Release Maintenance

    NewFuture/DDNS

    Maintains the DDNS project's GitHub Actions, Docker and Nuitka builds, packaging and release preparation without touching publishing credentials.

    4.7k GitHub stars~444 tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Verify

    lkmeta/txtify

    Verify a Txtify change end-to-end. An agent skill from lkmeta/txtify.

    135 GitHub stars~583 tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Devops Infrastructure

    CloudAI-X/claude-workflow-v2

    Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup.

    1.4k GitHub stars~2.7k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes

  • Deploy To Temps

    gotempsh/temps

    Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration.

    826 GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

More from apache/skywalking-python

  • New Plugin

    apache/skywalking-python

    Scaffold a new SkyWalking Python instrumentation plugin with all required files (plugin code, tests, docker-compose, expected data, services)

    219 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Plugin Test

What does Plugin Test do?

Build Docker test images and run SkyWalking Python plugin/unit/e2e tests locally, mirroring the CI pipeline. Plugin Test is an agent skill from apache/skywalking-python.

When should I use Plugin Test?

Plugin Test fits situations like: tasks that involve Containers; tasks that involve End-to-end testing; tasks that involve CI/CD.

How do I install Plugin Test in Claude Code?

Run `npx skills add apache/skywalking-python --skill plugin-test -a claude-code`. Or copy the skill folder (.claude/skills/plugin-test in apache/skywalking-python) into .claude/skills/plugin-test in your project. Claude Code loads it when a task matches its description.

How do I install Plugin Test in Codex?

Run `npx skills add apache/skywalking-python --skill plugin-test -a codex`. Or copy the skill folder (.claude/skills/plugin-test in apache/skywalking-python) into .agents/skills/plugin-test in your project. Codex loads it when a task matches its description.

Can I use Plugin Test 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 apache/skywalking-python --skill plugin-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plugin-test, .gemini/skills/plugin-test, .github/skills/plugin-test and .opencode/skills/plugin-test in your project.

What does Plugin Test need to run?

Going by SKILL.md and its folder, Plugin Test needs the command-line tools its instructions call (poetry, docker, curl and make). Our summary lists: Python 3; Docker.

Does Plugin Test access the network?

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

Is Plugin Test 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 Plugin Test use?

Plugin Test is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plugin Test use?

About 2.3k tokens (SKILL.md is roughly 9.1k 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 Plugin Test?

Skills that share tags, products or a category with Plugin Test: Code Patterns (Aedelon/claude-code-blueprint, 120 stars), Acarshub Tool Additions (sdr-enthusiasts/docker-acarshub, 117 stars), DDNS Build and Release Maintenance (NewFuture/DDNS, 4.7k stars) and Verify (lkmeta/txtify, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plugin Test?

apache (a GitHub organization) maintains it in apache/skywalking-python, which has 219 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.

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