export
/export
Export findings as SARIF 2.1.0 (GitHub code scanning), OSCAL Assessment Results or OCSF Compliance Finding events. Use for \"export SARIF\", \"OSCAL\", \"send findings to SIEM\".
- Author
- prathikcannotcode ↗
- Repository
- Vigil ↗
- Licence
- Apache-2.0
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Export findings as SARIF 2.1.0 (GitHub code scanning), OSCAL Assessment Results or OCSF Compliance Finding events. Use for \"export SARIF\", \"OSCAL\", \"send findings to SIEM\".
Triggers from the description
Original author description
Export findings as SARIF 2.1.0 (GitHub code scanning), OSCAL Assessment Results or OCSF Compliance Finding events. Use for \"export SARIF\", \"OSCAL\", \"send findings to SIEM\".
How it works
- Trigger
- Purpose
- Supported formats
- Severity mapping
- Commands
SKILL.md preview
--- name: export description: "Export findings as SARIF 2.1.0 (GitHub code scanning), OSCAL Assessment Results or OCSF Compliance Finding events. Use for \"export SARIF\", \"OSCAL\", \"send findings to SIEM\"." --- # Output Format Conversion (OSCAL, SARIF, OCSF) ## Trigger "export OSCAL", "export SARIF", "convert findings", "OSCAL output", "SARIF output", "OCSF output", "standard format" ## Purpose Convert Vigil findings and posture data into open standard formats for interoperability with other compliance tools, SIEMs, and reporting systems. Run the matching script; do not write these files by hand. Each export uses the company's latest report only. ## Supported formats ### SARIF 2.1.0 (Static Analysis Results Interchange Format) `npm run export:sarif -- --company <id> --output findings.sarif` For code-related findings (PII in code, missing encryption, dark patterns in UI). Findings with no `file` and findings that are `remediated` or `accepted` are left out, because code scanning has nowhere to display them or would show them as live alerts. The script names what it left out; tell the user. Maps to: - `result.ruleId` -> finding clause (e.g., "GDPR-Art-32-1-a") - `result.level` -> severity (critical/high -> error, medium -> warning, low -> note) - `result.message.text` -> finding issue and recommendation - `result.locations[].physicalLocation` -> file path and line number - `run.tool.driver.rules[]` -> regulatory clauses as rule definitions Use case: import into GitHub Code Scanning, VS Code SARIF Viewer, or any SARIF-compatible tool. ### OSCAL 1.1.2 (Open Security Controls Assessment Language) `npm run export:oscal -- --company <id> --output results.oscal.json` For control assessments and compliance posture. All findings, as an Assessment Results document. Maps to: - `result.findings[]` -> findings, with the clause as a `target-id` token and a `clause` prop - `result.observations[]` -> file evidence for findings that have a `file` - `reviewed-controls` -> include-all, because Vigil has no OSCAL control catalog Use case: import into GovReady or Compliance-as-Code pipelines. ### OCSF 1.3.0 (Open Cybersecurity Schema Framework) `npm run export:ocsf -- --company <id> --output findings.ocsf.jsonl` For security operations. All findings, one event per line. Maps to: - Compliance Finding (class 2003): - `finding_info.title` -> finding issue - `finding_info.uid` -> assessment and finding ID - `compliance.requirements[]` -> regulatory clauses - `severity_id` -> severity level - `status_id` -> open 1 (New), in progress or disputed 2 (In Progress), accepted 3 (Suppressed), remediated 4 (Resolved) - `remediation.desc` -> recommendation Use case: feed into SIEM/SOAR systems, integrate with security operations. ## Severity mapping | Vigil | SARIF level | OCSF severity_id | |---|---|---| | critical | error | 5 (Critical) | | high | error | 4 (High) | | medium | warning | 3 (Medium) | | low | note | 2 (Low) | ## Commands Invoke the skill directly, or describe the task in plain English and Claude picks it up. | Run | Action | |---|---| | `/export sarif` | Export code findings as SARIF 2.1.0 | | `/export oscal` | Export posture and findings as OSCAL | | `/export ocsf` | Export findings as OCSF | | `/export all` | Export all formats |
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · prathikcannotcode/Vigil | 90 | Apache-2.0 |
| chatcut-inc/agent-plugin | 100 | Apache-2.0 |
| chatcut-inc/agent-plugin | 100 | Apache-2.0 |
| zimoliao/scholaraio | 100 | MIT |
| stxrmik/antigravity-plus | 100 | MIT |
| d3uceY/SpriteWare | 100 | MIT |
| 0xsline/OpenChatCut | 100 | AGPL-3.0 |
| with-pebbly/aseprite-ai-artist | 100 | MIT |
| yha9806/academic-writing-toolkit | 100 | MIT |
Database snapshot: 13.11.2026 · package version 2ea0afcf13c8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95sarif-parsing
Parses and processes SARIF files from static analysis tools like CodeQL, Semgrep, or other scanners. Triggers on "parse sarif", "read scan results", "aggregate findings", "deduplicate alerts", or "process sarif output". Handles filtering, deduplication, format conversion, and… - 100sarif-parsing
Parses and processes SARIF files from static analysis tools like CodeQL, Semgrep, or other scanners. Triggers on "parse sarif", "read scan results", "aggregate findings", "deduplicate alerts", or "process sarif output". Handles filtering, deduplication, format conversion, and… - 100codeql
Comprehensive guide for setting up and configuring CodeQL code scanning via GitHub Actions workflows and the CodeQL CLI. This skill should be used when users need help with code scanning configuration, CodeQL workflow files, CodeQL CLI commands, SARIF output, security analysis… - 100trestle-assessment
Use this skill for OSCAL assessment plans and assessment results models in Compliance Trestle. Use it for assessment plans, assessment results, security assessments, SAP, SAR, assessment activities, findings, observations, or assessment-related OSCAL models. - 90sarif-parsing
Use when a user supplies existing SARIF to inspect, filter, aggregate, deduplicate, diff, convert, or gate findings. Not for running a scanner: use the relevant security-review skill. - 100report
This skill should be used when the user asks to "generate security report", "create appsec report", "export findings", "security summary", "findings report", "executive security summary", or "export to SARIF". Also triggers when the user wants a formatted overview of all…