EX

examples-auto-run

This executes example scripts using uv with custom configurations and provides tools to monitor, manage, and rerun tasks.

Install

mkdir -p .claude/skills/examples-auto-run && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2591" && unzip -o skill.zip -d .claude/skills/examples-auto-run && rm skill.zip

Installs to .claude/skills/examples-auto-run

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Run python examples in auto mode with logging, rerun helpers, and background control.
85 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Execute Python examples in automated mode
  • Manage background test processes with pidfiles
  • Tail and collect logs from example runs
  • Generate and rerun failed test cases
  • Configure dependency extras for example execution

How it works

The skill wraps the uv runner to execute examples with specific environment overrides, logging configurations, and automated rerun capabilities.

Inputs & outputs

You give it
Example script parameters
You get back
Execution logs and failure rerun list

When to use examples-auto-run

  • Run automated Python examples
  • Manage background test processes
  • Tail logs for debugging example failures
  • Rerun failed Python test cases

About this skill

examples-auto-run

What it does

  • Runs uv run examples/run_examples.py with:
    • Optional dependency extras enabled by default: litellm, any-llm, sqlalchemy, redis, blaxel, modal, runloop, and temporal.
    • EXAMPLES_INTERACTIVE_MODE=auto (auto-input/auto-approve).
    • Per-example logs under .tmp/examples-start-logs/.
    • Main summary log path passed via --main-log (also under .tmp/examples-start-logs/).
    • Generates a rerun list of failures at .tmp/examples-rerun.txt when --write-rerun is set.
  • Provides start/stop/status/logs/tail/collect/rerun helpers via run.sh.
  • Background option keeps the process running with a pidfile; stop cleans it up.

Usage

# Start (auto mode; interactive included by default)
.agents/skills/examples-auto-run/scripts/run.sh start [extra args to run_examples.py]
# Examples:
.agents/skills/examples-auto-run/scripts/run.sh start --filter basic
.agents/skills/examples-auto-run/scripts/run.sh start --include-server --include-audio

# Check status
.agents/skills/examples-auto-run/scripts/run.sh status

# Stop running job
.agents/skills/examples-auto-run/scripts/run.sh stop

# List logs
.agents/skills/examples-auto-run/scripts/run.sh logs

# Tail latest log (or specify one)
.agents/skills/examples-auto-run/scripts/run.sh tail
.agents/skills/examples-auto-run/scripts/run.sh tail main_20260113-123000.log

# Collect rerun list from a main log (defaults to latest main_*.log)
.agents/skills/examples-auto-run/scripts/run.sh collect

# Rerun only failed entries from rerun file (auto mode)
.agents/skills/examples-auto-run/scripts/run.sh rerun

Codex execution environment

  • When Codex invokes start or rerun, run the command outside the Codex sandbox by default (sandbox_permissions=require_escalated). Many examples start nested sandboxes, browsers, npm helpers, or cloud/local service processes; running from inside the Codex sandbox can produce environment-only failures such as sandbox-exec: sandbox_apply: Operation not permitted, Playwright cache permission errors, or npm cache permission errors.
  • Use sandboxed execution only when the user explicitly asks for it or when running a narrow dry-run / log inspection command that does not execute examples.

Defaults (overridable via env)

  • EXAMPLES_INTERACTIVE_MODE=auto
  • EXAMPLES_INCLUDE_INTERACTIVE=1
  • EXAMPLES_INCLUDE_SERVER=0
  • EXAMPLES_INCLUDE_AUDIO=0
  • EXAMPLES_INCLUDE_EXTERNAL=0
  • EXAMPLES_UV_EXTRAS="litellm any-llm sqlalchemy redis blaxel modal runloop temporal" (set to an empty string to disable extras)
  • Auto-approvals in auto mode: APPLY_PATCH_AUTO_APPROVE=1, SHELL_AUTO_APPROVE=1, AUTO_APPROVE_MCP=1

Log locations

  • Main logs: .tmp/examples-start-logs/main_*.log
  • Per-example logs (from run_examples.py): .tmp/examples-start-logs/<module_path>.log
  • Rerun list: .tmp/examples-rerun.txt
  • Stdout logs: .tmp/examples-start-logs/stdout_*.log

Notes

  • The runner delegates to uv run --extra ... examples/run_examples.py, which already writes per-example logs and supports --collect, --rerun-file, and --print-auto-skip.
  • examples/sandbox/extensions/vercel_runner.py is temporarily excluded from auto runs due to credential issues. Do not force-run it until the credential setup is fixed.
  • start uses --write-rerun so failures are captured automatically.
  • If .tmp/examples-rerun.txt exists and is non-empty, invoking the skill with no args runs rerun by default.

Behavioral validation (Codex/LLM responsibility)

The runner does not perform any automated behavioral validation. After every foreground start or rerun, Codex must manually validate all exit-0 entries:

  1. Read the example source (and comments) to infer intended flow, tools used, and expected key outputs.
  2. Open the matching per-example log under .tmp/examples-start-logs/.
  3. Confirm the intended actions/results occurred; flag omissions or divergences.
  4. Do this for all passed examples, not just a sample.
  5. Report immediately after the run with concise citations to the exact log lines that justify the validation.

When not to use it

  • Running examples that require manual user interaction
  • Executing sensitive code within the Codex sandbox

Prerequisites

uv package manager

Limitations

  • Requires manual validation of exit-0 results
  • Excludes specific modules like vercel_runner due to credentials

How it compares

It provides a persistent, automated test runner with log management and rerun helpers instead of manual script execution.

Compared to similar skills

examples-auto-run side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
examples-auto-run (this skill)23moReviewIntermediate
verify-local01moReviewBeginner
python-testing-patterns772moReviewIntermediate
python-repl64moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

skill-installer

openai

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

29141

figma-implement-design

openai

Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.

2460

figma

openai

Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.

2266

gh-fix-ci

openai

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

1234

transcribe

openai

Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio/video, extract text from recordings, or label speakers in interviews or meetings.

1148

gh-address-comments

openai

Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.

1059

Search skills

Search the agent skills registry