[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DJK0D7GN2THPKEYQTXSAYM":3,"skill-same:01M6DJK0D7GN2THPKEYQTXSAYM":93},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":61},"01M6DJK0D7GN2THPKEYQTXSAYM","thermo-nuclear-review",null,"Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch\u002FPR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.","danchamorro\u002Fpi-agent-toolkit","danchamorro","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F19739839?v=4","01M6DJG9M33RM5P1GFCFG9DSJE","Dan Chamorro","01M6DJG9QYKDT43HSTFG1JPK82",17,"MIT","https:\u002F\u002Fgithub.com\u002Fdanchamorro\u002Fpi-agent-toolkit\u002Fblob\u002Fmain\u002Fdotfiles\u002Fpersonal-skills\u002Fengineering\u002Fthermo-nuclear-review\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"review","thermo nuclear review","nuclear","security","pr","issues","deep review","audit","branch","use","diff","thermonuclear","gate","deep","feature","2026-11-10 10:12:30",false,"---\nname: thermo-nuclear-review\ndescription: Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch\u002FPR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.\ndisable-model-invocation: true\n---\n\n# Thermo Nuclear Review\n\nUse this skill for a comprehensive security and correctness audit of a checked-out branch.\n\n## Prompt\n\nYou are a security expert performing a comprehensive review of a checked out branch. Audit this branch and its changes extremely thoroughly for bugs, changes that break existing features\u002Ffunctionality, and security vulnerabilities. Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through.\n\n# Scope\nONLY report issues related to code that is being ADDED or MODIFIED in this PR.\nFocus on changes in the diff.\nDO NOT report vulnerabilities in existing code that is not being changed.\n\n# Guidelines\n\n## Breaking Functionality Guidelines\nThis is a complex codebase, with many cross-package\u002Fmodule dependencies. Often simple code changes in one place have subtle interactions that break functionality elsewhere. You MUST be extremely thorough in tracing through possible side effects of the changes.\n\n## Breaking Devex Guidelines\nIt can be easy to break developers' ability to run \u002F build the code locally. You MUST catch changes that will impact users' developer experience. Some examples (not exhaustive):\n- Modifying how secrets are read \u002F where they are read from\n- Updating environment variable names \u002F adding environment variables\n- Remapping ports \u002F networking\n- Adding scripts that must be run for certain functionality to continue working. Broadly speaking these are changes that will modify the way developers currently run \u002F build the code. This does not include changes that introduce new alternative ways to run\u002Fbuild things. Adding dependencies with package managers does not count as a devex breaking change, unless it requires the user to do some very new thing that is not part of their normal development workflow, like manually installing software off of a website \u002F App Store.\n\n## Feature Leak Guidelines\nThe codebase might carefully gate features behind feature flags or internal-only checks. You MUST NOT allow any features that are meant to be behind a feature gate leak. These leaks are often subtle. Be VERY careful and thorough.\n\n## Intended Breakage Guidelines\nIf you identify a high risk finding, but the intent of the branch is to introduce that finding – e.g. break some functionality, remove a feature flag, remove a safeguard – AND the scope of the change is well constrained, you SHOULD NOT waste the author's time by reporting the issue to them. However, if you believe it is likely that they are not aware of the full implications of their change, or you are worried that they are under-weighting the negative impacts (extreme example: a developer pushes a PR titled \"Delete the database\"), or you are worried that the change is actually malicious, you should still report the finding.\n\n## Over-reporting Guidelines\nIf you report issues as High priority when they are not in fact high priority \u002F meaningful issues, devs will lose trust in you and stop listening to you over time.\nNEVER misreport the priority \u002F importance of issues. Be extremely thorough in tracing issues end-to-end to gain complete, and total confidence before reporting.\n\n# Final Response\nIF you have medium-to-high priority \u002F risk findings, and there is a PR for this branch, then check the PR\u002FMR discussion using gh\u002Fglab cli to see if there are comments from BugBot or others present.\nIf so, take their findings into account. If they found issues you missed, evaluate them to determine if they are valid and include them in your report. If they found some of the same issues you did, see if there is anything from their findings that are worth incorporating into your response.\nFlag issues found by BugBot or others in the PR\u002FMR discussion that you include in your report.\n\n\n# Critical Rules\n- NEVER present issues with unfinished research. E.g. Never say something like, \"The client has issue X, but if handled in the backend then this is ok.\" if you have access to the backend code and can check for yourself.\n- You MUST wait to check the PR\u002FMR discussion until AFTER you have performed your audit. This way you have fresh eyes while you review.\n- Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through.\n","# Thermo Nuclear Review\n\nUse this skill for a comprehensive security and correctness audit of a checked-out branch.\n\n## Prompt\n\nYou are a security expert performing a comprehensive review of a checked out branch. Audit this branch and its changes extremely thoroughly for bugs, changes that break existing features\u002Ffunctionality, and security vulnerabilities. Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through.\n\n# Scope\nONLY report issues related to code that is being ADDED or MODIFIED in this PR.\nFocus on changes in the diff.\nDO NOT report vulnerabilities in existing code that is not being changed.\n\n# Guidelines\n\n## Breaking Functionality Guidelines\nThis is a complex codebase, with many cross-package\u002Fmodule dependencies. Often simple code changes in one place have subtle interactions that break functionality elsewhere. You MUST be extremely thorough in tracing through possible side effects of the changes.\n\n## Breaking Devex Guidelines\nIt can be easy to break developers' ability to run \u002F build the code locally. You MUST catch changes that will impact users' developer experience. Some examples (not exhaustive):\n- Modifying how secrets are read \u002F where they are read from\n- Updating environment variable names \u002F adding environment variables\n- Remapping ports \u002F networking\n- Adding scripts that must be run for certain functionality to continue working. Broadly speaking these are changes that will modify the way developers currently run \u002F build the code. This does not include changes that introduce new alternative ways to run\u002Fbuild things. Adding dependencies with package managers does not count as a devex breaking change, unless it requires the user to do some very new thing that is not part of their normal development workflow, like manually installing software off of a website \u002F App Store.\n\n## Feature Leak Guidelines\nThe codebase might carefully gate features behind feature flags or internal-only checks. You MUST NOT allow any features that are meant to be behind a feature gate leak. These leaks are often subtle. Be VERY careful and thorough.\n\n## Intended Breakage Guidelines\nIf you identify a high risk finding, but the intent of the branch is to introduce that finding – e.g. break some functionality, remove a feature flag, remove a safeguard – AND the scope of the change is well constrained, you SHOULD NOT waste the author's time by reporting the issue to them. However, if you believe it is likely that they are not aware of the full implications of their change, or you are worried that they are under-weighting the negative impacts (extreme example: a developer pushes a PR titled \"Delete the database\"), or you are worried that the change is actually malicious, you should still report the finding.\n\n## Over-reporting Guidelines\nIf you report issues as High priority when they are not in fact high priority \u002F meaningful issues, devs will lose trust in you and stop listening to you over time.\nNEVER misreport the priority \u002F importance of issues. Be extremely thorough in tracing issues end-to-end to gain complete, and total confidence before reporting.\n\n# Final Response\nIF you have medium-to-high priority \u002F risk findings, and there is a PR for this branch, then check the PR\u002FMR discussion using gh\u002Fglab cli to see if there are comments from BugBot or others present.\nIf so, take their findings into account. If they found issues you missed, evaluate them to determine if they are valid and include them in your report. If they found some of the same issues you did, see if there is anything from their findings that are worth incorporating into your response.\nFlag issues found by BugBot or others in the PR\u002FMR discussion that you include in your report.\n\n\n# Critical Rules\n- NEVER present issues with unfinished research. E.g. Never say something like, \"The client has issue X, but if handled in the backend then this is ok.\" if you have access to the backend code and can check for yourself.\n- You MUST wait to check the PR\u002FMR discussion until AFTER you have performed your audit. This way you have fresh eyes while you review.\n- Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through.\n",{"name":5,"description":7,"disable-model-invocation":39},true,"main","b762a116c343f012c9b23009a7f2d9af217b8b00","dotfiles\u002Fpersonal-skills\u002Fengineering\u002Fthermo-nuclear-review",1,"https:\u002F\u002Fgithub.com\u002Fdanchamorro\u002Fpi-agent-toolkit","https:\u002F\u002Fgithub.com\u002Fdanchamorro","https:\u002F\u002Fdanchamorro.com","Python engineer by day, SaaS founder by night","2026-08-24 04:44:54",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":39},[51,54,57],{"tool":52,"command":53},"npx","npx skills add danchamorro\u002Fpi-agent-toolkit --skill thermo-nuclear-review",{"tool":55,"command":56},"bunx","bunx skills add danchamorro\u002Fpi-agent-toolkit --skill thermo-nuclear-review",{"tool":58,"command":59},"pnpm","pnpm dlx skills add danchamorro\u002Fpi-agent-toolkit --skill thermo-nuclear-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanchamorro\u002Fpi-agent-toolkit\u002Fblob\u002Fmain\u002Fdotfiles\u002Fpersonal-skills\u002Fengineering\u002Fthermo-nuclear-review\u002FSKILL.md",[62,67,73,77,81,85,89],{"path":63,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"LICENSE","许可证",1063,"https:\u002F\u002Fgithub.com\u002Fdanchamorro\u002Fpi-agent-toolkit\u002Fblob\u002Fmain\u002Fdotfiles\u002Fpersonal-skills\u002Fengineering\u002Fthermo-nuclear-review\u002FLICENSE",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fadditional_features.md","REFERENCE","参考文档",10179,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fprotocolsio-integration\u002Freferences\u002Fadditional_features.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fauthentication.md",3374,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fprotocolsio-integration\u002Freferences\u002Fauthentication.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fdiscussions.md",6945,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fprotocolsio-integration\u002Freferences\u002Fdiscussions.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Ffile_manager.md",11106,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fprotocolsio-integration\u002Freferences\u002Ffile_manager.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fprotocols_api.md",7977,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fprotocolsio-integration\u002Freferences\u002Fprotocols_api.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fworkspaces.md",8128,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fprotocolsio-integration\u002Freferences\u002Fworkspaces.md",[94,130,148,163,195,208],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":110,"publishedAt":34},"01M6DJKPTTD68WF0YJRZ4XNRVH","1password-developer","Work with 1Password developer features including SSH key management, the SSH agent, 1Password Environments for secrets injection, and the op CLI. Use this skill whenever the user mentions 1Password, op CLI, 1Password SSH agent, 1Password Environments, secret references, op run, op inject, or wants to manage SSH keys through 1Password, secure .env files with 1Password, or inject secrets at runtime. Also trigger when the user wants to stop storing plaintext secrets on disk or asks about securing developer credentials.","https:\u002F\u002Fgithub.com\u002Fdanchamorro\u002Fpi-agent-toolkit\u002Fblob\u002Fmain\u002Fdotfiles\u002Fpersonal-skills\u002Fsecurity-environment\u002F1password-developer\u002FSKILL.md",[100,105],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[111,112,113,114,115,116,117,118,119,120,28,121,122,123,124,125,126,127,128,129],"1password developer","developer","1password","disk","trigger","env","runtime","references","manage","files","management","work","secrets","credentials","ssh","injection","run","secure","cli",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":34},"01M6DJKJ8FW4D1R7009DBJAN0Z","plan-reviewer","Use when creating, refining, or reviewing implementation plans, migration plans, refactoring proposals, feature plans, implementation trackers, or committable phase plans; especially when turning a rough plan into executable phases or checking whether a plan is concrete, testable, safe, dependency-aware, and suitable for parallel work.","https:\u002F\u002Fgithub.com\u002Fdanchamorro\u002Fpi-agent-toolkit\u002Fblob\u002Fmain\u002Fdotfiles\u002Fpersonal-skills\u002Fplanning\u002Fplan-reviewer\u002FSKILL.md",[],[137,138,139,33,140,141,142,28,143,122,144,145,146,147],"plan reviewer","reviewer","plan","implementation","migration","dependency","proposals","parallel","refactoring","safe","plans",{"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":154,"publishedAt":34},"01M6DJKC1N9DDSGDNE8AZJ4NZ0","brainstorm","Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions \"brainstorm\".","https:\u002F\u002Fgithub.com\u002Fdanchamorro\u002Fpi-agent-toolkit\u002Fblob\u002Fmain\u002Fdotfiles\u002Fpersonal-skills\u002Fplanning\u002Fbrainstorm\u002FSKILL.md",[],[150,155,156,157,158,28,27,159,139,160,161,162],"interview","get","shared","stress-test","decision","test","design","user",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":175,"publishedAt":34},"01M6DJK7Z2833PKW7PHQR7P956","youtube-video-context","Use this skill whenever the user gives a YouTube URL and asks to summarize, digest, analyze, extract transcript\u002Fcontext, decide whether a video is worth watching, or understand what a video is about. Prefer the summarize CLI for YouTube\u002Fvideo context instead of web search. Use Codex as the default summarize backend when possible, and use the local Whisper large-v3 model for transcription fallback. Do not use this for ordinary web pages; use the installed web-access tools for webpage research.","https:\u002F\u002Fgithub.com\u002Fdanchamorro\u002Fpi-agent-toolkit\u002Fblob\u002Fmain\u002Fdotfiles\u002Fpersonal-skills\u002Fmedia\u002Fyoutube-video-context\u002FSKILL.md",[169,172],{"categoryNo":170,"categoryName":171,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":173,"categoryName":174,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000021","资料检索与研究",[176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,28,194],"youtube video context","youtube","context","Video","web search","access","dlp","search","cpp","model","local","as","v3","pages","yt-dlp","local whisper","do","default","decide",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":34},"01M6DJK3RXFZP1M42D0MEG19D8","thermos","Launch both thermo-nuclear review subagents in parallel. Use for thermos, double thermo review, or combined bug\u002Fsecurity and code-quality branch audits.","https:\u002F\u002Fgithub.com\u002Fdanchamorro\u002Fpi-agent-toolkit\u002Fblob\u002Fmain\u002Fdotfiles\u002Fpersonal-skills\u002Fengineering\u002Fthermos\u002FSKILL.md",[],[197,202,21,203,28,27,204,144,205,206,207,22,19],"subagents","bug","quality","code-quality","code","launch",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":34},"01M6DJJVKQGPEC8Q059CHF2TDQ","thermo-nuclear-code-quality-review","Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.","https:\u002F\u002Fgithub.com\u002Fdanchamorro\u002Fpi-agent-toolkit\u002Fblob\u002Fmain\u002Fdotfiles\u002Fpersonal-skills\u002Fengineering\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[214],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},[216,21,19,204,206,217,218,26,219,127,120,32,220,221,28,30],"code quality","thermo nuclear code quality review","quality review","code quality audit","maintainability","growth"]