[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TK6RWYQNNV97JS37DPBT9":3,"skill-same:01M79TK6RWYQNNV97JS37DPBT9":77},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M79TK6RWYQNNV97JS37DPBT9","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.","Heverton-web\u002Fproj_livros","Heverton-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136394064?v=4","01M79STQDWSTA88J5CA9QR184V","Heverton Eduardo Peres","01M79STQEFTTYHD3AC7F2RRW5T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fciso-advisor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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\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 `..\u002Fagent-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","# 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 `..\u002Fagent-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",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"domain":26,"updated":27,"version":28,"category":29,"frameworks":30,"python-tools":31},"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","5eac686c0e84af1a5dc958c1bfb6c9d00699561d",".agents\u002Fskills\u002Fciso-advisor",1,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros","https:\u002F\u002Fgithub.com\u002FHeverton-web","2026-07-29 06:58:59",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add Heverton-web\u002Fproj_livros --skill ciso-advisor",{"tool":45,"command":46},"bunx","bunx skills add Heverton-web\u002Fproj_livros --skill ciso-advisor",{"tool":48,"command":49},"pnpm","pnpm dlx skills add Heverton-web\u002Fproj_livros --skill ciso-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fciso-advisor\u002FSKILL.md",true,[53,59,63,67,73],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fcompliance_roadmap.md","REFERENCE","参考文档",16627,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fciso-advisor\u002Freferences\u002Fcompliance_roadmap.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fincident_response.md",16423,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fciso-advisor\u002Freferences\u002Fincident_response.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fsecurity_strategy.md",12079,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fciso-advisor\u002Freferences\u002Fsecurity_strategy.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fcompliance_tracker.py","SCRIPT","脚本",31058,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fciso-advisor\u002Fscripts\u002Fcompliance_tracker.py",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Frisk_quantifier.py",28429,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fciso-advisor\u002Fscripts\u002Frisk_quantifier.py",[78,85,92,99,106,113],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7A3PZFSZ0K95BAD6QHJPX97","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7A3PH26QVPYRTM6EWS45YET","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7A3NVTC4N3NG1TA2SGSFGF6","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7A3NQNAJPSQ24VWSQ679AX8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7A3NE3FGSMGDY5XVKJ8297H","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[],{"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":119,"publishedAt":19},"01M7A3N4ZG6TVJ1TST9C0T5QAK","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fproj_livros\u002Fblob\u002Fmain\u002Fagentic\u002Fskills\u002Fwebinar-marketing\u002FSKILL.md",[],[]]