[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76H878XH3C987E00404QQDM":3,"skill-same:01M76H878XH3C987E00404QQDM":69},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":62},"01M76H878XH3C987E00404QQDM","golang-samber-do",null,"Dependency injection in Golang using samber\u002Fdo — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Apply when using or adopting samber\u002Fdo, when the codebase imports github.com\u002Fsamber\u002Fdo or github.com\u002Fsamber\u002Fdo\u002Fv2, or when refactoring manual constructor injection into a DI container.","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\u002Fgolang-samber-do\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: golang-samber-do\ndescription: \"Dependency injection in Golang using samber\u002Fdo — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Apply when using or adopting samber\u002Fdo, when the codebase imports github.com\u002Fsamber\u002Fdo or github.com\u002Fsamber\u002Fdo\u002Fv2, or when refactoring manual constructor injection into a DI container.\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code, Codex or similar harness, and for projects using Golang.\nmetadata:\n  author: samber\n  version: \"1.3.2\"\n  openclaw:\n    emoji: \"💉\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n    install: []\n    skill-library-version: \"2.0.0\"\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch mcp__context7__resolve-library-id mcp__context7__query-docs Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__*\npaths:\n  - \"**\u002F*.go\"\n---\n\n**Persona:** You are a Go architect setting up dependency injection. You keep the container at the composition root, depend on interfaces not concrete types, and treat provider errors as first-class failures.\n\n# Using samber\u002Fdo for Dependency Injection in Go\n\nType-safe dependency injection toolkit for Go based on Go 1.18+ generics.\n\n**Official Resources:**\n\n- [pkg.go.dev\u002Fgithub.com\u002Fsamber\u002Fdo\u002Fv2](https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fsamber\u002Fdo\u002Fv2)\n- [do.samber.dev](https:\u002F\u002Fdo.samber.dev)\n- [github.com\u002Fsamber\u002Fdo\u002Fv2](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fdo)\n\nThis skill is not exhaustive — refer to library documentation and code examples for more information:\n\n- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`), preferred over Context7 for Go package facts.\n- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`).\n- Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\nInstall v2 — v1 is superseded and lacks the generics-based container, scopes, and lifecycle hooks documented below, so v1-era guidance misleads on every API in this skill:\n\n```bash\ngo get -u github.com\u002Fsamber\u002Fdo\u002Fv2\n```\n\n## Core Concepts\n\n### The Injector (Container)\n\n```go\nimport \"github.com\u002Fsamber\u002Fdo\u002Fv2\"\n\ninjector := do.New()\n```\n\n### Service Types\n\n- **Lazy** (default): Created when first requested\n- **Eager**: Created immediately when the container starts\n- **Transient**: New instance created on every request\n- **Value**: Pre-created value, no instantiation\n\n### Provider Functions\n\nServices MUST be registered via provider functions:\n\n```go\ntype Provider[T any] func(i Injector) (T, error)\n```\n\n## Basic Usage\n\n### 1. Define and Register Services\n\nFollow \"Accept Interfaces, Return Structs\":\n\n```go\n\u002F\u002F Register a service (lazy by default)\ndo.Provide(injector, func(i do.Injector) (Database, error) {\n    return &PostgreSQLDatabase{connString: \"postgres:\u002F\u002F...\"}, nil\n})\n\n\u002F\u002F Register a pre-created value\ndo.ProvideValue(injector, &Config{Port: 8080})\n\n\u002F\u002F Register a transient service (new instance each time)\ndo.ProvideTransient(injector, func(i do.Injector) (*Logger, error) {\n    return &Logger{}, nil\n})\n\n\u002F\u002F Register an eager service (created immediately at startup)\ndo.ProvideValue(injector, &Config{Port: 8080})\n```\n\n### 2. Invoke Services\n\nThe container MUST only be accessed at the composition root:\n\n```go\n\u002F\u002F Invoke with error handling — reserve for call sites outside the DI graph\n\u002F\u002F (e.g. an HTTP handler that must degrade gracefully instead of crashing)\ndb, err := do.Invoke[Database](injector)\n\n\u002F\u002F MustInvoke panics on error — preferred in providers, recovered by do.Invoke on the parent call\ndb := do.MustInvoke[Database](injector)\n```\n\nInside a provider function, always use `do.MustInvoke` (or `MustInvokeAs`\u002F`MustInvokeNamed`\u002F`MustInvokeStruct`) rather than the error-returning variant:\n\n- A provider already returns `(T, error)`, so propagating a dependency failure with `do.Invoke` costs an extra `if err != nil { return nil, err }` on every call.\n- `do.MustInvoke` panics instead, but samber\u002Fdo correctly catches and recovers that panic at the enclosing `Invoke` call and converts it back into a regular error — this recover happens inside the library itself, not in caller code, so `MustInvoke` is safe to use inside providers.\n- The failure still surfaces as an error at the composition root, just without the manual boilerplate in every provider.\n\n### 3. Service Dependencies\n\n```go\nfunc NewUserService(i do.Injector) (UserService, error) {\n    db := do.MustInvoke[Database](i)\n    cache := do.MustInvoke[Cache](i)\n    return &userService{db: db, cache: cache}, nil\n}\n\ndo.Provide(injector, NewUserService)\n```\n\n### 4. Implicit Aliasing (Preferred)\n\nRegister a concrete type and invoke as an interface without explicit aliasing:\n\n```go\n\u002F\u002F Register concrete type\ndo.Provide(injector, func(i do.Injector) (*PostgreSQLDatabase, error) {\n    return &PostgreSQLDatabase{}, nil\n})\n\n\u002F\u002F Invoke directly as interface (implicit aliasing)\ndb := do.MustInvokeAs[Database](injector)\n```\n\n### 5. Named Services\n\nRegister multiple services of the same type:\n\n```go\ndo.ProvideNamed(injector, \"primary-db\", func(i do.Injector) (*Database, error) {\n    return &Database{URL: \"postgres:\u002F\u002Fprimary...\"}, nil\n})\n\nmainDB := do.MustInvokeNamed[*Database](injector, \"primary-db\")\n```\n\n## Package Organization\n\nUse `do.Package()` to organize service registration by module:\n\n```go\n\u002F\u002F infrastructure\u002Fpackage.go\nvar Package = do.Package(\n    do.Lazy(func(i do.Injector) (*postgres.DB, error) {\n        cfg := do.MustInvoke[*Config](i)\n        return postgres.Connect(cfg.DatabaseURL)\n    }),\n    do.Lazy(func(i do.Injector) (*redis.Client, error) {\n        cfg := do.MustInvoke[*Config](i)\n        return redis.NewClient(cfg.RedisURL), nil\n    }),\n)\n\n\u002F\u002F main.go\ninjector := do.New(infrastructure.Package, service.Package)\n```\n\n## Full Application Setup\n\n```go\nfunc main() {\n    injector := do.New(\n        infrastructure.Package,\n        repository.Package,\n        service.Package,\n        transport.Package,\n    )\n\n    server := do.MustInvoke[*http.Server](injector)\n    go server.ListenAndServe()\n\n    _ = injector.ShutdownOnSignalsWithContext(context.Background(), os.Interrupt)\n}\n```\n\n## Best Practices\n\n1. Depend on interfaces, not concrete types — lets you swap implementations in tests without touching production code\n2. Each service should have one job — services with multiple responsibilities are harder to test and harder to replace\n3. Keep dependency trees shallow — chains beyond 3-4 levels make initialization order fragile and errors harder to trace\n4. Handle errors in provider functions — a silently failing provider creates a broken service that crashes later in unexpected places\n5. Use scopes to organize services by lifecycle — request-scoped services prevent leaks, global services prevent redundant initialization\n6. Use `do.MustInvoke*` inside provider functions instead of `do.Invoke*` — samber\u002Fdo correctly catches and recovers the panic at the outer `Invoke` call, turning it back into a returned error, so it's safe to use inside providers and you get the same error propagation without the boilerplate\n\nFor scopes, lifecycle management, struct injection, and debugging, see [Advanced Usage](.\u002Freferences\u002Fadvanced.md).\n\nFor testing patterns (cloning, overrides, mocks), see [Testing](.\u002Freferences\u002Ftesting.md).\n\n## Quick Reference\n\n### Registration\n\n| Function                        | Purpose                          |\n| ------------------------------- | -------------------------------- |\n| `do.Provide[T]()`               | Register lazy service (default)  |\n| `do.ProvideNamed[T]()`          | Register named lazy service      |\n| `do.ProvideValue[T]()`          | Register pre-created value       |\n| `do.ProvideNamedValue[T]()`     | Register named value             |\n| `do.ProvideTransient[T]()`      | Register new instance each time  |\n| `do.ProvideNamedTransient[T]()` | Register named transient service |\n| `do.Package()`                  | Group service registrations      |\n\n### Invocation\n\n| Function                   | Purpose                                   |\n| -------------------------- | ----------------------------------------- |\n| `do.Invoke[T]()`           | Get service (with error)                  |\n| `do.InvokeNamed[T]()`      | Get named service                         |\n| `do.InvokeAs[T]()`         | Get first service matching interface      |\n| `do.InvokeStruct[T]()`     | Inject into struct fields using tags      |\n| `do.MustInvoke[T]()`       | Get service (panic on error)              |\n| `do.MustInvokeNamed[T]()`  | Get named service (panic on error)        |\n| `do.MustInvokeAs[T]()`     | Get service by interface (panic on error) |\n| `do.MustInvokeStruct[T]()` | Inject into struct (panic on error)       |\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-dependency-injection` skill for DI concepts, comparison, and when to adopt a DI library\n- → See `samber\u002Fcc-skills-golang@golang-structs-interfaces` skill for interface design patterns\n- → See `samber\u002Fcc-skills-golang@golang-testing` skill for general testing patterns\n","**Persona:** You are a Go architect setting up dependency injection. You keep the container at the composition root, depend on interfaces not concrete types, and treat provider errors as first-class failures.\n\n# Using samber\u002Fdo for Dependency Injection in Go\n\nType-safe dependency injection toolkit for Go based on Go 1.18+ generics.\n\n**Official Resources:**\n\n- [pkg.go.dev\u002Fgithub.com\u002Fsamber\u002Fdo\u002Fv2](https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fsamber\u002Fdo\u002Fv2)\n- [do.samber.dev](https:\u002F\u002Fdo.samber.dev)\n- [github.com\u002Fsamber\u002Fdo\u002Fv2](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fdo)\n\nThis skill is not exhaustive — refer to library documentation and code examples for more information:\n\n- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`), preferred over Context7 for Go package facts.\n- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`).\n- Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\nInstall v2 — v1 is superseded and lacks the generics-based container, scopes, and lifecycle hooks documented below, so v1-era guidance misleads on every API in this skill:\n\n```bash\ngo get -u github.com\u002Fsamber\u002Fdo\u002Fv2\n```\n\n## Core Concepts\n\n### The Injector (Container)\n\n```go\nimport \"github.com\u002Fsamber\u002Fdo\u002Fv2\"\n\ninjector := do.New()\n```\n\n### Service Types\n\n- **Lazy** (default): Created when first requested\n- **Eager**: Created immediately when the container starts\n- **Transient**: New instance created on every request\n- **Value**: Pre-created value, no instantiation\n\n### Provider Functions\n\nServices MUST be registered via provider functions:\n\n```go\ntype Provider[T any] func(i Injector) (T, error)\n```\n\n## Basic Usage\n\n### 1. Define and Register Services\n\nFollow \"Accept Interfaces, Return Structs\":\n\n```go\n\u002F\u002F Register a service (lazy by default)\ndo.Provide(injector, func(i do.Injector) (Database, error) {\n    return &PostgreSQLDatabase{connString: \"postgres:\u002F\u002F...\"}, nil\n})\n\n\u002F\u002F Register a pre-created value\ndo.ProvideValue(injector, &Config{Port: 8080})\n\n\u002F\u002F Register a transient service (new instance each time)\ndo.ProvideTransient(injector, func(i do.Injector) (*Logger, error) {\n    return &Logger{}, nil\n})\n\n\u002F\u002F Register an eager service (created immediately at startup)\ndo.ProvideValue(injector, &Config{Port: 8080})\n```\n\n### 2. Invoke Services\n\nThe container MUST only be accessed at the composition root:\n\n```go\n\u002F\u002F Invoke with error handling — reserve for call sites outside the DI graph\n\u002F\u002F (e.g. an HTTP handler that must degrade gracefully instead of crashing)\ndb, err := do.Invoke[Database](injector)\n\n\u002F\u002F MustInvoke panics on error — preferred in providers, recovered by do.Invoke on the parent call\ndb := do.MustInvoke[Database](injector)\n```\n\nInside a provider function, always use `do.MustInvoke` (or `MustInvokeAs`\u002F`MustInvokeNamed`\u002F`MustInvokeStruct`) rather than the error-returning variant:\n\n- A provider already returns `(T, error)`, so propagating a dependency failure with `do.Invoke` costs an extra `if err != nil { return nil, err }` on every call.\n- `do.MustInvoke` panics instead, but samber\u002Fdo correctly catches and recovers that panic at the enclosing `Invoke` call and converts it back into a regular error — this recover happens inside the library itself, not in caller code, so `MustInvoke` is safe to use inside providers.\n- The failure still surfaces as an error at the composition root, just without the manual boilerplate in every provider.\n\n### 3. Service Dependencies\n\n```go\nfunc NewUserService(i do.Injector) (UserService, error) {\n    db := do.MustInvoke[Database](i)\n    cache := do.MustInvoke[Cache](i)\n    return &userService{db: db, cache: cache}, nil\n}\n\ndo.Provide(injector, NewUserService)\n```\n\n### 4. Implicit Aliasing (Preferred)\n\nRegister a concrete type and invoke as an interface without explicit aliasing:\n\n```go\n\u002F\u002F Register concrete type\ndo.Provide(injector, func(i do.Injector) (*PostgreSQLDatabase, error) {\n    return &PostgreSQLDatabase{}, nil\n})\n\n\u002F\u002F Invoke directly as interface (implicit aliasing)\ndb := do.MustInvokeAs[Database](injector)\n```\n\n### 5. Named Services\n\nRegister multiple services of the same type:\n\n```go\ndo.ProvideNamed(injector, \"primary-db\", func(i do.Injector) (*Database, error) {\n    return &Database{URL: \"postgres:\u002F\u002Fprimary...\"}, nil\n})\n\nmainDB := do.MustInvokeNamed[*Database](injector, \"primary-db\")\n```\n\n## Package Organization\n\nUse `do.Package()` to organize service registration by module:\n\n```go\n\u002F\u002F infrastructure\u002Fpackage.go\nvar Package = do.Package(\n    do.Lazy(func(i do.Injector) (*postgres.DB, error) {\n        cfg := do.MustInvoke[*Config](i)\n        return postgres.Connect(cfg.DatabaseURL)\n    }),\n    do.Lazy(func(i do.Injector) (*redis.Client, error) {\n        cfg := do.MustInvoke[*Config](i)\n        return redis.NewClient(cfg.RedisURL), nil\n    }),\n)\n\n\u002F\u002F main.go\ninjector := do.New(infrastructure.Package, service.Package)\n```\n\n## Full Application Setup\n\n```go\nfunc main() {\n    injector := do.New(\n        infrastructure.Package,\n        repository.Package,\n        service.Package,\n        transport.Package,\n    )\n\n    server := do.MustInvoke[*http.Server](injector)\n    go server.ListenAndServe()\n\n    _ = injector.ShutdownOnSignalsWithContext(context.Background(), os.Interrupt)\n}\n```\n\n## Best Practices\n\n1. Depend on interfaces, not concrete types — lets you swap implementations in tests without touching production code\n2. Each service should have one job — services with multiple responsibilities are harder to test and harder to replace\n3. Keep dependency trees shallow — chains beyond 3-4 levels make initialization order fragile and errors harder to trace\n4. Handle errors in provider functions — a silently failing provider creates a broken service that crashes later in unexpected places\n5. Use scopes to organize services by lifecycle — request-scoped services prevent leaks, global services prevent redundant initialization\n6. Use `do.MustInvoke*` inside provider functions instead of `do.Invoke*` — samber\u002Fdo correctly catches and recovers the panic at the outer `Invoke` call, turning it back into a returned error, so it's safe to use inside providers and you get the same error propagation without the boilerplate\n\nFor scopes, lifecycle management, struct injection, and debugging, see [Advanced Usage](.\u002Freferences\u002Fadvanced.md).\n\nFor testing patterns (cloning, overrides, mocks), see [Testing](.\u002Freferences\u002Ftesting.md).\n\n## Quick Reference\n\n### Registration\n\n| Function                        | Purpose                          |\n| ------------------------------- | -------------------------------- |\n| `do.Provide[T]()`               | Register lazy service (default)  |\n| `do.ProvideNamed[T]()`          | Register named lazy service      |\n| `do.ProvideValue[T]()`          | Register pre-created value       |\n| `do.ProvideNamedValue[T]()`     | Register named value             |\n| `do.ProvideTransient[T]()`      | Register new instance each time  |\n| `do.ProvideNamedTransient[T]()` | Register named transient service |\n| `do.Package()`                  | Group service registrations      |\n\n### Invocation\n\n| Function                   | Purpose                                   |\n| -------------------------- | ----------------------------------------- |\n| `do.Invoke[T]()`           | Get service (with error)                  |\n| `do.InvokeNamed[T]()`      | Get named service                         |\n| `do.InvokeAs[T]()`         | Get first service matching interface      |\n| `do.InvokeStruct[T]()`     | Inject into struct fields using tags      |\n| `do.MustInvoke[T]()`       | Get service (panic on error)              |\n| `do.MustInvokeNamed[T]()`  | Get named service (panic on error)        |\n| `do.MustInvokeAs[T]()`     | Get service by interface (panic on error) |\n| `do.MustInvokeStruct[T]()` | Inject into struct (panic on error)       |\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-dependency-injection` skill for DI concepts, comparison, and when to adopt a DI library\n- → See `samber\u002Fcc-skills-golang@golang-structs-interfaces` skill for interface design patterns\n- → See `samber\u002Fcc-skills-golang@golang-testing` skill for general testing patterns\n",{"name":5,"paths":24,"license":15,"metadata":26,"description":7,"allowed-tools":37,"compatibility":38,"user-invocable":39},[25],"**\u002F*.go",{"author":27,"version":28,"openclaw":29},"samber","1.3.2",{"emoji":30,"install":31,"homepage":32,"requires":33,"skill-library-version":36},"💉",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":34},[35],"go","2.0.0","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch mcp__context7__resolve-library-id mcp__context7__query-docs Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__*","Designed for Claude Code, Codex or similar harness, and for projects using Golang.",true,"master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fmarketplace\u002Fgolang-samber-do",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":51,"prompt":61,"zipAvailable":39},[52,55,58],{"tool":53,"command":54},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill golang-samber-do",{"tool":56,"command":57},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill golang-samber-do",{"tool":59,"command":60},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill golang-samber-do","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fgolang-samber-do\u002FSKILL.md",[63],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"skill-report.json","REFERENCE","参考文档",52015,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fgolang-samber-do\u002Fskill-report.json",[70,78,85,92,99,106],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":77},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":77},"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":77},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":77},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":77},"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",[],[]]