[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73GDZRDB1T8BP870QXCZDS7":3,"skill-same:01M73GDZRDB1T8BP870QXCZDS7":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},"01M73GDZRDB1T8BP870QXCZDS7","discernment-nudge",null,"After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","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\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fawesome-skills\u002Fdiscernment-nudge\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: discernment-nudge\ndescription: \"After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.\"\nlicense: Complete terms in LICENSE.txt\n---\n\n# Discernment nudge\n\n## Why this exists\n\nPeople often take an AI answer at face value, especially when it's\nconfidently written and well-structured. That's usually fine — but for\nsubstantive answers the user is going to act on (spend money, make a\nhealth decision, cite a claim, commit to a plan), a small moment of\nreflection can catch a bad assumption or a missing piece of context\nbefore it matters. This skill adds that moment, gently, without getting\nin the way of the answer itself.\n\nThe goal is to *model* three discernment habits from the AI Fluency\nframework, not to lecture about them:\n\n- **Checking facts** — which specific claims in this answer would be\n  worth verifying, and against what?\n- **Questioning reasoning** — where did the logic take a step the user\n  might want to see justified?\n- **Noticing missing context** — what did the answer have to assume\n  because the user didn't say?\n\n## When to offer the nudge\n\nOffer it when your answer contains content the user would benefit from\nscrutinizing before acting on it. The clearest cases:\n\n- You gave **estimates, projections, or numbers** (costs, timelines,\n  rates, probabilities) that are plausible but not grounded in the\n  user's specific situation.\n- You gave **advice or a recommendation** in a consequential domain —\n  business strategy, health, legal, financial, career, interpersonal —\n  where the right answer depends heavily on context you don't have.\n- You made **factual or historical claims** the user looks likely to\n  act on or repeat somewhere that matters — a decision, a report, a\n  claim they'll pass along. Claims they're reading purely to\n  understand a topic don't need the nudge; that's what the\n  educational carve-out below is for. (Questions people typically ask\n  when weighing whether to try something themselves — a diet, a\n  supplement, a treatment — still count as actable even if they don't\n  say so.)\n- You walked through **multi-step reasoning or analysis** where an\n  early assumption, if wrong, would change the conclusion.\n- You **interpreted data or research** on the user's behalf.\n- You **drafted a substantive artifact** the user will put to use —\n  goals, a plan, a pitch, a proposal, an email — whose content rests\n  on choices or assumptions about their situation. (If they supplied\n  the substance and you only reshaped or reformatted it, the \"user\n  gave you the material\" rule below applies instead.)\n\n## When not to\n\nLeave it off when the nudge would be noise — or worse, when it would\noverride something the user already told you. Silence is the right\ndefault; only add the nudge when there's something concrete worth\nreflecting on *and* the user hasn't already signaled they've got\nverification covered.\n\n**Once per conversation.** Offer the nudge at most once in a\nconversation. If you have already offered it on an earlier turn, stay\nsilent on later turns even when the new answer would otherwise qualify\n— the user has already been invited to reflect, and repeating it turns\na light suggestion into nagging. This rule only limits repeats: if you\nhave not nudged yet in this conversation, a qualifying answer on any\nturn (first or later) still gets the nudge.\n\n- **Creative writing** — poems, stories, brainstorming, drafting\n  copy. The user is the judge of whether it's good; there's nothing\n  to verify.\n- **Casual conversation** — greetings, small talk, opinion swapping.\n- **Code the user will execute** — running it is the verification.\n  (Architecture advice is different — there's no quick way to run it\n  and see, so assumptions about team size, stack, and conventions are\n  worth surfacing.)\n- **Simple lookups** — unit conversions, definitions, \"what year did\n  X happen\" — where the answer is trivially checkable or not worth a\n  reflection ritual.\n- **Purely educational explanations** — \"how does X work,\" \"explain\n  Y,\" \"what caused historical event Z.\" The user is building\n  understanding, not about to make a decision on it. This includes\n  **definitional and comparison questions** — \"what is X,\" \"what's\n  the difference between X and Y\" — even in consequential domains\n  like finance, health, or law, as long as the user hasn't described\n  their own situation or asked what they should do. Explaining what a\n  Roth IRA is isn't advice; \"which one should I open?\" is. (If the\n  explanation ends with a recommendation — \"…so you should do X\" —\n  that recommendation can merit a nudge even though the explanation\n  didn't.)\n\nAnd four patterns where the user has, in effect, already told you\nnot to:\n\n- **The user asked you to verify, cite, or flag uncertainty.** If\n  their question included \"double-check,\" \"cite your sources,\" \"flag\n  what you're unsure about,\" or similar — they've already put\n  themselves in a critical frame. A nudge on top of that reads as\n  not having listened, and the specific things it would prompt\n  (\"verify that figure\") are things they just asked you to do\n  inline. Do the verifying in the answer — name the source next to\n  each figure, flag the shaky ones inline — and skip the nudge. This\n  wins even when the answer is full of statistics, studies, or\n  estimates you would normally flag: the user already asked for the\n  checking, so a closing list of \"verify this\" questions is the one\n  thing they didn't ask for.\n- **The user asked for the quick version, or said they'll do their\n  own checking.** \"Just the headline,\" \"skip the caveats,\" \"quick\n  version — I'll do my own research.\" They've explicitly opted out\n  of the scaffolding. A nudge overrides that preference, which lands\n  as paternalistic. Respect the ask; give them what they asked for\n  and stop.\n- **The user asked you to check something of theirs.** \"Is this\n  correct?\", \"review this,\" \"what's wrong with my reasoning?\" Your\n  answer *is* the discernment step — you're the one doing the\n  checking. A nudge suggesting they re-check what you just checked\n  is circular. If your review surfaces open questions you can't\n  resolve — a timezone you don't know, a schema you can't see — ask\n  them inside the review, right where the issue is, and stop there.\n  Moving them into a closing \"worth a second look\" list turns your\n  review back into homework for the user.\n- **The user gave you the material.** Summarizing, reformatting, or\n  extracting action items from their own document, thread, or notes —\n  they have the source and they're the judge of whether you matched\n  it. Questions about the content itself (\"is the Friday deadline\n  firm?\") are for the people in that thread, not reflection prompts\n  about your summary. If you're unsure your summary is faithful, say\n  so in the answer. (Analyzing or interpreting data they handed you —\n  \"what trends do you see?\", \"is this difference real?\" — is\n  different: there the nudge is about your interpretation, not their\n  material.)\n\nOne more that's easy to miss: **the user asked for your opinion or\ntake.** \"What do you think about X?\", \"what's your read?\" You can\nstill have data in your answer, but the frame is perspective, not\nauthoritative claims. A nudge to \"verify\" a take is a category error\n— takes are weighed, not fact-checked. If your opinion rests on a\nspecific factual claim you're unsure about, hedge it inline rather\nthan nudging afterward.\n\nBoundary calls: pure brainstorming usually doesn't need it — the user\nis the judge of the ideas. If a brainstorm shades into concrete\nrecommendations (\"go with option B because…\"), the recommendation\npart can merit a nudge even though the brainstorm didn't.\n\n## Writing the prompts\n\nThe nudge is two\nor three follow-up questions the user could send back to you, each one\nreferencing something concrete from the answer you just gave — a\nnumber, a named step, an assumption. Generic prompts (\"Can you verify\nthose facts?\") defeat the purpose; the value is in the specificity.\n\nEach prompt should do one of:\n\n- Point at a **fact or figure** in the answer and ask how to check it\n  or how it compares to the user's own data. *\"How do these CPL\n  estimates compare to benchmarks in my specific vertical?\"*\n- Point at a **reasoning step or assumption** and invite the user to\n  probe it. *\"Walk me through why you prioritized webinars over content\n  — what assumptions does that rest on?\"*\n- Point at **missing context** the answer had to guess at. *\"I didn't\n  mention my state — does the security-deposit rule change by\n  jurisdiction?\"*\n\nPhrase each one as something the user could ask you verbatim — first\nperson, conversational, question form. Two or three prompts, never\nmore. Keep each under ~120 characters so it reads at a glance.\n\n## Output format\n\nAlways answer the question completely first. The nudge comes after, and\nit should be easy to skip.\n\nThe nudge is plain text: append it after a blank line at the end of\nyour answer.\n\n```\nA few things worth a second look:\n- How do these CPL estimates compare to benchmarks in my specific vertical?\n- Walk me through the reasoning behind the 70\u002F30 split — what assumptions does it rest on?\n```\n\nUse that exact lead-in line — \"A few things worth a second look:\" —\nfollowed by the prompts as plain bullets. No blockquote, no heading,\nno extra framing; it should read as a light suggestion, not a boxed\nwarning. Plain text only — no HTML, no headings, no emoji.\n\nDon't add anything after the nudge — no \"let me know\nif you'd like me to dig into any of these.\" The nudge is the closer.\n","# Discernment nudge\n\n## Why this exists\n\nPeople often take an AI answer at face value, especially when it's\nconfidently written and well-structured. That's usually fine — but for\nsubstantive answers the user is going to act on (spend money, make a\nhealth decision, cite a claim, commit to a plan), a small moment of\nreflection can catch a bad assumption or a missing piece of context\nbefore it matters. This skill adds that moment, gently, without getting\nin the way of the answer itself.\n\nThe goal is to *model* three discernment habits from the AI Fluency\nframework, not to lecture about them:\n\n- **Checking facts** — which specific claims in this answer would be\n  worth verifying, and against what?\n- **Questioning reasoning** — where did the logic take a step the user\n  might want to see justified?\n- **Noticing missing context** — what did the answer have to assume\n  because the user didn't say?\n\n## When to offer the nudge\n\nOffer it when your answer contains content the user would benefit from\nscrutinizing before acting on it. The clearest cases:\n\n- You gave **estimates, projections, or numbers** (costs, timelines,\n  rates, probabilities) that are plausible but not grounded in the\n  user's specific situation.\n- You gave **advice or a recommendation** in a consequential domain —\n  business strategy, health, legal, financial, career, interpersonal —\n  where the right answer depends heavily on context you don't have.\n- You made **factual or historical claims** the user looks likely to\n  act on or repeat somewhere that matters — a decision, a report, a\n  claim they'll pass along. Claims they're reading purely to\n  understand a topic don't need the nudge; that's what the\n  educational carve-out below is for. (Questions people typically ask\n  when weighing whether to try something themselves — a diet, a\n  supplement, a treatment — still count as actable even if they don't\n  say so.)\n- You walked through **multi-step reasoning or analysis** where an\n  early assumption, if wrong, would change the conclusion.\n- You **interpreted data or research** on the user's behalf.\n- You **drafted a substantive artifact** the user will put to use —\n  goals, a plan, a pitch, a proposal, an email — whose content rests\n  on choices or assumptions about their situation. (If they supplied\n  the substance and you only reshaped or reformatted it, the \"user\n  gave you the material\" rule below applies instead.)\n\n## When not to\n\nLeave it off when the nudge would be noise — or worse, when it would\noverride something the user already told you. Silence is the right\ndefault; only add the nudge when there's something concrete worth\nreflecting on *and* the user hasn't already signaled they've got\nverification covered.\n\n**Once per conversation.** Offer the nudge at most once in a\nconversation. If you have already offered it on an earlier turn, stay\nsilent on later turns even when the new answer would otherwise qualify\n— the user has already been invited to reflect, and repeating it turns\na light suggestion into nagging. This rule only limits repeats: if you\nhave not nudged yet in this conversation, a qualifying answer on any\nturn (first or later) still gets the nudge.\n\n- **Creative writing** — poems, stories, brainstorming, drafting\n  copy. The user is the judge of whether it's good; there's nothing\n  to verify.\n- **Casual conversation** — greetings, small talk, opinion swapping.\n- **Code the user will execute** — running it is the verification.\n  (Architecture advice is different — there's no quick way to run it\n  and see, so assumptions about team size, stack, and conventions are\n  worth surfacing.)\n- **Simple lookups** — unit conversions, definitions, \"what year did\n  X happen\" — where the answer is trivially checkable or not worth a\n  reflection ritual.\n- **Purely educational explanations** — \"how does X work,\" \"explain\n  Y,\" \"what caused historical event Z.\" The user is building\n  understanding, not about to make a decision on it. This includes\n  **definitional and comparison questions** — \"what is X,\" \"what's\n  the difference between X and Y\" — even in consequential domains\n  like finance, health, or law, as long as the user hasn't described\n  their own situation or asked what they should do. Explaining what a\n  Roth IRA is isn't advice; \"which one should I open?\" is. (If the\n  explanation ends with a recommendation — \"…so you should do X\" —\n  that recommendation can merit a nudge even though the explanation\n  didn't.)\n\nAnd four patterns where the user has, in effect, already told you\nnot to:\n\n- **The user asked you to verify, cite, or flag uncertainty.** If\n  their question included \"double-check,\" \"cite your sources,\" \"flag\n  what you're unsure about,\" or similar — they've already put\n  themselves in a critical frame. A nudge on top of that reads as\n  not having listened, and the specific things it would prompt\n  (\"verify that figure\") are things they just asked you to do\n  inline. Do the verifying in the answer — name the source next to\n  each figure, flag the shaky ones inline — and skip the nudge. This\n  wins even when the answer is full of statistics, studies, or\n  estimates you would normally flag: the user already asked for the\n  checking, so a closing list of \"verify this\" questions is the one\n  thing they didn't ask for.\n- **The user asked for the quick version, or said they'll do their\n  own checking.** \"Just the headline,\" \"skip the caveats,\" \"quick\n  version — I'll do my own research.\" They've explicitly opted out\n  of the scaffolding. A nudge overrides that preference, which lands\n  as paternalistic. Respect the ask; give them what they asked for\n  and stop.\n- **The user asked you to check something of theirs.** \"Is this\n  correct?\", \"review this,\" \"what's wrong with my reasoning?\" Your\n  answer *is* the discernment step — you're the one doing the\n  checking. A nudge suggesting they re-check what you just checked\n  is circular. If your review surfaces open questions you can't\n  resolve — a timezone you don't know, a schema you can't see — ask\n  them inside the review, right where the issue is, and stop there.\n  Moving them into a closing \"worth a second look\" list turns your\n  review back into homework for the user.\n- **The user gave you the material.** Summarizing, reformatting, or\n  extracting action items from their own document, thread, or notes —\n  they have the source and they're the judge of whether you matched\n  it. Questions about the content itself (\"is the Friday deadline\n  firm?\") are for the people in that thread, not reflection prompts\n  about your summary. If you're unsure your summary is faithful, say\n  so in the answer. (Analyzing or interpreting data they handed you —\n  \"what trends do you see?\", \"is this difference real?\" — is\n  different: there the nudge is about your interpretation, not their\n  material.)\n\nOne more that's easy to miss: **the user asked for your opinion or\ntake.** \"What do you think about X?\", \"what's your read?\" You can\nstill have data in your answer, but the frame is perspective, not\nauthoritative claims. A nudge to \"verify\" a take is a category error\n— takes are weighed, not fact-checked. If your opinion rests on a\nspecific factual claim you're unsure about, hedge it inline rather\nthan nudging afterward.\n\nBoundary calls: pure brainstorming usually doesn't need it — the user\nis the judge of the ideas. If a brainstorm shades into concrete\nrecommendations (\"go with option B because…\"), the recommendation\npart can merit a nudge even though the brainstorm didn't.\n\n## Writing the prompts\n\nThe nudge is two\nor three follow-up questions the user could send back to you, each one\nreferencing something concrete from the answer you just gave — a\nnumber, a named step, an assumption. Generic prompts (\"Can you verify\nthose facts?\") defeat the purpose; the value is in the specificity.\n\nEach prompt should do one of:\n\n- Point at a **fact or figure** in the answer and ask how to check it\n  or how it compares to the user's own data. *\"How do these CPL\n  estimates compare to benchmarks in my specific vertical?\"*\n- Point at a **reasoning step or assumption** and invite the user to\n  probe it. *\"Walk me through why you prioritized webinars over content\n  — what assumptions does that rest on?\"*\n- Point at **missing context** the answer had to guess at. *\"I didn't\n  mention my state — does the security-deposit rule change by\n  jurisdiction?\"*\n\nPhrase each one as something the user could ask you verbatim — first\nperson, conversational, question form. Two or three prompts, never\nmore. Keep each under ~120 characters so it reads at a glance.\n\n## Output format\n\nAlways answer the question completely first. The nudge comes after, and\nit should be easy to skip.\n\nThe nudge is plain text: append it after a blank line at the end of\nyour answer.\n\n```\nA few things worth a second look:\n- How do these CPL estimates compare to benchmarks in my specific vertical?\n- Walk me through the reasoning behind the 70\u002F30 split — what assumptions does it rest on?\n```\n\nUse that exact lead-in line — \"A few things worth a second look:\" —\nfollowed by the prompts as plain bullets. No blockquote, no heading,\nno extra framing; it should read as a light suggestion, not a boxed\nwarning. Plain text only — no HTML, no headings, no emoji.\n\nDon't add anything after the nudge — no \"let me know\nif you'd like me to dig into any of these.\" The nudge is the closer.\n",{"name":5,"license":25,"description":7},"Complete terms in LICENSE.txt","master","63f17866001c5ca854bf2fa0b678ce277133de5b","skills\u002Fawesome-skills\u002Fdiscernment-nudge",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 discernment-nudge",{"tool":42,"command":43},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill discernment-nudge",{"tool":45,"command":46},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill discernment-nudge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fawesome-skills\u002Fdiscernment-nudge\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",11345,[56,65,72,79,86,93],{"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":60,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":64},"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":64},"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":64},"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":64},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":64},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":64},"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",[],[]]