[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76J2E1HB4G596CZDYP4S3QH":3,"skill-same:01M76J2E1HB4G596CZDYP4S3QH":57},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M76J2E1HB4G596CZDYP4S3QH","nestjs-architecture-principles",null,"Designs and reviews NestJS application architecture using cohesive feature modules, modular monoliths, layered or hexagonal boundaries, dependency inversion, and pragmatic engineering principles. Use when planning a NestJS project, changing module boundaries, evaluating Clean Architecture or DDD, resolving circular dependencies, defining ports and adapters, reviewing coupling, or deciding whether CQRS or microservices are justified. Do not use for pure frontend work or non-NestJS backends. When other skills also apply, reconcile ownership before mutation.","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\u002Fnestjs-architecture-principles\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: nestjs-architecture-principles\ndescription: 'Designs and reviews NestJS application architecture using cohesive feature modules, modular monoliths, layered or hexagonal boundaries, dependency inversion, and pragmatic engineering principles. Use when planning a NestJS project, changing module boundaries, evaluating Clean Architecture or DDD, resolving circular dependencies, defining ports and adapters, reviewing coupling, or deciding whether CQRS or microservices are justified. Do not use for pure frontend work or non-NestJS backends. When other skills also apply, reconcile ownership before mutation.'\nlicense: MIT\nmetadata:\n  author: amirtaherkhani\n  version: '1.1.2'\n---\n\n# NestJS Architecture and Principles\n\nMake architecture decisions from the repository's actual constraints. Prefer the least complex design that protects the required boundaries and can evolve safely.\n\n## Pre-execution conflict guard\n\nBefore editing files or running any state-changing command, reconcile active instructions. Read-only inspection may continue.\n\n### Prerequisites\n\nInspect repository instructions, installed versions, module wiring, contracts, callers, tests, and affected commands. Preserve user changes. Read other active skills only when their decisions overlap.\n\n### Primary ownership\n\nThis skill owns architecture level, capability\u002Fmodule APIs, dependency direction, data\u002Fwrite and transaction boundaries, ports, and service extraction. When installed and relevant, coordinate with:\n\n- `nestjs-oop-design-patterns`: object responsibilities, invariants, and patterns.\n- `nestjs-features-performance`: lifecycle, API\u002Fsecurity, testing, runtime, and performance.\n- `nestjs-professional-software-engineering`: implementation and verification.\n- `nestjs-code-audit`: read-only quality evidence and deduplicated reporting.\n- `nestjs-feature-audit`: branch-specific roadmap gate and feature reporting.\n- `nestjs-git-commit-pr-message`: authorized Git publication and CI follow-up.\n\nThese are decision boundaries, not required dependencies. Retain domain ownership when handing work to another workflow.\n\n### Conflict test\n\nCheck for incompatible edits\u002Fcontracts, command order or side effects, competing owners, and unmet version, evidence, authorization, or repository prerequisites. Resolve using explicit user intent, repository contracts, verified runtime constraints, then the narrowest owner. Assign one lead per decision; do not create parallel designs to satisfy incompatible advice. If a material conflict remains, stop before mutation and ask for the smallest missing decision. Audits stay read-only; explicit fix authorization applies in a distinct implementation phase.\n\n## Start with evidence\n\nBefore recommending or changing architecture:\n\n1. Read `package.json`, `nest-cli.json`, TypeScript configuration, bootstrap files, and the relevant modules.\n2. Map the module import graph, provider exports, entry points, persistence ownership, transports, and existing tests.\n3. Identify the business capability and the concrete change pressure: team ownership, independent scaling, volatile integrations, transaction boundaries, security, or delivery speed.\n4. State the current architecture in one sentence. Do not label a project \"Clean Architecture\" or \"DDD\" from folder names alone.\n5. Preserve healthy local conventions. Flag a convention only when it damages correctness, security, operability, or an explicit contract.\n\nIf the task is version-sensitive, verify the installed NestJS version and current official documentation before using an API or command.\n\n## Choose the architecture level\n\nUse the architecture ladder in [references\u002Farchitecture-ladder.md](references\u002Farchitecture-ladder.md).\n\nDefault direction:\n\n- Start with a modular monolith organized by business capability.\n- Add internal layers when domain logic or infrastructure volatility makes the boundary valuable.\n- Add ports where the application needs to isolate a replaceable external concern.\n- Add CQRS only when command and query behavior genuinely diverge.\n- Split a service only when it has an independent deployment, ownership, scaling, data, or failure boundary.\n\nNever introduce layers, buses, repositories, factories, or services only to make the folder tree resemble a diagram.\n\n## Protect these boundaries\n\n1. **Modules expose a small public API.** Providers are private unless another module has a real use for them.\n2. **A business capability owns its invariants and writes.** Other modules collaborate through an exported application service, port, event, or deliberately designed read model.\n3. **Dependencies point toward policy.** Domain code does not import NestJS, an ORM, HTTP types, queue jobs, or vendor SDKs.\n4. **Controllers and transport handlers adapt.** They authenticate\u002Fauthorize through framework mechanisms, validate transport input, invoke an application operation, and map the result.\n5. **Application operations coordinate.** They define use-case flow and transaction intent without absorbing persistence or transport details.\n6. **Infrastructure implements edges.** ORMs, brokers, caches, file systems, and external APIs stay behind explicit boundaries when their volatility or test cost warrants it.\n7. **Cycles are design feedback.** Treat `forwardRef()` as a last-resort compatibility tool, not the default fix.\n8. **The composition root owns wiring.** Nest modules and providers assemble implementations; business objects do not locate dependencies at runtime.\n\nFor the consolidated rule set, load [references\u002Farchitecture-rules.md](references\u002Farchitecture-rules.md). For detailed NestJS boundaries, load [references\u002Fmodule-boundaries.md](references\u002Fmodule-boundaries.md) and [references\u002Fdependency-injection.md](references\u002Fdependency-injection.md).\n\n## Apply principles pragmatically\n\nUse [references\u002Fengineering-principles.md](references\u002Fengineering-principles.md) as decision tests, not slogans.\n\nWhen principles conflict, prefer this order:\n\n1. correctness, security, and data integrity;\n2. explicit external contracts and backward compatibility;\n3. operability and failure containment;\n4. established repository conventions;\n5. design purity and local elegance.\n\nKISS does not mean hiding failure cases. DRY does not mean abstracting coincidental similarity. SOLID does not require one class per verb. YAGNI does not excuse a boundary already demanded by a known requirement.\n\n## Workflow\n\n### For a new design\n\n1. Define goals, constraints, non-goals, critical quality attributes, and expected change axes.\n2. Choose the lowest architecture level that satisfies them.\n3. Name capabilities and ownership before naming technical layers.\n4. Draw dependencies and data ownership. Reject ambiguous write ownership.\n5. Specify synchronous calls, events, transactions, and failure behavior.\n6. Produce one recommended design and explain what it intentionally does not optimize.\n7. Define architecture tests, integration tests, and operational checks that protect the decision.\n\n### For an implementation or refactor\n\n1. Trace the relevant request, message, or job end to end.\n2. Identify the smallest boundary violation that causes the problem.\n3. Move behavior toward its owner before adding an abstraction.\n4. Introduce a port only if there are multiple implementations, a volatile edge, or a valuable test seam.\n5. Keep the change incremental and preserve the public contract unless the user requested a migration.\n6. Update affected tests, module wiring, documentation, and callers.\n\n### For a review\n\nUse [references\u002Farchitecture-review.md](references\u002Farchitecture-review.md). Report evidence-backed findings with severity, impact, a minimal remedy, and a validation step. Do not propose a rewrite when a boundary repair is sufficient.\n\n## Reference routing\n\n| Task | Load |\n| --- | --- |\n| Apply or review the consolidated architecture rules | [architecture-rules.md](references\u002Farchitecture-rules.md) |\n| Choose modular monolith, layers, hexagonal, CQRS, or services | [architecture-ladder.md](references\u002Farchitecture-ladder.md) |\n| Design feature modules, exports, ownership, or remove cycles | [module-boundaries.md](references\u002Fmodule-boundaries.md) |\n| Define provider tokens, ports, scopes, factories, or dynamic modules | [dependency-injection.md](references\u002Fdependency-injection.md) |\n| Define database ownership, repositories, migrations, transactions, or ORM boundaries | [database-orm.md](references\u002Fdatabase-orm.md) |\n| Decide service extraction, distributed data ownership, contracts, or messaging semantics | [microservices.md](references\u002Fmicroservices.md) |\n| Apply KISS, YAGNI, DRY, cohesion, coupling, and dependency rules | [engineering-principles.md](references\u002Fengineering-principles.md) |\n| Audit a repository or plan an incremental migration | [architecture-review.md](references\u002Farchitecture-review.md) |\n\n## Expected response\n\nFor architecture work, make the result easy to evaluate:\n\n- **Baseline:** current architecture and evidence.\n- **Decision:** one recommended direction.\n- **Why:** constraints and trade-offs that drive it.\n- **Boundaries:** module ownership, dependency direction, data ownership, and integration style.\n- **Migration:** smallest safe sequence, when change is needed.\n- **Validation:** tests, graph checks, runtime checks, and operational signals.\n\nIf no architecture change is justified, say so directly.\n","# NestJS Architecture and Principles\n\nMake architecture decisions from the repository's actual constraints. Prefer the least complex design that protects the required boundaries and can evolve safely.\n\n## Pre-execution conflict guard\n\nBefore editing files or running any state-changing command, reconcile active instructions. Read-only inspection may continue.\n\n### Prerequisites\n\nInspect repository instructions, installed versions, module wiring, contracts, callers, tests, and affected commands. Preserve user changes. Read other active skills only when their decisions overlap.\n\n### Primary ownership\n\nThis skill owns architecture level, capability\u002Fmodule APIs, dependency direction, data\u002Fwrite and transaction boundaries, ports, and service extraction. When installed and relevant, coordinate with:\n\n- `nestjs-oop-design-patterns`: object responsibilities, invariants, and patterns.\n- `nestjs-features-performance`: lifecycle, API\u002Fsecurity, testing, runtime, and performance.\n- `nestjs-professional-software-engineering`: implementation and verification.\n- `nestjs-code-audit`: read-only quality evidence and deduplicated reporting.\n- `nestjs-feature-audit`: branch-specific roadmap gate and feature reporting.\n- `nestjs-git-commit-pr-message`: authorized Git publication and CI follow-up.\n\nThese are decision boundaries, not required dependencies. Retain domain ownership when handing work to another workflow.\n\n### Conflict test\n\nCheck for incompatible edits\u002Fcontracts, command order or side effects, competing owners, and unmet version, evidence, authorization, or repository prerequisites. Resolve using explicit user intent, repository contracts, verified runtime constraints, then the narrowest owner. Assign one lead per decision; do not create parallel designs to satisfy incompatible advice. If a material conflict remains, stop before mutation and ask for the smallest missing decision. Audits stay read-only; explicit fix authorization applies in a distinct implementation phase.\n\n## Start with evidence\n\nBefore recommending or changing architecture:\n\n1. Read `package.json`, `nest-cli.json`, TypeScript configuration, bootstrap files, and the relevant modules.\n2. Map the module import graph, provider exports, entry points, persistence ownership, transports, and existing tests.\n3. Identify the business capability and the concrete change pressure: team ownership, independent scaling, volatile integrations, transaction boundaries, security, or delivery speed.\n4. State the current architecture in one sentence. Do not label a project \"Clean Architecture\" or \"DDD\" from folder names alone.\n5. Preserve healthy local conventions. Flag a convention only when it damages correctness, security, operability, or an explicit contract.\n\nIf the task is version-sensitive, verify the installed NestJS version and current official documentation before using an API or command.\n\n## Choose the architecture level\n\nUse the architecture ladder in [references\u002Farchitecture-ladder.md](references\u002Farchitecture-ladder.md).\n\nDefault direction:\n\n- Start with a modular monolith organized by business capability.\n- Add internal layers when domain logic or infrastructure volatility makes the boundary valuable.\n- Add ports where the application needs to isolate a replaceable external concern.\n- Add CQRS only when command and query behavior genuinely diverge.\n- Split a service only when it has an independent deployment, ownership, scaling, data, or failure boundary.\n\nNever introduce layers, buses, repositories, factories, or services only to make the folder tree resemble a diagram.\n\n## Protect these boundaries\n\n1. **Modules expose a small public API.** Providers are private unless another module has a real use for them.\n2. **A business capability owns its invariants and writes.** Other modules collaborate through an exported application service, port, event, or deliberately designed read model.\n3. **Dependencies point toward policy.** Domain code does not import NestJS, an ORM, HTTP types, queue jobs, or vendor SDKs.\n4. **Controllers and transport handlers adapt.** They authenticate\u002Fauthorize through framework mechanisms, validate transport input, invoke an application operation, and map the result.\n5. **Application operations coordinate.** They define use-case flow and transaction intent without absorbing persistence or transport details.\n6. **Infrastructure implements edges.** ORMs, brokers, caches, file systems, and external APIs stay behind explicit boundaries when their volatility or test cost warrants it.\n7. **Cycles are design feedback.** Treat `forwardRef()` as a last-resort compatibility tool, not the default fix.\n8. **The composition root owns wiring.** Nest modules and providers assemble implementations; business objects do not locate dependencies at runtime.\n\nFor the consolidated rule set, load [references\u002Farchitecture-rules.md](references\u002Farchitecture-rules.md). For detailed NestJS boundaries, load [references\u002Fmodule-boundaries.md](references\u002Fmodule-boundaries.md) and [references\u002Fdependency-injection.md](references\u002Fdependency-injection.md).\n\n## Apply principles pragmatically\n\nUse [references\u002Fengineering-principles.md](references\u002Fengineering-principles.md) as decision tests, not slogans.\n\nWhen principles conflict, prefer this order:\n\n1. correctness, security, and data integrity;\n2. explicit external contracts and backward compatibility;\n3. operability and failure containment;\n4. established repository conventions;\n5. design purity and local elegance.\n\nKISS does not mean hiding failure cases. DRY does not mean abstracting coincidental similarity. SOLID does not require one class per verb. YAGNI does not excuse a boundary already demanded by a known requirement.\n\n## Workflow\n\n### For a new design\n\n1. Define goals, constraints, non-goals, critical quality attributes, and expected change axes.\n2. Choose the lowest architecture level that satisfies them.\n3. Name capabilities and ownership before naming technical layers.\n4. Draw dependencies and data ownership. Reject ambiguous write ownership.\n5. Specify synchronous calls, events, transactions, and failure behavior.\n6. Produce one recommended design and explain what it intentionally does not optimize.\n7. Define architecture tests, integration tests, and operational checks that protect the decision.\n\n### For an implementation or refactor\n\n1. Trace the relevant request, message, or job end to end.\n2. Identify the smallest boundary violation that causes the problem.\n3. Move behavior toward its owner before adding an abstraction.\n4. Introduce a port only if there are multiple implementations, a volatile edge, or a valuable test seam.\n5. Keep the change incremental and preserve the public contract unless the user requested a migration.\n6. Update affected tests, module wiring, documentation, and callers.\n\n### For a review\n\nUse [references\u002Farchitecture-review.md](references\u002Farchitecture-review.md). Report evidence-backed findings with severity, impact, a minimal remedy, and a validation step. Do not propose a rewrite when a boundary repair is sufficient.\n\n## Reference routing\n\n| Task | Load |\n| --- | --- |\n| Apply or review the consolidated architecture rules | [architecture-rules.md](references\u002Farchitecture-rules.md) |\n| Choose modular monolith, layers, hexagonal, CQRS, or services | [architecture-ladder.md](references\u002Farchitecture-ladder.md) |\n| Design feature modules, exports, ownership, or remove cycles | [module-boundaries.md](references\u002Fmodule-boundaries.md) |\n| Define provider tokens, ports, scopes, factories, or dynamic modules | [dependency-injection.md](references\u002Fdependency-injection.md) |\n| Define database ownership, repositories, migrations, transactions, or ORM boundaries | [database-orm.md](references\u002Fdatabase-orm.md) |\n| Decide service extraction, distributed data ownership, contracts, or messaging semantics | [microservices.md](references\u002Fmicroservices.md) |\n| Apply KISS, YAGNI, DRY, cohesion, coupling, and dependency rules | [engineering-principles.md](references\u002Fengineering-principles.md) |\n| Audit a repository or plan an incremental migration | [architecture-review.md](references\u002Farchitecture-review.md) |\n\n## Expected response\n\nFor architecture work, make the result easy to evaluate:\n\n- **Baseline:** current architecture and evidence.\n- **Decision:** one recommended direction.\n- **Why:** constraints and trade-offs that drive it.\n- **Boundaries:** module ownership, dependency direction, data ownership, and integration style.\n- **Migration:** smallest safe sequence, when change is needed.\n- **Validation:** tests, graph checks, runtime checks, and operational signals.\n\nIf no architecture change is justified, say so directly.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"amirtaherkhani","1.1.2","master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fmarketplace\u002Fnestjs-architecture-principles",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill nestjs-architecture-principles",{"tool":43,"command":44},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill nestjs-architecture-principles",{"tool":46,"command":47},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill nestjs-architecture-principles","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fnestjs-architecture-principles\u002FSKILL.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"skill-report.json","REFERENCE","参考文档",28407,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fnestjs-architecture-principles\u002Fskill-report.json",[58,66,73,80,87,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":65},"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":65},"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":65},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":65},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":65},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":65},"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",[],[]]