[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73GF1F0VMMDY0N6QWTMY569":3,"skill-same:01M73GF1F0VMMDY0N6QWTMY569":65},{"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},"01M73GF1F0VMMDY0N6QWTMY569","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\u002Fawesome-skills\u002Fdocx\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fawesome-skills\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- **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\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 -Xr ..\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- **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\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 -Xr ..\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","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fawesome-skills\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\u002Fawesome-skills\u002Fdocx\u002FSKILL.md",true,[50,56,61],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"docx-js.md","REFERENCE","参考文档",16509,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fawesome-skills\u002Fdocx\u002Fdocx-js.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",11357,{"path":62,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":63,"sourceHtmlUrl":64},"ooxml.md",23572,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fawesome-skills\u002Fdocx\u002Fooxml.md",[66,75,82,89,96,103],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":74},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":74},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"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":70,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":74},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\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":70,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":74},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":74},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]