# Test Build Error Visibility

Build systems often hide dependency failures or surface them without useful context. This skill provides a small failing fixture for checking how Claude, Codex, and Claude Code expose build step errors.

## Install

```bash
npx skillstore add enactprotocol/test-build-error
```

## Metadata

- Status: approved
- Slug: enactprotocol-test-build-error
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: cd6fe0b09093ca47e22e1524a0564a45882e7cd72bcffe55757bd6d8829ebc5f
- Author: EnactProtocol
- GitHub username: EnactProtocol
- License: MIT
- Repository: https://github.com/EnactProtocol/enact/tree/main/test-tools/build-error
- Ref: 30c73eac2afe762f6aa9c4553158769369d47351
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/enactprotocol-test-build-error
- Manifest: https://skillstore.pages.dev/api/skills/enactprotocol-test-build-error/manifest

## Capabilities

- Defines a minimal skill named test-build-error.
- Uses a Node 20 Alpine base image for build testing.
- Runs a build step that attempts to install a nonexistent npm package.
- Provides a simple command that would echo a success message after build completion.
- Documents that the purpose is testing build step error visibility.

## Use Cases

- Validate Marketplace Build Logs: Check whether a skill marketplace clearly displays failed dependency installation output.
- Test CI Failure Reporting: Use a predictable build failure to verify that CI jobs preserve useful error details.
- Confirm Agent Installation Feedback: Observe how Claude, Codex, or Claude Code reports a failed skill build during installation.

## Prompt Templates

### Run The Fixture

```
Install this skill and report the exact build error shown by the installer.
```

### Compare Build Logs

```
Run the skill build locally and in CI, then summarize differences in the failure output.
```

### Audit Error Clarity

```
Evaluate whether the build failure output identifies the missing package, failing step, and recovery path.
```

### Design A Failure Test

```
Use this fixture as a baseline and propose a checklist for testing skill build error reporting.
```

## Limitations

- It is a test fixture, not an end-user automation skill.
- The build step is intended to fail because the package name is nonexistent.
- It does not diagnose or repair build failures automatically.
- It does not provide runtime application behavior beyond a simple echo command.

## Best Practices

- Use this fixture only in test environments where a failed build is expected.
- Record the full installer output so missing build details are easy to compare.
- Pair this fixture with a passing skill to confirm both success and failure paths.

## Anti Patterns

- Do not publish it as a functional user-facing productivity skill.
- Do not treat the failed build as an unexpected runtime defect.
- Do not use it to validate production dependency availability.

## Security Audit

- Audited at: 2026-07-05T14:37:47.407\+00:00
- Summary: Static analysis reported no suspicious patterns, no risk factors, and no static findings requiring verdicts. Context review of SKILL.md found a test fixture for build failure visibility, with no evidence of prompt injection, data exfiltration intent, or unsafe user instructions.

## Stats

- Views: 135
- Downloads: 9
- Favorites: 0
- Popularity score: 0