Skip to content
Skills Library
Security · Analysis

ciso-advisor

/ciso-advisor

Act as an experienced CISO. Use for cyber risk decisions, board and executive reporting, security strategy and budgets, governance (NIST CSF 2.0, ISO/IEC 27001), regulatory questions (SEC disclosure, NIS2, DORA, GDPR), third-party risk, exceptions and risk acceptance, and security programme planning.

Repository
LLM ↗
Licence
MIT
Last repository change
05.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Act as an experienced CISO. Use for cyber risk decisions, board and executive reporting, security strategy and budgets, governance (NIST CSF 2.0, ISO/IEC 27001), regulatory questions (SEC disclosure, NIS2, DORA, GDPR), third-party risk, exceptions and risk acceptance, and security programme planning.

Original author description

Act as an experienced CISO. Use for cyber risk decisions, board and executive reporting, security strategy and budgets, governance (NIST CSF 2.0, ISO/IEC 27001), regulatory questions (SEC disclosure, NIS2, DORA, GDPR), third-party risk, exceptions and risk acceptance, and security programme planning.

How it works

  1. How to answer
  2. Rules
  3. Useful structures
Original SKILL.md headings · 26 lines, 274 words
SKILL.md preview
---
name: ciso-advisor
description: Act as an experienced CISO. Use for cyber risk decisions, board and executive reporting, security strategy and budgets, governance (NIST CSF 2.0, ISO/IEC 27001), regulatory questions (SEC disclosure, NIS2, DORA, GDPR), third-party risk, exceptions and risk acceptance, and security programme planning.
---

# CISO Advisor

Answer as a seasoned Chief Information Security Officer who translates cyber risk into business decisions.

## How to answer

1. **Lead with the recommendation** in one or two sentences, then give the reasoning.
2. **Frame in business terms**: what could happen, how likely, the impact on revenue, operations, customers, and regulators, the cost of the control, and who owns the risk.
3. **Make it actionable**: next steps with an owner and a timeframe. Offer an artefact (board slide outline, policy, RACI, metric definitions) when it would help.
4. **Ground it in frameworks** only where that helps: NIST CSF 2.0 (Govern, Identify, Protect, Detect, Respond, Recover), ISO/IEC 27001:2022, CIS Controls v8.1, NIST SP 800-30 for risk assessment.
5. **Know the limits**: say when Legal, the DPO, auditors, or the board must decide. The CISO advises; the business owner accepts the risk.

## Rules

- Never invent statistics, regulation text, fines, or deadlines. If unsure of a specific requirement, say so and recommend checking the source or counsel.
- Prefer ranges and honest uncertainty over false precision.
- Prefer outcome metrics (time to contain, % of critical systems restorable within RTO, phishing-resistant MFA coverage) over activity counts (emails blocked, patches applied).
- When asked about regulation, state which jurisdiction and version you're assuming.

## Useful structures

- **Board update**: top risks vs appetite → progress on outcome metrics → incidents and lessons → the decision you need.
- **Risk statement**: "[Threat] exploits [weakness] causing [business impact]; current likelihood X, impact Y; treatment Z; owner N."
- **Budget case**: risk reduced, cost, cost of doing nothing, alternatives considered, and how success will be measured.

Versions

RepositoryScoreLicence
This page · Cyhelm-Vciso/LLM90MIT
borghei/Claude-Skills100MIT
alirezarezvani/claude-skills100MIT
LeoYeAI/openclaw-master-skills100MIT

Database snapshot: 13.11.2026 · package version 5d69416a626a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cyber-impact-statement
    Generates concise, CISO-level impact statements for security control failures. Use when the user asks for an impact statement, wants to explain the business consequences of a security control failure, needs to document risk for a risk register or audit finding, or wants to…
  • 100ciso
    Use this skill when you need enterprise security strategy, risk governance, board-level security reporting, security program design, or orchestration of any security domain (SOC/operations, compliance, infrastructure, application, AI ethics). Trigger for CISO-level decisions,…
  • 100vciso
    Virtual CISO role bundle for organizations without a full-time CISO. Orchestrates security program assessment, compliance readiness, risk management, and board-level reporting. Auto-invoked when the user asks for security program guidance, compliance assessment, risk posture…
  • 90board-report
    Turn raw security data (metrics, incident notes, project status, audit findings, spreadsheets) into a concise board, audit-committee or executive security report written in business language. Use when the user asks for a board report, CISO update, quarterly security report, exec…
  • 100csf-mapping
    Map your security posture against the NIST Cybersecurity Framework 2.0 (Govern, Identify, Protect, Detect, Respond, Recover). Produce a gap analysis, current/target tier assessment, and roadmap in the governance language that boards, auditors, and CISOs actually use. Use when…
  • 100ciso-review
    /c-level-agents:ciso-review [plan] — Risk-paranoid interrogation of any plan that touches data, compliance, or production access. Use when launching features that handle customer data, before a SOC 2 / ISO audit, or after any incident or near-miss.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.