# Validate Oscal Package

> Validate an OSCAL package or Compliance Trestle workspace and produce a validation report, failing loudly when required tools are missing.

- Skill: `oscal-compass-lab/validate-oscal-package` (Agent Skill)
- Install (CLI): `npx skillmds@latest add oscal-compass-lab/validate-oscal-package`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oscal-compass-lab/validate-oscal-package/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: oscal-compass-lab (https://skillmd.com/u/oscal-compass-lab)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/oscal-compass-lab/validate-oscal-package

---


# Validate OSCAL Package

Validate an OSCAL package or Trestle workspace from Cursor.

## Read first

- `plugins/document-transform/oscal-document-workbench/commands/validate-oscal-package.md`
- `agent-skills/oscal-document-engineering/references/oscal-validation.md`
- `commands/workspace/validate.md`

## Run

```bash
bash plugins/document-transform/oscal-document-workbench/scripts/validate-oscal-package.sh <path> --output <workspace>/reports/validation-report.json
```

For a Trestle workspace without the workbench wrapper:

```bash
trestle validate -a
```

Or use the repository helper:

```bash
bash scripts/trestle-workflow.sh validate <workspace>
```

## Report requirements

- Record validator output or a documented skipped or missing-tool status.
- Do not claim validation passed if Trestle or OSCAL CLI was unavailable unless the user accepted partial validation.
- Distinguish structural validation from compliance effectiveness or authorization.

## After assemble, import, merge, create, or split

If the user recently ran `trestle assemble`, `trestle import`, `trestle merge`, `trestle create`, or `trestle split`, recommend targeted validation such as:

```bash
trestle validate -t <type> -n <name>
```