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.
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
Markdown
[](/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
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
- ---
- name: lazyweb
- description: Use Lazyweb to find real product evidence, improve conversion, and turn research into clear product decisions.
- router-exclude: true
- allowed-tools:
- - Bash
- ---
- # Lazyweb
- Use the live Lazyweb MCP tool list as the source of truth. This skill only
- routes; it does not carry schemas, scoring rules, taxonomies, or product logic.
- When the client advertises `lazyweb_discover_tools` and `lazyweb_execute`,
- discover the desired action's schema first, then await `tools.NAME(args)`
- inside `lazyweb_execute`. Individual action names need not appear in
- `tools/list`. When the client advertises actions directly, use those actions
- instead.
- 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
- then call `lazyweb_health`.
- | Intent | Skill / canonical tool |
- |---|---|
- | Get, explicitly generate, or compare Growth Scores | `lazyweb-growth-score` / `lazyweb_growth_score` |
- | Create or poll the unchanged Growth Report pipeline | `lazyweb-growth-report` / `lazyweb_growth_report` |
- | Improve or critique an existing design or screen | `lazyweb-growth-report` / `lazyweb_growth_report` |
- | List or add product Backlog specs | `lazyweb-growth-backlog` / `lazyweb_growth_backlog` |
- | Research experiments | `lazyweb-search-experiments` / `lazyweb_search_experiments` |
- | Research flows | `lazyweb-search-flows` / `lazyweb_search_flows` |
- | Research screens | `lazyweb-search-screens` / `lazyweb_search_screens` |
- | Apply the best specialist design skill for a UI craft task | `lazyweb-apply-design-best-practices` |
- For other safe app actions, inspect the live tools and use the compact domain
- tool (`lazyweb_products`, `lazyweb_connections`, `lazyweb_reports`, or
- `lazyweb_account`). Use `lazyweb_get_workflows` only for current routing help.
- Checkout, billing changes, identity changes, team invitations, and admin actions
- remain human-only.
- For product UI work, quietly gather only relevant evidence from screens,
- experiments, flows, and growth mechanics while you work. Use only the research
- types the task needs. Finalize useful selected evidence into Agentic Search and
- return its stable private link. Agentic Search sharing is a signed-in human
- action from the page's `Share` button. Never return an Agentic Search
- `share_url`, even if a legacy server sends one. Broad improvement requests may
- use a Growth Report when it best serves the user's goal; do not require the
- exact product name.
- Every successful action returns `lazyweb.resource-link.v1`. Open `open_url`
- once in the host's browser (Codex preview in Codex, Claude browser in Claude,
- otherwise the system browser), but never print, share, or log it. Give the user
- the stable `url` and, for non-Agentic resources, any optional `share_url`.
README.md · README · 224 lines · 1 finding marked
- # Lazyweb Skill Pack
- **Design with evidence, not vibes.**
- Lazyweb gives AI coding agents real product screenshots, UI references, and
- design research workflows before they build or critique an interface. It is a
- standalone skill pack plus a hosted Lazyweb MCP server, so it works in coding
- clients that support local skills even when they do not support plugins.
- ## Install
- Paste this into a local coding agent or terminal:
- ```bash
- 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
- ```
- 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.
- ## Visible Skills
- The installer surfaces a **focused set of slash commands**. Every other mode stays
- in the repo and is reachable through the `/lazyweb` router and the Lazyweb MCP
- (`lazyweb_get_workflows`), but is intentionally **not** installed as its own slash
- command:
- | Skill | Use when |
- |---|---|
- | `/lazyweb` | Start here: improve a product, research an idea, score a website, or organize growth work. |
- | `/lazyweb-growth-score` | Score a website's growth readiness or compare its progress over time. |
- | `/lazyweb-growth-report` | Get prioritized, evidence-backed design improvements for a product screen or webpage. |
- | `/lazyweb-growth-backlog` | Review growth recommendations or save a product improvement idea. |
- | `/lazyweb-search-experiments` | Find real product experiments for pricing, trials, paywalls, monetization, and conversion decisions. |
- | `/lazyweb-search-flows` | Study complete onboarding, checkout, paywall, signup, and other multi-step journeys. |
- | `/lazyweb-search-screens` | Find real product screens and UI patterns to guide a design or conversion decision. |
- | `/lazyweb-apply-design-best-practices` | Route a UI craft task to the best specialist design skill, then apply it. |
- | `/lazyweb-update` | Update the local Lazyweb skill pack and reinstall it into agentic IDEs. |
- `skills/lazyweb/SKILL.md` is the first-class high-level router package; the
- repo-root `SKILL.md` is an identical single-file entrypoint for platforms that
- expect it there. The installer copies the packaged file into each local client
- as a regular `lazyweb/SKILL.md` entrypoint (required for Codex catalog discovery). The router
- points to focused skills under `skills/`. Live MCP schemas own the contracts;
- the skills keep their user-facing descriptions focused on what someone can
- accomplish with Lazyweb.
- ## Verify
- After setup, reload or restart the client, then:
- 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.
- 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.
- 3. Call `lazyweb_discover_tools` with `{"query":"lazyweb_get_workflows","limit":1}` to read the current schema, then call `lazyweb_execute` with:
- ```json
- {"code":"return await tools.lazyweb_get_workflows({operation:'list',task_context:'first run Lazyweb capabilities'});"}
- ```
- 4. Check the returned result for `isError`, then summarize the available workflows. Discover the schema for the user's next action before executing it.
- 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.
- A Lazyweb MCP token is a bearer setup credential, not proof of paid access.
- Creating or reusing one does not charge the user, but data-bearing tools still
- follow the account's persisted experiment assignment and plan. Tokens do not
- authorize purchases, paid spend, private user data, or destructive actions.
- Keep tokens out of public git, but ignored local MCP config is fine.
- The hosted MCP enforces abuse controls, including per-token transport quotas;
- clients that ignore backoff may receive `429 mcp_rate_limited`.
- ## Manual Setup
- If your client is not detected, configure MCP manually:
- - URL: `https://www.lazyweb.com/mcp`
- - Transport: Streamable HTTP
- - Header: `Authorization: Bearer <token from ~/.lazyweb/lazyweb_mcp_token>`
- To run setup for a specific client:
- ```bash
- ~/.lazyweb/repos/lazyweb-skill/setup --host cursor
- ```
- Use `--host all` to install every supported local skill root.
- To update an existing install from GitHub and refresh every supported local
- skill root:
- ```bash
- ~/.lazyweb/bin/lazyweb-update --host all
- ```
- ## Auto-updates (opt-in)
- Lazyweb checks for a newer version on every invocation. By default it tells
- the agent to surface the upgrade command to you. To apply updates silently
- without confirmation, opt in once:
- ```bash
- touch ~/.lazyweb/auto_update
- ```
- `./setup` prompts you for this on first interactive run; pass `--auto-update`
- or `--no-auto-update` to skip the prompt in scripted installs. Disable later
- with `rm ~/.lazyweb/auto_update`. The check itself is non-blocking
- (time-boxed to 3s, cached 24h) and never delays your request.
- ## Tool Surfaces
- Use MCP tools for Lazyweb database access. Always inspect the live tool list
- before assuming optional filters or backend aliases are available.
- Current public gateway tools:
- | MCP tool | Use |
- |---|---|
- | `lazyweb_health` | Check Lazyweb backend connectivity. |
- | `lazyweb_growth_score` | Get, explicitly generate, or compare immutable Growth Scores in batches. |
- | `lazyweb_growth_report` | Naming façade over the unchanged report generator and poller. |
- | `lazyweb_growth_backlog` | List or add owner/product-scoped Backlog specs. |
- | `lazyweb_search_screens` | Search screens and automatically record stable result references in Agentic Search. |
- | `lazyweb_search_flows` | Search ordered flows and accumulate them into the same Agentic Search. |
- | `lazyweb_search_experiments` | Search growth experiments and accumulate them into the same Agentic Search. |
- | `lazyweb_agentic_search_finalize` | Finalize ordered selected `result_ref` values and return the private web link; sharing is human-only from the page. |
- | `lazyweb_products` | Safe product CRUD; deletion requires an exact matching confirmation. |
- | `lazyweb_connections` | Read connection status or open canonical setup. |
- | `lazyweb_reports` | List/open reports or save owner-authorized feedback. |
- | `lazyweb_account` | Read-only account and plan status. |
- | `lazyweb_compare_image` | Find visually similar screenshots from an image URL or base64 image; results include optimized image URLs. |
- | `lazyweb_find_similar` | Find visually similar screenshots from a returned Lazyweb `imageUrl` or an image payload; do not pass screenshot IDs. |
- | `lazyweb_list_categories` | List public company categories. |
- | `lazyweb_get_workflows` | Discover and fetch current Lazyweb workflow instructions. |
- Legacy names such as `lazyweb_search`, `lazyweb_get_flows`,
- `lazyweb_search_ab_tests`, `lazyweb_generate_report`, and `lazyweb_get_report`
- remain compatibility aliases during their deprecation window.
- All Lazyweb screenshot-bearing tools return usable optimized URLs for screenshots.
- Supabase storage-backed image URLs are signed for 365 days. Do not ask tools for
- screenshot IDs, do not pass screenshot IDs between Lazyweb tools, and do not
- construct storage URLs from raw paths; embed the returned `imageUrl`/`image_url`
- or A/B `control_image_url`/`variant_image_url` fields directly.
- Richer backend/internal surfaces may also expose `lazyweb_find_experiments`,
- `lazyweb_recent_experiments`, and
- `list_companies_by_categories`. Use those only when the live schema shows them.
- Installing the workflow skills and configuring MCP do not determine tool
- entitlement. Inspect the live tool list and honor the server response: real
- data-bearing MCP tool availability and usage limits depend on the account's
- persisted experiment assignment and plan. A missing tool can reflect plan,
- experiment, rollout, or availability; an empty authorized result is a coverage
- outcome.
- ## Repository Structure
- - `SKILL.md` - canonical high-level Lazyweb router skill.
- - `skills/*/SKILL.md` - visible mode skills.
- - `setup` - standalone multi-host installer.
- - `bin/` - helper scripts used by skills and setup, including
- `lazyweb-update` for refreshing an existing install.
- - `browse/` - optional browser capture helper for web screenshots.
- - `scripts/validate-skill-pack.mjs` - static skill-pack validation.
- - `test/` - installer, helper, and contract tests.
- ## Development
- ```bash
- npm test
- ```
- The test command runs unit tests plus standalone skill-pack validation.
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.