review-oscal-mappings
Skill16 starsChanged 4 months agoApache-2.0View on GitHub
Review source-to-OSCAL mappings, triage needs_review rows, and update the review queue before treating generated OSCAL as ready for stakeholders.
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
- validate-oscal-packageSkill
- workspace-validateSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
make sure the source text supports the OSCAL target
- Distinctive: line 37
Use explicit statuses in the traceability map.
- Distinctive: line 54
Do not silently rewrite uncertain source statements as implemented technical reality.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
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:- make sure the source text supports the OSCAL target
- mark unsupported claims
needs_revieworreject - identify missing evidence
- keep reviewer notes
- Make 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.
Allowed source-map.csv statuses:
mappedneeds_reviewunmappedreject
Allowed reviewer decisions in the queue. Keep these separate from mapping status:
approveremaprejectneeds_more_evidencedefer
Do not silently rewrite uncertain source statements as implemented technical reality.
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.

