[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E83EMEM0V0S342MBQVF0H8":3,"skill-same:01M7E83EMEM0V0S342MBQVF0H8":69},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7E83EMEM0V0S342MBQVF0H8","tailwind-spacing-audit",null,"Use when Tailwind spacing looks uneven or too wide: gap, space-x, margin, or padding mixed on navbars, toolbars, and flex rows.","tony\u002Fskills","tony","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F26336?v=4","01M72E5RNJ7SQV8F9KBM5RKRMN","Tony Narlock","01M7E7MBN5C6YZ4JJJ5Y82KBJG",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftailwind-spacing-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tailwind-spacing-audit\ndescription: >-\n  Use when Tailwind spacing looks uneven or too wide: gap, space-x, margin,\n  or padding mixed on navbars, toolbars, and flex rows.\nmetadata:\n  argument-hint: \"\u003Cfile-or-directory-to-audit>\"\n  source: \"plugins\u002Ftailwind\u002Fskills\u002Fspacing-audit\u002FSKILL.md\"\n---\n\n# Tailwind spacing audit\n\nDetect and fix inconsistent spacing in Tailwind CSS layouts. Most spacing\nbugs come from fragmented spacing authority: gap, margin, padding, and\nfixed widths all control the space between the same visual peers. Each\npair of adjacent items gets exactly one mechanism.\n\nUse `$ARGUMENTS` as the target scope. If it is empty and the user pasted\nmarkup, audit the paste. Otherwise ask which component or file to audit;\nwhen asking is not allowed, stop with the halted result below.\n\nAsk only through a question tool, and never when the user said not to\nask. Without a question tool, or after that instruction, asking is not\nallowed: decide per the steps below and end with no question.\n\nRun scripts from the project root so targets stay relative to the\nproject. Resolve `references\u002Fdetect.py` against this skill's directory,\nprint the absolute path once, and write it literally in each command,\nsince shell variables do not persist between Bash calls.\n\n## Workflow\n\n### Step 0: Detect framework and Tailwind version\n\nFind the template files in scope and the class attribute each uses:\n\n- `*.tsx`, `*.jsx`: `className=`\n- `*.vue`: `class=`, `:class=`\n- `*.svelte`, `*.astro`, `*.html`, `*.erb`, `*.php`, `*.twig`, `*.njk`,\n  `*.hbs`, `*.heex`, `*.mdx`, `*.liquid`: `class=`\n\nThe detect commands in `references\u002Fpatterns.md` run\n`references\u002Fdetect.py` and name an `rg` fallback. If neither runs,\nread the files in scope.\n\nRead the installed Tailwind version with the `version` command described\nin `references\u002Fpatterns.md`, run on the project root. If it prints\n`version: unknown`, say so in the result and keep `space-x` and\n`space-y` advice version-neutral.\n\n### Step 1: Structural audit\n\nScan the component and draw a spacing map in the list form shown under\nOutput: every spacing mechanism acting on the group the user cares\nabout. Then read the Detect command limits and Decision tree sections\nof `references\u002Fpatterns.md`, and only the pattern sections the findings\nmatch.\n\nCall out how many mechanisms act between visual peers, which items sit\nin different containers yet read as one group, and any fixed `w-*` on\nan item whose siblings size to content.\n\n### Step 2: Classify\n\nMatch each finding to a pattern in `references\u002Fpatterns.md`. Run that\npattern's detect command for codebase-wide scope. Each match needs a\nread in context before it counts. A command that returns nothing for a\nfile the user named is not a clean bill: read the file.\n\n### Step 3: Refactor\n\nPropose the changes as a diff or before\u002Fafter; edit files only when the\nuser asked to fix or apply them. For a pasted snippet, reply with the\ncode. Preserve existing breakpoints, and change only spacing and sizing\nclasses. Work in this order:\n\n1. Merge fragmented containers. Put one visual group in one flex\n   container with one `gap-*`. Remove the outer `me-*` and `ms-*` that\n   compensated for the split.\n2. Pick one authority per relationship. `gap-*` on the parent for\n   uniform spacing; margin on a child only for a deliberate exception;\n   padding only for space inside an item.\n3. Standardize peer envelopes. Peer buttons, links, and toggles\n   share one height class and one horizontal padding, and no `w-*`\n   unless every peer has the same one.\n4. Flatten single-child wrappers. Move the alignment classes onto\n   the child.\n5. Keep intentional breaks. A divider between nav groups is\n   deliberate, and so is the margin around it (`mx-*` on a `w-px` or\n   `\u003Chr>` element): keep both, never remove or shrink it, and list it as\n   a kept difference with the distance it produces. Ask before\n   normalizing a difference that may be design; when asking is not\n   allowed, keep the break and report it as a kept difference after the\n   findings, never as a finding, with no guessed rationale. Offer a\n   divider, a separate group, or any way to keep a wide gap only when\n   the user said the wide gap is meant to stay. When you keep separate\n   containers, name the evidence that they are separate groups (a\n   divider, different roles, a `justify-between`), or merge them.\n6. Report every difference you leave unchanged, such as a peer with\n   different padding: list it as a kept difference or fix it as a\n   finding; never mention it only to guess why it is fine.\n\n### Step 4: Validate\n\nAfter editing files, re-run the detect command for each pattern fixed\non the edited files and read the changed lines back; report any hit that\nremains. Then redraw the spacing map and confirm:\n\n- [ ] Every adjacent pair has exactly one spacing authority\n- [ ] Each visual group shares one parent container\n- [ ] Peer interactive elements share envelope classes\n- [ ] No `w-*` on content-sized items, unless all peers match\n- [ ] Hit targets are consistent across peers\n\nLeave a box `[ ]` and give the reason for any unmet item; never tick a\nbox and then argue against it.\n\n## Output\n\nWrite it per `references\u002Fprose-rules.md`. Present these sections\nin order, with these headings:\n\n1. Spacing map\n2. Anti-patterns found: one plain sentence per finding, naming the\n   mechanism (\"margin stacked on gap\") and the elements involved, never\n   a pattern number, with no bold lead-ins. For a file or directory\n   audit, name each finding's `path:line`. Put each kept difference in\n   one plain sentence after the last finding, not among them\n3. Proposed refactor: a focused diff or before\u002Fafter, with every\n   distance the refactor changes given as old to new (\"12px to 8px\")\n4. Validation checklist: Step 4 filled in\n\nReply in this shape, as plain text outside any code fence, with plain\nbullets, no bold (never `- **Label:** ...`), and no local paths:\n\n````text\n## Spacing map\n\nnav (p-4, no gap)\n- Docs, gap-2, Pricing\n- ms-3 on the second group\n- Sign in (px-2 h-8), nothing, Sign up (h-8)\n\n## Anti-patterns found\n\n- The `ms-3` on the second group (`src\u002FNav.tsx:11`) sets the space between groups, a margin stacked on the parent's gap.\n- \"Sign in\" has `px-2` and \"Sign up\" has none, so the buttons differ in width.\n\n## Proposed refactor\n\n```tsx\n\u003Cnav className=\"flex items-center gap-3 p-4\">\n  ...\n\u003C\u002Fnav>\n```\n\n## Validation checklist\n\n- [x] Every adjacent pair has one spacing authority.\n- [x] Peer buttons share `h-8 px-2`.\n````\n\nUse the full shape when auditing a file or directory. For a pasted\nsnippet with one finding, collapse it to a short explanation and the\ncode, with no bold anywhere and no counted lead-in (\"for three\nreasons:\"). State each visible change once. Do not restate that distances stay\nthe same.\n\nState the Tailwind version only when it changes the advice. Distances\nassume the default spacing scale (`gap-3` is 12px in v3 and in v4, where\n`--spacing` is `0.25rem`: [v3.4.0 `stubs\u002Fconfig.full.js`](https:\u002F\u002Fgithub.com\u002Ftailwindlabs\u002Ftailwindcss\u002Fblob\u002Fv3.4.0\u002Fstubs\u002Fconfig.full.js),\n[v4.0.0 `theme.css`](https:\u002F\u002Fgithub.com\u002Ftailwindlabs\u002Ftailwindcss\u002Fblob\u002Fv4.0.0\u002Fpackages\u002Ftailwindcss\u002Ftheme.css));\nsay so once if the project sets a custom `theme.spacing` or `--spacing`.\nWhen `detect.py` reports that it stopped at its hit cap, say which files\nit counted and that later files were not scanned.\n\nEnd a full audit with a next-step panel through the question tool, one\noption per fix found plus one to extend the audit to another path. Where\nasking is not allowed, print the options as a plain list, one per line,\nand stop.\n\nHalted or empty runs give one result sentence, then what the user does:\n\n- No target given: \"Nothing audited: no file or directory was given.\"\n  Pass a file or directory.\n- No Tailwind class attributes in scope: \"No Tailwind classes found in\n  `\u003Cscope>`.\" Check the path, or point at the template files.\n- Issues found but all kept as deliberate: \"No spacing changes made in\n  `\u003Cscope>`.\" Stop after one sentence naming the kept break and the one change\n  that would alter it. Do not reprint unchanged code or recap.\n- No issues found: \"No spacing issues found in `\u003Cscope>`.\" Name the files\n  you read, since the detect commands can miss dynamic classes.\n\n\n## Portability notes\n\n- `$ARGUMENTS` — the text the user passed when invoking this skill. If your host does not substitute it, read it as the user's request in the current turn, and ask when there is none.\n- Bundled files — every relative path in this skill points at a file shipped inside this skill directory. Read them from here, not from the host's plugin tree.\n","# Tailwind spacing audit\n\nDetect and fix inconsistent spacing in Tailwind CSS layouts. Most spacing\nbugs come from fragmented spacing authority: gap, margin, padding, and\nfixed widths all control the space between the same visual peers. Each\npair of adjacent items gets exactly one mechanism.\n\nUse `$ARGUMENTS` as the target scope. If it is empty and the user pasted\nmarkup, audit the paste. Otherwise ask which component or file to audit;\nwhen asking is not allowed, stop with the halted result below.\n\nAsk only through a question tool, and never when the user said not to\nask. Without a question tool, or after that instruction, asking is not\nallowed: decide per the steps below and end with no question.\n\nRun scripts from the project root so targets stay relative to the\nproject. Resolve `references\u002Fdetect.py` against this skill's directory,\nprint the absolute path once, and write it literally in each command,\nsince shell variables do not persist between Bash calls.\n\n## Workflow\n\n### Step 0: Detect framework and Tailwind version\n\nFind the template files in scope and the class attribute each uses:\n\n- `*.tsx`, `*.jsx`: `className=`\n- `*.vue`: `class=`, `:class=`\n- `*.svelte`, `*.astro`, `*.html`, `*.erb`, `*.php`, `*.twig`, `*.njk`,\n  `*.hbs`, `*.heex`, `*.mdx`, `*.liquid`: `class=`\n\nThe detect commands in `references\u002Fpatterns.md` run\n`references\u002Fdetect.py` and name an `rg` fallback. If neither runs,\nread the files in scope.\n\nRead the installed Tailwind version with the `version` command described\nin `references\u002Fpatterns.md`, run on the project root. If it prints\n`version: unknown`, say so in the result and keep `space-x` and\n`space-y` advice version-neutral.\n\n### Step 1: Structural audit\n\nScan the component and draw a spacing map in the list form shown under\nOutput: every spacing mechanism acting on the group the user cares\nabout. Then read the Detect command limits and Decision tree sections\nof `references\u002Fpatterns.md`, and only the pattern sections the findings\nmatch.\n\nCall out how many mechanisms act between visual peers, which items sit\nin different containers yet read as one group, and any fixed `w-*` on\nan item whose siblings size to content.\n\n### Step 2: Classify\n\nMatch each finding to a pattern in `references\u002Fpatterns.md`. Run that\npattern's detect command for codebase-wide scope. Each match needs a\nread in context before it counts. A command that returns nothing for a\nfile the user named is not a clean bill: read the file.\n\n### Step 3: Refactor\n\nPropose the changes as a diff or before\u002Fafter; edit files only when the\nuser asked to fix or apply them. For a pasted snippet, reply with the\ncode. Preserve existing breakpoints, and change only spacing and sizing\nclasses. Work in this order:\n\n1. Merge fragmented containers. Put one visual group in one flex\n   container with one `gap-*`. Remove the outer `me-*` and `ms-*` that\n   compensated for the split.\n2. Pick one authority per relationship. `gap-*` on the parent for\n   uniform spacing; margin on a child only for a deliberate exception;\n   padding only for space inside an item.\n3. Standardize peer envelopes. Peer buttons, links, and toggles\n   share one height class and one horizontal padding, and no `w-*`\n   unless every peer has the same one.\n4. Flatten single-child wrappers. Move the alignment classes onto\n   the child.\n5. Keep intentional breaks. A divider between nav groups is\n   deliberate, and so is the margin around it (`mx-*` on a `w-px` or\n   `\u003Chr>` element): keep both, never remove or shrink it, and list it as\n   a kept difference with the distance it produces. Ask before\n   normalizing a difference that may be design; when asking is not\n   allowed, keep the break and report it as a kept difference after the\n   findings, never as a finding, with no guessed rationale. Offer a\n   divider, a separate group, or any way to keep a wide gap only when\n   the user said the wide gap is meant to stay. When you keep separate\n   containers, name the evidence that they are separate groups (a\n   divider, different roles, a `justify-between`), or merge them.\n6. Report every difference you leave unchanged, such as a peer with\n   different padding: list it as a kept difference or fix it as a\n   finding; never mention it only to guess why it is fine.\n\n### Step 4: Validate\n\nAfter editing files, re-run the detect command for each pattern fixed\non the edited files and read the changed lines back; report any hit that\nremains. Then redraw the spacing map and confirm:\n\n- [ ] Every adjacent pair has exactly one spacing authority\n- [ ] Each visual group shares one parent container\n- [ ] Peer interactive elements share envelope classes\n- [ ] No `w-*` on content-sized items, unless all peers match\n- [ ] Hit targets are consistent across peers\n\nLeave a box `[ ]` and give the reason for any unmet item; never tick a\nbox and then argue against it.\n\n## Output\n\nWrite it per `references\u002Fprose-rules.md`. Present these sections\nin order, with these headings:\n\n1. Spacing map\n2. Anti-patterns found: one plain sentence per finding, naming the\n   mechanism (\"margin stacked on gap\") and the elements involved, never\n   a pattern number, with no bold lead-ins. For a file or directory\n   audit, name each finding's `path:line`. Put each kept difference in\n   one plain sentence after the last finding, not among them\n3. Proposed refactor: a focused diff or before\u002Fafter, with every\n   distance the refactor changes given as old to new (\"12px to 8px\")\n4. Validation checklist: Step 4 filled in\n\nReply in this shape, as plain text outside any code fence, with plain\nbullets, no bold (never `- **Label:** ...`), and no local paths:\n\n````text\n## Spacing map\n\nnav (p-4, no gap)\n- Docs, gap-2, Pricing\n- ms-3 on the second group\n- Sign in (px-2 h-8), nothing, Sign up (h-8)\n\n## Anti-patterns found\n\n- The `ms-3` on the second group (`src\u002FNav.tsx:11`) sets the space between groups, a margin stacked on the parent's gap.\n- \"Sign in\" has `px-2` and \"Sign up\" has none, so the buttons differ in width.\n\n## Proposed refactor\n\n```tsx\n\u003Cnav className=\"flex items-center gap-3 p-4\">\n  ...\n\u003C\u002Fnav>\n```\n\n## Validation checklist\n\n- [x] Every adjacent pair has one spacing authority.\n- [x] Peer buttons share `h-8 px-2`.\n````\n\nUse the full shape when auditing a file or directory. For a pasted\nsnippet with one finding, collapse it to a short explanation and the\ncode, with no bold anywhere and no counted lead-in (\"for three\nreasons:\"). State each visible change once. Do not restate that distances stay\nthe same.\n\nState the Tailwind version only when it changes the advice. Distances\nassume the default spacing scale (`gap-3` is 12px in v3 and in v4, where\n`--spacing` is `0.25rem`: [v3.4.0 `stubs\u002Fconfig.full.js`](https:\u002F\u002Fgithub.com\u002Ftailwindlabs\u002Ftailwindcss\u002Fblob\u002Fv3.4.0\u002Fstubs\u002Fconfig.full.js),\n[v4.0.0 `theme.css`](https:\u002F\u002Fgithub.com\u002Ftailwindlabs\u002Ftailwindcss\u002Fblob\u002Fv4.0.0\u002Fpackages\u002Ftailwindcss\u002Ftheme.css));\nsay so once if the project sets a custom `theme.spacing` or `--spacing`.\nWhen `detect.py` reports that it stopped at its hit cap, say which files\nit counted and that later files were not scanned.\n\nEnd a full audit with a next-step panel through the question tool, one\noption per fix found plus one to extend the audit to another path. Where\nasking is not allowed, print the options as a plain list, one per line,\nand stop.\n\nHalted or empty runs give one result sentence, then what the user does:\n\n- No target given: \"Nothing audited: no file or directory was given.\"\n  Pass a file or directory.\n- No Tailwind class attributes in scope: \"No Tailwind classes found in\n  `\u003Cscope>`.\" Check the path, or point at the template files.\n- Issues found but all kept as deliberate: \"No spacing changes made in\n  `\u003Cscope>`.\" Stop after one sentence naming the kept break and the one change\n  that would alter it. Do not reprint unchanged code or recap.\n- No issues found: \"No spacing issues found in `\u003Cscope>`.\" Name the files\n  you read, since the detect commands can miss dynamic classes.\n\n\n## Portability notes\n\n- `$ARGUMENTS` — the text the user passed when invoking this skill. If your host does not substitute it, read it as the user's request in the current turn, and ask when there is none.\n- Bundled files — every relative path in this skill points at a file shipped inside this skill directory. Read them from here, not from the host's plugin tree.\n",{"name":5,"metadata":24,"description":7},{"source":25,"argument-hint":26},"plugins\u002Ftailwind\u002Fskills\u002Fspacing-audit\u002FSKILL.md","\u003Cfile-or-directory-to-audit>","main","5fbeb3b47beedea13813be7b7023f736a8d97a65",".agents\u002Fskills\u002Ftailwind-spacing-audit","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills","https:\u002F\u002Fgithub.com\u002Ftony","https:\u002F\u002Ftony.sh","lighthouse keeper","2026-11-08 17:57:34",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add tony\u002Fskills --skill tailwind-spacing-audit",{"tool":41,"command":42},"bunx","bunx skills add tony\u002Fskills --skill tailwind-spacing-audit",{"tool":44,"command":45},"pnpm","pnpm dlx skills add tony\u002Fskills --skill tailwind-spacing-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftailwind-spacing-audit\u002FSKILL.md",true,[49,55,61,65],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",262,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftailwind-spacing-audit\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fdetect.py","SCRIPT","脚本",10005,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftailwind-spacing-audit\u002Freferences\u002Fdetect.py",{"path":62,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fpatterns.md",15427,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftailwind-spacing-audit\u002Freferences\u002Fpatterns.md",{"path":66,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fprose-rules.md",4644,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftailwind-spacing-audit\u002Freferences\u002Fprose-rules.md",[70,77,84,91,98,105],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7E8NCSHXV2JPW4J61R0TQS7","serene-bliss","Use when asked to make a CLI --help, docs page, error message, or tooling UX more serene or calmer for developer experience; returns text, no edits.","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fserene-bliss\u002FSKILL.md",[],[],{"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},"01M7E8N87MAVJD8RRQKQB1ZPS6","review","Weave code review: run independent adversarial reviews in parallel, then synthesize findings","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Freview\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},"01M7E8N402XG4ZBFNACQ413163","refine","Use when asked to refine a draft, iterate on code until cleaner, or polish a README through repeated critique and improvement.","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Frefine\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},"01M7E8N01KB86A7136P00GVKJW","prompt","Weave prompt: compare independent adversarial implementations, then adopt the single best one","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fprompt\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},"01M7E8MW7YJW2PCMDW3G9RTGNK","plan","Weave planning: compare independent adversarial plans, then synthesize the best one","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fplan\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},"01M7E8MSBYXNCV4ZYWDS4PFJXK","fix-review","Fix weave review findings: validate, add test coverage, fix, and commit each as atomic changes","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Ffix-review\u002FSKILL.md",[],[]]