[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756NWCNDQEPD368J1AMSPTY":3,"skill-same:01M756NWCNDQEPD368J1AMSPTY":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M756NWCNDQEPD368J1AMSPTY","computer-specs",null,"Profile the hardware of the machine you're running on — RAM, CPU(s), GPU(s), and free disk space — then describe it in plain natural language. Use whenever the user asks about their computer's specs or hardware — e.g. \"what are my specs\", \"what's my hardware\", \"how much RAM \u002F how many cores \u002F what GPU do I have\", \"system profile\", \"spec out this machine\", or \"can my computer handle \u003Cworkload>\".","SoftwareAssassin2\u002FPlugins","SoftwareAssassin2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38842958?v=4","01M756NS55ARTH4KENH9HKVRNZ","01M756NS6B3QB1XR6QN6BPMR76",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcomputer-specs\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: computer-specs\ndescription: Profile the hardware of the machine you're running on — RAM, CPU(s), GPU(s), and free disk space — then describe it in plain natural language. Use whenever the user asks about their computer's specs or hardware — e.g. \"what are my specs\", \"what's my hardware\", \"how much RAM \u002F how many cores \u002F what GPU do I have\", \"system profile\", \"spec out this machine\", or \"can my computer handle \u003Cworkload>\".\n---\n\n# computer-specs\n\nReport the running machine's hardware, in natural language.\n\n## How\n\n1. **Run the bundled profiler:** `bash \"${CLAUDE_PLUGIN_ROOT:-plugins\u002Fcomputer-specs}\u002Fspecs.sh\"`. It is cross-platform (macOS + Linux), read-only, and degrades gracefully — a field it can't determine comes back as `unknown` rather than failing. It prints a labeled block:\n   ```\n   OS:    \u003Cos \u002F kernel \u002F arch>\n   CPU:   \u003Cmodel — cores\u002Fthreads>\n   RAM:   \u003Ctotal>\n   GPU:   \u003Cchipset(s)>\n   Disk:  root volume \u002F — \u003Ctotal> total, \u003Cfree> free\n   ```\n2. **Translate that block into a natural-language profile** — don't just echo it back. Open with a one-line headline (e.g. *\"You're on a well-specced Apple Silicon Mac…\"*), then describe the RAM, CPU(s), GPU(s), and free disk in prose. If the user asked in the context of a workload (\"can it handle X?\"), answer that using the numbers.\n3. If a field is `unknown` (a tool wasn't available on this OS), **say so plainly** — never guess or invent a value.\n\n## Notes\n\n- **Read-only.** The script only queries hardware; it changes nothing.\n- Keep it conversational and brief — a profile, not a data dump.\n- Covers macOS and Linux; on any other OS it reports that plainly.\n","# computer-specs\n\nReport the running machine's hardware, in natural language.\n\n## How\n\n1. **Run the bundled profiler:** `bash \"${CLAUDE_PLUGIN_ROOT:-plugins\u002Fcomputer-specs}\u002Fspecs.sh\"`. It is cross-platform (macOS + Linux), read-only, and degrades gracefully — a field it can't determine comes back as `unknown` rather than failing. It prints a labeled block:\n   ```\n   OS:    \u003Cos \u002F kernel \u002F arch>\n   CPU:   \u003Cmodel — cores\u002Fthreads>\n   RAM:   \u003Ctotal>\n   GPU:   \u003Cchipset(s)>\n   Disk:  root volume \u002F — \u003Ctotal> total, \u003Cfree> free\n   ```\n2. **Translate that block into a natural-language profile** — don't just echo it back. Open with a one-line headline (e.g. *\"You're on a well-specced Apple Silicon Mac…\"*), then describe the RAM, CPU(s), GPU(s), and free disk in prose. If the user asked in the context of a workload (\"can it handle X?\"), answer that using the numbers.\n3. If a field is `unknown` (a tool wasn't available on this OS), **say so plainly** — never guess or invent a value.\n\n## Notes\n\n- **Read-only.** The script only queries hardware; it changes nothing.\n- Keep it conversational and brief — a profile, not a data dump.\n- Covers macOS and Linux; on any other OS it reports that plainly.\n",{"name":5,"description":7},"main","d01d9bbc815bb1c77bf61f24152dd84fca29ca41","plugins\u002Fcomputer-specs","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2","2026-07-23 21:04:05",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add SoftwareAssassin2\u002FPlugins --skill computer-specs",{"tool":35,"command":36},"bunx","bunx skills add SoftwareAssassin2\u002FPlugins --skill computer-specs",{"tool":38,"command":39},"pnpm","pnpm dlx skills add SoftwareAssassin2\u002FPlugins --skill computer-specs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcomputer-specs\u002FSKILL.md",true,[43],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"specs.sh","SCRIPT","脚本",3617,"https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcomputer-specs\u002Fspecs.sh",[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M756R6NM9JCPKPDDEYYQ8756","wendy","Summon Wendy, a performance coach modeled on Wendy Rhoades from Billions, when the user invokes \u002Fwendy or asks for Wendy by name, or explicitly asks to get his head right — tilting, stalling, spiraling, avoiding, flat, or needing to lock in before a hard push. Wendy works the operator's state, never the plan. Do NOT use for feedback on strategies, plans, or decisions, and do not trigger uninvited.","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwendy\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M756R3CHWZP6F4XEYZAHD0E7","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to .\u002Fdocs\u002Fubiquitous-language.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\". Forked from Matt Pocock's \"ubiquitous-language\" skill.","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fubiquitous-language\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M756QYHCNZKH4EW9CGJPB4GT","tdd","Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions \"red-green-refactor\", wants integration tests, or asks for test-first development. Forked from Matt Pocock's \"tdd\" skill.","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M756QSQJ0WCP4HPW3SHBAFD5","voice","Speak Claude's responses aloud through the native OS voice (macOS `say`) — on demand via \u002Fspeak:speak (last response) or \u002Fspeak:specify (pick one), or automatically on every response via a toggleable Stop hook. Works locally on a Mac and, through a manually started host listener, from inside a Dev Container. Use when the user wants responses read aloud \u002F spoken \u002F voice output, wants auto-speak turned on or off, or asks whether the speak install is healthy.","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fspeak\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M756QGEMD1DF8YQ22FJ5DCAE","merge-request:review","Review a pull\u002Fmerge request (by id) or batch-review every open one against Chris's own engineering standards, staging high-signal findings to .data\u002Fmerge\u002F\u003CID>.md for later posting. Fetches head SHAs and applies the \"Reviewed at commit\" skip check BEFORE any checkout, resolves the head fork-safely, builds\u002Ftests it in a dedicated worktree, and treats a failing build\u002Fcheckout as the top blocking finding. First runs \u002Fdetect-source-control and hard-stops when the forge is unsupported. Use as \"review the PR\", \"review the open MRs\", \"any PRs need my eyes\", \"review \u003Cid>\".","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmerge-request\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M756Q7S9ABZSR6AT45GEDA9T","merge-request:post-findings","Take the findings staged by \u002Fmerge-request:review in .data\u002Fmerge\u002F\u003CID>.md and, with per-finding approval, post the approved ones to the forge as inline comments (general-comment fallback when a finding has no valid diff location) — or formally sign off a clean PR\u002FMR with a single \"Looks good.\" First runs \u002Fdetect-source-control and hard-stops when the forge is unsupported. Nothing reaches the forge except through the bundled scripts. Also runs a propose-then-confirm learned-preferences loop that teaches \u002Fmerge-request:review what you value (Don't-raise \u002F Wording \u002F Confirmed-valued), and records skipped findings to the artifact's","https:\u002F\u002Fgithub.com\u002FSoftwareAssassin2\u002FPlugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmerge-request\u002Fskills\u002Fpost-findings\u002FSKILL.md",[],[]]