Skip to content
Back to skills

Export Oscal

ASecurity

NIST OSCAL JSON export of compliance evidence from ArangoDB graph

  • 6 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 11, 2026
researchgobashtestingdatabasesecurity

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 11, 2026

npx -y skills add grahama1970/agent-skills --skill export-oscal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Export Oscal?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Export Oscal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/grahama1970-export-oscal/badge)](https://www.skillsdirectory.com/skills/grahama1970-export-oscal)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: export-oscal
description: NIST OSCAL JSON export of compliance evidence from ArangoDB graph
triggers:
  - "export oscal"
  - "oscal export"
  - "compliance export"
allowed-tools:
  - Bash
provides:
  - export-oscal
composes:
  - task-monitor
  - agentic-evals
disciplines:
  - compliance-security
---

# Export OSCAL

Export NIST OSCAL (Open Security Controls Assessment Language) JSON from compliance
evidence stored in the ArangoDB graph. Supports NIST 800-171 and CMMC Level 2
frameworks.

## Usage

### Export compliance evidence

```bash
./run.sh export --framework NIST-800-171
./run.sh export --framework CMMC-L2
```

### Dry run (no ArangoDB required)

```bash
./run.sh export --framework NIST-800-171 --dry-run
```

Generates a valid OSCAL assessment-results structure with example data. Useful for
testing downstream consumers without a running database.

### Validate an OSCAL file

```bash
./run.sh validate <file.json>
```

Checks that the JSON file contains required OSCAL assessment-results fields:
`uuid`, `metadata`, and `results`.

## Output

All output goes to stdout as formatted JSON. Redirect to a file as needed:

```bash
./run.sh export --framework NIST-800-171 > oscal-export.json
```

## OSCAL Structure

The exported JSON follows the OSCAL assessment-results model:

- `uuid` -- unique identifier for this export
- `metadata.title` -- framework name and export context
- `metadata.last-modified` -- ISO 8601 timestamp
- `metadata.version` -- export version
- `metadata.oscal-version` -- OSCAL specification version
- `results[]` -- array of assessment results, each mapping a control to evidence
  - `uuid` -- unique result identifier
  - `title` -- control identifier and name
  - `start` -- assessment timestamp
  - `findings[]` -- evidence entries from QRA and lessons collections

## Data Sources

Queries three ArangoDB collections in the `sparta` database:

| Collection | Purpose |
|------------|---------|
| `sparta_controls` | Control definitions and status |
| `sparta_qra` | QRA (Question-Response-Action) evidence entries |
| `lessons` | Lessons learned linked to controls |

Files in this skill

  • SKILL.md2.1 KB
  • fixtures/agentic_eval.json490 B
  • pyproject.toml114 B
  • run.sh7 KB
  • sanity.sh937 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.