How do I install the Cui Marker skill?

Run npx skillmds add majiayu000/cui-marker in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cui Marker safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cui Marker?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cui Marker free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cui Marker?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cui Marker by majiayu000 — Agent Skill

Name: Cui Marker
Rating: 4.2 (5 reviews)
Author: majiayu000

Cui Marker

Detect, classify, and mark Controlled Unclassified Information (CUI) per 32 CFR Part 2002. Scans documents and ArangoDB collections for CUI indicators, applies proper markings, and tracks CUI flow through the system.

majiayu000 d572e9a 2 files · 3.2 KB Updated Sep 9, 2026 567 repo stars

File contents

CUI Marker

Detect, classify, and mark Controlled Unclassified Information per 32 CFR Part 2002. Without this skill, CUI documents enter uncontrolled ArangoDB collections with no marking, no distribution controls, and no audit trail — a compliance failure.

Commands

Command	Description
`./run.sh scan <path>`	Scan file/directory for CUI indicators
`./run.sh scan --collection <name>`	Scan ArangoDB collection for unmarked CUI
`./run.sh mark <doc_id> --category <cat>`	Apply CUI marking to document
`./run.sh mark <doc_id> --auto`	Auto-detect and apply appropriate marking
`./run.sh verify <doc_id>`	Verify document has proper CUI markings
`./run.sh categories`	List CUI categories and subcategories
`./run.sh report`	Generate CUI inventory report
`./run.sh flow <doc_id>`	Trace CUI flow through system
`./run.sh audit`	Audit all collections for unmarked CUI

CUI Categories (Relevant to DIB)

Category	Subcategory	Indicators
CTI	Controlled Technical Information	Engineering specs, test data, drawings
EXPT	Export Controlled	ITAR/EAR controlled data
PROPIN	Proprietary Business	Contractor proprietary, trade secrets
PRVCY	Privacy	PII, PHI
PROCURE	Procurement & Acquisition	Source selection, bid/proposal
INTEL	Intelligence	Threat data, assessments
INFOSEC	Information Security	Vulnerability data, pen test results

CUI Marking Format (per NARA CUI Registry)

CUI//SP-CTI
CUI//SP-EXPT
CUI//REL TO USA, AUS, GBR
CUI//NOFORN

Documents receive:

Banner marking — top/bottom of each page
Portion marking — individual paragraphs containing CUI
Distribution statement — who can receive
Destruction notice — how to dispose

Detection Patterns

The scanner uses regex + LLM classification for:

Technical data indicators (specifications, test procedures, drawings)
Export control markers (ITAR, EAR, USML categories)
PII patterns (SSN, DoD ID, clearance levels)
Procurement language (source selection, FOUO markers)
Legacy markings (FOUO, SBU, LES) that need CUI conversion

---name: cui-markerdescription: Detect, classify, and mark Controlled Unclassified Information (CUI) per 32 CFR Part 2002. Scans documents and ArangoDB collections for CUI indicators, applies proper markings, and tracks CUI flow through the system.--- # CUI Marker Detect, classify, and mark Controlled Unclassified Information per 32 CFR Part 2002. Without this skill, CUI documents enter uncontrolled ArangoDB collections with no marking, no distribution controls, and no audit trail — a compliance failure. ## Commands | Command | Description | |---------|-------------| | `./run.sh scan <path>` | Scan file/directory for CUI indicators | | `./run.sh scan --collection <name>` | Scan ArangoDB collection for unmarked CUI | | `./run.sh mark <doc_id> --category <cat>` | Apply CUI marking to document | | `./run.sh mark <doc_id> --auto` | Auto-detect and apply appropriate marking | | `./run.sh verify <doc_id>` | Verify document has proper CUI markings | | `./run.sh categories` | List CUI categories and subcategories | | `./run.sh report` | Generate CUI inventory report | | `./run.sh flow <doc_id>` | Trace CUI flow through system | | `./run.sh audit` | Audit all collections for unmarked CUI | ## CUI Categories (Relevant to DIB) | Category | Subcategory | Indicators | |----------|-------------|------------| | CTI | Controlled Technical Information | Engineering specs, test data, drawings | | EXPT | Export Controlled | ITAR/EAR controlled data | | PROPIN | Proprietary Business | Contractor proprietary, trade secrets | | PRVCY | Privacy | PII, PHI | | PROCURE | Procurement & Acquisition | Source selection, bid/proposal | | INTEL | Intelligence | Threat data, assessments | | INFOSEC | Information Security | Vulnerability data, pen test results | ## CUI Marking Format (per NARA CUI Registry) ``` CUI//SP-CTI CUI//SP-EXPT CUI//REL TO USA, AUS, GBR CUI//NOFORN ``` Documents receive: 1. **Banner marking** — top/bottom of each page 2. **Portion marking** — individual paragraphs containing CUI 3. **Distribution statement** — who can receive 4. **Destruction notice** — how to dispose ## Detection Patterns The scanner uses regex + LLM classification for: - Technical data indicators (specifications, test procedures, drawings) - Export control markers (ITAR, EAR, USML categories) - PII patterns (SSN, DoD ID, clearance levels) - Procurement language (source selection, FOUO markers) - Legacy markings (FOUO, SBU, LES) that need CUI conversion

Frequently asked questions