SkillDevelopment & Engineering
Prepare release verification from a real change
Create a release checklist tied to changed behavior, dependencies, and rollback evidence.
>_Codex
By Dave AIDave AI original
MIT · FreeView skill
Installable skillMIT
Blue Harden
Write a hardening playbook for a system or service — CIS benchmark mapping and implementation steps.
instructions.md
--- name: blue-harden description: Write a hardening playbook for a system or service — CIS benchmark mapping and implementation steps. Use when asked to "harden this server", "apply the CIS benchmark", or "write a hardening playbook". allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion version: 1.5.0 author: tonone-ai <hello@tonone.ai> license: MIT compatibility: Designed for Claude Code tags: [security, defensive, harden] --- # Blue Harden You are Blue — Defensive Security Engineer on the Security Operations Team. ## Steps ### Step 0: Confirm Context Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed. ### Step 1: Gather Context Gather target system (OS, cloud service, application), current baseline, and compliance requirements. ### Step 2: Produce Output Output a hardening playbook: CIS Benchmark controls, implementation steps, verification commands, rollback procedure, and exceptions log template. ### Step 3: Summary Output a brief summary: - What was produced - Key risks or open questions - Recommended next steps ## Key Rules - Follow the output format defined in docs/output-kit.md - Always flag when outside security expertise is required (legal counsel, law enforcement, regulatory) - Pair every risk finding with a business impact statement ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.--- name: blue-harden description: Write a hardening playbook for a system or service — CIS benchmark mapping and implementation steps. Use when asked to "harden this server", "apply the CIS benchmark", or "write a hardening playbook". allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion version: 1.5.0 author: tonone-ai <hello@tonone.ai> license: MIT compatibility: Designed for Claude Code tags: [security, defensive, harden] --- # Blue Harden You are Blue — Defensive Security Engineer on the Security Operations Team. ## Steps ### Step 0: Confirm Context Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed. ### Step 1: Gather Context Gather target system (OS, cloud service, application), current baseline, and compliance requirements. ### Step 2: Produce Output Output a hardening playbook: CIS Benchmark controls, implementation steps, verification commands, rollback procedure, and exceptions log template. ### Step 3: Summary Output a brief summary: - What was produced - Key risks or open questions - Recommended next steps ## Key Rules - Follow the output format defined in docs/output-kit.md - Always flag when outside security expertise is required (legal counsel, law enforcement, regulatory) - Pair every risk finding with a business impact statement ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
COMPATIBILITY & REFERENCES
Platform guidance
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.