[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N5QEZ4419K31ZEVTY2F54B":3,"skill-same:01M6N5QEZ4419K31ZEVTY2F54B":112},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":29,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":73,"install":74,"resources":87},"01M6N5QEZ4419K31ZEVTY2F54B","ciso-advisor",null,"Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.","ibragimov-oasis\u002Fvibe-coder","ibragimov-oasis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F240665573?v=4","01M6DF78Y45R8228FHAZ7G6JXM","IBRAGIMOV MUKHAMMADJON","01M6K5ZYR8TDPAFG4R6693E2A6",3,"MIT","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fciso-advisor\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"ciso","ciso advisor","advisor","roadmap","source","quantification","iso","leadership","incident","artifact","tracker","security","Budget","defense","zero-trust","soc","defense-in-depth","reporting","architecture","incident response","2026-11-10 10:12:30",false,"---\nname: \"ciso-advisor\"\ndescription: \"Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: ciso-leadership\n  updated: 2026-03-05\n  python-tools: risk_quantifier.py, compliance_tracker.py\n  frameworks: risk-based-security, zero-trust, defense-in-depth\ntags:\n  - domain\u002Fagents\n  - artifact\u002Fskill\n  - source\u002Fskills-claude\n---\n\n# CISO Advisor\n\nRisk-based security frameworks for growth-stage companies. Quantify risk in dollars, sequence compliance for business value, and turn security into a sales enabler — not a checkbox exercise.\n\n## Keywords\nCISO, security strategy, risk quantification, ALE, SLE, ARO, security posture, compliance roadmap, SOC 2, ISO 27001, HIPAA, GDPR, zero trust, defense in depth, incident response, board security reporting, vendor assessment, security budget, cyber risk, program maturity\n\n## Quick Start\n\n```bash\npython scripts\u002Frisk_quantifier.py      # Quantify security risks in $, prioritize by ALE\npython scripts\u002Fcompliance_tracker.py   # Map framework overlaps, estimate effort and cost\n```\n\n## Core Responsibilities\n\n### 1. Risk Quantification\nTranslate technical risks into business impact: revenue loss, regulatory fines, reputational damage. Use ALE to prioritize. See `references\u002Fsecurity_strategy.md`.\n\n**Formula:** `ALE = SLE × ARO` (Single Loss Expectancy × Annual Rate of Occurrence). Board language: \"This risk has $X expected annual loss. Mitigation costs $Y.\"\n\n### 2. Compliance Roadmap\nSequence for business value: SOC 2 Type I (3–6 mo) → SOC 2 Type II (12 mo) → ISO 27001 or HIPAA based on customer demand. See `references\u002Fcompliance_roadmap.md` for timelines and costs.\n\n### 3. Security Architecture Strategy\nZero trust is a direction, not a product. Sequence: identity (IAM + MFA) → network segmentation → data classification. Defense in depth beats single-layer reliance. See `references\u002Fsecurity_strategy.md`.\n\n### 4. Incident Response Leadership\nThe CISO owns the executive IR playbook: communication decisions, escalation triggers, board notification, regulatory timelines. See `references\u002Fincident_response.md` for templates.\n\n### 5. Security Budget Justification\nFrame security spend as risk transfer cost. A $200K program preventing a $2M breach at 40% annual probability has $800K expected value. See `references\u002Fsecurity_strategy.md`.\n\n### 6. Vendor Security Assessment\nTier vendors by data access: Tier 1 (PII\u002FPHI) — full assessment annually; Tier 2 (business data) — questionnaire + review; Tier 3 (no data) — self-attestation.\n\n## Key Questions a CISO Asks\n\n- \"What's our crown jewel data, and who can access it right now?\"\n- \"If we had a breach today, what's our regulatory notification timeline?\"\n- \"Which compliance framework do our top 3 prospects actually require?\"\n- \"What's our blast radius if our largest SaaS vendor is compromised?\"\n- \"We spent $X on security last year — what specific risks did that reduce?\"\n\n## Security Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Risk | ALE coverage (mitigated risk \u002F total risk) | > 80% |\n| Detection | Mean Time to Detect (MTTD) | \u003C 24 hours |\n| Response | Mean Time to Respond (MTTR) | \u003C 4 hours |\n| Compliance | Controls passing audit | > 95% |\n| Hygiene | Critical patches within SLA | > 99% |\n| Access | Privileged accounts reviewed quarterly | 100% |\n| Vendor | Tier 1 vendors assessed annually | 100% |\n| Training | Phishing simulation click rate | \u003C 5% |\n\n## Red Flags\n\n- Security budget justified by \"industry benchmarks\" rather than risk analysis\n- Certifications pursued before basic hygiene (patching, MFA, backups)\n- No documented asset inventory — can't protect what you don't know you have\n- IR plan exists but has never been tested (tabletop or live drill)\n- Security team reports to IT, not executive level — misaligned incentives\n- Single vendor for identity + endpoint + email — one breach, total exposure\n- Security questionnaire backlog > 30 days — silently losing enterprise deals\n\n## Integration with Other C-Suite Roles\n\n| When... | CISO works with... | To... |\n|---------|--------------------|-------|\n| Enterprise sales | CRO | Answer questionnaires, unblock deals |\n| New product features | CTO\u002FCPO | Threat modeling, security review |\n| Compliance budget | CFO | Size program against risk exposure |\n| Vendor contracts | Legal\u002FCOO | Security SLAs and right-to-audit |\n| M&A due diligence | CEO\u002FCFO | Target security posture assessment |\n| Incident occurs | CEO\u002FLegal | Response coordination and disclosure |\n\n## Detailed References\n- `references\u002Fsecurity_strategy.md` — risk-based security, zero trust, maturity model, board reporting\n- `references\u002Fcompliance_roadmap.md` — SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR timelines, costs, overlaps\n- `references\u002Fincident_response.md` — executive IR playbook, communication templates, tabletop design\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- No security audit in 12+ months → schedule one before a customer asks\n- Enterprise deal requires SOC 2 and you don't have it → compliance roadmap needed now\n- New market expansion planned → check data residency and privacy requirements\n- Key system has no access logging → flag as compliance and forensic risk\n- Vendor with access to sensitive data hasn't been assessed → vendor security review\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Assess our security posture\" | Risk register with quantified business impact (ALE) |\n| \"We need SOC 2\" | Compliance roadmap with timeline, cost, effort, quick wins |\n| \"Prep for security audit\" | Gap analysis against target framework with remediation plan |\n| \"We had an incident\" | IR coordination plan + communication templates |\n| \"Security board section\" | Risk posture summary, compliance status, incident report |\n\n## Reasoning Technique: Risk-Based Reasoning\n\nEvaluate every decision through probability × impact. Quantify risks in business terms (dollars, not severity labels). Prioritize by expected annual loss.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: ? verified, ? medium, ? assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n\n## ? Связи\n\n- [[MOC - Skills]] — Skills library\n- [[skills\u002Fskills-claude]] — Category: skills-claude\n- [[MOC - Agents]] — Claude agents\n\n","# CISO Advisor\n\nRisk-based security frameworks for growth-stage companies. Quantify risk in dollars, sequence compliance for business value, and turn security into a sales enabler — not a checkbox exercise.\n\n## Keywords\nCISO, security strategy, risk quantification, ALE, SLE, ARO, security posture, compliance roadmap, SOC 2, ISO 27001, HIPAA, GDPR, zero trust, defense in depth, incident response, board security reporting, vendor assessment, security budget, cyber risk, program maturity\n\n## Quick Start\n\n```bash\npython scripts\u002Frisk_quantifier.py      # Quantify security risks in $, prioritize by ALE\npython scripts\u002Fcompliance_tracker.py   # Map framework overlaps, estimate effort and cost\n```\n\n## Core Responsibilities\n\n### 1. Risk Quantification\nTranslate technical risks into business impact: revenue loss, regulatory fines, reputational damage. Use ALE to prioritize. See `references\u002Fsecurity_strategy.md`.\n\n**Formula:** `ALE = SLE × ARO` (Single Loss Expectancy × Annual Rate of Occurrence). Board language: \"This risk has $X expected annual loss. Mitigation costs $Y.\"\n\n### 2. Compliance Roadmap\nSequence for business value: SOC 2 Type I (3–6 mo) → SOC 2 Type II (12 mo) → ISO 27001 or HIPAA based on customer demand. See `references\u002Fcompliance_roadmap.md` for timelines and costs.\n\n### 3. Security Architecture Strategy\nZero trust is a direction, not a product. Sequence: identity (IAM + MFA) → network segmentation → data classification. Defense in depth beats single-layer reliance. See `references\u002Fsecurity_strategy.md`.\n\n### 4. Incident Response Leadership\nThe CISO owns the executive IR playbook: communication decisions, escalation triggers, board notification, regulatory timelines. See `references\u002Fincident_response.md` for templates.\n\n### 5. Security Budget Justification\nFrame security spend as risk transfer cost. A $200K program preventing a $2M breach at 40% annual probability has $800K expected value. See `references\u002Fsecurity_strategy.md`.\n\n### 6. Vendor Security Assessment\nTier vendors by data access: Tier 1 (PII\u002FPHI) — full assessment annually; Tier 2 (business data) — questionnaire + review; Tier 3 (no data) — self-attestation.\n\n## Key Questions a CISO Asks\n\n- \"What's our crown jewel data, and who can access it right now?\"\n- \"If we had a breach today, what's our regulatory notification timeline?\"\n- \"Which compliance framework do our top 3 prospects actually require?\"\n- \"What's our blast radius if our largest SaaS vendor is compromised?\"\n- \"We spent $X on security last year — what specific risks did that reduce?\"\n\n## Security Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Risk | ALE coverage (mitigated risk \u002F total risk) | > 80% |\n| Detection | Mean Time to Detect (MTTD) | \u003C 24 hours |\n| Response | Mean Time to Respond (MTTR) | \u003C 4 hours |\n| Compliance | Controls passing audit | > 95% |\n| Hygiene | Critical patches within SLA | > 99% |\n| Access | Privileged accounts reviewed quarterly | 100% |\n| Vendor | Tier 1 vendors assessed annually | 100% |\n| Training | Phishing simulation click rate | \u003C 5% |\n\n## Red Flags\n\n- Security budget justified by \"industry benchmarks\" rather than risk analysis\n- Certifications pursued before basic hygiene (patching, MFA, backups)\n- No documented asset inventory — can't protect what you don't know you have\n- IR plan exists but has never been tested (tabletop or live drill)\n- Security team reports to IT, not executive level — misaligned incentives\n- Single vendor for identity + endpoint + email — one breach, total exposure\n- Security questionnaire backlog > 30 days — silently losing enterprise deals\n\n## Integration with Other C-Suite Roles\n\n| When... | CISO works with... | To... |\n|---------|--------------------|-------|\n| Enterprise sales | CRO | Answer questionnaires, unblock deals |\n| New product features | CTO\u002FCPO | Threat modeling, security review |\n| Compliance budget | CFO | Size program against risk exposure |\n| Vendor contracts | Legal\u002FCOO | Security SLAs and right-to-audit |\n| M&A due diligence | CEO\u002FCFO | Target security posture assessment |\n| Incident occurs | CEO\u002FLegal | Response coordination and disclosure |\n\n## Detailed References\n- `references\u002Fsecurity_strategy.md` — risk-based security, zero trust, maturity model, board reporting\n- `references\u002Fcompliance_roadmap.md` — SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR timelines, costs, overlaps\n- `references\u002Fincident_response.md` — executive IR playbook, communication templates, tabletop design\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- No security audit in 12+ months → schedule one before a customer asks\n- Enterprise deal requires SOC 2 and you don't have it → compliance roadmap needed now\n- New market expansion planned → check data residency and privacy requirements\n- Key system has no access logging → flag as compliance and forensic risk\n- Vendor with access to sensitive data hasn't been assessed → vendor security review\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Assess our security posture\" | Risk register with quantified business impact (ALE) |\n| \"We need SOC 2\" | Compliance roadmap with timeline, cost, effort, quick wins |\n| \"Prep for security audit\" | Gap analysis against target framework with remediation plan |\n| \"We had an incident\" | IR coordination plan + communication templates |\n| \"Security board section\" | Risk posture summary, compliance status, incident report |\n\n## Reasoning Technique: Risk-Based Reasoning\n\nEvaluate every decision through probability × impact. Quantify risks in business terms (dollars, not severity labels). Prioritize by expected annual loss.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: ? verified, ? medium, ? assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n\n## ? Связи\n\n- [[MOC - Skills]] — Skills library\n- [[skills\u002Fskills-claude]] — Category: skills-claude\n- [[MOC - Agents]] — Claude agents\n\n",{"name":5,"tags":55,"license":15,"metadata":59,"description":7},[56,57,58],"domain\u002Fagents","artifact\u002Fskill","source\u002Fskills-claude",{"author":60,"domain":61,"updated":62,"version":63,"category":64,"frameworks":65,"python-tools":66},"Alireza Rezvani","ciso-leadership",1772668800000,"1.0.0","c-level","risk-based-security, zero-trust, defense-in-depth","risk_quantifier.py, compliance_tracker.py","main","bdd9f958d7bb1a0f19b8ad8da020b0bab0f53eb1","vc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fciso-advisor",1,"https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis","2026-06-24 16:31:18",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add ibragimov-oasis\u002Fvibe-coder --skill ciso-advisor",{"tool":80,"command":81},"bunx","bunx skills add ibragimov-oasis\u002Fvibe-coder --skill ciso-advisor",{"tool":83,"command":84},"pnpm","pnpm dlx skills add ibragimov-oasis\u002Fvibe-coder --skill ciso-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fciso-advisor\u002FSKILL.md",true,[88,94,98,102,108],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fcompliance_roadmap.md","REFERENCE","参考文档",16817,"https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fciso-advisor\u002Freferences\u002Fcompliance_roadmap.md",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fincident_response.md",16613,"https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fciso-advisor\u002Freferences\u002Fincident_response.md",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fsecurity_strategy.md",12269,"https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fciso-advisor\u002Freferences\u002Fsecurity_strategy.md",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fcompliance_tracker.py","SCRIPT","脚本",31058,"https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fciso-advisor\u002Fscripts\u002Fcompliance_tracker.py",{"path":109,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":110,"sourceHtmlUrl":111},"scripts\u002Frisk_quantifier.py",28429,"https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fciso-advisor\u002Fscripts\u002Frisk_quantifier.py",[113,148,174,193,219,250],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":127,"publishedAt":50},"01M6Q4Q22KKKVMJJYA411DQ4ER","ckm:ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fui-styling\u002FSKILL.md",[119,124],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147],"ui styling","ui","styling","ckm:ui styling","ckm","design","css","canvas","components","component","create","design systems","Tailwind","across","themes","utility","mode","implementing","artifact\u002Fui-component","source\u002Fui-design",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":162,"publishedAt":50},"01M6Q4PQ2NX4NDVWTEHA3MQ2R0","ckm:design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fdesign\u002FSKILL.md",[154,157,158,161],{"categoryNo":155,"categoryName":156,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},{"categoryNo":159,"categoryName":160,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[133,150,132,163,137,128,164,138,165,166,167,168,169,170,171,172,39,173,146,147],"google","presentations","generate","screenshot","actions","Media","logo","ads","youtube","tiktok","chart",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":182,"publishedAt":50},"01M6Q4PJE27GEA3M0CECEBCZKS","ckm:design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fdesign-system\u002FSKILL.md",[180,181],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[133,183,184,185,150,132,134,137,48,164,39,186,187,188,189,190,191,192,146,147],"design system","system","ckm:design system","token","creation","systematic","css variables","Variables","spacing","layer",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":204,"publishedAt":50},"01M6Q4P90JXFYMH2S634QM6SQJ","ckm:banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fbanner-design\u002FSKILL.md",[199,202,203],{"categoryNo":200,"categoryName":201,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[133,205,206,207,132,208,167,168,209,210,211,212,213,214,215,216,146,147,217,218],"banner design","ckm:banner design","banner","frontend","3D","generated","Art","social","dimensions","neon","direction","display","frontend-design","hero",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":231,"publishedAt":50},"01M6Q2RZXBJ9TBE413GXCYQNDB","seo","Comprehensive SEO analysis for any website or business type. Performs full site audits, single-page deep analysis, technical SEO checks (crawlability, indexability, Core Web Vitals with INP), schema markup detection\u002Fvalidation\u002Fgeneration, content quality assessment (E-E-A-T framework per Dec 2025 update extending to all competitive queries), image optimization, sitemap analysis, and Generative Engine Optimization (GEO) for AI Overviews, ChatGPT, and Perplexity citations. Analyzes AI crawler accessibility (GPTBot, ClaudeBot, PerplexityBot), llms.txt compliance, brand mention signals, and passage-level citability. Industry detection for SaaS, e-commerce, local business, publishers, agencies. Triggers on: \"SEO\", \"audit\", \"schema\", \"Core Web Vitals\", \"sitemap\", \"E-E-A-T\", \"AI Overviews\", \"GEO\", \"technical SEO\", \"content quality\", \"page speed\", \"structured data\".","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-seo\u002Fseo\u002Fclaude-seo\u002Fskills\u002Fseo\u002FSKILL.md",[225,228],{"categoryNo":226,"categoryName":227,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000035","市场营销",[221,232,233,234,235,236,237,39,238,239,240,241,242,243,244,245,246,247,248,249],"image","llms","assessment","deep analysis","Citations","analysis","local","deep","crawlability","seo analysis","2025","commerce","URL","domain\u002Fseo","source\u002Fskills-seo","vitals","generative","publishers",{"skillNo":251,"name":252,"nameZh":6,"description":253,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":254,"categories":255,"keywords":258,"publishedAt":50},"01M6Q2RVE7VGFCFQKBK468NHVY","seo-technical","Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says \"technical SEO\", \"crawl issues\", \"robots.txt\", \"Core Web Vitals\", \"site speed\", or \"security headers\".","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-seo\u002Fseo\u002Fclaude-seo\u002Fskills\u002Fseo-technical\u002FSKILL.md",[256,257],{"categoryNo":226,"categoryName":227,"taxonomyType":122,"taxonomyTypeDesc":123},{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},[221,259,260,261,262,263,264,265,266,39,141,240,267,268,244,269,270,245,246,247],"technical","seo technical","issues","audit","data","mobile","crawl","structure","rendering","technical seo audit","headers","categories"]