validate-oscal-package
Skill16 starsChanged 3 months agoApache-2.0View on GitHub
Validate an OSCAL package or Compliance Trestle workspace and produce a validation report, failing loudly when required tools are missing.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/compliance-trestle.mdcCursor rule
- .cursor/rules/oscal-json-edit.mdcCursor rule
- .cursor/rules/oscal-workspace-guardrails.mdcCursor rule
- import-legacy-sspSkill
- review-oscal-mappingsSkill
- workspace-validateSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
Do not claim validation passed if Trestle or OSCAL CLI was unavailable unless the user accepted partial validation.
- Very specific: line 43
If the user recently ran trestle assemble, trestle import, trestle merge, trestle create, or trestle split, recommend targeted validation …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Validate OSCAL Package
Validate an OSCAL package or Trestle workspace from Cursor.
Read first
plugins/document-transform/oscal-document-workbench/commands/validate-oscal-package.mdagent-skills/oscal-document-engineering/references/oscal-validation.mdcommands/workspace/validate.md
Run
bash plugins/document-transform/oscal-document-workbench/scripts/validate-oscal-package.sh <path> --output <workspace>/reports/validation-report.jsonFor a Trestle workspace without the workbench wrapper:
trestle validate -aOr use the repository helper:
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:
trestle validate -t <type> -n <name>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

