agentsclimarketplace

Import legacy ssp

Skill ethanolivertroy/compliance-trestle-skills/.cursor/skills/import-legacy-ssp

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.

Install
npx -y skills add ethanolivertroy/compliance-trestle-skills --skill import-legacy-ssp

Assembled 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

Import a legacy SSP, PDF, DOCX, or Markdown package into a traceable OSCAL Document Workbench workspace using extraction, source mapping, Trestle bootstrap, and validation.

SKILL.md

2.1 KB, as published. Nobody here has run it

Import Legacy SSP

Run the end-to-end legacy SSP import workflow for Cursor.

Before you start

Read:

  • AGENTS.md
  • agent-skills/oscal-document-engineering/SKILL.md
  • agent-skills/compliance-trestle-engineering/SKILL.md
  • plugins/document-transform/oscal-document-workbench/commands/ingest-ssp.md

Steps

  1. Confirm source files and the target workspace path, usually workspaces/<system>-ssp-import/.
  2. Copy source documents into input/ without modifying originals.
  3. Extract source text and section structure:
bash plugins/document-transform/oscal-document-workbench/scripts/extract-legacy-doc.sh <input> --output <workspace>/extracted
  1. Bootstrap or reuse a Compliance Trestle workspace:
bash plugins/document-transform/oscal-document-workbench/scripts/bootstrap-trestle-workspace.sh <workspace> [--profile <name>]
  1. Map extracted content to OSCAL SSP fields with source-map.csv traceability.
  2. Mark uncertain mappings as needs_review; do not invent compliance facts.
  3. 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
  1. 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
  1. Produce:
  • reports/import-summary.md
  • reports/validation-report.json
  • reports/unmapped-items.md
  • reports/review-queue.md

Synthetic example

bash examples/legacy-ssp-to-oscal/scripts/run-example.sh

Safety

  • Do not commit real customer SSPs or sensitive evidence.
  • Schema-valid OSCAL does not prove compliance effectiveness.
  • Require human review for all needs_review and unmapped rows before assessment use.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.