[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M747QR3VN12KXYDZGRXETTGS":3,"skill-same:01M747QR3VN12KXYDZGRXETTGS":55},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M747QR3VN12KXYDZGRXETTGS","docx",null,"Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fskills\u002Fdocx\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fskills\u002Fdocx\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: docx\ndescription: \"Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.\"\nlicense: Complete terms in LICENSE.txt\n---\n\n# DOCX creation, editing, and analysis\n\nA `.docx` is a ZIP archive of XML files. Choose your approach by task:\n\n| Task | Approach |\n|---|---|\n| **Create** a new document | Write a `docx` (npm) script — see gotchas below |\n| **Edit** an existing document | `unzip` → edit `word\u002Fdocument.xml` → `zip` (docx-js cannot open existing files) |\n| **Read** content | `pandoc -t markdown file.docx` |\n\n> Script paths below are relative to this skill's directory.\n\n## Creating with docx-js — gotchas\n\n`docx` is preinstalled — do not run `npm install` first; write the script and `require('docx')` directly. Only if that require fails: `npm install docx`. The model knows the API; these are the footguns:\n\n- **Page size defaults to A4.** For US Letter set `page: { size: { width: 12240, height: 15840 } }` (DXA; 1440 = 1″).\n- **Landscape:** pass portrait dimensions and `orientation: PageOrientation.LANDSCAPE` — docx-js swaps width\u002Fheight internally.\n- **Tables need dual widths:** set `columnWidths` on the table AND `width` on every cell, both in `WidthType.DXA` (PERCENTAGE breaks in Google Docs). Column widths must sum to the table width.\n- **Table shading:** use `ShadingType.CLEAR`, never `SOLID` (renders black).\n- **Lists:** never insert `•` literally; use a `numbering` config with `LevelFormat.BULLET`.\n- **`ImageRun` requires `type:`** (`\"png\"`, `\"jpg\"`, …).\n- **`PageBreak` must be inside a `Paragraph`.**\n- **Never use `\\n`** — use separate `Paragraph` elements.\n- **Headings:** style every level you use (`title`, `heading1`, `heading2`…) in `styles.default`: `heading1: { run: { font: \"Arial\", size: 32, bold: true }, paragraph: { spacing: { before: 240, after: 120 }, keepNext: true } }`. Every level needs its own font (even with a document default), `before` and `after` (even if 0) and `keepNext`: the built-in styles set none of them.\n- **TOC:** headings must use built-in `HeadingLevel.*`; custom heading styles need `outlineLevel` set or they won't appear.\n- **Don't use a table as a horizontal rule** — use a paragraph bottom border instead.\n- **Dot-leader \u002F right-aligned-on-same-line:** use `PositionalTab` (`alignment: PositionalTabAlignment.RIGHT`, `leader: PositionalTabLeader.DOT`) inside a `TextRun`, not literal `.` or space padding.\n\n## Verify the output\n\nAfter writing a `.docx`, render it and look at it:\n\n```bash\nzip -d output.docx '*\u002F' >\u002Fdev\u002Fnull || true   # drop the ZIP's folder entries: Word has refused a file that has them when opened through a cloud co-editing service\npython scripts\u002Foffice\u002Fsoffice.py --headless --convert-to pdf output.docx\npdftoppm -jpeg -r 100 output.pdf page\nls page-*.jpg   # then Read the images\n```\n\n`pdftoppm` zero-pads page numbers to the width of the page count (`page-01.jpg`…`page-12.jpg`).\n\n## Editing existing documents\n\nLegacy `.doc` files must be converted first: `python scripts\u002Foffice\u002Fsoffice.py --headless --convert-to docx file.doc`.\n\n```bash\nunzip -q doc.docx -d unpacked\u002F\nfind unpacked -type l -delete   # strip symlink entries — docx from external parties is untrusted\npython scripts\u002Fmerge_runs.py unpacked\u002F   # coalesce fragmented runs so text is findable\n# edit unpacked\u002Fword\u002Fdocument.xml in place — do NOT reformat or pretty-print\n(cd unpacked && rm -f ..\u002Fout.docx && zip -XrD ..\u002Fout.docx .)\npython scripts\u002Foffice\u002Fvalidate.py out.docx --original doc.docx   # XSD checks; --auto-repair fixes common issues\n# redlining? add --author \"\u003Cthe name you redlined under>\" to check every edit is tracked\n```\n\nWord splits text across many `\u003Cw:r>` runs (revision ids, spell-check markers), so a phrase you can see in the document often doesn't exist as a contiguous string in the XML. `merge_runs.py` merges adjacent identically-formatted runs in `word\u002Fdocument.xml` without changing content or rendering; it also accepts a `.docx` directly (`python scripts\u002Fmerge_runs.py doc.docx -o merged.docx`).\n\n**Tracked changes:** when redlining, validate with `--author \"\u003Cthe name you redlined under>\"` (needs `--original`) — it reports any text you changed without a `\u003Cw:ins>`\u002F`\u003Cw:del>` around it, which is easy to do by accident and invisible in the accepted view. Wrap runs in `\u003Cw:ins>`\u002F`\u003Cw:del>` with `w:id`, `w:author`, `w:date` attributes. Inside `\u003Cw:del>`, the text element is `\u003Cw:delText>`, not `\u003Cw:t>`. A deleted paragraph mark (`\u003Cw:pPr>\u003Cw:rPr>\u003Cw:del w:id=\"..\" w:author=\"..\" w:date=\"..\"\u002F>\u003C\u002Fw:rPr>\u003C\u002Fw:pPr>`) means \"merge this paragraph into the next\" — so deleting a paragraph outright is that plus a `\u003Cw:del>` around every run. The `\u003Cw:del\u002F>` must come before the rPr's other children; their order is schema-enforced.\n\nTo produce a clean copy with all tracked changes accepted: `python scripts\u002Faccept_changes.py in.docx out.docx`.\n\nAccepting a deleted paragraph mark should join that paragraph to the one below it, so a paragraph whose runs are *all* deleted vanishes. Word does this; `accept_changes.py` and `pandoc --track-changes=accept` don't always. Both fail the same way — they strip the deleted text but leave the emptied paragraph behind, which reads as a stray empty bullet when it was auto-numbered:\n\n- `pandoc --track-changes=accept` never joins the paragraphs.\n- `accept_changes.py` (LibreOffice) joins them correctly, except when the deleted paragraph is followed by an empty spacer paragraph.\n\nAn empty bullet in either view is an artifact of that view, not a defect in the document. Check paragraph deletions in the XML.\n\n## Comments\n\nComments require six cross-linked files. Use the helper — directory mode when you'll also be editing `document.xml` (saves an unzip\u002Frezip cycle), `.docx`-direct mode otherwise:\n\n```bash\n# Against an already-unpacked directory (preferred when also placing markers)\npython scripts\u002Fcomment.py unpacked\u002F \"Fees & expenses cap is too low\"\npython scripts\u002Fcomment.py unpacked\u002F \"Agreed\" --parent 0\n\n# Against a .docx directly\npython scripts\u002Fcomment.py contract.docx \"This cap is too low\" -o annotated.docx\n```\n\nThe script writes `comments.xml`, `commentsExtended.xml`, `commentsIds.xml`, `commentsExtensible.xml`, the relationships, and the content-type overrides. Comment IDs are auto-assigned. It then prints the `\u003Cw:commentRangeStart>`\u002F`\u003Cw:commentRangeEnd>`\u002F`\u003Cw:commentReference>` snippet to add to `word\u002Fdocument.xml` so the comment anchors to specific text — until you place those markers, the comment exists but is not visible.\n\n## Dependencies\n\n`docx` (npm, preinstalled — install only if `require('docx')` fails) · `pandoc` · LibreOffice (`soffice`) · `pdftoppm` (Poppler)\n","# DOCX creation, editing, and analysis\n\nA `.docx` is a ZIP archive of XML files. Choose your approach by task:\n\n| Task | Approach |\n|---|---|\n| **Create** a new document | Write a `docx` (npm) script — see gotchas below |\n| **Edit** an existing document | `unzip` → edit `word\u002Fdocument.xml` → `zip` (docx-js cannot open existing files) |\n| **Read** content | `pandoc -t markdown file.docx` |\n\n> Script paths below are relative to this skill's directory.\n\n## Creating with docx-js — gotchas\n\n`docx` is preinstalled — do not run `npm install` first; write the script and `require('docx')` directly. Only if that require fails: `npm install docx`. The model knows the API; these are the footguns:\n\n- **Page size defaults to A4.** For US Letter set `page: { size: { width: 12240, height: 15840 } }` (DXA; 1440 = 1″).\n- **Landscape:** pass portrait dimensions and `orientation: PageOrientation.LANDSCAPE` — docx-js swaps width\u002Fheight internally.\n- **Tables need dual widths:** set `columnWidths` on the table AND `width` on every cell, both in `WidthType.DXA` (PERCENTAGE breaks in Google Docs). Column widths must sum to the table width.\n- **Table shading:** use `ShadingType.CLEAR`, never `SOLID` (renders black).\n- **Lists:** never insert `•` literally; use a `numbering` config with `LevelFormat.BULLET`.\n- **`ImageRun` requires `type:`** (`\"png\"`, `\"jpg\"`, …).\n- **`PageBreak` must be inside a `Paragraph`.**\n- **Never use `\\n`** — use separate `Paragraph` elements.\n- **Headings:** style every level you use (`title`, `heading1`, `heading2`…) in `styles.default`: `heading1: { run: { font: \"Arial\", size: 32, bold: true }, paragraph: { spacing: { before: 240, after: 120 }, keepNext: true } }`. Every level needs its own font (even with a document default), `before` and `after` (even if 0) and `keepNext`: the built-in styles set none of them.\n- **TOC:** headings must use built-in `HeadingLevel.*`; custom heading styles need `outlineLevel` set or they won't appear.\n- **Don't use a table as a horizontal rule** — use a paragraph bottom border instead.\n- **Dot-leader \u002F right-aligned-on-same-line:** use `PositionalTab` (`alignment: PositionalTabAlignment.RIGHT`, `leader: PositionalTabLeader.DOT`) inside a `TextRun`, not literal `.` or space padding.\n\n## Verify the output\n\nAfter writing a `.docx`, render it and look at it:\n\n```bash\nzip -d output.docx '*\u002F' >\u002Fdev\u002Fnull || true   # drop the ZIP's folder entries: Word has refused a file that has them when opened through a cloud co-editing service\npython scripts\u002Foffice\u002Fsoffice.py --headless --convert-to pdf output.docx\npdftoppm -jpeg -r 100 output.pdf page\nls page-*.jpg   # then Read the images\n```\n\n`pdftoppm` zero-pads page numbers to the width of the page count (`page-01.jpg`…`page-12.jpg`).\n\n## Editing existing documents\n\nLegacy `.doc` files must be converted first: `python scripts\u002Foffice\u002Fsoffice.py --headless --convert-to docx file.doc`.\n\n```bash\nunzip -q doc.docx -d unpacked\u002F\nfind unpacked -type l -delete   # strip symlink entries — docx from external parties is untrusted\npython scripts\u002Fmerge_runs.py unpacked\u002F   # coalesce fragmented runs so text is findable\n# edit unpacked\u002Fword\u002Fdocument.xml in place — do NOT reformat or pretty-print\n(cd unpacked && rm -f ..\u002Fout.docx && zip -XrD ..\u002Fout.docx .)\npython scripts\u002Foffice\u002Fvalidate.py out.docx --original doc.docx   # XSD checks; --auto-repair fixes common issues\n# redlining? add --author \"\u003Cthe name you redlined under>\" to check every edit is tracked\n```\n\nWord splits text across many `\u003Cw:r>` runs (revision ids, spell-check markers), so a phrase you can see in the document often doesn't exist as a contiguous string in the XML. `merge_runs.py` merges adjacent identically-formatted runs in `word\u002Fdocument.xml` without changing content or rendering; it also accepts a `.docx` directly (`python scripts\u002Fmerge_runs.py doc.docx -o merged.docx`).\n\n**Tracked changes:** when redlining, validate with `--author \"\u003Cthe name you redlined under>\"` (needs `--original`) — it reports any text you changed without a `\u003Cw:ins>`\u002F`\u003Cw:del>` around it, which is easy to do by accident and invisible in the accepted view. Wrap runs in `\u003Cw:ins>`\u002F`\u003Cw:del>` with `w:id`, `w:author`, `w:date` attributes. Inside `\u003Cw:del>`, the text element is `\u003Cw:delText>`, not `\u003Cw:t>`. A deleted paragraph mark (`\u003Cw:pPr>\u003Cw:rPr>\u003Cw:del w:id=\"..\" w:author=\"..\" w:date=\"..\"\u002F>\u003C\u002Fw:rPr>\u003C\u002Fw:pPr>`) means \"merge this paragraph into the next\" — so deleting a paragraph outright is that plus a `\u003Cw:del>` around every run. The `\u003Cw:del\u002F>` must come before the rPr's other children; their order is schema-enforced.\n\nTo produce a clean copy with all tracked changes accepted: `python scripts\u002Faccept_changes.py in.docx out.docx`.\n\nAccepting a deleted paragraph mark should join that paragraph to the one below it, so a paragraph whose runs are *all* deleted vanishes. Word does this; `accept_changes.py` and `pandoc --track-changes=accept` don't always. Both fail the same way — they strip the deleted text but leave the emptied paragraph behind, which reads as a stray empty bullet when it was auto-numbered:\n\n- `pandoc --track-changes=accept` never joins the paragraphs.\n- `accept_changes.py` (LibreOffice) joins them correctly, except when the deleted paragraph is followed by an empty spacer paragraph.\n\nAn empty bullet in either view is an artifact of that view, not a defect in the document. Check paragraph deletions in the XML.\n\n## Comments\n\nComments require six cross-linked files. Use the helper — directory mode when you'll also be editing `document.xml` (saves an unzip\u002Frezip cycle), `.docx`-direct mode otherwise:\n\n```bash\n# Against an already-unpacked directory (preferred when also placing markers)\npython scripts\u002Fcomment.py unpacked\u002F \"Fees & expenses cap is too low\"\npython scripts\u002Fcomment.py unpacked\u002F \"Agreed\" --parent 0\n\n# Against a .docx directly\npython scripts\u002Fcomment.py contract.docx \"This cap is too low\" -o annotated.docx\n```\n\nThe script writes `comments.xml`, `commentsExtended.xml`, `commentsIds.xml`, `commentsExtensible.xml`, the relationships, and the content-type overrides. Comment IDs are auto-assigned. It then prints the `\u003Cw:commentRangeStart>`\u002F`\u003Cw:commentRangeEnd>`\u002F`\u003Cw:commentReference>` snippet to add to `word\u002Fdocument.xml` so the comment anchors to specific text — until you place those markers, the comment exists but is not visible.\n\n## Dependencies\n\n`docx` (npm, preinstalled — install only if `require('docx')` fails) · `pandoc` · LibreOffice (`soffice`) · `pdftoppm` (Poppler)\n",{"name":5,"license":25,"description":7},"Complete terms in LICENSE.txt","master","d1bf1474e82e818f76589f67d1af88a4d178bf04","skills\u002Fskills\u002Fdocx",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill docx",{"tool":42,"command":43},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill docx",{"tool":45,"command":46},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill docx","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fskills\u002Fdocx\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",11357,[56,64,72,81,89,96],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":20},"01M748668J70YKWKS2VFVZ0ZRF","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fskills\u002Fxlsx\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fskills\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":20},"01M747X09GNGYJ7V4YE3NGGH7A","pptx","Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fskills\u002Fpptx\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fskills\u002Fpptx\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":20},"01M76KTXGSTXVVDC7YSBM41ZZS","wxpusher-integration","Use when（适用场景）：用户明确询问、指定或上下文已选定 WxPusher，需要了解、接入或排查通知（含微信 ClawBot\u002FiLink、appToken、UID、Topic、SPT）；仅说“微信通知”、未选服务商，或只出现通用 UID\u002FTopic 时不触发。","MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fwxpusher-integration\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fwxpusher-integration\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"01M748C5DS5BQBVBMG22FCGG34","branding","When the user wants to define, audit, or apply brand strategy—purpose, values, positioning, storytelling, voice, narrative (not only visuals). Also use when the user mentions \"brand strategy\", \"brand story\", \"brand storytelling\" or \"brand voice\". For typography, colors, design tokens, and frontend visuals, use brand-visual-generator.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fsuperskills\u002Fbranding\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":88},"01M748C1GXJ9WRKP18X45DKP6G","brand-visual-generator","When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics). Also use when the user mentions \"brand style guide\", \"visual identity\", \"design system\" or \"typography\". For brand story, positioning, and voice, use branding.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fsuperskills\u002Fbrand-visual-generator\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":88},"01M747T565TFEP3RAVWM0Y899Y","mcp-builder","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node\u002FTypeScript (MCP SDK).","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fskills\u002Fmcp-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fskills\u002Fmcp-builder\u002FSKILL.md",[],[]]