# U Worker Compliance

> Static analysis validator for worker and orchestrator .md protocol compliance (rules W01–W06 — terminal events, canonical phase values, register_worker arguments, emit.py skill declaration). Run scripts/check_worker.py on .claude/agents/**/*.md before promoting to dist/; enforced in CI by tests/test_worker_compliance_gate.py, which fails the suite on any W01–W06 violation. Not user-invocable — re…

- **Type:** Skill
- **Install:** `agentstack add skill-zig999-siegard-code-u-worker-compliance`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [zig999](https://agentstack.voostack.com/s/zig999)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [zig999](https://github.com/zig999)
- **Source:** https://github.com/zig999/siegard-code/tree/main/dist/.claude/skills/u-worker-compliance

## Install

```sh
agentstack add skill-zig999-siegard-code-u-worker-compliance
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# SKILL: Worker Compliance Validator

## Purpose

Static analysis tool that validates worker agent `.md` files for protocol compliance before promotion to `dist/`. Eliminates the manual review gap that causes repeated critical issues on every worker audit cycle.

---

## When to Use

- Before promoting any worker or orchestrator to `dist/`
- When a new worker is created or an existing one is modified
- As a gate in the review phase — run `check_worker.py` on every `.claude/agents/**/*.md`

---

## What It Checks

### Rule W01 — Terminal event: task_completed

Every worker must contain a `task_completed` emit block with the required schema fields.

**Required fields in `--data`:** `phase`, `artifacts`

**Detection:** grep for `--kind completed` followed by `--data` containing `"phase"` and `"artifacts"`.

**Violation:** worker emits completed but omits `phase` or `artifacts`.

---

### Rule W02 — Terminal event: task_failed

Every worker must contain a `task_failed` emit block with the required schema fields.

**Required fields in `--data`:** `phase`, `reason`, `retryable`

**Detection:** grep for `--kind failed` followed by `--data` containing `"phase"`, `"reason"`, and `"retryable"`.

**Violation:** worker emits failed but omits any of the three required fields.

---

### Rule W03 — No terminal event

Worker contains no `emit.py` call with `--kind completed` or `--kind failed`.

**Severity:** CRITICAL — on_subagent_stop.py will synthesize task_failed for every run, including successes.

---

### Rule W04 — Non-canonical phase value

Worker hardcodes `"phase":"default"` in any emit call.

**Valid values:** any string except `"default"` (which signals missing implementation). Canonical values: `sdd`, `dev`, `review`, `test`.

**Detection:** grep for `"phase":"default"` or `"phase": "default"` in any emit.py call.

---

### Rule W05 — register_worker missing phase argument

Orchestrator file calls `register_worker(...)` without `phase=` keyword argument.

**Detection:** grep for `register_worker(` lines that do not contain `phase=`.

**Applies to:** orchestrator files only (filename starts with `orchestrator`).

**Violation:** on_subagent_stop.py falls back to full log replay to discover phase — unnecessary cost.

---

### Rule W06 — emit.py not in skills frontmatter

Worker YAML frontmatter `skills:` list does not include `orch-report`.

**Detection:** parse frontmatter block; check `skills` list for `orch-report` entry.

**Violation:** emit.py may not be available in the worker's context.

---

## Output Format

```yaml
file: 
status: pass | fail
violations:
  - rule: W03
    severity: critical
    detail: "No --kind completed or --kind failed emit.py call found"
  - rule: W04
    severity: error
    detail: 'Hardcoded "phase":"default" in emit call at line 55'
```

Exit code: `0` = all pass, `1` = any violation found.

---

## Usage

### Validate a single worker

```bash
python3 .claude/skills/u-worker-compliance/scripts/check_worker.py \
  --file .claude/agents/dev/u-be-developer.md
```

### Validate all workers in a directory

```bash
python3 .claude/skills/u-worker-compliance/scripts/check_worker.py \
  --dir .claude/agents/
```

### Validate and emit structured JSON report

```bash
python3 .claude/skills/u-worker-compliance/scripts/check_worker.py \
  --dir .claude/agents/ \
  --format json > compliance-report.json
```

---

## Integration Points

- Run before any `git commit` that touches `.claude/agents/`
- Can be wired as a Claude Code hook: `UserPromptSubmit` → run on changed `.md` files
- Orchestrator can call it as a pre-promotion gate before `phase_transitioned`

---

## Limitations

- Static analysis only — does not execute workers or simulate orchestration
- Cannot verify that `task_id` and `attempt` are correctly interpolated at runtime
- Does not validate the semantic correctness of `artifacts` paths

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [zig999](https://github.com/zig999)
- **Source:** [zig999/siegard-code](https://github.com/zig999/siegard-code)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-zig999-siegard-code-u-worker-compliance
- Seller: https://agentstack.voostack.com/s/zig999
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.