[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73R6SZHVCYZD9W7V9BXZPQH":3,"skill-same:01M73R6SZHVCYZD9W7V9BXZPQH":68},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M73R6SZHVCYZD9W7V9BXZPQH","compound-docs",null,"Capture solved problems as searchable documentation with pattern detection. This skill auto-triggers when users confirm a fix worked (\"that worked\", \"it's fixed\", \"working now\") or manually via \u002Fcompound command.","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\u002Fcompound-docs\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: compound-docs\ndescription: Capture solved problems as searchable documentation with pattern detection. This skill auto-triggers when users confirm a fix worked (\"that worked\", \"it's fixed\", \"working now\") or manually via \u002Fcompound command.\nversion: 0.1.0-beta\nlicense: MIT\ncompatibility: opencode\n---\n\n## Auto-Invoke Triggers\n\nThis skill auto-triggers when the user says:\n\n- \"that worked\"\n- \"it's fixed\"\n- \"working now\"\n- \"problem solved\"\n- \"that did it\"\n\nManual command: `\u002Fcompound`\n\n## Workflow\n\n### Step 1: Detect Trigger\n\nWhen a trigger phrase is detected or `\u002Fcompound` is invoked:\n\n1. Confirm the problem is actually solved (not still in progress)\n2. Check if the fix is worth documenting\n\n**Skip documentation for trivial fixes:**\n\n- Simple typos\n- Obvious syntax errors (missing semicolon, bracket)\n- Single-line fixes that were immediately obvious\n\nIf skipping, briefly explain why: \"This was a simple typo fix - skipping documentation.\"\n\n### Step 2: Gather Context\n\nRead [schema.yaml](schema.yaml) to get valid enum values, then extract from the conversation:\n\n| Field      | Required | Description                                       |\n| ---------- | -------- | ------------------------------------------------- |\n| Symptom    | Yes      | Error message or observable behavior              |\n| Category   | Yes      | From schema.yaml `category.values` (or add new)   |\n| Component  | No       | From schema.yaml `component.values` (or add new)  |\n| Root cause | No       | From schema.yaml `root_cause.values` (or add new) |\n| Solution   | Yes      | The fix that worked                               |\n| Prevention | No       | How to avoid this in the future                   |\n\n**If a value doesn't exist in schema.yaml:**\n\n1. Add the new value to the appropriate enum in `schema.yaml`\n2. If it's a new category, create the directory: `mkdir -p {output_dir}\u002F{new-category}`\n\n**If critical info is missing, ask:**\n\n```\nTo document this fix, I need a few details:\n\n1. Category: What type of issue was this?\n   [list current values from schema.yaml]\n   Or suggest a new category if none fit\n```\n\n### Step 3: Check for Similar Issues\n\nBefore creating a new doc, search for similar existing issues:\n\n1. **Keyword match** - Search `{output_dir}\u002F` for error message fragments or key symptom phrases\n2. **File path match** - Check if the same files are involved in existing docs\n3. **Import\u002Fdependency match** - Check if the same libraries or modules are mentioned\n\n```bash\n# Example searches\ngrep -rl \"ErrorMessage\" docs\u002Fsolutions\u002F\ngrep -l \"path\u002Fto\u002Ffile\" docs\u002Fsolutions\u002F**\u002F*.md\n```\n\n**If potential matches found:**\n\n```\nFound potentially related issues:\n- docs\u002Fsolutions\u002Fintegration\u002Fapi-timeout-20250102.md\n- docs\u002Fsolutions\u002Fintegration\u002Fauth-header-missing-20250105.md\n\nAre any of these the same or related issue? (y\u002Fn)\n```\n\nIf related, add to the `related` field in frontmatter.\n\n### Step 4: Create Documentation\n\n**Validate against schema.yaml:**\n\n1. Read schema.yaml for current valid enum values\n2. Ensure all required fields are present\n3. Ensure enum values exist (or add them first)\n\n**Generate filename:**\n\n- Format: `{sanitized-symptom}-{YYYYMMDD}.md`\n- Sanitize: lowercase, replace spaces with hyphens, remove special chars, truncate to 80 chars\n\n**Create file at:** `{output_dir}\u002F{category}\u002F{filename}`\n\n**Ensure directory exists:**\n\n```bash\nmkdir -p {output_dir}\u002F{category}\n```\n\n**Use the Solution Doc Template below.**\n\n### Step 5: Pattern Promotion\n\nAfter creating the doc, check if this issue has occurred multiple times.\n\n**If similar issues >= threshold (default: 2):**\n\n```\nThis issue has occurred {N} times:\n- {link to issue 1}\n- {link to issue 2}\n- {link to current issue}\n\nPromote to patterns.md? This surfaces it prominently for future sessions.\n1. Yes - Add to patterns\n2. No - Keep as regular doc only\n```\n\n**If yes:** Append to `{output_dir}\u002Fpatterns.md` using the Pattern Template below.\n\n## Solution Doc Template\n\n````markdown\n---\ndate: { YYYY-MM-DD }\ncategory: { category }\nsymptoms:\n  - { symptom 1 }\n  - { symptom 2 }\ncomponent: { component }\nroot_cause: { root_cause }\ntags: [{ keyword1 }, { keyword2 }]\nrelated: []\n---\n\n# {Problem Title}\n\n## Problem\n\n{1-2 sentence description of what went wrong}\n\n## Symptoms\n\n- {What you observed - error messages, behavior, etc.}\n\n## What Didn't Work\n\n- {Attempted solution 1} - {Why it failed}\n- {Attempted solution 2} - {Why it failed}\n\n## Solution\n\n{Description of the fix}\n\n```{language}\n# Before (broken)\n{code before}\n\n# After (fixed)\n{code after}\n```\n````\n\n## Why This Works\n\n{Technical explanation of the root cause and why the solution addresses it}\n\n## Prevention\n\n{How to avoid this in the future - tests, linting rules, patterns to follow}\n\n````\n\n## Pattern Template\n\nWhen adding to `patterns.md`:\n\n```markdown\n## {Pattern Name}\n\n**Occurrences:** {N} times ({link1}, {link2}, ...)\n\n### WRONG\n\n```{language}\n{code that causes the problem}\n````\n\n### CORRECT\n\n```{language}\n{code that fixes it}\n```\n\n**Why:** {Technical explanation}\n\n**When this applies:** {Context or conditions when this pattern is relevant}\n\n````\n\n## Integration\n\n### Reference in AGENTS.md\n\nAdd to your project's AGENTS.md to ensure patterns are checked:\n\n```markdown\n## Required Reading\n\nBefore making changes, review known patterns:\n- [Solution Patterns](docs\u002Fsolutions\u002Fpatterns.md)\n````\n\n### Consuming Solutions\n\nOther workflows can discover and apply documented solutions:\n\n**Search by keyword:**\n\n```bash\ngrep -rl \"keyword\" docs\u002Fsolutions\u002F\n```\n\n**Search by category:**\n\n```bash\nls docs\u002Fsolutions\u002Fdeployment\u002F\n```\n\n**Search by tag:**\n\n```bash\ngrep -l \"tags:.*docker\" docs\u002Fsolutions\u002F**\u002F*.md\n```\n\n`patterns.md` is the primary integration point - check it first for critical patterns before making changes.\n\n## Example Scenario\n\n**User:** \"That worked! The Docker build was failing because of the cache issue.\"\n\n**Agent response:**\n\n```\nGreat! Let me document this fix.\n\n**Reading schema.yaml...**\nCurrent categories: developer-experience, deployment, ui, integration, performance, testing\nCurrent components: (none yet)\nCurrent root_causes: (none yet)\n\n**Gathering context...**\n\nFrom our conversation:\n- Symptom: Docker build failing with \"layer not found\" error\n- Category: deployment\n- Component: docker (adding to schema.yaml)\n- Root cause: stale-cache (adding to schema.yaml)\n- Solution: Added `--no-cache` flag and updated base image tag\n- Prevention: Pin base image versions, use `docker system prune` periodically\n\n**Updating schema.yaml...**\nAdded 'docker' to component.values\nAdded 'stale-cache' to root_cause.values\n\n**Checking for similar issues...**\nNo related issues found.\n\n**Creating documentation...**\nCreated: docs\u002Fsolutions\u002Fdeployment\u002Fdocker-layer-not-found-20250106.md\n\nDocumentation complete.\n```\n","## Auto-Invoke Triggers\n\nThis skill auto-triggers when the user says:\n\n- \"that worked\"\n- \"it's fixed\"\n- \"working now\"\n- \"problem solved\"\n- \"that did it\"\n\nManual command: `\u002Fcompound`\n\n## Workflow\n\n### Step 1: Detect Trigger\n\nWhen a trigger phrase is detected or `\u002Fcompound` is invoked:\n\n1. Confirm the problem is actually solved (not still in progress)\n2. Check if the fix is worth documenting\n\n**Skip documentation for trivial fixes:**\n\n- Simple typos\n- Obvious syntax errors (missing semicolon, bracket)\n- Single-line fixes that were immediately obvious\n\nIf skipping, briefly explain why: \"This was a simple typo fix - skipping documentation.\"\n\n### Step 2: Gather Context\n\nRead [schema.yaml](schema.yaml) to get valid enum values, then extract from the conversation:\n\n| Field      | Required | Description                                       |\n| ---------- | -------- | ------------------------------------------------- |\n| Symptom    | Yes      | Error message or observable behavior              |\n| Category   | Yes      | From schema.yaml `category.values` (or add new)   |\n| Component  | No       | From schema.yaml `component.values` (or add new)  |\n| Root cause | No       | From schema.yaml `root_cause.values` (or add new) |\n| Solution   | Yes      | The fix that worked                               |\n| Prevention | No       | How to avoid this in the future                   |\n\n**If a value doesn't exist in schema.yaml:**\n\n1. Add the new value to the appropriate enum in `schema.yaml`\n2. If it's a new category, create the directory: `mkdir -p {output_dir}\u002F{new-category}`\n\n**If critical info is missing, ask:**\n\n```\nTo document this fix, I need a few details:\n\n1. Category: What type of issue was this?\n   [list current values from schema.yaml]\n   Or suggest a new category if none fit\n```\n\n### Step 3: Check for Similar Issues\n\nBefore creating a new doc, search for similar existing issues:\n\n1. **Keyword match** - Search `{output_dir}\u002F` for error message fragments or key symptom phrases\n2. **File path match** - Check if the same files are involved in existing docs\n3. **Import\u002Fdependency match** - Check if the same libraries or modules are mentioned\n\n```bash\n# Example searches\ngrep -rl \"ErrorMessage\" docs\u002Fsolutions\u002F\ngrep -l \"path\u002Fto\u002Ffile\" docs\u002Fsolutions\u002F**\u002F*.md\n```\n\n**If potential matches found:**\n\n```\nFound potentially related issues:\n- docs\u002Fsolutions\u002Fintegration\u002Fapi-timeout-20250102.md\n- docs\u002Fsolutions\u002Fintegration\u002Fauth-header-missing-20250105.md\n\nAre any of these the same or related issue? (y\u002Fn)\n```\n\nIf related, add to the `related` field in frontmatter.\n\n### Step 4: Create Documentation\n\n**Validate against schema.yaml:**\n\n1. Read schema.yaml for current valid enum values\n2. Ensure all required fields are present\n3. Ensure enum values exist (or add them first)\n\n**Generate filename:**\n\n- Format: `{sanitized-symptom}-{YYYYMMDD}.md`\n- Sanitize: lowercase, replace spaces with hyphens, remove special chars, truncate to 80 chars\n\n**Create file at:** `{output_dir}\u002F{category}\u002F{filename}`\n\n**Ensure directory exists:**\n\n```bash\nmkdir -p {output_dir}\u002F{category}\n```\n\n**Use the Solution Doc Template below.**\n\n### Step 5: Pattern Promotion\n\nAfter creating the doc, check if this issue has occurred multiple times.\n\n**If similar issues >= threshold (default: 2):**\n\n```\nThis issue has occurred {N} times:\n- {link to issue 1}\n- {link to issue 2}\n- {link to current issue}\n\nPromote to patterns.md? This surfaces it prominently for future sessions.\n1. Yes - Add to patterns\n2. No - Keep as regular doc only\n```\n\n**If yes:** Append to `{output_dir}\u002Fpatterns.md` using the Pattern Template below.\n\n## Solution Doc Template\n\n````markdown\n---\ndate: { YYYY-MM-DD }\ncategory: { category }\nsymptoms:\n  - { symptom 1 }\n  - { symptom 2 }\ncomponent: { component }\nroot_cause: { root_cause }\ntags: [{ keyword1 }, { keyword2 }]\nrelated: []\n---\n\n# {Problem Title}\n\n## Problem\n\n{1-2 sentence description of what went wrong}\n\n## Symptoms\n\n- {What you observed - error messages, behavior, etc.}\n\n## What Didn't Work\n\n- {Attempted solution 1} - {Why it failed}\n- {Attempted solution 2} - {Why it failed}\n\n## Solution\n\n{Description of the fix}\n\n```{language}\n# Before (broken)\n{code before}\n\n# After (fixed)\n{code after}\n```\n````\n\n## Why This Works\n\n{Technical explanation of the root cause and why the solution addresses it}\n\n## Prevention\n\n{How to avoid this in the future - tests, linting rules, patterns to follow}\n\n````\n\n## Pattern Template\n\nWhen adding to `patterns.md`:\n\n```markdown\n## {Pattern Name}\n\n**Occurrences:** {N} times ({link1}, {link2}, ...)\n\n### WRONG\n\n```{language}\n{code that causes the problem}\n````\n\n### CORRECT\n\n```{language}\n{code that fixes it}\n```\n\n**Why:** {Technical explanation}\n\n**When this applies:** {Context or conditions when this pattern is relevant}\n\n````\n\n## Integration\n\n### Reference in AGENTS.md\n\nAdd to your project's AGENTS.md to ensure patterns are checked:\n\n```markdown\n## Required Reading\n\nBefore making changes, review known patterns:\n- [Solution Patterns](docs\u002Fsolutions\u002Fpatterns.md)\n````\n\n### Consuming Solutions\n\nOther workflows can discover and apply documented solutions:\n\n**Search by keyword:**\n\n```bash\ngrep -rl \"keyword\" docs\u002Fsolutions\u002F\n```\n\n**Search by category:**\n\n```bash\nls docs\u002Fsolutions\u002Fdeployment\u002F\n```\n\n**Search by tag:**\n\n```bash\ngrep -l \"tags:.*docker\" docs\u002Fsolutions\u002F**\u002F*.md\n```\n\n`patterns.md` is the primary integration point - check it first for critical patterns before making changes.\n\n## Example Scenario\n\n**User:** \"That worked! The Docker build was failing because of the cache issue.\"\n\n**Agent response:**\n\n```\nGreat! Let me document this fix.\n\n**Reading schema.yaml...**\nCurrent categories: developer-experience, deployment, ui, integration, performance, testing\nCurrent components: (none yet)\nCurrent root_causes: (none yet)\n\n**Gathering context...**\n\nFrom our conversation:\n- Symptom: Docker build failing with \"layer not found\" error\n- Category: deployment\n- Component: docker (adding to schema.yaml)\n- Root cause: stale-cache (adding to schema.yaml)\n- Solution: Added `--no-cache` flag and updated base image tag\n- Prevention: Pin base image versions, use `docker system prune` periodically\n\n**Updating schema.yaml...**\nAdded 'docker' to component.values\nAdded 'stale-cache' to root_cause.values\n\n**Checking for similar issues...**\nNo related issues found.\n\n**Creating documentation...**\nCreated: docs\u002Fsolutions\u002Fdeployment\u002Fdocker-layer-not-found-20250106.md\n\nDocumentation complete.\n```\n",{"name":5,"license":15,"version":24,"description":7,"compatibility":25},"0.1.0-beta","opencode","master","63f17866001c5ca854bf2fa0b678ce277133de5b","skills\u002Fmarketplace\u002Fcompound-docs",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 compound-docs",{"tool":42,"command":43},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill compound-docs",{"tool":45,"command":46},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill compound-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fcompound-docs\u002FSKILL.md",true,[50,56,60,64],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"README.md","REFERENCE","参考文档",1201,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fcompound-docs\u002FREADME.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"schema.yaml",1842,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fcompound-docs\u002Fschema.yaml",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"skill-report.json",53568,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fcompound-docs\u002Fskill-report.json",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"skill.json",349,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fcompound-docs\u002Fskill.json",[69,77,84,91,98,105],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":76},"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":76},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":76},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":76},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":76},"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":76},"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",[],[]]