Review oscal mappings
Skill ethanolivertroy/compliance-trestle-skills/.cursor/skills/review-oscal-mappings
Agent-portable Compliance Trestle and OSCAL engineering toolkit: convert legacy SSPs to OSCAL, validate with Trestle and oscal-cli, FedRAMP Rev 5 and 20x KSI workflows. Claude Code plugin plus portable skills for Cursor, Codex, Gemini, and more.
npx -y skills add ethanolivertroy/compliance-trestle-skills --skill review-oscal-mappingsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Review source-to-OSCAL mappings, triage needs_review rows, and update the review queue before treating generated OSCAL as ready for stakeholders.
SKILL.md
1.5 KB, as published. Nobody here has run it
Review OSCAL Mappings
Human-in-the-loop review workflow for source traceability and mapping quality.
Read first
docs/OSCAL-REVIEW-WORKFLOW.mdadapters/generic-agent-package/prompts/review-oscal-mappings.mdplugins/document-transform/oscal-document-workbench/templates/review-queue.mdplugins/document-transform/oscal-document-workbench/templates/control-mapping-review.csv
Steps
- Load
source-map.csvand any generatedreports/review-queue.md. - For each
needs_reviewor unmapped row:- confirm the source text supports the OSCAL target;
- mark unsupported claims
needs_revieworreject; - identify missing evidence;
- preserve reviewer notes.
- Regenerate or update the review queue:
bash plugins/document-transform/oscal-document-workbench/scripts/build-review-queue.sh <workspace>/extracted/source-map.csv --output <workspace>/reports/review-queue.md
- Summarize counts of mapped,
needs_review, and unmapped items. - Block "ready for assessment" claims while unresolved review rows remain.
Reviewer decisions
Use explicit statuses in the traceability map:
mappedneeds_reviewunmappedreject
Do not silently rewrite uncertain source statements as implemented technical reality.