Validate OSCAL documents for schema non-conformances and structural integrity.
npx skills add https://github.com/euCann/OSCAL-GRC-SKILLS --skill oscal-validator
Please help me install this Agent Skill. Skill: oscal-validator Source: https://github.com/euCann/OSCAL-GRC-SKILLS/tree/main/skills/oscal-validator Command: npx skills add https://github.com/euCann/OSCAL-GRC-SKILLS --skill oscal-validator
Validate OSCAL documents for structural integrity and OSCAL-specific requirements, ensuring proper formatting before downstream processing.
Provide an OSCAL document to the validator to receive a structured validation report.
High-intent search queries and answers about installing and using this skill.
To validate an OSCAL document, provide it to the validator to check structural integrity and schema conformance against the NIST OSCAL model, receiving a report of errors, warnings, and info.
OSCAL cross-reference validation checks essential metadata, UUIDs, and cross-references to ensure data quality and detect structural integrity issues before downstream processing.
Yes, you can validate OSCAL component definitions and SSPs. The validator covers OSCAL catalogs, SSPs, and component definitions to detect schema non-conformances.
Your OSCAL file fails structural integrity checks because it contains schema non-conformances, missing metadata, or invalid cross-references that violate the NIST OSCAL model specifications.
You need to validate OSCAL catalogs when you want to identify structural issues early in your workflow, preventing downstream errors and ensuring proper formatting before processing.
euCannCreate reusable OSCAL component definitions with unique UUIDs and schema validation.
euCannValidate OSCAL documents for schema, UUID, and cross-reference compliance.
williamzujkowskiValidate OSCAL System Security Plan documents against schemas and profiles.
euCannValidate OSCAL SSPs against NIST 800-18 Rev 1 and FedRAMP baselines.
