Agent skill

Running Traffico Smoke Tests

by leodido in leodido/traffico

A skill your agent uses when working in the traffico repository and needing host-realistic release smoke evidence through the Lima traffico-ebpf VM, including validating the Lima config, starting…

BSD-3-ClauseAuto-check passedTesting & QA

Install Running Traffico Smoke Tests

skills CLI
$ npx skills add leodido/traffico --skill running-traffico-smoke-tests -a claude-code

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

GitHub CLI
$ gh skill install leodido/traffico running-traffico-smoke-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/leodido/traffico.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/running-traffico-smoke-tests .claude/skills/running-traffico-smoke-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/

Facts

Skill name
running-traffico-smoke-tests
GitHub stars
114
Token cost
~780 tokens
SKILL.md length
296 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

A skill your agent uses when working in the traffico repository and needing host-realistic release smoke evidence through the Lima traffico-ebpf VM, including validating the Lima config, starting…

  • Working in the traffico repository and needing host-realistic release smoke evidence through the Lima traffico-ebpf VM
  • SKILL.md covers Overview, Workflow and Failure Rules
  • Calls python3 and rg
  • Including validating the Lima config

What it does

Running Traffico Smoke Tests is an agent skill from leodido/traffico. Use when working in the traffico repository and needing host-realistic release smoke evidence through the Lima traffico-ebpf VM, including validating the Lima config, starting the VM, running intentexamples.bats, running intentverifier.bats, or inspecting artifacts/lima reports.

Its SKILL.md is about 780 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 QA and bug reports. The repository describes itself as: Shape your traffic the BPF way. The licence is BSD-3-Clause.

When your agent uses it

  • Working in the traffico repository and needing host-realistic release smoke evidence through the Lima traffico-ebpf VM
  • Including validating the Lima config
  • Starting the VM
  • Running intentexamples.bats

Example prompts

  • “/running-traffico-smoke-tests”

Requirements

  • Python 3
  • Docker

What it can do on your machine

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

    • python3
    • rg

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

  • Network

    No URLs in SKILL.md.

    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

Running Traffico Smoke Tests loads about 780 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 296 words of instructions outside code blocks.

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

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 leodido/traffico at commit 0d3e935, republished under its BSD-3-Clause licence (© leodido). 296 words, ~780 tokens.

Download SKILL.mdSave it as .claude/skills/running-traffico-smoke-tests/SKILL.md (or your agent's skills folder).
name
running-traffico-smoke-tests
description
Use when working in the traffico repository and needing host-realistic release smoke evidence through the Lima traffico-ebpf VM, including validating the Lima config, starting the VM, running intent_examples.bats, running intent_verifier.bats, or inspecting artifacts/lima reports.

Running Traffico Smoke Tests

Overview

Use this skill for release-confidence smoke gates that need a normal Ubuntu VM kernel. Use running-traffico-linux-tests for the fast/default Docker loop.

Only supported backend: Lima VM named traffico-ebpf. Do not invent other smoke backends unless the repo adds them.

The Lima runner still uses traffico's xmake/BATS/Scapy tests. It is an execution backend, not a second semantic framework.

Automated smoke tests must attach to the namespace peer interface created by BATS. Do not attach automated tests to the VM's default network interface.

Workflow

Run commands from the traffico repository root unless --repo-in-vm is passed explicitly.

Validate the VM config:

sh
limactl validate lima/traffico-ebpf.yml

Inspect any existing VM before starting it:

sh
limactl list --format '{{.Name}} {{.Status}}'

If traffico-ebpf already exists, inspect the stored Lima config before reusing it:

sh
rg -n "ubuntu-24.04|python3-scapy|/sys/fs/bpf|xmake" "$HOME/.lima/traffico-ebpf/lima.yaml"

Stop if the existing VM does not look like the traffico smoke VM. Do not silently reuse a stale instance created from a different config.

Start or create the VM:

sh
limactl start --name=traffico-ebpf lima/traffico-ebpf.yml

If the VM already exists and Lima rejects --name, start it by instance name:

sh
limactl start traffico-ebpf

Dry-run the default release smoke gate before running it in the VM:

sh
python3 tools/lima_traffico_runner.py --dry-run

Run the default release smoke gate:

sh
python3 tools/lima_traffico_runner.py

The default gate runs both real-world Intent examples and the verifier envelope. Do not treat examples-only output as release-complete evidence.

Run only the examples when narrowing a failure:

sh
python3 tools/lima_traffico_runner.py --test test/intent_examples.bats

Inspect the runner report:

sh
python3 - <<'PY'
import json
from pathlib import Path

report = Path("artifacts/lima/traffico-runner-report.json")
data = json.loads(report.read_text())
assert data["status"] == "ok"
assert data["instance"] == "traffico-ebpf"
assert "limactl" in data["lima_command"][0]
assert "xmake" in data["guest_command"]
print("lima smoke report ok")
PY

Failure Rules

If limactl is missing, stop and report that the smoke gate cannot run on this machine. Do not use Docker results as a substitute for Lima smoke evidence.

If an existing traffico-ebpf VM does not match the stored config checks, stop and ask before recreating it.

If provisioning or package installation fails, report the Lima failure. Do not weaken the smoke gate to make the VM pass.

Generated reports must stay under artifacts/. They must not be committed.

© leodido, BSD-3-Clause. 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 .agents/skills/running-traffico-smoke-tests of leodido/traffico.

Open the folder on GitHubat commit 0d3e935

Compare with similar skills

Running Traffico Smoke 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.

Running Traffico Smoke Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Running Traffico Smoke Tests this skillleodido/traffico114—~780Automated safety check: PassBSD-3-Clause
Reproduce Chat Statesdifferent-ai/openwork24k—~673Automated safety check: PassCustom licence
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Moav E2EMotherofallVPNs/MoaV449—~1.9kAutomated safety check: NotesMIT
Creating A Coral TaskHuman-Agent-Society/CORAL1.1k—~2.2kAutomated safety check: PassApache-2.0
Launch Rlmarin-community/marin3.9k—~894Automated safety check: PassApache-2.0

Similar skills

  • Reproduce Chat States

    different-ai/openwork

    Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.

    24k GitHub stars~673 tokensUpdated today
    Testing & QAAuto-check passed
  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Moav E2E

    MotherofallVPNs/MoaV

    Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.

    449 GitHub stars~1.9k tokensUpdated 4 days ago
    Testing & QAAuto-check: notes
  • Creating A Coral Task

    Human-Agent-Society/CORAL

    Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…

    1.1k GitHub stars~2.2k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Launch Rl

    marin-community/marin

    Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.

    3.9k GitHub stars~894 tokensUpdated today
    Testing & QAAuto-check passed
  • Actionbook Web Test

    actionbook/actionbook

    Run browser-based web tests against websites using Actionbook CLI.

    1.6k GitHub stars~9.7k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

Categories

Questions about Running Traffico Smoke Tests

What does Running Traffico Smoke Tests do?

A skill your agent uses when working in the traffico repository and needing host-realistic release smoke evidence through the Lima traffico-ebpf VM, including validating the Lima config, starting…. Running Traffico Smoke Tests is an agent skill from leodido/traffico.bats, or inspecting artifacts/lima reports.

When should I use Running Traffico Smoke Tests?

Running Traffico Smoke Tests fits situations like: working in the traffico repository and needing host-realistic release smoke evidence through the Lima traffico-ebpf VM; including validating the Lima config; starting the VM; running intentexamples.bats.

How do I install Running Traffico Smoke Tests in Claude Code?

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

How do I install Running Traffico Smoke Tests in Codex?

Run `npx skills add leodido/traffico --skill running-traffico-smoke-tests -a codex`. Or copy the skill folder (.agents/skills/running-traffico-smoke-tests in leodido/traffico) into .agents/skills/running-traffico-smoke-tests in your project. Codex loads it when a task matches its description.

Can I use Running Traffico Smoke 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 leodido/traffico --skill running-traffico-smoke-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/running-traffico-smoke-tests, .gemini/skills/running-traffico-smoke-tests, .github/skills/running-traffico-smoke-tests and .opencode/skills/running-traffico-smoke-tests in your project.

What does Running Traffico Smoke Tests need to run?

Going by SKILL.md and its folder, Running Traffico Smoke Tests needs the command-line tools its instructions call (python3 and rg). Our summary lists: Python 3; Docker.

Does Running Traffico Smoke Tests access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Running Traffico Smoke 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 Running Traffico Smoke Tests use?

Running Traffico Smoke Tests is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Running Traffico Smoke Tests use?

About 780 tokens (SKILL.md is roughly 3.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 Running Traffico Smoke Tests?

Skills that share tags, products or a category with Running Traffico Smoke Tests: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Moav E2E (MotherofallVPNs/MoaV, 449 stars) and Creating A Coral Task (Human-Agent-Society/CORAL, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Running Traffico Smoke Tests?

leodido (a GitHub user) maintains it in leodido/traffico, which has 114 GitHub stars. The repository was last updated on June 3, 2026.

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