About lazyweb
lazyweb is a routing skill that directs product and design tasks to Lazyweb's live MCP tools and specialist skills. It relies on the current tool list rather than embedding schemas or product logic, and keeps sensitive account actions human-controlled.
Key features
- 01Route growth and design tasks
- 02Use live MCP tools as source of truth
- 03Research screens, flows, and experiments
- 04Finalize evidence in Agentic Search
- 05Keep sensitive account actions human-only
Use cases
- 01Request a Growth Score or report
- 02Review a product screen or design
- 03Research product flows and experiments
- 04Find relevant evidence for UI work
MCP support
lazyweb routes tasks to Lazyweb's live MCP tool list and canonical tools. If MCP is unavailable, it provides an installation command and health check.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ lazywebhq/ lazyweb-skill --skill lazywebAfter installing, type/lazywebin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
VERSION.gitignoreREADME.mdCLAUDE.mdAGENTS.mdLICENSE.github/workflows/release-manifest.ymlbin/lazyweb-loglazyweb-context-detectlazyweb-hosts.shlazyweb-telemetry-flushlazyweb-updatelazyweb-update-checkbrowse/setuppackage.jsonbrowse/dist/.gitkeepbrowse/scripts/build-node-server.shbrowse/src/activity.tsbuffers.tsbun-polyfill.cjscommands.tsconfig.tsbrowser-manager.tscli.tscookie-picker-routes.tsfind-browse.tsplatform.tscookie-import-browser.tscookie-picker-ui.tsmeta-commands.tsDetails
From the project READMELazyweb
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.
If MCP is unavailable, run curl -fsSL https://www.lazyweb.com/install.sh | bash,
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.