cyber-framework-mapping
Maintains sparse, reviewable cybersecurity framework edges with versioned IDs, relation, rationale, source, and review status. Use when mapping exercise observations or procedures to NIST, ATT&CK, or another named framework.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 3
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 82caaeb04e42b6ba… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Cyber Framework Mapping
Priority: P1 (HIGH)
Map only evidenced relationships; catalog context is not proof of efficacy, compliance, or coverage.
Structure
cyber-framework-mapping/
├── SKILL.md
├── references/edge-record.md
└── evals/evals.json
Workflow
- Name framework, version, stable ID, and exact source URL or document section.
- Choose relation (
supports,describes,observed-as,partial,unknown, orconflicts). - Write a bounded rationale tied to an evidence record, not a generic similarity.
- Set review status:
reviewed,needs-review, orunreviewed; include reviewer and date when reviewed. - Preserve empty or unknown mappings explicitly; do not infer a complete catalog.
- On a version/source change, preserve the prior versioned edge and its evidence unchanged. Create a separately versioned candidate linked to the prior record, mark it
needs-review, and re-review; never overwrite historical mappings.
Rules
- Prefer primary framework publications and official technique catalogs.
- Keep framework IDs version-qualified; never silently merge revisions.
- Separate a mapped edge from a control claim, measured efficacy, or compliance assertion.
- Link shared evidence fields for observation provenance.
For mapped observations, carry
engagement_scope_ref,skill_version,source,observed_at,finding_status,evidence_refs,limitations, andaccountable_owner.
Anti-Patterns
- No broad equivalence: One keyword does not establish a mapping.
- No version drift: Verify the current revision before reusing an ID.
- No compliance leap: Mapping never certifies a control or outcome.
- No fabricated completeness: Mark unknown edges and gaps.
References
Files
3- SKILL.md
98fa30a5392.3 KB - evals/evals.json
6f8b86e0a82.5 KB - references/edge-record.md
590c057759801 B
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from HoangNguyen0403/agent-skills-standard8
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci
Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.