import-legacy-ssp
Skill16 starsChanged 4 months agoApache-2.0View on GitHub
Import a legacy SSP, PDF, DOCX, or Markdown package into a traceable OSCAL Document Workbench workspace using extraction, source mapping, Trestle bootstrap, and validation.
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
- review-oscal-mappingsSkill
- validate-oscal-packageSkill
- workspace-validateSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Run the full legacy SSP import workflow for Cursor.
- Very specific: line 26
Make sure you know the source files and the target workspace path.
- Distinctive: line 28
Do not change the original files.
- Very specific: line 56
Keep unmatched sections needs_review.
- Distinctive: line 93
Do not commit real customer SSPs or sensitive evidence.
≈ “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
Import Legacy SSP
Run the full legacy SSP import workflow for Cursor.
Before you start
Read:
AGENTS.mdagent-skills/oscal-document-engineering/SKILL.mdagent-skills/compliance-trestle-engineering/SKILL.mdplugins/document-transform/oscal-document-workbench/commands/ingest-ssp.md
This repository is an OSCAL and Compliance Trestle toolkit. FedRAMP Rev 5 heading maps and 20x KSI coverage are optional adapters. They are not the default product claim.
Steps
- Make sure you know the source files and the target workspace path. Usual path:
workspaces/<system>-ssp-import/. - Copy source documents into
input/. - Do not change the original files.
- Extract source text and section structure:
bash plugins/document-transform/oscal-document-workbench/scripts/extract-legacy-doc.sh <input> --output <workspace>/extracted- Bootstrap or reuse a Compliance Trestle workspace:
bash plugins/document-transform/oscal-document-workbench/scripts/bootstrap-trestle-workspace.sh <workspace> [--profile <name>]- Optionally import a real NIST or FedRAMP baseline when the source is a FedRAMP-style SSP:
bash plugins/document-transform/oscal-document-workbench/scripts/fetch-oscal-baseline.sh <workspace>/trestle-workspace --baseline moderate- Draft a schema-valid SSP from extracted sections when Trestle is available:
bash plugins/document-transform/oscal-document-workbench/scripts/draft-ssp-from-extraction.sh <workspace> [--baseline-profile fedramp-rev5-moderate] [--overwrite]Omit --baseline-profile to make offline stub catalog and profile models.
Replace stubs before authorization use.
For non-FedRAMP sources, do not treat the FedRAMP heading map as authoritative.
Keep unmatched sections needs_review.
- Map remaining content in
source-map.csv. Mark uncertain mappings asneeds_review. Do not invent compliance facts. - Build 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- Validate the package or document missing tools explicitly:
bash plugins/document-transform/oscal-document-workbench/scripts/validate-oscal-package.sh <workspace>/trestle-workspace --output <workspace>/reports/validation-report.json- Optionally report FedRAMP 20x KSI documentation coverage:
bash plugins/document-transform/oscal-document-workbench/scripts/fetch-fedramp-2026-rules.sh
bash plugins/document-transform/oscal-document-workbench/scripts/ksi-coverage-report.sh <ssp.json> --output <workspace>/reports/ksi-coverage.md- Make:
reports/import-summary.mdreports/validation-report.jsonreports/unmapped-items.mdreports/review-queue.md
Synthetic example
bash examples/legacy-ssp-to-oscal/scripts/run-example.shSafety
- Do not commit real customer SSPs or sensitive evidence.
- Schema-valid OSCAL does not prove compliance effectiveness.
- Require human review for all
needs_reviewand unmapped rows before assessment use.
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.

