[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R9FE31EDCWAFG6XM7XPW8Z":3,"skill-same:01M6R9FE31EDCWAFG6XM7XPW8Z":72},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6R9FE31EDCWAFG6XM7XPW8Z","thermo-nuclear-code-quality-review",null,"Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked via Task after a parent gathers diff and file contents. Loads the rubric from the `thermo-nuclear-code-quality-review` skill in the cursor-team-kit plugin.","Nairon-AI\u002Fagentic-starter-pack","Nairon-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260662138?v=4","01M6R8PZ1Y8CSQGFN61VACZGTH","Nairon AI","01M6R8PZ6184VR3BA88YZFBC3N",4,"MIT","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fengineering\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"code quality","review","code","thermo nuclear code quality review","nuclear","quality","quality review","kit","cursor-team","loads","via","structure","task","diff","cursor","code-quality","team","audit","file","plugin","2026-11-10 10:12:30",false,"---\nname: thermo-nuclear-code-quality-review\ndescription: Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked via Task after a parent gathers diff and file contents. Loads the rubric from the `thermo-nuclear-code-quality-review` skill in the cursor-team-kit plugin.\n---\n\n# Thermo-Nuclear Code Quality Review\n\nYou are a **Task subagent**. The parent agent already collected git output and changed-file contents; your prompt is the **user message** with labeled sections (typically `### Git \u002F diff output` and `### Changed file contents`).\n\n## Rubric\n\n1. Load the `thermo-nuclear-code-quality-review` skill (shipped in the cursor-team-kit plugin) and treat its `SKILL.md` as the **complete** rubric - tone, approval bar, output ordering, code-judo \u002F 1k-line \u002F spaghetti rules.\n2. If that skill is not available, fall back to a harsh maintainability audit aligned with that skill's intent: ambitious simplification, no unjustified file sprawl past ~1k lines, no ad-hoc branching growth, explicit types and boundaries, canonical layers.\n3. Enforce **Jane Street house style** for naming: prefer precise verb-object names that state the real transformation or effect. Flag terse lifecycle labels such as `ingest`, `announce`, `hydrate`, and `finalize` when they hide what the code actually does. Trace call sites and task-identity behavior before proposing renames.\n\n## Work\n\n- Apply the rubric **only** to what the diff and contents show. Trace cross-file impact when the change touches module boundaries.\n- Output in the **priority order** the rubric specifies. Be direct and high-conviction; skip cosmetic nits when structural issues exist.\n- Do **not** spawn nested subagents unless the user or parent explicitly asks.\n\n## Parent orchestration\n\nTypical flow: in **one** message, run two `Task` calls in parallel - `subagent_type: \"shell\"` and `subagent_type: \"explore\"` - to collect `git diff \u003Cbase>...HEAD` output and full contents of changed files (default base `main`). Then invoke this agent with `subagent_type: \"thermo-nuclear-code-quality-review\"` and a user prompt containing `### Git \u002F diff output` and `### Changed file contents`.\n","# Thermo-Nuclear Code Quality Review\n\nYou are a **Task subagent**. The parent agent already collected git output and changed-file contents; your prompt is the **user message** with labeled sections (typically `### Git \u002F diff output` and `### Changed file contents`).\n\n## Rubric\n\n1. Load the `thermo-nuclear-code-quality-review` skill (shipped in the cursor-team-kit plugin) and treat its `SKILL.md` as the **complete** rubric - tone, approval bar, output ordering, code-judo \u002F 1k-line \u002F spaghetti rules.\n2. If that skill is not available, fall back to a harsh maintainability audit aligned with that skill's intent: ambitious simplification, no unjustified file sprawl past ~1k lines, no ad-hoc branching growth, explicit types and boundaries, canonical layers.\n3. Enforce **Jane Street house style** for naming: prefer precise verb-object names that state the real transformation or effect. Flag terse lifecycle labels such as `ingest`, `announce`, `hydrate`, and `finalize` when they hide what the code actually does. Trace call sites and task-identity behavior before proposing renames.\n\n## Work\n\n- Apply the rubric **only** to what the diff and contents show. Trace cross-file impact when the change touches module boundaries.\n- Output in the **priority order** the rubric specifies. Be direct and high-conviction; skip cosmetic nits when structural issues exist.\n- Do **not** spawn nested subagents unless the user or parent explicitly asks.\n\n## Parent orchestration\n\nTypical flow: in **one** message, run two `Task` calls in parallel - `subagent_type: \"shell\"` and `subagent_type: \"explore\"` - to collect `git diff \u003Cbase>...HEAD` output and full contents of changed files (default base `main`). Then invoke this agent with `subagent_type: \"thermo-nuclear-code-quality-review\"` and a user prompt containing `### Git \u002F diff output` and `### Changed file contents`.\n",{"name":5,"description":7},"main","c9d0c408715983e993b2f9ebffdbfa7f10153bcb","engineering\u002Fthermo-nuclear-code-quality-review",0,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack","https:\u002F\u002Fgithub.com\u002FNairon-AI","https:\u002F\u002Fwww.naironai.com\u002F","Building the future of Work","2026-09-20 17:40:05",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add Nairon-AI\u002Fagentic-starter-pack --skill thermo-nuclear-code-quality-review",{"tool":64,"command":65},"bunx","bunx skills add Nairon-AI\u002Fagentic-starter-pack --skill thermo-nuclear-code-quality-review",{"tool":67,"command":68},"pnpm","pnpm dlx skills add Nairon-AI\u002Fagentic-starter-pack --skill thermo-nuclear-code-quality-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fengineering\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",true,[],[73,107,128,149,169,190],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":87,"publishedAt":44},"01M6RBCG630Y8X99XWR9Q4GYNY","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-shape\u002FSKILL.md",[79,84],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[88,89,90,91,92,42,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"writing","writing shape","shape","notes","help","markdown","format","session","use","take","draft","article","material","it","about","quotes","at","candidate","when",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":115,"publishedAt":44},"01M6RBCCCB1KMF01P5SYGFWBSW","writing-fragments","Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions \"fragments\", \"ideate\", or \"raw material\" for writing.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-fragments\u002FSKILL.md",[113,114],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[88,116,117,118,119,120,95,96,121,35,122,99,123,100,124,125,126,127,106],"writing fragments","grilling","ideate","develop","user","document","ideas","as","sharp","claims","for","single",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":136,"publishedAt":44},"01M6RBC8V7NHHKMTAZB4BPXVYQ","writing-beats","Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-beats\u002FSKILL.md",[134,135],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[88,137,138,139,96,140,141,90,142,143,144,99,145,123,146,100,147,148,126,106],"writing beats","choose","write","assemble","only","journey","next","options","end","style","narrative","argument",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":157,"publishedAt":44},"01M6RBC58SG5Y5SC4ZV4ZNEFHC","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fstop-slop\u002FSKILL.md",[155,156],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[158,159,160,88,161,162,163,164,165,96,166,167,168,126,106],"stop","stop slop","slop","content","https","text","editing","remove","prose","patterns","drafts",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":177,"publishedAt":44},"01M6RBBJTTCJ7KZCP16G9JDFZH","humanizer","Remove signs of AI-generated writing from text. Use when editing or reviewing\ntext to make it sound more natural and human-written. Based on Wikipedia's\ncomprehensive \"Signs of AI writing\" guide. Detects and fixes patterns including:\ninflated symbolism, promotional language, superficial -ing analyses, vague\nattributions, em dash overuse, rule of three, AI vocabulary words, passive\nvoice, negative parallelisms, and filler phrases.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fhumanizer\u002FSKILL.md",[175,176],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},[171,88,26,178,163,179,139,180,181,165,182,183,167,184,185,186,187,188,189,106],"em dash","read","edit","generated","guide","opencode","three","human","make","wikipedia","vague","dash",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":44},"01M6RBBEQKJ5HRH8AV9J85QB1T","feedback","Prepare, deliver, and debrief timely interpersonal feedback using a question-first coaching flow, observable behavior, owned experience, and concrete impact. Use when drafting feedback, coaching managers, rehearsing a feedback conversation, praising specific behavior, or reviewing whether feedback landed.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Ffeedback\u002FSKILL.md",[],[192,197,198,199,200,201,96,202,203,204,205,206,106,207],"prepare","flow","first","question","behavior","conversation","coaching","debrief","impact","managers","deliver"]