home / skills / basher83 / agent-auditor / test-blocked-fixture

test-blocked-fixture skill

safe

This skill helps identify and report BLOCKED statuses in skills-auditor tests by flagging B5 and W2 violations for regression testing.

npx playbooks add skill basher83/agent-auditor --skill test-blocked-fixture

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

827 B

---
name: test-blocked-fixture
description: >
  This is a test fixture with intentional violations for regression testing.
  It contains <angle brackets> which trigger B5, and has an unexpected
  frontmatter property which triggers W2.
extra_property: this-is-not-allowed
---

# Test Blocked Fixture

This skill exists solely for testing the skill-auditor. It should always
report as BLOCKED with the following violations:

## Expected Violations

- **B5**: Description contains angle brackets (< or >)
- **W2**: Unexpected frontmatter property: extra_property

## Usage

```bash
# Should exit 1 with BLOCKED status
uv run skill-auditor skills/test-blocked-fixture

# Hybrid mode should show structured blockers
uv run skill-auditor --hybrid skills/test-blocked-fixture
```

Do not fix these violations - they are intentional.

Overview

This skill is a dedicated test fixture designed to trigger specific validation rules. It intentionally contains prohibited patterns and unexpected metadata so audit tools report a BLOCKED status. Use it to verify that regressions or changes in auditing logic correctly detect and report the expected violations.

How this skill works

The fixture includes angle brackets in the description to trigger a B5 violation and an extra frontmatter property to trigger a W2 warning. Audit tools inspect the description and frontmatter metadata, then surface structured errors and blocker statuses when these issues are found. It is not meant to be corrected; its contents are static to ensure repeatable test outcomes.

When to use it

Validate that an auditor correctly identifies B5 (angle brackets in description).
Confirm detection of unexpected frontmatter properties (W2).
Test CI gating behavior when a skill is BLOCKED by policy violations.
Exercise hybrid or structured reporting modes that output detailed blocker data.
Regression test changes to parsing, frontmatter handling, or rule sets.

Best practices

Keep the fixture immutable so tests remain deterministic.
Use this skill only in test or staging environments, never production catalogs.
Run auditors in both standard and hybrid modes to validate output formats.
Combine with unit tests that assert specific error codes and messages.
Isolate test runs to avoid side effects on other audit data.

Example use cases

Automated CI job that ensures auditors reject blocked skills by exiting with non-zero status.
Hybrid reporting validation where structured blocker data must match expected fields.
Regression suites that verify no silent changes occur to rule detection for B5 or W2.
Developer testing when updating parsing logic to ensure frontmatter validation remains strict.

FAQ

Should I fix the violations in this fixture?

No. The violations are intentional and the fixture must remain unchanged to serve as a reliable test asset.

What outputs should an auditor produce when checking this skill?

Auditors should report a BLOCKED status, include a B5 violation for angle brackets in the description, and a W2 warning for the unexpected frontmatter property.