[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"extension-skill-rockscy-postmortem-solo-en":3,"guides-for-rockscy-postmortem-solo":341,"similar-k17e4bj5a4f37047sdy6kcstsx86m2qv-en":342},{"_creationTime":4,"_id":5,"children":6,"community":7,"display":9,"evaluation":15,"identity":242,"isFallback":228,"parentExtension":247,"providers":248,"relations":253,"repo":255,"tags":337,"workflow":338},1778696562316.011,"k17e4bj5a4f37047sdy6kcstsx86m2qv",[],{"reviewCount":8},0,{"description":10,"installMethods":11,"name":13,"sourceUrl":14},"Run a lightweight, blame-free postmortem after an incident, failed launch, or missed deadline — for one person. Use when the user says \"that didn't go well\", \"the launch flopped\", \"we had an outage\", \"I missed my deadline\", or wants to learn from a recent failure.",{"claudeCode":12},"rockscy/solo-skills","postmortem-solo","https://github.com/rockscy/solo-skills",{"_creationTime":16,"_id":17,"extensionId":5,"locale":18,"result":19,"trustSignals":226,"workflow":240},1778696635807.3386,"kn7cc17s0jnsw10rykx6ksegk586mxqe","en",{"checks":20,"evaluatedAt":196,"extensionSummary":197,"features":198,"nonGoals":203,"promptVersionExtension":208,"promptVersionScoring":209,"purpose":210,"rationale":211,"score":212,"summary":213,"tags":214,"targetMarket":219,"tier":220,"useCases":221},[21,26,29,33,37,41,45,48,52,56,60,63,66,69,72,76,79,82,85,88,91,95,100,103,107,110,113,116,119,122,125,129,132,136,140,143,146,149,152,156,159,162,165,168,171,174,178,182,186,189,193],{"category":22,"check":23,"severity":24,"summary":25},"Invocation","Precise Purpose","pass","The skill clearly defines its purpose as running a blame-free, one-person postmortem and specifies when to use it (missed deadlines, outages) and when not to (active incidents, emotional processing).",{"category":22,"check":27,"severity":24,"summary":28},"Concise Frontmatter","The frontmatter in SKILL.md is concise and self-contained, accurately summarizing the core capability within the desired character limit.",{"category":30,"check":31,"severity":24,"summary":32},"Documentation","Concise Body","The SKILL.md body is concise, adhering to the approximate line limit and effectively using progressive disclosure for detailed sections and examples.",{"category":34,"check":35,"severity":24,"summary":36},"Context","Progressive Disclosure","The SKILL.md clearly outlines the postmortem structure and delegates detailed sections like 'Worked example' and anti-patterns implicitly by keeping the main file concise, rather than embedding large amounts of external material.",{"category":34,"check":38,"severity":39,"summary":40},"Forked exploration","not_applicable","This skill is a short-form, structured output task and does not involve deep exploration or code review, making the 'context: fork' setting not applicable.",{"category":42,"check":43,"severity":24,"summary":44},"Practical Utility","Usage examples","A clear, worked example demonstrating input and expected output is provided, illustrating the skill's core functionality.",{"category":42,"check":46,"severity":24,"summary":47},"Edge cases","The skill documents limitations and anti-patterns, such as the 'no blame but yes accountability' rule and the maximum number of changes, guiding users on failure modes and recovery by suggesting process changes.",{"category":49,"check":50,"severity":39,"summary":51},"Code Execution","Tool Fallback","The skill does not rely on external tools like MCP servers; it operates directly within the Claude Code environment.",{"category":53,"check":54,"severity":24,"summary":55},"Portability","Stack assumptions","The skill assumes a standard Bash shell and Claude Code environment, with no exotic language runtimes or external dependencies declared or implied.",{"category":57,"check":58,"severity":24,"summary":59},"Safety","Halt on unexpected state","The skill's structure and instructions implicitly encourage halting on unexpected states by enforcing strict word limits and focusing on concrete, actionable changes, rather than attempting to proceed with ambiguous inputs.",{"category":53,"check":61,"severity":24,"summary":62},"Cross-skill coupling","The skill is self-contained and focuses on personal postmortems, not implicitly relying on or overlapping with other specific skills.",{"category":42,"check":64,"severity":24,"summary":65},"Problem relevance","The description clearly names a concrete user problem: running a blame-free postmortem for individuals after a failure.",{"category":42,"check":67,"severity":24,"summary":68},"Unique selling proposition","The skill offers a unique value proposition by focusing specifically on solo postmortems with strict word limits and a 'when not to use' section, differentiating it from general-purpose postmortem frameworks.",{"category":42,"check":70,"severity":24,"summary":71},"Production readiness","The skill is production-ready, providing a complete lifecycle for generating a concise postmortem document with clear instructions and output format.",{"category":73,"check":74,"severity":24,"summary":75},"Scope","Single responsibility principle","The skill has a single, well-defined responsibility: facilitating a solo postmortem analysis.",{"category":73,"check":77,"severity":24,"summary":78},"Description quality","The displayed description accurately reflects the skill's functionality as detailed in the SKILL.md.",{"category":22,"check":80,"severity":39,"summary":81},"Scoped tools","This is a skill that operates via LLM prompting and does not expose discrete tools with specific command names.",{"category":30,"check":83,"severity":39,"summary":84},"Configuration & parameter reference","The skill does not have configurable parameters or options beyond the initial user prompt.",{"category":73,"check":86,"severity":39,"summary":87},"Tool naming","This is a skill and does not expose user-facing tools with names.",{"category":73,"check":89,"severity":39,"summary":90},"Minimal I/O surface","This skill operates via natural language prompts and does not expose specific tools with input/output schemas.",{"category":92,"check":93,"severity":24,"summary":94},"License","License usability","The project is licensed under MIT, a permissive open-source license, as indicated by the LICENSE file and README badge.",{"category":96,"check":97,"severity":98,"summary":99},"Maintenance","Commit recency","warning","The last commit was on April 30, 2026, which is more than 12 months ago, indicating potential unmaintained status.",{"category":96,"check":101,"severity":39,"summary":102},"Dependency Management","The skill does not use any third-party dependencies.",{"category":104,"check":105,"severity":39,"summary":106},"Security","Secret Management","The skill does not handle or expose any secrets.",{"category":104,"check":108,"severity":24,"summary":109},"Injection","The skill processes user input for postmortem analysis and does not load or execute untrusted third-party data.",{"category":104,"check":111,"severity":24,"summary":112},"Transitive Supply-Chain Grenades","The skill does not fetch external files or code at runtime; all content is bundled within the repository.",{"category":104,"check":114,"severity":24,"summary":115},"Sandbox Isolation","The skill operates within the Claude Code environment and does not modify files outside its designated scope.",{"category":104,"check":117,"severity":24,"summary":118},"Sandbox escape primitives","No detached-process spawns or deny-retry loops were found in the skill's logic.",{"category":104,"check":120,"severity":24,"summary":121},"Data Exfiltration","The skill does not read or submit confidential data; all processing is local to the analysis of user input.",{"category":104,"check":123,"severity":24,"summary":124},"Hidden Text Tricks","The bundled content is free of hidden-steering tricks, and descriptions use clean, printable ASCII.",{"category":126,"check":127,"severity":24,"summary":128},"Hooks","Opaque code execution","The skill's logic is contained within readable SKILL.md and does not involve obfuscated code, base64 payloads, or runtime script fetching.",{"category":53,"check":130,"severity":24,"summary":131},"Structural Assumption","The skill does not make assumptions about user project structure, as it operates solely on the provided text input.",{"category":133,"check":134,"severity":24,"summary":135},"Trust","Issues Attention","There are 0 open and 0 closed issues in the last 90 days, indicating a low volume or new project, which is acceptable.",{"category":137,"check":138,"severity":98,"summary":139},"Versioning","Release Management","The repository does not have a clear versioning signal (e.g., SKILL.md frontmatter version, GitHub releases, CHANGELOG), and installation instructions reference 'main', making it difficult to pin a specific version.",{"category":49,"check":141,"severity":39,"summary":142},"Validation","The skill relies on LLM interpretation of natural language and does not have executable code or structured parameters requiring schema validation.",{"category":104,"check":144,"severity":39,"summary":145},"Unguarded Destructive Operations","The skill is purely analytical and does not perform any destructive operations.",{"category":49,"check":147,"severity":39,"summary":148},"Error Handling","As a skill that processes natural language and returns structured text, there are no executable scripts with explicit error paths to evaluate.",{"category":49,"check":150,"severity":39,"summary":151},"Logging","The skill does not perform actions that require local audit logging.",{"category":153,"check":154,"severity":39,"summary":155},"Compliance","GDPR","The skill does not operate on personal data; it analyzes user-provided text for a postmortem.",{"category":153,"check":157,"severity":24,"summary":158},"Target market","The skill's functionality is general and not bound to any specific geography or legal jurisdiction; targetMarket is global.",{"category":53,"check":160,"severity":24,"summary":161},"Runtime stability","The skill relies on standard Claude Code runtime capabilities and does not assume specific editors, shells, or operating systems.",{"category":30,"check":163,"severity":24,"summary":164},"README","The README file clearly introduces the purpose of the solo-skills pack and provides installation and usage instructions.",{"category":73,"check":166,"severity":39,"summary":167},"Tool surface size","This is a single skill, not a collection of tools.",{"category":22,"check":169,"severity":39,"summary":170},"Overlapping near-synonym tools","This skill does not expose multiple tools, so there are no overlapping synonyms to evaluate.",{"category":30,"check":172,"severity":24,"summary":173},"Phantom features","All features described in the README and SKILL.md (postmortem generation, specific structure) have corresponding implementations.",{"category":175,"check":176,"severity":24,"summary":177},"Install","Installation instruction","The README provides clear, copy-pasteable installation instructions using a one-liner curl command and a manual git clone option.",{"category":179,"check":180,"severity":39,"summary":181},"Errors","Actionable error messages","The skill operates on natural language input and returns structured text, without distinct error paths that require user-facing error messages.",{"category":183,"check":184,"severity":39,"summary":185},"Execution","Pinned dependencies","The skill does not have bundled scripts or third-party dependencies that require pinning.",{"category":73,"check":187,"severity":39,"summary":188},"Dry-run preview","The skill is analytical and does not perform state-changing operations or send data outward.",{"category":190,"check":191,"severity":39,"summary":192},"Protocol","Idempotent retry & timeouts","The skill does not involve remote calls or state-changing operations that would require idempotency or timeouts.",{"category":153,"check":194,"severity":39,"summary":195},"Telemetry opt-in","The skill does not emit any telemetry.",1778696635686,"This skill guides a single user through conducting a blame-free postmortem after an incident, failed launch, or missed deadline, adhering to strict word limits for analysis and actionable changes.",[199,200,201,202],"Structured postmortem generation for individuals","Strict word limits for each section","Focus on systemic causes over personal blame","Definition of concrete, actionable changes",[204,205,206,207],"Conducting team-based postmortems","Providing emotional support or venting","Generating lengthy, formal postmortem reports","Analyzing ongoing incidents","3.0.0","4.4.0","To help individuals learn from failures by systematically analyzing what happened, its impact, root causes, and defining concrete changes for improvement.","The skill is well-documented and provides a clear value proposition, but the lack of clear versioning and recent commits lowers the score.",75,"A focused skill for conducting solo postmortems, emphasizing brevity and actionable outcomes.",[215,216,217,218],"postmortem","incident-response","incident-analysis","personal-productivity","global","community",[222,223,224,225],"Analyzing a recent outage or production incident","Reviewing a failed product launch","Understanding why a deadline was missed","Learning from a significant customer churn spike",{"codeQuality":227,"collectedAt":229,"documentation":230,"maintenance":233,"security":237,"testCoverage":239},{"hasLockfile":228},false,1778696622486,{"descriptionLength":231,"readmeSize":232},264,4083,{"closedIssues90d":8,"forks":234,"hasChangelog":228,"openIssues90d":8,"pushedAt":235,"stars":236},1,1777544653000,2,{"hasNpmPackage":228,"license":238,"smitheryVerified":228},"MIT",{"hasCi":228,"hasTests":228},{"updatedAt":241},1778696635807,{"basePath":243,"githubOwner":244,"githubRepo":245,"locale":18,"slug":13,"type":246},"skills/postmortem-solo","rockscy","solo-skills","skill",null,{"evaluate":249,"extract":251},{"promptVersionExtension":208,"promptVersionScoring":209,"score":212,"tags":250,"targetMarket":219,"tier":220},[215,216,217,218],{"commitSha":252},"HEAD",{"repoId":254},"kd74cxyv8jz07d5s5wewf3nzcx86mx2v",{"_creationTime":256,"_id":254,"identity":257,"providers":258,"workflow":333},1778696558241.7397,{"githubOwner":244,"githubRepo":245,"sourceUrl":14},{"classify":259,"discover":317,"github":320},{"commitSha":252,"extensions":260},[261,272,280,288,296,301,309],{"basePath":262,"description":263,"displayName":264,"installMethods":265,"rationale":266,"selectedPaths":267,"source":271,"sourceLanguage":18,"type":246},"skills/bug-from-user","Convert a vague user complaint into a reproducible bug report a solo dev can act on. Use when the user pastes a confusing customer message, says \"user says it's broken but I can't repro\", \"this email makes no sense\", or wants to triage a bug report.","bug-from-user",{"claudeCode":12},"SKILL.md frontmatter at skills/bug-from-user/SKILL.md",[268],{"path":269,"priority":270},"SKILL.md","mandatory","rule",{"basePath":273,"description":274,"displayName":275,"installMethods":276,"rationale":277,"selectedPaths":278,"source":271,"sourceLanguage":18,"type":246},"skills/changelog-from-commits","Generate a user-facing CHANGELOG entry from raw git log output. Use when the user is preparing a release, says \"what changed since last version\", asks to write release notes, or wants to summarize a batch of commits for end users.","changelog-from-commits",{"claudeCode":12},"SKILL.md frontmatter at skills/changelog-from-commits/SKILL.md",[279],{"path":269,"priority":270},{"basePath":281,"description":282,"displayName":283,"installMethods":284,"rationale":285,"selectedPaths":286,"source":271,"sourceLanguage":18,"type":246},"skills/email-customer","Draft a polite-but-firm reply to a tricky customer email — refund request, scope creep, complaint, billing dispute. Use when the user pastes a customer email and asks for a reply, mentions \"how do I respond\", \"user is asking for a refund\", \"they want a discount\", or any awkward customer-facing communication.","email-customer",{"claudeCode":12},"SKILL.md frontmatter at skills/email-customer/SKILL.md",[287],{"path":269,"priority":270},{"basePath":289,"description":290,"displayName":291,"installMethods":292,"rationale":293,"selectedPaths":294,"source":271,"sourceLanguage":18,"type":246},"skills/launch-tweet","Draft a launch tweet or short thread for a solo product launch on X / Twitter. Use when the user is shipping something (new product, major feature, side project) and asks for a launch post, \"help me announce X\", or mentions Product Hunt / Show HN / X launch.","launch-tweet",{"claudeCode":12},"SKILL.md frontmatter at skills/launch-tweet/SKILL.md",[295],{"path":269,"priority":270},{"basePath":243,"description":10,"displayName":13,"installMethods":297,"rationale":298,"selectedPaths":299,"source":271,"sourceLanguage":18,"type":246},{"claudeCode":12},"SKILL.md frontmatter at skills/postmortem-solo/SKILL.md",[300],{"path":269,"priority":270},{"basePath":302,"description":303,"displayName":304,"installMethods":305,"rationale":306,"selectedPaths":307,"source":271,"sourceLanguage":18,"type":246},"skills/ship-decision","Force a fast, regret-minimizing product decision when a solo founder is stuck choosing between options. Use when the user is paralyzed by a binary or tri-way choice (build A vs B, ship now vs polish, free vs paid, etc.), says \"I can't decide\", \"should I\", or asks for a sanity check on a roadmap call.","ship-decision",{"claudeCode":12},"SKILL.md frontmatter at skills/ship-decision/SKILL.md",[308],{"path":269,"priority":270},{"basePath":310,"description":311,"displayName":312,"installMethods":313,"rationale":314,"selectedPaths":315,"source":271,"sourceLanguage":18,"type":246},"skills/standup-solo","Run a 5-minute personal standup for a solo dev — what shipped yesterday, what's blocked, what's next today. Use when the user asks for a daily check-in, says \"what should I work on today\", \"what did I do yesterday\", or wants to break out of a productivity slump.","standup-solo",{"claudeCode":12},"SKILL.md frontmatter at skills/standup-solo/SKILL.md",[316],{"path":269,"priority":270},{"sources":318},[319],"manual",{"closedIssues90d":8,"description":321,"forks":234,"license":238,"openIssues90d":8,"pushedAt":235,"readmeSize":232,"stars":236,"topics":322},"Claude Code skills for people who ship alone. 7 bilingual (EN+中文) skills for solo founders and indie devs: launch tweets, customer emails, decision frameworks, postmortems, and more.",[323,324,325,326,327,328,329,330,331,332],"ai-agents","awesome-list","bilingual","claude-code","claude-skills","developer-tools","indie-hacker","llm","productivity","solo-founder",{"classifiedAt":334,"discoverAt":335,"extractAt":336,"githubAt":336,"updatedAt":334},1778696562075,1778696558241,1778696560238,[217,216,218,215],{"evaluatedAt":241,"extractAt":339,"updatedAt":340},1778696562316,1778696725493,[],[343,374,404,432,464,496],{"_creationTime":344,"_id":345,"community":346,"display":347,"identity":353,"providers":358,"relations":367,"tags":370,"workflow":371},1778699018122.8042,"k17abp7zvtjnjpkkgy6mns5tbn86m7kr",{"reviewCount":8},{"description":348,"installMethods":349,"name":351,"sourceUrl":352},"Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.",{"claudeCode":350},"wshobson/agents","Postmortem Writing","https://github.com/wshobson/agents",{"basePath":354,"githubOwner":355,"githubRepo":356,"locale":18,"slug":357,"type":246},"plugins/incident-response/skills/postmortem-writing","wshobson","agents","postmortem-writing",{"evaluate":359,"extract":366},{"promptVersionExtension":208,"promptVersionScoring":209,"score":360,"tags":361,"targetMarket":219,"tier":220},96,[215,216,362,363,364,365],"blameless-culture","root-cause-analysis","documentation","reporting",{"commitSha":252,"license":238},{"parentExtensionId":368,"repoId":369},"k1777rhhwvnev0shetr3vsy9vh86n1ps","kd74de64zj0axtg5b8t7eqqe2x86nske",[362,364,216,215,365,363],{"evaluatedAt":372,"extractAt":373,"updatedAt":372},1778701584815,1778699018122,{"_creationTime":375,"_id":376,"community":377,"display":378,"identity":384,"providers":388,"relations":397,"tags":400,"workflow":401},1778675414637.841,"k1767n0q425w8paz4fgbwkrpfh86ndsa",{"reviewCount":8},{"description":379,"installMethods":380,"name":382,"sourceUrl":383},"Run an incident response workflow — triage, communicate, and write postmortem. Trigger with \"we have an incident\", \"production is down\", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.",{"claudeCode":381},"anthropics/knowledge-work-plugins","Incident Response","https://github.com/anthropics/knowledge-work-plugins",{"basePath":385,"githubOwner":386,"githubRepo":387,"locale":18,"slug":216,"type":246},"engineering/skills/incident-response","anthropics","knowledge-work-plugins",{"evaluate":389,"extract":395},{"promptVersionExtension":208,"promptVersionScoring":209,"score":390,"tags":391,"targetMarket":219,"tier":220},78,[216,392,215,393,394],"communication","workflow","production",{"commitSha":252,"license":396},"Apache-2.0",{"parentExtensionId":398,"repoId":399},"k17fvd5gvt4wg4g8wwmn1ntyz186nnzm","kd7d9w1wpah4hqnbsfzwwax72986mh7d",[392,216,215,394,393],{"evaluatedAt":402,"extractAt":403,"updatedAt":402},1778676969045,1778675414637,{"_creationTime":405,"_id":406,"community":407,"display":408,"identity":414,"providers":417,"relations":426,"tags":428,"workflow":429},1778696113180.8066,"k17ad4da3hgtxbv0bf8a1xea1986mkrj",{"reviewCount":8},{"description":409,"installMethods":410,"name":412,"sourceUrl":413},"Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.",{"claudeCode":411},"rampstackco/claude-skills","after-action-report","https://github.com/rampstackco/claude-skills",{"basePath":415,"githubOwner":416,"githubRepo":327,"locale":18,"slug":412,"type":246},"skills/after-action-report","rampstackco",{"evaluate":418,"extract":425},{"promptVersionExtension":208,"promptVersionScoring":209,"score":419,"tags":420,"targetMarket":219,"tier":424},100,[215,421,422,364,423],"retrospective","operations","incident-management","verified",{"commitSha":252},{"repoId":427},"kd7bebccrrd1xf6w868aggftrd86m86v",[364,423,422,215,421],{"evaluatedAt":430,"extractAt":431,"updatedAt":430},1778696189739,1778696113180,{"_creationTime":433,"_id":434,"community":435,"display":436,"identity":442,"providers":446,"relations":457,"tags":460,"workflow":461},1778695548458.391,"k17f88kn4jcq99brftj42t15jn86nzkz",{"reviewCount":8},{"description":437,"installMethods":438,"name":440,"sourceUrl":441},"Implement regenerative recovery using triage, scaffolding, and progressive rebuild. Covers damage assessment, wound classification, emergency stabilization, scar tissue management, and resilience strengthening for systems that have sustained structural damage. Use when a system has suffered an incident needing structured recovery, when a failed transformation left the system in a damaged intermediate state, when accumulated technical debt has caused partial failure, or when a system is functional but degraded and the degradation is worsening.\n",{"claudeCode":439},"pjt222/agent-almanac","repair-damage","https://github.com/pjt222/agent-almanac",{"basePath":443,"githubOwner":444,"githubRepo":445,"locale":18,"slug":440,"type":246},"skills/repair-damage","pjt222","agent-almanac",{"evaluate":447,"extract":456},{"promptVersionExtension":208,"promptVersionScoring":209,"score":448,"tags":449,"targetMarket":219,"tier":424},98,[450,451,452,453,454,216,455],"morphic","repair","regeneration","resilience","wound-healing","system-recovery",{"commitSha":252},{"parentExtensionId":458,"repoId":459},"k170h0janaa9kwn7cfgfz2ykss86mmh9","kd7aryv63z61j39n2td1aeqkvh86mh12",[216,450,452,451,453,455,454],{"evaluatedAt":462,"extractAt":463,"updatedAt":462},1778700660199,1778695548458,{"_creationTime":465,"_id":466,"community":467,"display":468,"identity":474,"providers":479,"relations":489,"tags":492,"workflow":493},1778692159341.6611,"k174s36edj2zjzvat6r6h5rqdd86m6wk",{"reviewCount":8},{"description":469,"installMethods":470,"name":472,"sourceUrl":473},"Elite incident response and legal compliance guidance for data breaches under GDPR Articles 33 & 34. Use when: (1) User reports a data breach or security incident, (2) User asks about breach notification obligations or deadlines, (3) User mentions \"72 hours\", Art. 33, Art. 34, or notification requirements, (4) Discussion involves security incidents affecting personal data, (5) User needs breach risk assessment using ENISA methodology, (6) User mentions \"Data Breach\" or \"Incident\" or \"Data Leakage\" or \"Ransomeware\" or \"Exfiltration\", (7) User needs to determine Controller vs Processor obligations, (8) Cross-border breach scenarios requiring Lead SA determination, (9) User needs a mitigation playbook or immediate response recommendations, (10) User needs to generate audit-ready breach documentation (.docx).\n",{"claudeCode":471},"lawvable/awesome-legal-skills","GDPR Breach Response Sentinel","https://github.com/lawvable/awesome-legal-skills",{"basePath":475,"githubOwner":476,"githubRepo":477,"locale":18,"slug":478,"type":246},"skills/gdpr-breach-sentinel-oliver-schmidt-prietz","lawvable","awesome-legal-skills","gdpr-breach-sentinel-oliver-schmidt-prietz",{"evaluate":480,"extract":487},{"promptVersionExtension":208,"promptVersionScoring":209,"score":448,"tags":481,"targetMarket":219,"tier":424},[482,483,484,485,216,486],"gdpr","legal","compliance","data-breach","regulation",{"commitSha":252,"license":488},"AGPL-3.0",{"parentExtensionId":490,"repoId":491},"k17ft5x8rpkn75h77cqmbj5gzn86nz20","kd7334qxfqk8gjtm28t64b58cn86nkk0",[484,485,482,216,483,486],{"evaluatedAt":494,"extractAt":495,"updatedAt":494},1778693413434,1778692159341,{"_creationTime":497,"_id":498,"community":499,"display":500,"identity":506,"providers":510,"relations":518,"tags":521,"workflow":522},1778675056600.2212,"k17fpzkh7rzjqcdyhkrpnp4f0n86nx59",{"reviewCount":8},{"description":501,"installMethods":502,"name":504,"sourceUrl":505},"Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2/ISO 27001/HIPAA/GDPR), 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.",{"claudeCode":503},"alirezarezvani/claude-skills","CISO Advisor","https://github.com/alirezarezvani/claude-skills",{"basePath":507,"githubOwner":508,"githubRepo":327,"locale":18,"slug":509,"type":246},"c-level-advisor/skills/ciso-advisor","alirezarezvani","ciso-advisor",{"evaluate":511,"extract":517},{"promptVersionExtension":208,"promptVersionScoring":209,"score":448,"tags":512,"targetMarket":219,"tier":424},[513,514,515,484,516,216],"security","ciso","risk-management","strategy",{"commitSha":252,"license":238},{"parentExtensionId":519,"repoId":520},"k17cfc0w65zrpv9bnzn3b6xayx86m40f","kd7ff9s1w43mfyy1n7hf87816186m6px",[514,484,216,515,513,516],{"evaluatedAt":523,"extractAt":524,"updatedAt":523},1778677266271,1778675056600]