cui-phase1-language

Define permitted and prohibited CUI labeling phrases under targeted SELinux policy.

Updated Dec 4, 2025

Search Tags:#documentation #language #enforcement #policy #cui #phase1

Ready to run

npx skills add https://github.com/jamieadams-nerd/umrs-project --skill cui-phase1-language

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cui-phase1-language
Source: https://github.com/jamieadams-nerd/umrs-project/tree/main/.claude/skills/cui-phase1-language
Command: npx skills add https://github.com/jamieadams-nerd/umrs-project --skill cui-phase1-language

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides precise guidance on what can be stated about UMRS CUI handling under targeted SELinux policy, helping writers avoid misrepresentations.

Core Features & Use Cases

Permitted Language: Defines phrases that describe labeling and custody without enforcement claims.
Prohibited Language: Flags language that implies enforcement or mandatory access control in Phase 1.
Use Case: Ideal for documentation, policy briefs, and training materials describing Phase 1 CUI language constraints.

Quick Start

Summarize the allowed and prohibited language for Phase 1 CUI descriptions to guide your draft documentation.

Frequently Asked Questions about cui-phase1-language

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What language is permitted when documenting CUI Phase 1 under SELinux policy?▼

Permitted CUI Phase 1 language includes phrases that describe labeling and custody without making enforcement claims. Writers should use terminology that accurately reflects the targeted SELinux policy state without implying mandatory access control.

How do I avoid enforcement claims in Phase 1 CUI documentation?▼

To avoid enforcement claims in Phase 1 CUI documentation, you must exclude language that implies mandatory access control. The Skill flags prohibited phrases and guides you toward safe descriptions of UMRS CUI handling and custody.

What phrases are prohibited in targeted SELinux policy briefs?▼

Prohibited phrases in targeted SELinux policy briefs include any language implying mandatory access control or enforcement claims for Phase 1. The Skill identifies these misrepresentations to ensure documentation remains technically accurate.

Can I use this Skill for CUI training materials?▼

Yes, this Skill is ideal for CUI training materials, policy briefs, and technical documentation. It defines permitted and prohibited language to guide safe, accurate communication regarding Phase 1 CUI constraints.

Why does Phase 1 CUI language need to avoid enforcement claims?▼

Phase 1 CUI language must avoid enforcement claims because the underlying targeted SELinux policy does not enforce mandatory access control yet. Documenting enforcement inaccurately misrepresents UMRS CUI handling capabilities.

Does this Skill define permitted versus prohibited CUI language?▼

Yes, the Skill explicitly defines permitted versus prohibited language for Phase 1 CUI descriptions. It provides precise guidance to summarize allowed phrases and flag prohibited ones for your draft documentation.