webmcpify
Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for "webmcpify", "add WebMCP", or "expose app actions to AI agents".
Profile →npx skills add github/awesome-copilot --skill webmcpify --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# webmcpify — make any web app agent-ready, verifiably You are running the webmcpify pipeline. It takes an existing web application and exposes its user-facing functionality as [WebMCP](https://webmachinelearning.github.io/webmcp/) tools (`document.modelContext` — a proposed web standard incubated in the W3C Web Machine Learning Community Group, currently a Chrome origin trial), so browser AI agents can operate the app through structured tool calls instead of guessing at the DOM. ``` DETECT ──▶ INVENTORY ──▶ [HUMAN GATE: manifest approval] ──▶ INTEGRATE ──▶ VERIFY ──▶ HEAL ──▶ AUDIT ▲ loop per-area batches on big apps ▲ loop ▲ loop ▲ loop └── per area └── per manifest entry ──┘ ``` Everything you need ships inside this skill directory: phase guides in `references/`, and vendorable code in `templates/` (runtime, ambient types, JS variant, React JSX typings, verification spec). Never assume files exist outside the skill dir. **Out of scope** (stop and say so): backend-only MCP servers (that's classic MCP, not WebMCP), automating third-party sites you don't control, and generic SEO work. ## Invocation modes The user may pass an argument (`/webmcpify <mode>` or plain words): | Argument
- Invocation modes
- Ground rules (non-negotiable, enforce in every phase)
- Fresh, authoritative guidance
- The state protocol — .webmcpify/ in the target repo
- Phase 0 — DETECT
- Phase 1 — INVENTORY (loop; scales to any size)
- GATE — manifest approval (the one main checkpoint)
- Phase 2 — INTEGRATE (loop)
- Phase 3 — VERIFY (loop)
- Phase 4 — HEAL (loop)
- Final — AUDIT + report
- References (read on demand, not upfront)
npx -y modern-web-guidance@latest retrieve "webmcp,agentic-forms,agentic-javascript-tools"
What does the webmcpify skill do?
Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for "webmcpify", "add WebMCP", or "expose app actions to AI agents".
How do I install it?
Run `npx skills add github/awesome-copilot --skill webmcpify --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.