[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73VBJGN7YVSS5D4W57BGE6D":3,"skill-same:01M73VBJGN7YVSS5D4W57BGE6D":58},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M73VBJGN7YVSS5D4W57BGE6D","generating-images",null,"ALWAYS read this skill before generating or editing any image, or calling image_generate — text-to-image or image-to-image, simple or complex. Turns a text brief, optionally guided by reference images (a character, a style to follow, an existing photo to edit), into a still image. Analyzes intent, routes to the best model, and structures the prompt. Use whenever the user asks to generate, create, make, design, or edit an image — except commercial photography of a product being sold, which belongs to generating-product-photos.","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\u002Fmarketplace\u002Fgenerating-images\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: generating-images\ndescription: ALWAYS read this skill before generating or editing any image, or calling image_generate — text-to-image or image-to-image, simple or complex. Turns a text brief, optionally guided by reference images (a character, a style to follow, an existing photo to edit), into a still image. Analyzes intent, routes to the best model, and structures the prompt. Use whenever the user asks to generate, create, make, design, or edit an image — except commercial photography of a product being sold, which belongs to generating-product-photos.\nlicense: Apache-2.0\nmetadata:\n  version: \"0.1.0\"\n  category: creative\n  summary: \"Routes your brief to the best of 10+ SOTA image models (like Nano Banana, GPT Image), writes detailed prompts as per model specifications and generates multiple variations instantly.\"\n---\n\n# Image Generation\n\nTurn a brief — text, optionally with reference image(s) — into a still image via the\n`image_generate` tool. Two decisions drive quality: **which model** (always) and **which format\nrecipe** (only when the deliverable is a known one).\n\n**Before you route:** if the brief is commercial **product photography** — a packshot, a product in\na styled scene, a hero or banner for a product, a product ad or carousel, an on-model or try-on shot,\nor restyling an existing product photo — hand off to the **`generating-product-photos`** skill, which\nowns that surface. Stay here for everything else: general images, graphics and posters, portraits,\nillustrations, cinematic stills, infographics, and one-off reference edits.\n\n## Workflow\n\n### Step 1: Route to a model\n\nRoute by what the image has to **do** — read the brief for intent.\nThe descriptions below are signals to weigh, not a literal router — the examples are illustrative,\nnot a checklist to match against. Then **read the chosen model's prompt guide before writing\nanything**.\n\n| Route when the brief is about… | Model | Prompt guide |\n| --- | --- | --- |\n| Rendering **words** legibly, or a designed layout where elements sit in deliberate positions — for example a poster, ad, banner, thumbnail, or infographic | `gpt-image-2` | `references\u002Fprompt-gpt-image-2.md` |\n| A **drawn or rendered** look rather than a photograph — for example a cartoon, anime, illustration, flat vector, or 3D render | `nano-banana-2` | `references\u002Fprompt-nano-banana.md` |\n| A convincing **real person**, or a photographic frame with deliberate cinematography — for example a creator or influencer portrait, UGC, or a film-like still | `nano-banana-pro` | `references\u002Fprompt-nano-banana.md` |\n| **Altering a supplied image** — for example swapping a background, removing or replacing an element, or restaging the scene | `gpt-image-2` | `references\u002Fprompt-gpt-image-2.md` |\n| Altering a supplied image where a **real face must stay recognisable** | `seedream-5` | `references\u002Fprompt-seedream.md` |\n\nWhen more than one applies, take them in this order:\n\n1. The user named a model → use it.\n2. Legible text is required → `gpt-image-2`, even over a person or a scene.\n3. The look is non-photographic → `nano-banana-2`, even when a person is involved.\n4. A supplied image is being altered → `gpt-image-2`; switch to `seedream-5` when a real person\n   must stay recognisable.\n5. A supplied image is only a **style or mood cue** (match this look, don't edit that image) →\n   `nano-banana-2`, or `seedream-5` if a specific face must carry over too.\n\nIf nothing clearly fits — an ordinary object or scene — use `nano-banana-2` (read\n`references\u002Fprompt-nano-banana.md`); or call `list_image_models` and pick by `strengths`. Use\n`grok-imagine` (`references\u002Fprompt-grok.md`), `flux-2-pro`, or `flux-2-klein-4b` (both\n`references\u002Fprompt-flux.md`) only when the user names them.\n\n### Step 2: Read a format recipe if one fits (optional)\n\nMany briefs are a standard deliverable with a layout worth following. Check the table below. **If a\nrow matches, read that recipe and follow its sections and example. If none matches, skip this step**\n— the model's prompt guide is enough.\n\n| Deliverable                          | Recipe                           |\n| ------------------------------------ | -------------------------------- |\n| Poster \u002F ad \u002F banner \u002F social graphic | `references\u002Fformat-poster.md`    |\n| Portrait \u002F avatar \u002F influencer        | `references\u002Fformat-portrait.md`  |\n| Cinematic still                       | `references\u002Fformat-cinematic.md` |\n\n### Step 3: Get any missing inputs\n\nAsk only for what would change the result and can't be sensibly defaulted — for example the exact\ntext that has to appear on the image, a source image for an edit, or the desired aspect ratio when that\ndecides the crop. Bundle everything you need into one ask rather than a back-and-forth; if the user\nhas signalled they don't want questions, choose sensible defaults, state them in a line, and proceed.\n\n### Step 4: Look at the reference images — only when references are supplied\n\nCall `image_analysis` on each reference, asking whatever the prompt will have to carry — enough to\nname what must stay fixed and to avoid contradicting the source.\n\nSkip when you already know what's in the image — you generated it this turn, or it arrived with a\ndescription.\n\nIf what you find changes the routing — a face to keep recognisable, a stylized source — go back to\nStep 1.\n\n### Step 5: Write the prompt\n\nBuild the prompt as the chosen model's prompt guide specifies. If you read a format recipe, start\nfrom its sections and worked example. With a reference image, use what Step 4 turned up to say what\nstays fixed (the product, the face, the palette) and what changes.\n\n**Write a complete, self-contained prompt** — the model sees only this one prompt. Specify the whole\nframe: subject, wardrobe \u002F materials, setting, lighting, colour palette, camera \u002F lens, medium, and\nmood. A dense, concrete, technical description beats a thin one-liner or vague adjectives (\"nice\",\n\"cool\") — that density is what separates an editorial result from a generic one.\n\n### Step 6: Generate\n\nCall `image_generate` with a `requests` list (one object per image):\n\n- Per object: `prompt` (required); `model` from Step 1; `aspect_ratio`; `resolution` — step up a tier\n  when the image carries a lot of text; `reference_images` for a supplied source.\n- For several **different** images (an A\u002FB set, a carousel), add one request object per image to the\n  same call.\n\n**Same subject or style across a set.** Requests are generated independently, so a back-reference\n(\"the same woman\", \"same outfit\") produces a different result each time. Write the appearance,\nwardrobe, and style once and repeat that description word-for-word in every request; vary only the\nshot, framing, and aspect ratio, and hold one lighting and palette across the set.\n\nImages are polled for you, but a heavy one — a large model, 4k, or a big batch — can come back as\n`{status: \"pending\", …}` (a job handle, not a failure). Pass that exact handle to `job_status` to\nretrieve the finished image — **never re-run a pending image** with `image_generate`; that starts a\nnew, separately-billed job. If it's still pending, call `job_status` again with the same handle.\n\n### Step 7: Return\n\nOnce every image has finished (rejoin any `pending` ones via `job_status` first), share the resulting\nimage URL(s) and local file path(s) with the user.\n\n## Edge cases\n\n- **Fits no kind** → use `nano-banana-2` (read `references\u002Fprompt-nano-banana.md`) or call\n  `list_image_models`.\n- **Fits no format** → skip Step 2; the prompt guide alone is enough.\n- **Safety\u002FNSFW rejection** → name a workable stand-in for whatever tripped the filter (cover the\n  wardrobe, change the setting) and resubmit. A second rejection: tell the user which element is\n  blocked instead of retrying blind.\n- **Still generating (`status: \"pending\"`) or the call times out** → the image is still rendering on\n  the server, **not** a failure — do **not** resubmit (that starts a second billed job). If you got a\n  pending handle, call `job_status` with it to rejoin; if the call timed out with no handle, wait and\n  tell the user it's still processing rather than firing a fresh generation.\n- **Generic failure** (an explicit error result, not a timeout) → read the error. If it names a\n  parameter or a limit, correct that and resubmit. Otherwise resubmit once; if it fails again, give\n  the user the error text rather than guessing.\n- **`reference_images` rejected on count** → the error states the model's limit; drop to it.\n- **`error: \"no_provider_configured\"`** → relay the tool's `hint` (the user must set their key).\n\n## Reference\n\n**Prompt guides** — read the one for the chosen model:\n\n- `references\u002Fprompt-gpt-image-2.md` — labeled blocks, verbatim text rendering, reference identity.\n- `references\u002Fprompt-nano-banana.md` — instruction-following (subject\u002Fscene → style → instructions → constraints).\n- `references\u002Fprompt-seedream.md` — instruction-style editing, compositing, and preservation.\n- `references\u002Fprompt-flux.md` — linear prompt sequence, no negatives, camera\u002Flens specs.\n- `references\u002Fprompt-grok.md` — natural-language director style.\n\n**Format recipes** — read only if the deliverable matches:\n\n- `references\u002Fformat-poster.md`, `references\u002Fformat-portrait.md`, `references\u002Fformat-cinematic.md`.\n","# Image Generation\n\nTurn a brief — text, optionally with reference image(s) — into a still image via the\n`image_generate` tool. Two decisions drive quality: **which model** (always) and **which format\nrecipe** (only when the deliverable is a known one).\n\n**Before you route:** if the brief is commercial **product photography** — a packshot, a product in\na styled scene, a hero or banner for a product, a product ad or carousel, an on-model or try-on shot,\nor restyling an existing product photo — hand off to the **`generating-product-photos`** skill, which\nowns that surface. Stay here for everything else: general images, graphics and posters, portraits,\nillustrations, cinematic stills, infographics, and one-off reference edits.\n\n## Workflow\n\n### Step 1: Route to a model\n\nRoute by what the image has to **do** — read the brief for intent.\nThe descriptions below are signals to weigh, not a literal router — the examples are illustrative,\nnot a checklist to match against. Then **read the chosen model's prompt guide before writing\nanything**.\n\n| Route when the brief is about… | Model | Prompt guide |\n| --- | --- | --- |\n| Rendering **words** legibly, or a designed layout where elements sit in deliberate positions — for example a poster, ad, banner, thumbnail, or infographic | `gpt-image-2` | `references\u002Fprompt-gpt-image-2.md` |\n| A **drawn or rendered** look rather than a photograph — for example a cartoon, anime, illustration, flat vector, or 3D render | `nano-banana-2` | `references\u002Fprompt-nano-banana.md` |\n| A convincing **real person**, or a photographic frame with deliberate cinematography — for example a creator or influencer portrait, UGC, or a film-like still | `nano-banana-pro` | `references\u002Fprompt-nano-banana.md` |\n| **Altering a supplied image** — for example swapping a background, removing or replacing an element, or restaging the scene | `gpt-image-2` | `references\u002Fprompt-gpt-image-2.md` |\n| Altering a supplied image where a **real face must stay recognisable** | `seedream-5` | `references\u002Fprompt-seedream.md` |\n\nWhen more than one applies, take them in this order:\n\n1. The user named a model → use it.\n2. Legible text is required → `gpt-image-2`, even over a person or a scene.\n3. The look is non-photographic → `nano-banana-2`, even when a person is involved.\n4. A supplied image is being altered → `gpt-image-2`; switch to `seedream-5` when a real person\n   must stay recognisable.\n5. A supplied image is only a **style or mood cue** (match this look, don't edit that image) →\n   `nano-banana-2`, or `seedream-5` if a specific face must carry over too.\n\nIf nothing clearly fits — an ordinary object or scene — use `nano-banana-2` (read\n`references\u002Fprompt-nano-banana.md`); or call `list_image_models` and pick by `strengths`. Use\n`grok-imagine` (`references\u002Fprompt-grok.md`), `flux-2-pro`, or `flux-2-klein-4b` (both\n`references\u002Fprompt-flux.md`) only when the user names them.\n\n### Step 2: Read a format recipe if one fits (optional)\n\nMany briefs are a standard deliverable with a layout worth following. Check the table below. **If a\nrow matches, read that recipe and follow its sections and example. If none matches, skip this step**\n— the model's prompt guide is enough.\n\n| Deliverable                          | Recipe                           |\n| ------------------------------------ | -------------------------------- |\n| Poster \u002F ad \u002F banner \u002F social graphic | `references\u002Fformat-poster.md`    |\n| Portrait \u002F avatar \u002F influencer        | `references\u002Fformat-portrait.md`  |\n| Cinematic still                       | `references\u002Fformat-cinematic.md` |\n\n### Step 3: Get any missing inputs\n\nAsk only for what would change the result and can't be sensibly defaulted — for example the exact\ntext that has to appear on the image, a source image for an edit, or the desired aspect ratio when that\ndecides the crop. Bundle everything you need into one ask rather than a back-and-forth; if the user\nhas signalled they don't want questions, choose sensible defaults, state them in a line, and proceed.\n\n### Step 4: Look at the reference images — only when references are supplied\n\nCall `image_analysis` on each reference, asking whatever the prompt will have to carry — enough to\nname what must stay fixed and to avoid contradicting the source.\n\nSkip when you already know what's in the image — you generated it this turn, or it arrived with a\ndescription.\n\nIf what you find changes the routing — a face to keep recognisable, a stylized source — go back to\nStep 1.\n\n### Step 5: Write the prompt\n\nBuild the prompt as the chosen model's prompt guide specifies. If you read a format recipe, start\nfrom its sections and worked example. With a reference image, use what Step 4 turned up to say what\nstays fixed (the product, the face, the palette) and what changes.\n\n**Write a complete, self-contained prompt** — the model sees only this one prompt. Specify the whole\nframe: subject, wardrobe \u002F materials, setting, lighting, colour palette, camera \u002F lens, medium, and\nmood. A dense, concrete, technical description beats a thin one-liner or vague adjectives (\"nice\",\n\"cool\") — that density is what separates an editorial result from a generic one.\n\n### Step 6: Generate\n\nCall `image_generate` with a `requests` list (one object per image):\n\n- Per object: `prompt` (required); `model` from Step 1; `aspect_ratio`; `resolution` — step up a tier\n  when the image carries a lot of text; `reference_images` for a supplied source.\n- For several **different** images (an A\u002FB set, a carousel), add one request object per image to the\n  same call.\n\n**Same subject or style across a set.** Requests are generated independently, so a back-reference\n(\"the same woman\", \"same outfit\") produces a different result each time. Write the appearance,\nwardrobe, and style once and repeat that description word-for-word in every request; vary only the\nshot, framing, and aspect ratio, and hold one lighting and palette across the set.\n\nImages are polled for you, but a heavy one — a large model, 4k, or a big batch — can come back as\n`{status: \"pending\", …}` (a job handle, not a failure). Pass that exact handle to `job_status` to\nretrieve the finished image — **never re-run a pending image** with `image_generate`; that starts a\nnew, separately-billed job. If it's still pending, call `job_status` again with the same handle.\n\n### Step 7: Return\n\nOnce every image has finished (rejoin any `pending` ones via `job_status` first), share the resulting\nimage URL(s) and local file path(s) with the user.\n\n## Edge cases\n\n- **Fits no kind** → use `nano-banana-2` (read `references\u002Fprompt-nano-banana.md`) or call\n  `list_image_models`.\n- **Fits no format** → skip Step 2; the prompt guide alone is enough.\n- **Safety\u002FNSFW rejection** → name a workable stand-in for whatever tripped the filter (cover the\n  wardrobe, change the setting) and resubmit. A second rejection: tell the user which element is\n  blocked instead of retrying blind.\n- **Still generating (`status: \"pending\"`) or the call times out** → the image is still rendering on\n  the server, **not** a failure — do **not** resubmit (that starts a second billed job). If you got a\n  pending handle, call `job_status` with it to rejoin; if the call timed out with no handle, wait and\n  tell the user it's still processing rather than firing a fresh generation.\n- **Generic failure** (an explicit error result, not a timeout) → read the error. If it names a\n  parameter or a limit, correct that and resubmit. Otherwise resubmit once; if it fails again, give\n  the user the error text rather than guessing.\n- **`reference_images` rejected on count** → the error states the model's limit; drop to it.\n- **`error: \"no_provider_configured\"`** → relay the tool's `hint` (the user must set their key).\n\n## Reference\n\n**Prompt guides** — read the one for the chosen model:\n\n- `references\u002Fprompt-gpt-image-2.md` — labeled blocks, verbatim text rendering, reference identity.\n- `references\u002Fprompt-nano-banana.md` — instruction-following (subject\u002Fscene → style → instructions → constraints).\n- `references\u002Fprompt-seedream.md` — instruction-style editing, compositing, and preservation.\n- `references\u002Fprompt-flux.md` — linear prompt sequence, no negatives, camera\u002Flens specs.\n- `references\u002Fprompt-grok.md` — natural-language director style.\n\n**Format recipes** — read only if the deliverable matches:\n\n- `references\u002Fformat-poster.md`, `references\u002Fformat-portrait.md`, `references\u002Fformat-cinematic.md`.\n",{"name":5,"license":15,"metadata":24,"description":7},{"summary":25,"version":26,"category":27},"Routes your brief to the best of 10+ SOTA image models (like Nano Banana, GPT Image), writes detailed prompts as per model specifications and generates multiple variations instantly.","0.1.0","creative","master","63f17866001c5ca854bf2fa0b678ce277133de5b","skills\u002Fmarketplace\u002Fgenerating-images",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":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill generating-images",{"tool":44,"command":45},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill generating-images",{"tool":47,"command":48},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill generating-images","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fgenerating-images\u002FSKILL.md",true,[52],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"skill-report.json","REFERENCE","参考文档",43279,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fgenerating-images\u002Fskill-report.json",[59,68,75,82,89,96],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"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.","MIT","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":63,"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":63,"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":63,"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":63,"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":63,"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",[],[]]