Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/cui-marker
Metadata
Additional technical details for this skill
- short description
- CUI detection, marking, and flow tracking (32 CFR Part 2002)
SKILL.md
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?