cyber-engagement-planning
Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates. Use when preparing an exercise or assessment plan before execution.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 3
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 577af76fec7fc216… — 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 Engagement Planning
Priority: P0 (CRITICAL)
Produce a reviewable plan that separates intended activity from host-enforced permission.
Structure
cyber-engagement-planning/
├── SKILL.md
├── references/engagement-brief.md
└── evals/evals.json
Workflow
- State objective, success observation, engagement/scope reference, dates, and accountable owner.
- List in-scope synthetic assets or explicitly authorized targets; list exclusions and non-goals.
- Assign requester, approver, operator, exercise control, adjudicator, and escalation roles.
- Record allowed actions, prohibited actions, data handling, communications, and runtime controls.
- Define expiry, stop triggers, restart authority, evidence fields, and unresolved decisions.
- Mark live execution
blockedand the plan offline-only when required runtime support is absent; never imply production readiness. - Restart requires both current authorization and verified host enforcement of scope. Owner approval, risk acceptance, documented exceptions, or proposed compensating controls cannot waive either prerequisite; unverified alternatives keep the live lane blocked.
Rules
- Plan only; do not include payloads, attack commands, credentials, real targets, or destructive steps.
- Treat production modifications as separately approved actions.
- Reuse authorization, evidence, and mapping.
- Use primary framework sources; mark uncertain mappings explicitly.
Plan evidence fields explicitly:
engagement_scope_ref,skill_version,source,observed_at,finding_status,evidence_refs,limitations, andaccountable_owner.
Anti-Patterns
- No implied authorization: A completed plan is not approval.
- No vague scope: Name boundaries and exclusions.
- No hidden runtime dependency: State unsupported controls and block live work.
- No team-color shortcut: Roles do not replace authorization.
References
Files
3- SKILL.md
f7607259862.7 KB - evals/evals.json
701824c7663.9 KB - references/engagement-brief.md
9593da69ca869 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.