Compliance trestle engineering
Skill ethanolivertroy/compliance-trestle-skills/agent-skills/compliance-trestle-engineering
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 compliance-trestle-engineeringAssembled 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
Use Compliance Trestle to manage OSCAL catalogs, profiles, component definitions, SSPs, markdown assembly, validation, and source-traceable updates from legacy compliance documents.
SKILL.md
3.0 KB, as published. Nobody here has run it
Compliance Trestle Engineering
Use this skill when an agent needs to operate a Compliance Trestle workspace, import or validate OSCAL models, assemble markdown, regenerate OSCAL, or turn legacy SSP content into a traceable Trestle-managed workflow.
Non-negotiable guardrails
- Preserve source traceability for every generated OSCAL field that came from a legacy PDF, DOCX, Markdown, TXT file, interview note, spreadsheet, ticket, or evidence package.
- Never invent control mappings. If the source does not clearly support a mapping, set status to
needs_reviewand explain the uncertainty. - Schema-valid OSCAL is not a statement of compliance effectiveness.
- Keep reviewer-owned decisions in review queues or traceability maps, not hidden in generated prose.
- Prefer small, reversible Trestle operations over large opaque rewrites.
Standard workflow
- Initialize or inspect the workspace.
trestle inittrestle versionfind . -maxdepth 3 -type d | sort
- Import or create OSCAL artifacts.
- catalogs under
catalogs/ - profiles under
profiles/ - component definitions under
component-definitions/ - SSPs under
system-security-plans/
- catalogs under
- Resolve the applicable profile before writing control implementations.
- Author or update markdown with source references.
- Assemble markdown back into OSCAL.
- Validate with Compliance Trestle and any available OSCAL validator.
- Generate review outputs for
needs_review, unmapped, or low-confidence items.
Typical commands
Use the wrapper when you want consistent reports:
bash scripts/trestle-workflow.sh init workspaces/acme/trestle-workspace
bash scripts/trestle-workflow.sh validate workspaces/acme/trestle-workspace
bash scripts/trestle-workflow.sh assemble workspaces/acme/trestle-workspace system-security-plans/acme-ssp
bash scripts/trestle-workflow.sh status workspaces/acme/trestle-workspace
Use raw Trestle when the reviewer needs exact CLI control:
trestle init
trestle validate -a
trestle author ssp-generate -n acme-ssp -p profiles/fedramp-moderate/profile.json
trestle author ssp-assemble -m markdown/system-security-plans/acme-ssp -o system-security-plans/acme-ssp.json
Output expectations
Every Trestle-backed document import should leave behind:
source-map.csvwith source IDs, target OSCAL fields, status, and notes.reports/import-summary.mdexplaining source counts and known gaps.reports/review-queue.mdforneeds_reviewand unmapped items.- validation output from
trestle validateor a documented skipped/missing-tool status.
See:
references/trestle-workspace-lifecycle.mdreferences/trestle-oscal-operations.mdtemplates/trestle-workflow-checklist.mdtemplates/trestle-command-log.md