[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76FNFW7A255GEXQWPQJ645A":3,"skill-same:01M76FNFW7A255GEXQWPQJ645A":59},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M76FNFW7A255GEXQWPQJ645A","bambu-labs",null,"Dry-run, upload, and cautiously initiate local Bambu Lab print jobs from validated plain `.gcode`, using Bambu LAN FTPS\u002FMQTT handoffs.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fbambu-labs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fbambu-labs\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: bambu-labs\ndescription: Dry-run, upload, and cautiously initiate local Bambu Lab print jobs from validated plain `.gcode`, using Bambu LAN FTPS\u002FMQTT handoffs.\n---\n\n# Bambu Labs\n\nProvenance: maintained in [earthtojake\u002Ftext-to-cad](https:\u002F\u002Fgithub.com\u002Fearthtojake\u002Ftext-to-cad).\nUse the installed local skill files as the runtime source of truth; the\nrepository link is only for provenance and release review.\n\nUse this skill for local-network Bambu Lab print handoffs after a plain `.gcode`\nfile already exists and has been validated. This skill does not slice models.\n\n## Safety Rules\n\n- Default to dry-run plans. Real printer traffic requires `--execute`.\n- Never start a print without `--execute --confirm-start-print`.\n- Pause and cancel controls are live printer requests; default to dry-run plans.\n  Canceling a print requires `--execute --confirm-cancel-print`.\n- Treat an explicit user request to print or start a specific job as live-start\n  authorization; do not pause for a second confirmation solely for physical\n  checks. Still validate the G-code, inspect the dry-run payload, read printer\n  status, prefer upload-only before upload-start, state the physical checks, and\n  stop if validation\u002Fstatus\u002Fintent is unsafe or ambiguous.\n- Do not ask for the printer serial by default; fetch it from the printer TLS certificate with `serial` or let `send` cache it.\n- Prefer workspace-root `bambu-printers.json` over repeating access codes in commands. The file is local config and should be ignored by Git.\n- Before a live start, state the physical checks: clear build plate, correct plate\u002Ffilament\u002Fnozzle, safe surroundings, and operator nearby.\n- Publishing MQTT is only a start request. Confirm acceptance with printer status\u002FUI and physical observation.\n\n## CAD Viewer Handoff\n\nAfter completing Bambu work that creates or modifies a local `.3mf` print artifact, you must ALWAYS hand the explicit file path to `$cad-viewer` when that skill is installed. CAD Viewer does not open `.gcode`, so a plain G-code artifact takes no handoff. `$cad-viewer` must start CAD Viewer if it is not already running and return link(s) to the relevant created or updated file(s); if `$cad-viewer` is unavailable or startup fails, report that instead of silently omitting the handoff.\n\n## Workflow\n\n1. Generate and validate plain G-code with `$gcode`.\n   If no slicer is installed, install OrcaSlicer and retry; do not treat the missing slicer as a blocker. On macOS, prefer `brew install --cask orcaslicer`.\n2. Configure the printer. The user can either give the IP\u002Faccess code in the thread and let the agent write JSON, or edit `bambu-printers.json` directly.\n   For a new printer setup or onboarding request, read\n   `references\u002Fnew-printer-onboarding.md` first. Walk the user through the\n   model-specific touchscreen steps to find the IP and LAN access code, and make\n   **Enable LAN Only** plus **Enable Developer Mode** explicit before running\n   local start workflows.\n\n```bash\npython scripts\u002Fbambu_lan_print.py config set \\\n  --printer a1-mini \\\n  --host 192.168.1.34 \\\n  --access-code 12345678 \\\n  --model a1-mini \\\n  --fetch-serial\n```\n\nManual JSON shape:\n\n```json\n{\n  \"printers\": {\n    \"a1-mini\": {\n      \"host\": \"192.168.1.34\",\n      \"access_code\": \"12345678\",\n      \"model\": \"a1-mini\"\n    }\n  }\n}\n```\n\nOn A1\u002FA1 Mini, find the IP and LAN access code on the printer touchscreen under\nnetwork\u002FLAN settings. Enable LAN Only and Developer Mode when offered, then\npower-cycle before retrying local start commands.\n\n3. Read status before live work:\n\n```bash\npython scripts\u002Fbambu_lan_print.py status \\\n  --printer a1-mini \\\n  --push-all \\\n  --wait-seconds 10\n```\n\n4. Dry-run the exact handoff, inspect the JSON payload, then run upload-only.\nOnly after upload succeeds should you run upload-start. If the user explicitly\nasked to print or start the job, proceed to `upload-start --execute\n--confirm-start-print` after the validation, status, and upload checks pass. If\nthe user only asked to prepare, slice, upload, or review, stop before the start\nrequest.\n\n## Handoff Modes\n\n`--handoff template-project` is the A1 Mini path validated against a real\nprinter over LAN. It starts from validated plain `.gcode`, copies a known-good\nsame-printer `.gcode.3mf` template, replaces `Metadata\u002Fplate_N.gcode`, writes\nthe plate MD5, uploads the project to the FTPS root, and publishes\n`print.project_file` with `url: ftp:\u002F\u002F\u002F\u003Cname>.gcode.3mf`.\n\n```bash\npython scripts\u002Fbambu_lan_print.py send \\\n  --printer a1-mini \\\n  --gcode \u002Ftmp\u002Fjob.gcode \\\n  --handoff template-project \\\n  --template-project \u002Fpath\u002Fto\u002Fsame-printer-template.gcode.3mf \\\n  --action upload-start\n```\n\nExecute after review when the user explicitly asked to print or start, or after\nphysical confirmation when intent is unclear:\n\n```bash\npython scripts\u002Fbambu_lan_print.py send \\\n  --printer a1-mini \\\n  --gcode \u002Ftmp\u002Fjob.gcode \\\n  --handoff template-project \\\n  --template-project \u002Fpath\u002Fto\u002Fsame-printer-template.gcode.3mf \\\n  --action upload-start \\\n  --execute \\\n  --confirm-start-print\n```\n\n`--handoff plain` uploads `cache\u002F\u003Cname>.gcode` and publishes\n`print.gcode_file`. Keep it for diagnostics or printers\u002Ffirmware where this is\nknown to work. On the tested A1 Mini, direct plain G-code was uploaded\nsuccessfully but `gcode_file` failed or was ignored, so do not use it as the\nA1 Mini live-start path.\n\n`--handoff bambox-project` packages plain `.gcode` with `bambox`, uploads the\n`.gcode.3mf` project to FTPS root, and publishes `print.project_file`.\nCurrently enabled only for `p1s-0.4` with `PLA`, `ASA`, or `PETG-CF`.\nKnown but disabled until validated profiles exist: `a1-mini-0.4`, `a1-0.4`,\n`x1c-0.4`, and `p1p-0.4`.\n\n## Common Debugging Commands\n\nFetch\u002Fcache serial:\n\n```bash\npython scripts\u002Fbambu_lan_print.py serial \\\n  --printer a1-mini \\\n  --json\n```\n\nClear a stale printer error after fixing the underlying cause:\n\n```bash\npython scripts\u002Fbambu_lan_print.py clear-error \\\n  --printer a1-mini \\\n  --execute\n```\n\nUse `--mqtt-qos 1 --wait-after-publish 10` on `send` when debugging whether the\nprinter acknowledged the MQTT publish and what status it reported immediately\nafterward.\n\n## Print Controls\n\nFor a running print, use dedicated print-control commands rather than ad hoc\nMQTT snippets. These commands publish only a control request; they do not upload\nfiles or start a new job. Read status after execution to confirm the printer\nstate changed.\n\nDry-run pause payload:\n\n```bash\npython scripts\u002Fbambu_lan_print.py pause \\\n  --printer a1-mini\n```\n\nExecute pause and collect printer reports:\n\n```bash\npython scripts\u002Fbambu_lan_print.py pause \\\n  --printer a1-mini \\\n  --execute \\\n  --mqtt-qos 1 \\\n  --wait-after-publish 10\n```\n\nDry-run cancel payload. The Bambu LAN command sent to the printer is `stop`:\n\n```bash\npython scripts\u002Fbambu_lan_print.py cancel \\\n  --printer a1-mini\n```\n\nExecute cancel only when the user explicitly asks to cancel\u002Fstop the print or\nafter confirmation when intent is ambiguous:\n\n```bash\npython scripts\u002Fbambu_lan_print.py cancel \\\n  --printer a1-mini \\\n  --execute \\\n  --confirm-cancel-print \\\n  --mqtt-qos 1 \\\n  --wait-after-publish 10\n```\n\n## Failure Modes\n\n- `gcode_file` returns `result: fail` or leaves the printer `IDLE`: plain G-code upload worked, but the firmware rejected or ignored direct local start. For A1 Mini, switch to `template-project`.\n- Project uploaded under `cache\u002F` starts then fails with `print_error: 83935248` or `0500-C010`: clear the error, upload project handoffs to FTPS root, and use `ftp:\u002F\u002F\u002F\u003Cname>.gcode.3mf`.\n- `file:\u002F\u002F\u002Fsdcard\u002Fcache\u002F...` or local HTTP URLs appear accepted but nothing starts: stop using those URL forms for this workflow.\n- Bambu Studio or OrcaSlicer project export crashes on macOS: do not keep retrying GUI-backed project export. Use OrcaSlicer for plain `.gcode`, then this skill for handoff.\n- Stale `gcode_state: FAILED` or HMS after enabling Developer Mode: clear the printer error and power-cycle before retrying.\n- FTPS login works but upload fails with `553` or missing `cache\u002F`: check printer storage\u002FSD card status before MQTT start.\n- MQTT status works but start does not: confirm serial, access code, Developer Mode\u002FLAN Only status, and the exact handoff payload before retrying.\n\nRead `references\u002Fnew-printer-onboarding.md` for new printer setup,\n`references\u002Flocal-lan-protocol.md` for protocol details, and\n`references\u002Freal-printer-checklist.md` before first live use on a new printer.\n","# Bambu Labs\n\nProvenance: maintained in [earthtojake\u002Ftext-to-cad](https:\u002F\u002Fgithub.com\u002Fearthtojake\u002Ftext-to-cad).\nUse the installed local skill files as the runtime source of truth; the\nrepository link is only for provenance and release review.\n\nUse this skill for local-network Bambu Lab print handoffs after a plain `.gcode`\nfile already exists and has been validated. This skill does not slice models.\n\n## Safety Rules\n\n- Default to dry-run plans. Real printer traffic requires `--execute`.\n- Never start a print without `--execute --confirm-start-print`.\n- Pause and cancel controls are live printer requests; default to dry-run plans.\n  Canceling a print requires `--execute --confirm-cancel-print`.\n- Treat an explicit user request to print or start a specific job as live-start\n  authorization; do not pause for a second confirmation solely for physical\n  checks. Still validate the G-code, inspect the dry-run payload, read printer\n  status, prefer upload-only before upload-start, state the physical checks, and\n  stop if validation\u002Fstatus\u002Fintent is unsafe or ambiguous.\n- Do not ask for the printer serial by default; fetch it from the printer TLS certificate with `serial` or let `send` cache it.\n- Prefer workspace-root `bambu-printers.json` over repeating access codes in commands. The file is local config and should be ignored by Git.\n- Before a live start, state the physical checks: clear build plate, correct plate\u002Ffilament\u002Fnozzle, safe surroundings, and operator nearby.\n- Publishing MQTT is only a start request. Confirm acceptance with printer status\u002FUI and physical observation.\n\n## CAD Viewer Handoff\n\nAfter completing Bambu work that creates or modifies a local `.3mf` print artifact, you must ALWAYS hand the explicit file path to `$cad-viewer` when that skill is installed. CAD Viewer does not open `.gcode`, so a plain G-code artifact takes no handoff. `$cad-viewer` must start CAD Viewer if it is not already running and return link(s) to the relevant created or updated file(s); if `$cad-viewer` is unavailable or startup fails, report that instead of silently omitting the handoff.\n\n## Workflow\n\n1. Generate and validate plain G-code with `$gcode`.\n   If no slicer is installed, install OrcaSlicer and retry; do not treat the missing slicer as a blocker. On macOS, prefer `brew install --cask orcaslicer`.\n2. Configure the printer. The user can either give the IP\u002Faccess code in the thread and let the agent write JSON, or edit `bambu-printers.json` directly.\n   For a new printer setup or onboarding request, read\n   `references\u002Fnew-printer-onboarding.md` first. Walk the user through the\n   model-specific touchscreen steps to find the IP and LAN access code, and make\n   **Enable LAN Only** plus **Enable Developer Mode** explicit before running\n   local start workflows.\n\n```bash\npython scripts\u002Fbambu_lan_print.py config set \\\n  --printer a1-mini \\\n  --host 192.168.1.34 \\\n  --access-code 12345678 \\\n  --model a1-mini \\\n  --fetch-serial\n```\n\nManual JSON shape:\n\n```json\n{\n  \"printers\": {\n    \"a1-mini\": {\n      \"host\": \"192.168.1.34\",\n      \"access_code\": \"12345678\",\n      \"model\": \"a1-mini\"\n    }\n  }\n}\n```\n\nOn A1\u002FA1 Mini, find the IP and LAN access code on the printer touchscreen under\nnetwork\u002FLAN settings. Enable LAN Only and Developer Mode when offered, then\npower-cycle before retrying local start commands.\n\n3. Read status before live work:\n\n```bash\npython scripts\u002Fbambu_lan_print.py status \\\n  --printer a1-mini \\\n  --push-all \\\n  --wait-seconds 10\n```\n\n4. Dry-run the exact handoff, inspect the JSON payload, then run upload-only.\nOnly after upload succeeds should you run upload-start. If the user explicitly\nasked to print or start the job, proceed to `upload-start --execute\n--confirm-start-print` after the validation, status, and upload checks pass. If\nthe user only asked to prepare, slice, upload, or review, stop before the start\nrequest.\n\n## Handoff Modes\n\n`--handoff template-project` is the A1 Mini path validated against a real\nprinter over LAN. It starts from validated plain `.gcode`, copies a known-good\nsame-printer `.gcode.3mf` template, replaces `Metadata\u002Fplate_N.gcode`, writes\nthe plate MD5, uploads the project to the FTPS root, and publishes\n`print.project_file` with `url: ftp:\u002F\u002F\u002F\u003Cname>.gcode.3mf`.\n\n```bash\npython scripts\u002Fbambu_lan_print.py send \\\n  --printer a1-mini \\\n  --gcode \u002Ftmp\u002Fjob.gcode \\\n  --handoff template-project \\\n  --template-project \u002Fpath\u002Fto\u002Fsame-printer-template.gcode.3mf \\\n  --action upload-start\n```\n\nExecute after review when the user explicitly asked to print or start, or after\nphysical confirmation when intent is unclear:\n\n```bash\npython scripts\u002Fbambu_lan_print.py send \\\n  --printer a1-mini \\\n  --gcode \u002Ftmp\u002Fjob.gcode \\\n  --handoff template-project \\\n  --template-project \u002Fpath\u002Fto\u002Fsame-printer-template.gcode.3mf \\\n  --action upload-start \\\n  --execute \\\n  --confirm-start-print\n```\n\n`--handoff plain` uploads `cache\u002F\u003Cname>.gcode` and publishes\n`print.gcode_file`. Keep it for diagnostics or printers\u002Ffirmware where this is\nknown to work. On the tested A1 Mini, direct plain G-code was uploaded\nsuccessfully but `gcode_file` failed or was ignored, so do not use it as the\nA1 Mini live-start path.\n\n`--handoff bambox-project` packages plain `.gcode` with `bambox`, uploads the\n`.gcode.3mf` project to FTPS root, and publishes `print.project_file`.\nCurrently enabled only for `p1s-0.4` with `PLA`, `ASA`, or `PETG-CF`.\nKnown but disabled until validated profiles exist: `a1-mini-0.4`, `a1-0.4`,\n`x1c-0.4`, and `p1p-0.4`.\n\n## Common Debugging Commands\n\nFetch\u002Fcache serial:\n\n```bash\npython scripts\u002Fbambu_lan_print.py serial \\\n  --printer a1-mini \\\n  --json\n```\n\nClear a stale printer error after fixing the underlying cause:\n\n```bash\npython scripts\u002Fbambu_lan_print.py clear-error \\\n  --printer a1-mini \\\n  --execute\n```\n\nUse `--mqtt-qos 1 --wait-after-publish 10` on `send` when debugging whether the\nprinter acknowledged the MQTT publish and what status it reported immediately\nafterward.\n\n## Print Controls\n\nFor a running print, use dedicated print-control commands rather than ad hoc\nMQTT snippets. These commands publish only a control request; they do not upload\nfiles or start a new job. Read status after execution to confirm the printer\nstate changed.\n\nDry-run pause payload:\n\n```bash\npython scripts\u002Fbambu_lan_print.py pause \\\n  --printer a1-mini\n```\n\nExecute pause and collect printer reports:\n\n```bash\npython scripts\u002Fbambu_lan_print.py pause \\\n  --printer a1-mini \\\n  --execute \\\n  --mqtt-qos 1 \\\n  --wait-after-publish 10\n```\n\nDry-run cancel payload. The Bambu LAN command sent to the printer is `stop`:\n\n```bash\npython scripts\u002Fbambu_lan_print.py cancel \\\n  --printer a1-mini\n```\n\nExecute cancel only when the user explicitly asks to cancel\u002Fstop the print or\nafter confirmation when intent is ambiguous:\n\n```bash\npython scripts\u002Fbambu_lan_print.py cancel \\\n  --printer a1-mini \\\n  --execute \\\n  --confirm-cancel-print \\\n  --mqtt-qos 1 \\\n  --wait-after-publish 10\n```\n\n## Failure Modes\n\n- `gcode_file` returns `result: fail` or leaves the printer `IDLE`: plain G-code upload worked, but the firmware rejected or ignored direct local start. For A1 Mini, switch to `template-project`.\n- Project uploaded under `cache\u002F` starts then fails with `print_error: 83935248` or `0500-C010`: clear the error, upload project handoffs to FTPS root, and use `ftp:\u002F\u002F\u002F\u003Cname>.gcode.3mf`.\n- `file:\u002F\u002F\u002Fsdcard\u002Fcache\u002F...` or local HTTP URLs appear accepted but nothing starts: stop using those URL forms for this workflow.\n- Bambu Studio or OrcaSlicer project export crashes on macOS: do not keep retrying GUI-backed project export. Use OrcaSlicer for plain `.gcode`, then this skill for handoff.\n- Stale `gcode_state: FAILED` or HMS after enabling Developer Mode: clear the printer error and power-cycle before retrying.\n- FTPS login works but upload fails with `553` or missing `cache\u002F`: check printer storage\u002FSD card status before MQTT start.\n- MQTT status works but start does not: confirm serial, access code, Developer Mode\u002FLAN Only status, and the exact handoff payload before retrying.\n\nRead `references\u002Fnew-printer-onboarding.md` for new printer setup,\n`references\u002Flocal-lan-protocol.md` for protocol details, and\n`references\u002Freal-printer-checklist.md` before first live use on a new printer.\n",{"name":5,"description":7},"master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fmarketplace\u002Fbambu-labs",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill bambu-labs",{"tool":41,"command":42},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill bambu-labs",{"tool":44,"command":45},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill bambu-labs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fbambu-labs\u002FSKILL.md",true,[49,53],{"path":50,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":16},"LICENSE","许可证",1074,{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"skill-report.json","REFERENCE","参考文档",114295,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fbambu-labs\u002Fskill-report.json",[60,68,75,82,89,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"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.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":67},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":67},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":67},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":67},"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":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":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":67},"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",[],[]]