How do I install the Oscal Document Workbench Expert skill?

Run npx skillmds@latest add oscal-compass-lab/oscal-document-workbench-expert in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Oscal Document Workbench Expert safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Oscal Document Workbench Expert?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Oscal Document Workbench Expert free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Oscal Document Workbench Expert?

oscal-compass-lab (@oscal-compass-lab) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Oscal Document Workbench Expert by oscal-compass-lab

Name: Oscal Document Workbench Expert
Author: oscal-compass-lab

File contents

oscal-document-workbench-expert

Use this skill when a user wants to modernize legacy compliance documents into OSCAL. Use it also to maintain an OSCAL SSP with agent help.

Required behavior

Keep original source files unchanged.
Make or update a source traceability map.
Map content into OSCAL only when there is source support or an explicit user assertion.
Mark uncertain content as needs_review.
Validate generated OSCAL structurally with available tools.
Make an import summary and an unmapped-items report.

Composition

Use agent-skills/oscal-document-engineering/SKILL.md for portable workflow details.
Use root Compliance Trestle commands and trestle validate for OSCAL validation and workspace checks.
Use official FedRAMP or OSCAL converters outside this repository when source material matches those specialized tools.
Use reviewed evidence packages to update control narratives and POA&M content.
Preserve source traceability.

Typical sequence

bash plugins/document-transform/oscal-document-workbench/scripts/extract-legacy-doc.sh input/old-ssp.docx --output workspaces/acme/extracted
bash plugins/document-transform/oscal-document-workbench/scripts/bootstrap-trestle-workspace.sh workspaces/acme --profile fedramp-moderate
bash plugins/document-transform/oscal-document-workbench/scripts/fetch-oscal-baseline.sh workspaces/acme/trestle-workspace --baseline moderate
bash plugins/document-transform/oscal-document-workbench/scripts/draft-ssp-from-extraction.sh workspaces/acme --baseline-profile fedramp-rev5-moderate --overwrite
bash plugins/document-transform/oscal-document-workbench/scripts/build-review-queue.sh workspaces/acme/extracted/source-map.csv --output workspaces/acme/reports/review-queue.md
bash plugins/document-transform/oscal-document-workbench/scripts/validate-oscal-package.sh workspaces/acme/trestle-workspace --output workspaces/acme/reports/validation-report.json

Skip baseline fetch and --baseline-profile for offline stub models. Skip the FedRAMP heading-map assumptions for non-FedRAMP sources.

Validation success means the package is structurally valid. It is not an attestation, authorization, or audit opinion.

---name: oscal-document-workbench-expertdescription: Convert legacy SSP/PDF/DOCX source material into traceable, validated OSCAL workspaces with Compliance Trestle and OSCAL CLI.---# oscal-document-workbench-expertUse this skill when a user wants to modernize legacy compliance documents into OSCAL.Use it also to maintain an OSCAL SSP with agent help.## Required behavior1. Keep original source files unchanged.2. Make or update a source traceability map.3. Map content into OSCAL only when there is source support or an explicit user assertion.4. Mark uncertain content as `needs_review`.5. Validate generated OSCAL structurally with available tools.6. Make an import summary and an unmapped-items report.## Composition- Use `agent-skills/oscal-document-engineering/SKILL.md` for portable workflow details.- Use root Compliance Trestle commands and `trestle validate` for OSCAL validation and workspace checks.- Use official FedRAMP or OSCAL converters outside this repository when source material matches those specialized tools.- Use reviewed evidence packages to update control narratives and POA&M content.- Preserve source traceability.## Typical sequence```bashbash plugins/document-transform/oscal-document-workbench/scripts/extract-legacy-doc.sh input/old-ssp.docx --output workspaces/acme/extractedbash plugins/document-transform/oscal-document-workbench/scripts/bootstrap-trestle-workspace.sh workspaces/acme --profile fedramp-moderatebash plugins/document-transform/oscal-document-workbench/scripts/fetch-oscal-baseline.sh workspaces/acme/trestle-workspace --baseline moderatebash plugins/document-transform/oscal-document-workbench/scripts/draft-ssp-from-extraction.sh workspaces/acme --baseline-profile fedramp-rev5-moderate --overwritebash plugins/document-transform/oscal-document-workbench/scripts/build-review-queue.sh workspaces/acme/extracted/source-map.csv --output workspaces/acme/reports/review-queue.mdbash plugins/document-transform/oscal-document-workbench/scripts/validate-oscal-package.sh workspaces/acme/trestle-workspace --output workspaces/acme/reports/validation-report.json```Skip baseline fetch and `--baseline-profile` for offline stub models.Skip the FedRAMP heading-map assumptions for non-FedRAMP sources.Validation success means the package is structurally valid.It is not an attestation, authorization, or audit opinion.

Frequently asked questions

Oscal Document Workbench Expert