Skills test-failing-test
📦

test-failing-test

v1.0.0 Content revision r1 High Risk

Validate Failing Tool Output

Developers need predictable failure output when testing agent tool handling. This skill prints stdout, stderr, and a simulated stack trace before exiting with an error.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "test-failing-test" from https://skillstore.io/skills/enactprotocol-test-failing-test.md and its manifest at https://skillstore.io/api/skills/enactprotocol-test-failing-test/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/enactprotocol-test-failing-test.md Signed manifest GET /api/skills/enactprotocol-test-failing-test/manifest Signed lockfile GET /api/skills/enactprotocol-test-failing-test/lockfile

Test it

Using "test-failing-test". Run the tool with the default message.

Expected outcome:

The run starts, prints the default message, reports stderr output, shows a simulated failure, and ends with a nonzero exit.

Using "test-failing-test". Run the tool with the message: Pipeline check.

Expected outcome:

The output includes the custom message, standard output text, error output text, and a stack trace for the simulated failure.

Using "test-failing-test". Separate the visible stdout and stderr content.

Expected outcome:

The response identifies the normal progress lines separately from the error marker, stderr text, and simulated stack trace.

Security Audit

High Risk
v4 • 7/6/2026 Open versioned report

Static analysis reported no findings, and the JavaScript file only prints output, creates a simulated error, and exits. Manual review found one semantic concern: the skill metadata places user input inside a shell-style command template.

2
Files scanned
40
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

High
SKILL.md:6
Unsanitized Command Argument Interpolation
SKILL.md embeds the message input directly in a shell-style command string. If the runner substitutes input before shell execution, quote characters could alter the command.
The command template includes user-controlled input on the command line. Exact exploitability depends on runner escaping, which is not visible in this skill.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/enactprotocol-test-failing-test/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/enactprotocol-test-failing-test/security.svg)](https://skillstore.io/skills/enactprotocol-test-failing-test?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/enactprotocol-test-failing-test?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/enactprotocol-test-failing-test/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/enactprotocol-test-failing-test.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

EnactProtocol. (2026). test-failing-test security audit report (audit version 4) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/enactprotocol-test-failing-test/audits/4

BibTeX citation

@techreport{enactprotocol-enactprotocol-test-failing-test-2026, author = {EnactProtocol}, title = {test-failing-test security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/enactprotocol-test-failing-test/audits/4}, note = {Author version 1.0.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "test-failing-test security audit report (audit version 4)" version: "1.0.0" type: report authors: - name: "EnactProtocol" date-released: "2026-07-06" url: "https://skillstore.io/skills/enactprotocol-test-failing-test/audits/4" identifiers: - type: other value: "skillstore:enactprotocol-test-failing-test:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
100
Maintainability
85
Content
69
Community
83
Spec Compliance

What You Can Build

Agent Error Handling Checks

Verify that Claude, Codex, or Claude Code displays tool stdout, stderr, and stack traces clearly.

Pipeline Failure Visibility

Run a predictable failing command to confirm logs and nonzero exits appear in automation.

Support Reproduction

Generate consistent failure output when documenting how an agent environment reports tool errors.

Try These Prompts

Run Default Failure 
Run the failing test tool with its default message and summarize the visible stdout and stderr.
Use Custom Message 
Run the failing test tool with the message: Release check failure. Tell me which lines appear before the stack trace.
Compare Output Channels 
Run the tool and separate the stdout lines from the stderr lines in your response.
Audit Failure Handling 
Run the tool with a unique trace label, then explain whether the environment preserved the label, stack trace, and failed exit.

Best Practices

  • Use short, non-sensitive messages because the message is printed to logs.
  • Run it only in test environments where a nonzero exit is expected.
  • Review stdout, stderr, and exit status separately when validating agent behavior.

Avoid

  • Do not use it as a real health check because it always fails.
  • Do not pass secrets or personal data in the message value.
  • Do not rely on it to validate application test suites or business logic.

Frequently Asked Questions

What does this skill do?
It runs a Node script that prints stdout, prints stderr, shows a simulated stack trace, and exits with failure.
Why does it always fail?
The failure is intentional. It helps users confirm that agent environments expose failed tool output clearly.
Can I provide a custom message?
Yes. The skill accepts a message value and prints it before the simulated error output.
Does it test my application code?
No. It only tests failure visibility for this controlled command.
Should I include secrets in the message?
No. The message is printed to logs and should not contain secrets or personal data.
Which tools can use this skill?
The report lists support for Claude, Codex, and Claude Code.

Developer Details

License

MIT

Author version

v1.0.0

Skillstore revision

r1

Repository

https://github.com/EnactProtocol/enact/tree/main/test-tools/failing-test

Ref

a06681402992ceae98ba04d54cfd4ab004862696

Maintenance freshness

7/18/2026

Usage

4 downloads · 150 views

File structure

📄 script.js

📄 SKILL.md