skill-tester

Record observable test runs and write a Markdown debug report.

2|1|Updated May 7, 2026
One-click install
npx skills add https://github.com/shenmuxing/EtaSkill --skill skill-tester-shenmuxing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-tester
Source: https://github.com/shenmuxing/EtaSkill/tree/main/skill-examples/skill-tester
Command: npx skills add https://github.com/shenmuxing/EtaSkill --skill skill-tester-shenmuxing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you inspect how another Codex skill behaves on a real request by producing a local debug report of the run, including visible actions, files read, commands executed, and any errors or artifacts.

Core Features & Use Cases

  • Observable Skill Testing: Captures the steps taken during a concrete skill run so you can understand what happened.
  • Debug Reporting: Writes a non-overwriting Markdown report that records inputs, outputs, and decisions for troubleshooting.
  • Use Case: Use it when a skill seems unclear or unexpected and you want a reproducible record of its behavior without turning the process into a formal pass/fail evaluation.

Quick Start

Use the skill-tester skill to test the target skill on my request and write a local debug report.

Frequently Asked Questions about skill-tester

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

FAQPage Schema
How do I debug a Codex skill run and record what happened?

To debug a Codex skill run, you can use a skill tester to capture observable actions like files read and commands run, then write a local Markdown debug report documenting the behavior for troubleshooting.

What is a dry run for Codex skills and when do I need one?

A dry run for Codex skills is a behavior inspection process that captures steps taken during a concrete skill run. You need it when a skill seems unclear or produces unexpected results and you want a reproducible record.

How do I generate a Markdown report of files read and commands executed by a skill?

You generate a Markdown debug report by running a skill tester against a target skill on a specific request, which records inputs, outputs, commands executed, changed artifacts, and errors into a non-overwriting local file.

Can I compare a Codex skill's behavior against a specific user request?

Yes, you can compare a Codex skill's behavior against a concrete user request by running an observable test that documents the skill's decisions, visible actions, and changed artifacts in a local debug report.

Does the skill testing report overwrite previous debug runs?

No, the skill testing report does not overwrite previous runs. It writes a non-overwriting Markdown file to ensure you retain a reproducible record of every debug session and behavior inspection.

What should I do if a Codex skill behaves unexpectedly on my request?

If a Codex skill behaves unexpectedly, run an observable skill test on your request to capture visible actions, errors, and changed artifacts, then review the generated Markdown debug report to understand the behavior.