smoke-test

Generate chain-curl smoke tests for API endpoints with AI_ACCESS_KEY authentication.

2|1|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/inernoro/prd_agent --skill smoke-test-inernoro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/inernoro/prd_agent/tree/main/.claude/skills/smoke-test
Command: npx skills add https://github.com/inernoro/prd_agent --skill smoke-test-inernoro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of chain-curl smoke tests for API endpoints, enabling teams to quickly validate core workflows with minimal setup.

Core Features & Use Cases

  • Generates chained curl commands that pass resource IDs between steps
  • Authenticates using AI_ACCESS_KEY and configurable hosts
  • Supports three execution modes (local, MAP direct, and CDS container-exec fallback) for reliable remote testing

Quick Start

Tell the skill which API module to smoke-test and it will generate a complete chain-curl script ready to run.

Frequently Asked Questions about smoke-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate automated smoke tests for API endpoints?▼

Chain-curl smoke tests automate end-to-end API validation by generating sequential curl commands that pass resource IDs between steps. This approach validates core CRUD workflows and backend service reliability with minimal manual configuration.

How do I pass authentication tokens automatically in API smoke tests?▼

You can handle API smoke test authentication automatically by configuring environment variables like AI_ACCESS_KEY. This enables zero-configuration authentication for your test scripts, allowing chained curl commands to authenticate seamlessly against configurable hosts without manual token entry.

Can I run end-to-end API smoke tests in different execution environments?▼

End-to-end API smoke tests can run across three execution modes: local, MAP direct, and container-exec CDS fallback. This environment-driven configuration ensures quick, repeatable testing and reliable remote validation across different deployment targets.

What is the best way to automate chained curl commands for CRUD workflows?▼

The best way to automate chained curl commands for CRUD workflows is to use a zero-configuration generator that links sequential API requests. It automatically passes dynamic resource IDs between steps, ensuring deterministic multi-step scripts for repeatable end-to-end testing.

Do I need to manually configure environment variables for API smoke testing?▼

You do not need to manually configure complex environment variables for API smoke testing if you use AI_ACCESS_KEY for zero-configuration authentication. The environment-driven setup handles configurable hosts automatically, delivering quick and repeatable test scripts.