gen-smoke

Verify sagaflow interpreter execution by writing report.md via write_artifact.

4|Updated Feb 23, 2026

Search Tags:#smoke testing #artifact writing #temporal workflow #sagaflow #generic interpreter #write_artifact

Ready to run

npx skills add https://github.com/npow/claude-skills --skill gen-smoke

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gen-smoke
Source: https://github.com/npow/claude-skills/tree/main/gen-smoke
Command: npx skills add https://github.com/npow/claude-skills --skill gen-smoke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that the sagaflow generic interpreter can complete a basic workflow and write the expected greeting artifact.

Core Features & Use Cases

Interpreter Smoke Test: Checks sagaflow availability before running the workflow.
Artifact Validation: Writes a personalized greeting to report.md through the write_artifact tool.
Use Case: Use it after configuring a sagaflow worker to confirm that the Temporal-backed interpreter can execute a skill and produce a report.

Quick Start

Use the gen-smoke skill with a name argument to write a personalized greeting to report.md.

Frequently Asked Questions about gen-smoke

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

FAQPage Schema

How do I run a smoke test on a sagaflow Temporal worker?▼

To smoke test a sagaflow Temporal worker, execute a basic artifact-writing workflow through the generic interpreter to verify it can successfully create report.md using the write_artifact tool.

What is sagaflow generic interpreter artifact writing?▼

Sagaflow generic interpreter artifact writing is the end-to-end process where a Temporal-backed worker executes a workflow and uses the write_artifact tool to create a report.md file.

Do I need a reachable sagaflow worker to test artifact writes?▼

Yes, a reachable sagaflow worker is required. The smoke test checks sagaflow availability before executing the workflow to ensure the Temporal-backed interpreter can successfully produce the report.md artifact.

How do I verify my sagaflow installation works end to end?▼

Verify a sagaflow installation by running an interpreter round-trip smoke test that executes a basic workflow and confirms the write_artifact tool successfully creates the expected report.md output file.

What are the limitations of sagaflow smoke testing for artifact validation?▼

Sagaflow smoke testing is limited to verifying basic workflow execution and writing a single report.md artifact; it does not test complex Temporal workflow logic or validate multiple artifact formats.