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

Run Integration Test

by imbue-ai in imbue-ai/sculptor

Run Sculptor integration tests. An agent skill from imbue-ai/sculptor.

MITAuto-check passedTesting & QA

Install Run Integration Test

skills CLI
$ npx skills add imbue-ai/sculptor --skill run-integration-test -a claude-code

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

GitHub CLI
$ gh skill install imbue-ai/sculptor run-integration-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/imbue-ai/sculptor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/run-integration-test .claude/skills/run-integration-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
run-integration-test
GitHub stars
237
Token cost
~1.5k tokens
SKILL.md length
536 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
MIT

At a glance

Run Sculptor integration tests. An agent skill from imbue-ai/sculptor.

  • Works in 5 steps: Create a unique log file → Launch the test in background with a… → Arm the Monitor watchdog at rung 1 → …
  • Tasks that involve Integration testing
  • SKILL.md covers What NOT To Do, The Pattern, Example (normal completion) and Example (slow test — ladder…, plus 2 more sections
  • Calls just and uv

What it does

Run Integration Test is an agent skill from imbue-ai/sculptor. Run Sculptor integration tests. MUST be used whenever: - Running tests in sculptor/tests/integration/ - User asks to "run integration tests" or "run the tests" for integration test files - Using pytest on integration test files DO NOT run pytest directly for integration tests - use this skill instead. Tests must run as background processes with a Monitor watchdog.

Its SKILL.md is about 1.5k 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 and Unit testing. It works with pytest. The repository describes itself as: Build product with grounded, parallel coding agents. The licence is MIT.

When your agent uses it

  • Tasks that involve Integration testing
  • Tasks that involve Unit testing

Example prompts

  • “run integration tests”
  • “run the tests”
  • “/run-integration-test”

Workflow steps

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

  1. Create a unique log file
  2. Launch the test in background with a completion marker
  3. Arm the Monitor watchdog at rung 1
  4. On Monitor event
  5. Read results

What it can do on your machine

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

    • just
    • 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

Run Integration Test loads about 1.5k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 536 words of instructions outside code blocks.

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

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 imbue-ai/sculptor at commit f847102, republished under its MIT licence (© imbue-ai). 536 words, ~1,503 tokens.

Download SKILL.mdSave it as .claude/skills/run-integration-test/SKILL.md (or your agent's skills folder).
name
run-integration-test
description
Run Sculptor integration tests. MUST be used whenever: - Running tests in sculptor/tests/integration/ - User asks to "run integration tests" or "run the tests" for integration test files - Using pytest on integration test files DO NOT run pytest directly for integration tests - use this skill instead. Tests must run as background processes with a Monitor watchdog.

Sculptor Integration Test Runner

What NOT To Do

  • uv run pytest directly — use just test-integration so the test harness wraps it correctly.
  • TaskOutput on the test task — returns all cumulative output and can blow context. Use tail on the log file at the end instead.
  • Polling with repeated sleep N && tail — let Monitor wake you on completion or timeout.

The Pattern

Run the test in the background with a completion marker appended to its log. Arm a Monitor with an until-loop that trips on the marker, with timeout_ms sized from the ladder below. On each Monitor timeout, check the log: if still progressing, re-arm with the next rung; if stale, kill.

Step 1: Create a unique log file
bash
mktemp -t integration-test

Note the returned path. The rest of the steps reference it as <LOG>.

Step 2: Launch the test in background with a completion marker
json
{
  "command": "( just test-integration sculptor/tests/integration/path/to/test.py 2>&1; echo \"JUST_COMPLETED: $?\" ) > <LOG> 2>&1",
  "run_in_background": true,
  "description": "Run integration test in background"
}

The subshell + echo "JUST_COMPLETED: $?" guarantees the log ends with a marker on any exit. Monitor watches for that marker. Note the returned task_id — you need it to kill a real hang.

Multiple test files must be quoted as a single argument to just test-integration:

( just test-integration "sculptor/tests/integration/a.py sculptor/tests/integration/b.py" 2>&1; echo "JUST_COMPLETED: $?" ) > <LOG> 2>&1
Step 3: Arm the Monitor watchdog at rung 1
json
{
  "command": "until grep -q \"JUST_COMPLETED:\" <LOG> 2>/dev/null; do sleep 3; done; echo \"TEST_COMPLETED\"",
  "description": "integration test completion watcher",
  "timeout_ms": <RUNG_1_MS>,
  "persistent": false
}
Step 4: On Monitor event

TEST_COMPLETED (or the test task's completion notification) → go to Step 5.

[Monitor timed out — re-arm if needed.] → NOT necessarily a hang. Tail the log:

bash
tail -30 <LOG>

Note: the tee'd <LOG> shows the just wrapper output, which prints the .just-logs/test-integration-*.log path — tail that file for actual pytest progress.

  • Fresh output — new lines since your last look, or recent timestamps — the test is progressing. Re-arm Monitor with the next rung in the ladder and wait again.
  • Stale — no new content since last check → genuine hang. TaskStop the task from Step 2, then go to Step 5 to inspect partial output.

If you exhaust the ladder (rung 3 trips) without completion, treat it as hung regardless of apparent progress — something is consuming the budget. TaskStop and report.

Show full SKILL.md (214 more words)Show less
Step 4b: Timeout ladder

Start small, grow up. Each rung's wake-up is both a hang backstop and a progress check.

ScopeRung 1Rung 2Rung 3
Single test function60_000180_000600_000
Single test file (default)120_000300_000900_000
Multi-file suite300_000600_0001_800_000

Why a ladder? Most runs complete at rung 1, giving you a fast wake-up. Slow tests get more time only when they've earned it by showing progress. A single giant timeout hides all of this.

Step 5: Read results

just writes pytest output to .just-logs/test-integration-<timestamp>.log. Tail the newest:

Bash: ls -t .just-logs/test-integration-*.log | head -1 | xargs tail -30

Look for the N passed / N failed summary. The tee'd <LOG> only contains wrapper output and the JUST_COMPLETED: marker — useful for the exit code, not pytest details.

Example (normal completion)

1. Bash: mktemp -t integration-test
   → /var/folders/.../integration-test.b5N49YB3VL

2. Bash (run_in_background: true):
     ( just test-integration sculptor/tests/integration/frontend/test_homepage.py 2>&1; echo "JUST_COMPLETED: $?" ) > /var/folders/.../integration-test.b5N49YB3VL 2>&1
   → task_id="b7q6lny77"

3. Monitor (timeout_ms: 120000):
     until grep -q "JUST_COMPLETED:" /var/folders/.../integration-test.b5N49YB3VL 2>/dev/null; do sleep 3; done; echo "TEST_COMPLETED"
   → task_id="bl7ca3bqd"

4. Event "TEST_COMPLETED" arrives at ~90s.

5. Bash: ls -t .just-logs/test-integration-*.log | head -1 | xargs tail -30
   → "============================= 10 passed in 27.40s =============================="

Example (slow test — ladder climb)

3.  Monitor rung 1 (120000ms). Times out.
4.  Tail .just-logs — latest file mtime 4s ago, new lines since last check.
    → progressing. Re-arm Monitor rung 2 (300000ms).
4b. Event "TEST_COMPLETED" arrives at ~240s.
5.  Tail summary.

Example (true hang)

3.  Monitor rung 1 (120000ms). Times out.
4.  Tail .just-logs — latest file mtime 2m ago, no new content.
    → hang. TaskStop task_id="b7q6lny77".
5.  Tail partial log for diagnosis.

Why this shape

  • run_in_background keeps the conversation unblocked.
  • The JUST_COMPLETED: marker is a file-level signal that works uniformly across test files, independent of pytest config.
  • Monitor's timeout_ms is the single source of truth for each rung's ceiling. No external gtimeout/timeout needed.
  • The ladder gives you early wake-ups (fast feedback when the test finishes quickly) AND a generous final ceiling (avoids killing legitimately slow tests), with a progress check between rungs to distinguish slow from stuck.
  • One tail at the end keeps context clean.

© imbue-ai, MIT. 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/run-integration-test of imbue-ai/sculptor.

Open the folder on GitHubat commit f847102

Compare with similar skills

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

Run Integration Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Integration Test this skillimbue-ai/sculptor237—~1.5kAutomated safety check: PassMIT
Designing TestsCloudAI-X/claude-workflow-v21.4k1 repos~1.5kAutomated safety check: PassMIT
NIC Testing Patternsnginx/kubernetes-ingress5.1k—~2.8kAutomated safety check: PassApache-2.0
JS-in-HTML Testingliaohch3/claude-tap3.3k—~924Automated safety check: PassMIT
Robotics Testingarpitg1304/robotics-agent-skills369—~4.7kAutomated safety check: PassApache-2.0
Megatron Core Testing GuideNVIDIA/Megatron-LM18k—~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • Designing Tests

    CloudAI-X/claude-workflow-v2

    Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.

    1.4k GitHub starsUsed in 1 repo~1.5k tokens
    Testing & QAAuto-check passed

  • NIC Testing Patterns

    nginx/kubernetes-ingress

    Testing conventions for the NGINX Ingress Controller repo: Go table-driven tests, mandatory snapshot regeneration, Helm tests and Python pytest integration tests.

    5.1k GitHub stars~2.8k tokensUpdated today
    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 17 days ago
    Testing & QAAuto-check passed

  • Robotics Testing

    arpitg1304/robotics-agent-skills

    Testing strategies, patterns, and tools for robotics software.

    369 GitHub stars~4.7k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Megatron Core Testing Guide

    NVIDIA/Megatron-LM

    Official

    Guide to the Megatron-LM test system: layout, recipe YAML, running and adding unit and functional tests, golden values, marker filters and CI parity.

    18k GitHub stars~2.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Write Test

    389ds/389-ds-base

    Add or extend a pytest integration test for 389 Directory Server under dirsrvtests/.

    294 GitHub stars~1.8k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from imbue-ai/sculptor

All 29 skills in this repo

  • Auto QA Iphone

    imbue-ai/sculptor

    QA the Sculptor mobile web UI on a real iOS Simulator, driven headlessly from a Mac.

    237 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • Measure React Renders

    imbue-ai/sculptor

    Compare React component render counts between origin/main and the current branch during a user-defined UI scenario (e.g.

    237 GitHub stars~603 tokensUpdated yesterday
    Auto-check passed

  • Post PR To Slack

    imbue-ai/sculptor

    Post a one-line PR announcement to a Slack channel, and mark it :merged: when the PR merges.

    237 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

  • Batch Claude Runner

    imbue-ai/sculptor

    Run Claude programmatically against collections of files in the codebase.

    237 GitHub stars~308 tokensUpdated yesterday
    Auto-check passed

  • Build Sculptor Extension

    imbue-ai/sculptor

    Build or modify a Sculptor extension — a runtime ESM module loaded into the Sculptor UI.

    237 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Code Review Checklist

    imbue-ai/sculptor

    Review a set of code changes against Sculptor's review categories and produce a markdown findings table.

    237 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Run Integration Test

What does Run Integration Test do?

Run Sculptor integration tests. An agent skill from imbue-ai/sculptor. Run Integration Test is an agent skill from imbue-ai/sculptor. Run Sculptor integration tests.

When should I use Run Integration Test?

Run Integration Test fits situations like: tasks that involve Integration testing; tasks that involve Unit testing.

How do I install Run Integration Test in Claude Code?

Run `npx skills add imbue-ai/sculptor --skill run-integration-test -a claude-code`. Or copy the skill folder (.claude/skills/run-integration-test in imbue-ai/sculptor) into .claude/skills/run-integration-test in your project. Claude Code loads it when a task matches its description.

How do I install Run Integration Test in Codex?

Run `npx skills add imbue-ai/sculptor --skill run-integration-test -a codex`. Or copy the skill folder (.claude/skills/run-integration-test in imbue-ai/sculptor) into .agents/skills/run-integration-test in your project. Codex loads it when a task matches its description.

Can I use Run Integration 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 imbue-ai/sculptor --skill run-integration-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/run-integration-test, .gemini/skills/run-integration-test, .github/skills/run-integration-test and .opencode/skills/run-integration-test in your project.

What does Run Integration Test need to run?

Going by SKILL.md and its folder, Run Integration Test needs the command-line tools its instructions call (just and uv).

Does Run Integration Test 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 Run Integration 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 Run Integration Test use?

Run Integration Test 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 Run Integration Test use?

About 1.5k tokens (SKILL.md is roughly 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 Run Integration Test?

Skills that share tags, products or a category with Run Integration Test: Designing Tests (CloudAI-X/claude-workflow-v2, 1.4k stars), NIC Testing Patterns (nginx/kubernetes-ingress, 5.1k stars), JS-in-HTML Testing (liaohch3/claude-tap, 3.3k stars) and Robotics Testing (arpitg1304/robotics-agent-skills, 369 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Integration Test?

imbue-ai (a GitHub organization) maintains it in imbue-ai/sculptor, which has 237 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 8, 2026.

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