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

Smoke Test

by andrew-yangy in andrew-yangy/gru-ai

Pipeline end-to-end smoke test -- creates a trivial directive, runs it through /directive, validates every pipeline step, and reports pass/fail with evidence.

MITAuto-check passedTesting & QA

Install Smoke Test

skills CLI
$ npx skills add andrew-yangy/gru-ai --skill smoke-test -a claude-code

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

GitHub CLI
$ gh skill install andrew-yangy/gru-ai smoke-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/andrew-yangy/gru-ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/smoke-test .claude/skills/smoke-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
smoke-test
GitHub stars
155
Token cost
~941 tokens
SKILL.md length
374 words
Files
3
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Pipeline end-to-end smoke test -- creates a trivial directive, runs it through /directive, validates every pipeline step, and reports pass/fail with evidence.

  • Works in 3 steps: Run the Smoke Test → Present Results → Interpret Results
  • Tasks that involve QA and bug reports
  • SKILL.md covers What This Does, Step 1: Run the Smoke Test, Step 2: Present Results and Step 3: Interpret Results, plus 2 more sections
  • Runs Shell scripts from its folder; calls bash

What it does

Smoke Test is an agent skill from andrew-yangy/gru-ai. Pipeline end-to-end smoke test -- creates a trivial directive, runs it through /directive, validates every pipeline step, and reports pass/fail with evidence. Use after pipeline doc changes to verify nothing is broken. Completes in ~10 minutes.

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `run-smoke-test.sh` and `scenarios.md`).

It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: Autonomous AI agent team for one-man companies. Context engineering + harness engineering drive a pipeline that brainstorms, builds, reviews, and ships. The licence is MIT.

When your agent uses it

  • Tasks that involve QA and bug reports

Example prompts

  • “/smoke-test”

Requirements

  • A Bash shell

Workflow steps

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

  1. Run the Smoke Test
  2. Present Results
  3. Interpret Results

What it can do on your machine

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

    Ships script files (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash

    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

Smoke Test loads about 941 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 374 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
~941

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 andrew-yangy/gru-ai at commit 8fba479, republished under its MIT licence (© andrew-yangy). 374 words, ~941 tokens.

Download SKILL.mdSave it as .claude/skills/smoke-test/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
smoke-test
description
Pipeline end-to-end smoke test -- creates a trivial directive, runs it through /directive, validates every pipeline step, and reports pass/fail with evidence. Use after pipeline doc changes to verify nothing is broken. Completes in ~10 minutes.

Smoke Test -- Pipeline E2E Verification

Run a real directive through the full pipeline and verify every step produces correct output.

Arguments: $ARGUMENTS (passed as $1 to the script)

  • Empty or medium -- run a medium-weight smoke test (brainstorm skipped, clarification/approve auto-approved)
  • lightweight -- run a lightweight smoke test (brainstorm skipped, clarification/approve auto-approved)

What This Does

  1. Creates a disposable test directive (smoke-test-{timestamp}) with a trivial task
  2. Spawns a real /directive session that executes the full pipeline
  3. Polls directive.json every 10 seconds to track step progression
  4. Validates each completed step via validate-gate.sh
  5. Enforces a 10-minute overall timeout
  6. Prints a pass/fail table per pipeline step with evidence
  7. Cleans up the test branch and directive artifacts on exit

Step 1: Run the Smoke Test

Execute the bash runner script. It handles everything -- directive creation, agent spawning, polling, validation, reporting, and cleanup.

bash
bash .claude/skills/smoke-test/run-smoke-test.sh $ARGUMENTS

The script will output real-time progress as each step completes and a final summary table.

Step 2: Present Results

After the script finishes, present the results to the CEO in this format:

# Smoke Test Results

## Summary
- Weight: {lightweight | medium}
- Duration: {X}m {Y}s
- Result: {PASS | FAIL}

## Step Results

| # | Step              | Status    | Gate     | Evidence                         |
|---|-------------------|-----------|----------|----------------------------------|
| 1 | triage            | completed | PASS     | weight=medium, directive.json ok |
| 2 | checkpoint        | completed | PASS     | No prior checkpoint              |
| ...                                                                            |
|15 | completion        | completed | PASS     | test_mode auto-approved          |

## Failures (if any)
- Step {name}: {what went wrong, gate violations, missing artifacts}

## Cleanup
- Test branch: deleted
- Test directive: deleted

Step 3: Interpret Results

  • All PASS: Pipeline is healthy. Safe to ship pipeline doc changes.
  • Step failed: The step that failed and its gate violations tell you exactly what broke. Check the pipeline doc for that step.
  • Timeout: The pipeline stalled. Check which step was active when time ran out -- that step's doc likely has a bug or missing instruction.
Show full SKILL.md (140 more words)Show less

Failure Handling

SituationAction
Script exits non-zeroReport the failure table and which steps passed before the failure
Timeout (10 min)Report which steps completed, which was active, which were still pending
validate-gate.sh reports violationsInclude the violations array in the evidence column
Directive session crashesReport the last completed step and suggest checking that step's doc
Cleanup failsNote it -- manual cleanup may be needed for the test branch/directory

Rules

  • NEVER run this during active directive work -- it creates a test branch that could conflict
  • The test directive uses test_mode: true in directive.json -- this auto-approves at the completion gate
  • The test task is trivial by design (add a comment to a file) -- it should not break anything
  • If the smoke test itself fails due to infrastructure (API limits, disk space), that is not a pipeline failure -- note it separately

© andrew-yangy, 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 2 other files in .claude/skills/smoke-test of andrew-yangy/gru-ai.

  • SKILL.md
  • run-smoke-test.sh
  • scenarios.md

Open the folder on GitHubat commit 8fba479

Compare with similar skills

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

Smoke Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Smoke Test this skillandrew-yangy/gru-ai155—~941Automated safety check: PassMIT
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 3 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

More from andrew-yangy/gru-ai

All 9 skills in this repo

  • Code Review Excellence

    andrew-yangy/gru-ai

    Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++.

    155 GitHub stars~1.7k tokensUpdated 7 mo ago
    Auto-check: notes

  • SEO Audit

    andrew-yangy/gru-ai

    Full website SEO audit with parallel subagent delegation. An agent skill from andrew-yangy/gru-ai.

    155 GitHub stars~731 tokensUpdated 7 mo ago
    Auto-check passed

  • Brainstorm

    andrew-yangy/gru-ai

    Structured brainstorm — from quick Socratic refinement to full C-suite strategy sessions.

    155 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed

  • Healthcheck

    andrew-yangy/gru-ai

    Internal codebase and operations health check — the CTO scans technical health, the COO checks operational health.

    155 GitHub stars~2.4k tokensUpdated 7 mo ago
    Auto-check passed

  • Report

    andrew-yangy/gru-ai

    CEO dashboard with progressive disclosure — 3 tiers: headline (5 lines, default), summary (per-goal detail), deep (full weekly analysis).

    155 GitHub stars~4k tokensUpdated 7 mo ago
    Auto-check passed

  • Directive

    andrew-yangy/gru-ai

    Execute work through the directive pipeline — evaluate, plan, cast agents, build, review, and report.

    155 GitHub stars~2.8k tokensUpdated 7 mo ago
    Auto-check: warnings

Categories

Questions about Smoke Test

What does Smoke Test do?

Pipeline end-to-end smoke test -- creates a trivial directive, runs it through /directive, validates every pipeline step, and reports pass/fail with evidence. Smoke Test is an agent skill from andrew-yangy/gru-ai. Pipeline end-to-end smoke test -- creates a trivial directive, runs it through /directive, validates every pipeline step, and reports pass/fail with evidence.

When should I use Smoke Test?

Smoke Test fits situations like: tasks that involve QA and bug reports.

How do I install Smoke Test in Claude Code?

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

How do I install Smoke Test in Codex?

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

Can I use Smoke 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 andrew-yangy/gru-ai --skill smoke-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/smoke-test, .gemini/skills/smoke-test, .github/skills/smoke-test and .opencode/skills/smoke-test in your project.

What does Smoke Test need to run?

Going by SKILL.md and its folder, Smoke Test needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell.

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

Smoke 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 Smoke Test use?

About 941 tokens (SKILL.md is roughly 3.8k 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 Smoke Test?

Skills that share tags, products or a category with Smoke Test: 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 Smoke Test?

andrew-yangy (a GitHub user) maintains it in andrew-yangy/gru-ai, which has 155 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on March 11, 2026.

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