[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72D1S0XMEGRFCFAWPPNKJM9":3,"skill-same:01M72D1S0XMEGRFCFAWPPNKJM9":76},{"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":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M72D1S0XMEGRFCFAWPPNKJM9","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.","WeekendGoCo\u002FWeekendGo_W","WeekendGoCo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F283486665?v=4","01M72CJX1N2BRHCB707478WMSH","Weekend Go","01M72CJX2D7FKB2GF1EVTJXPT5",0,"MIT","https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002FSKILL.md",[],[],"2026-11-10 18:39:20",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 `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","# 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",{"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","552d679ad23c4089ef17177e381989a077e125ad","claude-skills-temp\u002Fclaude-skills-main\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor","https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W","https:\u002F\u002Fgithub.com\u002FWeekendGoCo","2026-05-13 18:39:49",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add WeekendGoCo\u002FWeekendGo_W --skill ciso-advisor",{"tool":44,"command":45},"bunx","bunx skills add WeekendGoCo\u002FWeekendGo_W --skill ciso-advisor",{"tool":47,"command":48},"pnpm","pnpm dlx skills add WeekendGoCo\u002FWeekendGo_W --skill ciso-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002FSKILL.md",true,[52,58,62,66,72],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcompliance_roadmap.md","REFERENCE","参考文档",16627,"https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002Freferences\u002Fcompliance_roadmap.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fincident_response.md",16423,"https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002Freferences\u002Fincident_response.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fsecurity_strategy.md",12079,"https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002Freferences\u002Fsecurity_strategy.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fcompliance_tracker.py","SCRIPT","脚本",31058,"https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002Fscripts\u002Fcompliance_tracker.py",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Frisk_quantifier.py",28429,"https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002Fscripts\u002Frisk_quantifier.py",[77,84,91,98,105,112],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M72DS3MQ8ZFGR8EZAW6PEAT9","ra-qm-skills","12 regulatory & QM agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. ISO 13485 QMS, MDR 2017\u002F745, FDA 510(k)\u002FPMA, ISO 27001 ISMS, GDPR\u002FDSGVO, risk management (ISO 14971), CAPA, document control, auditing. Python tools (stdlib-only).","https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fra-qm-team\u002Fskills\u002Fra-qm-skills\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M72DQE5ADFWNW85S0G7B8XNG","scrum-master","Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.","https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fproject-management\u002Fskills\u002Fscrum-master\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M72DQC2EXMJ1XR1E1416Y0A2","pm-skills","6 project management agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Senior PM, scrum master, Jira expert (JQL), Confluence expert, Atlassian admin, template creator. MCP integration for live Jira\u002FConfluence automation.","https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fproject-management\u002Fskills\u002Fpm-skills\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M72DP31HR3ZK7MDJ94PM0GBX","product-skills","10 product agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. PM toolkit (RICE), agile PO, product strategist (OKR), UX researcher, UI design system, competitive teardown, landing page generator, SaaS scaffolder, research summarizer. Python tools (stdlib-only).","https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fproduct-team\u002Fskills\u002Fproduct-skills\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M72DNAWRN366W1M2VXS9RZSN","research-summarizer","Structured research summarization agent skill for non-dev users. Handles academic papers, web articles, reports, and documentation. Extracts key findings, generates comparative analyses, and produces properly formatted citations. Use when: user wants to summarize a research paper, compare multiple sources, extract citations from documents, or create structured research briefs. Plugin for Claude Code, Codex, Gemini CLI, and OpenClaw.","https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fproduct-team\u002Fresearch-summarizer\u002Fskills\u002Fresearch-summarizer\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M72DN4TBSGKPVYDSYCFF2VK4","code-to-prd","Reverse-engineer any codebase into a complete Product Requirements Document (PRD).\nAnalyzes routes, components, state management, API integrations, and user interactions to produce\nbusiness-readable documentation detailed enough for engineers or AI agents to fully reconstruct\nevery page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt),\nbackend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications.\n\nTrigger when users mention: generate PRD, reverse-engineer requirements, code to documentation,\nextract product specs from code, document page logic, analyze page fields and interactions,\ncreate a functional inventory, write requirements from an existing codebase, document API endpoints,\nor analyze backend routes.","https:\u002F\u002Fgithub.com\u002FWeekendGoCo\u002FWeekendGo_W\u002Fblob\u002Fmain\u002Fclaude-skills-temp\u002Fclaude-skills-main\u002Fproduct-team\u002Fcode-to-prd\u002Fskills\u002Fcode-to-prd\u002FSKILL.md",[],[]]