Skip to content
Back to search

lazyweb

Use Lazyweb to find real product evidence, improve conversion, and turn research into clear product decisions.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/LazywebHQ/lazyweb-skill with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/LazywebHQ/lazyweb-skill'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/aboul3ata--lazyweb-skill/badge.svg)](/listings/aboul3ata--lazyweb-skill)

HTML

<a href="/listings/aboul3ata--lazyweb-skill"><img src="/api/listings/aboul3ata--lazyweb-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

Paste this into a local coding agent or terminal:

curl -fsSL https://www.lazyweb.com/install.sh | bash

Fresh installs may receive a signed installation-experiment assignment when this script is served. Agents can pass the user's actual goal, discovery evidence, company, and intended outcome, but missing or invalid attribution never blocks installation. The installer never invents those answers. Valid discovery sources are `user_request`, `web_search`, `reddit`, `shared_url`, `llms_txt`, `agent_docs`, `webmcp`, `other`, and `unknown`. Never include private chain-of-thought. When the command came from a tracked Lazyweb agent document, the wrapper also passes an internal `--journey-id` so the installation can be joined to the public Lazyweb resources that agent fetched first. Valid signed assignments and journey context are recorded when available; setup continues without them. Existing-token updates never ask for acquisition context again.

The installer clones this repo to `~/.lazyweb/repos/lazyweb-skill`, creates or reuses `~/.lazyweb/lazyweb_mcp_token`, installs the visible Lazyweb skills into detected local clients, and configures Lazyweb MCP at `https://www.lazyweb.com/mcp`.

Approved private-workspace users should sign in with OAuth on the existing `lazyweb` MCP entry. In Codex, run `codex mcp add lazyweb --url https://www.lazyweb.com/mcp --oauth-client-registration dcr` and verify the account email. Future skill-pack updates preserve that OAuth connection instead of replacing it with the public install token.

When an agent client launches the installer, setup targets that active client only. A plain terminal run without an active-client signal still detects local clients; use `--host all` when you deliberately want every supported client.

Downloading or updating the skill pack, installing or configuring a client, and creating or reusing a bearer token are available to everyone without charge. Setup, health, and workflow discovery remain usable regardless of plan; real data-bearing MCP tool availability and usage limits depend on the account's persisted experiment assignment and plan.

Supported local skill roots:

- Codex: `~/.codex/skills` - Claude Code: `~/.claude/skills` - Cursor: `~/.cursor/skills` - OpenCode: `~/.config/opencode/skills` - Kiro: `~/.kiro/skills` - Factory Droid: `~/.factory/skills` - Slate: `~/.slate/skills` - Hermes: `~/.hermes/skills`

Direct MCP config is written for Codex, Claude Code, Cursor, and Antigravity. For hosted Claude or ChatGPT surfaces, use the connector instructions at `https://www.lazyweb.com/claude.md` or `https://www.lazyweb.com/chatgpt.md`; a local shell script cannot configure those cloud UIs.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 52 lines · 1 finding marked
  1. ---
  2. name: lazyweb
  3. description: Use Lazyweb to find real product evidence, improve conversion, and turn research into clear product decisions.
  4. router-exclude: true
  5. allowed-tools:
  6. - Bash
  7. ---
  8. # Lazyweb
  9. Use the live Lazyweb MCP tool list as the source of truth. This skill only
  10. routes; it does not carry schemas, scoring rules, taxonomies, or product logic.
  11. When the client advertises `lazyweb_discover_tools` and `lazyweb_execute`,
  12. discover the desired action's schema first, then await `tools.NAME(args)`
  13. inside `lazyweb_execute`. Individual action names need not appear in
  14. `tools/list`. When the client advertises actions directly, use those actions
  15. instead.
  16. If MCP is unavailable, run `curl -fsSL https://www.lazyweb.com/install.sh | bash`,
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 20 on GitHub
  17. then call `lazyweb_health`.
  18. | Intent | Skill / canonical tool |
  19. |---|---|
  20. | Get, explicitly generate, or compare Growth Scores | `lazyweb-growth-score` / `lazyweb_growth_score` |
  21. | Create or poll the unchanged Growth Report pipeline | `lazyweb-growth-report` / `lazyweb_growth_report` |
  22. | Improve or critique an existing design or screen | `lazyweb-growth-report` / `lazyweb_growth_report` |
  23. | List or add product Backlog specs | `lazyweb-growth-backlog` / `lazyweb_growth_backlog` |
  24. | Research experiments | `lazyweb-search-experiments` / `lazyweb_search_experiments` |
  25. | Research flows | `lazyweb-search-flows` / `lazyweb_search_flows` |
  26. | Research screens | `lazyweb-search-screens` / `lazyweb_search_screens` |
  27. | Apply the best specialist design skill for a UI craft task | `lazyweb-apply-design-best-practices` |
  28. For other safe app actions, inspect the live tools and use the compact domain
  29. tool (`lazyweb_products`, `lazyweb_connections`, `lazyweb_reports`, or
  30. `lazyweb_account`). Use `lazyweb_get_workflows` only for current routing help.
  31. Checkout, billing changes, identity changes, team invitations, and admin actions
  32. remain human-only.
  33. For product UI work, quietly gather only relevant evidence from screens,
  34. experiments, flows, and growth mechanics while you work. Use only the research
  35. types the task needs. Finalize useful selected evidence into Agentic Search and
  36. return its stable private link. Agentic Search sharing is a signed-in human
  37. action from the page's `Share` button. Never return an Agentic Search
  38. `share_url`, even if a legacy server sends one. Broad improvement requests may
  39. use a Growth Report when it best serves the user's goal; do not require the
  40. exact product name.
  41. Every successful action returns `lazyweb.resource-link.v1`. Open `open_url`
  42. once in the host's browser (Codex preview in Codex, Claude browser in Claude,
  43. otherwise the system browser), but never print, share, or log it. Give the user
  44. the stable `url` and, for non-Agentic resources, any optional `share_url`.
README.md · README · 224 lines · 1 finding marked
  1. # Lazyweb Skill Pack
  2. **Design with evidence, not vibes.**
  3. Lazyweb gives AI coding agents real product screenshots, UI references, and
  4. design research workflows before they build or critique an interface. It is a
  5. standalone skill pack plus a hosted Lazyweb MCP server, so it works in coding
  6. clients that support local skills even when they do not support plugins.
  7. ## Install
  8. Paste this into a local coding agent or terminal:
  9. ```bash
  10. curl -fsSL https://www.lazyweb.com/install.sh | bash
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 15 on GitHub
  11. ```
  12. Fresh installs may receive a signed installation-experiment assignment when
  13. this script is served. Agents can pass the user's actual goal, discovery
  14. evidence, company, and intended outcome, but missing or invalid attribution
  15. never blocks installation. The installer never invents those answers. Valid discovery sources are
  16. `user_request`, `web_search`, `reddit`, `shared_url`, `llms_txt`, `agent_docs`,
  17. `webmcp`, `other`, and `unknown`. Never include private chain-of-thought.
  18. When the command came from a tracked Lazyweb agent document, the wrapper also
  19. passes an internal `--journey-id` so the installation can be joined to the
  20. public Lazyweb resources that agent fetched first. Valid signed assignments and
  21. journey context are recorded when available; setup continues without them.
  22. Existing-token updates never ask for acquisition context again.
  23. The installer clones this repo to `~/.lazyweb/repos/lazyweb-skill`, creates or
  24. reuses `~/.lazyweb/lazyweb_mcp_token`, installs the visible Lazyweb skills into
  25. detected local clients, and configures Lazyweb MCP at
  26. `https://www.lazyweb.com/mcp`.
  27. Approved private-workspace users should sign in with OAuth on the existing
  28. `lazyweb` MCP entry. In Codex, run
  29. `codex mcp add lazyweb --url https://www.lazyweb.com/mcp --oauth-client-registration dcr`
  30. and verify the account email. Future skill-pack updates preserve that OAuth
  31. connection instead of replacing it with the public install token.
  32. When an agent client launches the installer, setup targets that active client
  33. only. A plain terminal run without an active-client signal still detects local
  34. clients; use `--host all` when you deliberately want every supported client.
  35. Downloading or updating the skill pack, installing or configuring a client,
  36. and creating or reusing a bearer token are available to everyone without
  37. charge. Setup, health, and workflow discovery remain usable regardless
  38. of plan; real data-bearing MCP tool availability and usage limits depend on the
  39. account's persisted experiment assignment and plan.
  40. Supported local skill roots:
  41. - Codex: `~/.codex/skills`
  42. - Claude Code: `~/.claude/skills`
  43. - Cursor: `~/.cursor/skills`
  44. - OpenCode: `~/.config/opencode/skills`
  45. - Kiro: `~/.kiro/skills`
  46. - Factory Droid: `~/.factory/skills`
  47. - Slate: `~/.slate/skills`
  48. - Hermes: `~/.hermes/skills`
  49. Direct MCP config is written for Codex, Claude Code, Cursor, and Antigravity.
  50. For hosted Claude or ChatGPT surfaces, use the connector instructions at
  51. `https://www.lazyweb.com/claude.md` or `https://www.lazyweb.com/chatgpt.md`;
  52. a local shell script cannot configure those cloud UIs.
  53. ## Visible Skills
  54. The installer surfaces a **focused set of slash commands**. Every other mode stays
  55. in the repo and is reachable through the `/lazyweb` router and the Lazyweb MCP
  56. (`lazyweb_get_workflows`), but is intentionally **not** installed as its own slash
  57. command:
  58. | Skill | Use when |
  59. |---|---|
  60. | `/lazyweb` | Start here: improve a product, research an idea, score a website, or organize growth work. |
  61. | `/lazyweb-growth-score` | Score a website's growth readiness or compare its progress over time. |
  62. | `/lazyweb-growth-report` | Get prioritized, evidence-backed design improvements for a product screen or webpage. |
  63. | `/lazyweb-growth-backlog` | Review growth recommendations or save a product improvement idea. |
  64. | `/lazyweb-search-experiments` | Find real product experiments for pricing, trials, paywalls, monetization, and conversion decisions. |
  65. | `/lazyweb-search-flows` | Study complete onboarding, checkout, paywall, signup, and other multi-step journeys. |
  66. | `/lazyweb-search-screens` | Find real product screens and UI patterns to guide a design or conversion decision. |
  67. | `/lazyweb-apply-design-best-practices` | Route a UI craft task to the best specialist design skill, then apply it. |
  68. | `/lazyweb-update` | Update the local Lazyweb skill pack and reinstall it into agentic IDEs. |
  69. `skills/lazyweb/SKILL.md` is the first-class high-level router package; the
  70. repo-root `SKILL.md` is an identical single-file entrypoint for platforms that
  71. expect it there. The installer copies the packaged file into each local client
  72. as a regular `lazyweb/SKILL.md` entrypoint (required for Codex catalog discovery). The router
  73. points to focused skills under `skills/`. Live MCP schemas own the contracts;
  74. the skills keep their user-facing descriptions focused on what someone can
  75. accomplish with Lazyweb.
  76. ## Verify
  77. After setup, reload or restart the client, then:
  78. 1. Show the Welcome to Lazyweb message from setup, or fetch `https://www.lazyweb.com/api/mcp/welcome-message` and show it to the user.
  79. 2. List MCP tools. If the client advertises `lazyweb_discover_tools` and `lazyweb_execute`, use the steps below; individual actions do not need to appear in that list.
  80. 3. Call `lazyweb_discover_tools` with `{"query":"lazyweb_get_workflows","limit":1}` to read the current schema, then call `lazyweb_execute` with:
  81. ```json
  82. {"code":"return await tools.lazyweb_get_workflows({operation:'list',task_context:'first run Lazyweb capabilities'});"}
  83. ```
  84. 4. Check the returned result for `isError`, then summarize the available workflows. Discover the schema for the user's next action before executing it.
  85. If the client advertises `lazyweb_get_workflows` directly, call it with `{"operation":"list","task_context":"first run Lazyweb capabilities"}`. Use the tools actually advertised by the client; absent individual action names are not a reason to reinstall.
  86. A Lazyweb MCP token is a bearer setup credential, not proof of paid access.
  87. Creating or reusing one does not charge the user, but data-bearing tools still
  88. follow the account's persisted experiment assignment and plan. Tokens do not
  89. authorize purchases, paid spend, private user data, or destructive actions.
  90. Keep tokens out of public git, but ignored local MCP config is fine.
  91. The hosted MCP enforces abuse controls, including per-token transport quotas;
  92. clients that ignore backoff may receive `429 mcp_rate_limited`.
  93. ## Manual Setup
  94. If your client is not detected, configure MCP manually:
  95. - URL: `https://www.lazyweb.com/mcp`
  96. - Transport: Streamable HTTP
  97. - Header: `Authorization: Bearer <token from ~/.lazyweb/lazyweb_mcp_token>`
  98. To run setup for a specific client:
  99. ```bash
  100. ~/.lazyweb/repos/lazyweb-skill/setup --host cursor
  101. ```
  102. Use `--host all` to install every supported local skill root.
  103. To update an existing install from GitHub and refresh every supported local
  104. skill root:
  105. ```bash
  106. ~/.lazyweb/bin/lazyweb-update --host all
  107. ```
  108. ## Auto-updates (opt-in)
  109. Lazyweb checks for a newer version on every invocation. By default it tells
  110. the agent to surface the upgrade command to you. To apply updates silently
  111. without confirmation, opt in once:
  112. ```bash
  113. touch ~/.lazyweb/auto_update
  114. ```
  115. `./setup` prompts you for this on first interactive run; pass `--auto-update`
  116. or `--no-auto-update` to skip the prompt in scripted installs. Disable later
  117. with `rm ~/.lazyweb/auto_update`. The check itself is non-blocking
  118. (time-boxed to 3s, cached 24h) and never delays your request.
  119. ## Tool Surfaces
  120. Use MCP tools for Lazyweb database access. Always inspect the live tool list
  121. before assuming optional filters or backend aliases are available.
  122. Current public gateway tools:
  123. | MCP tool | Use |
  124. |---|---|
  125. | `lazyweb_health` | Check Lazyweb backend connectivity. |
  126. | `lazyweb_growth_score` | Get, explicitly generate, or compare immutable Growth Scores in batches. |
  127. | `lazyweb_growth_report` | Naming façade over the unchanged report generator and poller. |
  128. | `lazyweb_growth_backlog` | List or add owner/product-scoped Backlog specs. |
  129. | `lazyweb_search_screens` | Search screens and automatically record stable result references in Agentic Search. |
  130. | `lazyweb_search_flows` | Search ordered flows and accumulate them into the same Agentic Search. |
  131. | `lazyweb_search_experiments` | Search growth experiments and accumulate them into the same Agentic Search. |
  132. | `lazyweb_agentic_search_finalize` | Finalize ordered selected `result_ref` values and return the private web link; sharing is human-only from the page. |
  133. | `lazyweb_products` | Safe product CRUD; deletion requires an exact matching confirmation. |
  134. | `lazyweb_connections` | Read connection status or open canonical setup. |
  135. | `lazyweb_reports` | List/open reports or save owner-authorized feedback. |
  136. | `lazyweb_account` | Read-only account and plan status. |
  137. | `lazyweb_compare_image` | Find visually similar screenshots from an image URL or base64 image; results include optimized image URLs. |
  138. | `lazyweb_find_similar` | Find visually similar screenshots from a returned Lazyweb `imageUrl` or an image payload; do not pass screenshot IDs. |
  139. | `lazyweb_list_categories` | List public company categories. |
  140. | `lazyweb_get_workflows` | Discover and fetch current Lazyweb workflow instructions. |
  141. Legacy names such as `lazyweb_search`, `lazyweb_get_flows`,
  142. `lazyweb_search_ab_tests`, `lazyweb_generate_report`, and `lazyweb_get_report`
  143. remain compatibility aliases during their deprecation window.
  144. All Lazyweb screenshot-bearing tools return usable optimized URLs for screenshots.
  145. Supabase storage-backed image URLs are signed for 365 days. Do not ask tools for
  146. screenshot IDs, do not pass screenshot IDs between Lazyweb tools, and do not
  147. construct storage URLs from raw paths; embed the returned `imageUrl`/`image_url`
  148. or A/B `control_image_url`/`variant_image_url` fields directly.
  149. Richer backend/internal surfaces may also expose `lazyweb_find_experiments`,
  150. `lazyweb_recent_experiments`, and
  151. `list_companies_by_categories`. Use those only when the live schema shows them.
  152. Installing the workflow skills and configuring MCP do not determine tool
  153. entitlement. Inspect the live tool list and honor the server response: real
  154. data-bearing MCP tool availability and usage limits depend on the account's
  155. persisted experiment assignment and plan. A missing tool can reflect plan,
  156. experiment, rollout, or availability; an empty authorized result is a coverage
  157. outcome.
  158. ## Repository Structure
  159. - `SKILL.md` - canonical high-level Lazyweb router skill.
  160. - `skills/*/SKILL.md` - visible mode skills.
  161. - `setup` - standalone multi-host installer.
  162. - `bin/` - helper scripts used by skills and setup, including
  163. `lazyweb-update` for refreshing an existing install.
  164. - `browse/` - optional browser capture helper for web screenshots.
  165. - `scripts/validate-skill-pack.mjs` - static skill-pack validation.
  166. - `test/` - installer, helper, and contract tests.
  167. ## Development
  168. ```bash
  169. npm test
  170. ```
  171. The test command runs unit tests plus standalone skill-pack validation.
  172. ## License
  173. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.