Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
WebMCP
This skill should be used when browsing or automating web pages that expose tools via the WebMCP API (window.navigator.modelContext). It teaches agents how to discover, inspect, and invoke WebMCP tools on websites instead of relying on DOM scraping or UI actuation.
skill openclawclawhub Free
This skill should be used when browsing or automating web pages that expose tools via the WebMCP API (window.navigator.modelContext). It teaches agents how to discover, inspect, and invoke WebMCP tools on websites instead of relying on DOM scraping or UI actuation.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- brunobuddy
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
What is WebMCP
WebMCP is a browser API that lets websites expose JavaScript functions as structured tools for AI agents. Pages register tools via window.navigator.modelContext, each with a name, description, JSON Schema input, and an execute callback. Think of it as an MCP server running inside the web page itself. Spec: https://github.com/webmachinelearning/webmcp
Detecting WebMCP Support
Before interacting with tools, check whether the current page supports WebMCP: const supported = "modelContext" in window.navigator; If false, the page does not expose WebMCP tools โ fall back to DOM interaction or actuation.
Discovering Available Tools
Tools are registered by the page via provideContext() or registerTool(). The browser mediates access. To list available tools from an agent's perspective, evaluate: // Browser-specific โ the exact discovery API depends on the agent runtime. // Typically the browser exposes registered tools to connected agents automatically. // From page-script perspective, tools are registered like this: window.navigator.modelContext.provideContext({ tools: [ { name: "tool-name", description: "What this tool does", inputSchema: { type: "object", properties: { /* ... */ }, required: [] }, execute: (params, agent) => { /* ... */ } } ] }); Key points: Each tool has name, description, inputSchema (JSON Schema), and execute. provideContext() replaces all previously registered tools (useful for SPA state changes). registerTool() / unregisterTool() add/remove individual tools without resetting. Tools may change as the user navigates or as SPA state updates โ re-check after page transitions.
Tool Schema Format
Tool input schemas follow JSON Schema (aligned with MCP SDK and Prompt API tool use): { name: "add-stamp", description: "Add a new stamp to the collection", inputSchema: { type: "object", properties: { name: { type: "string", description: "The name of the stamp" }, year: { type: "number", description: "Year the stamp was issued" }, imageUrl: { type: "string", description: "Optional image URL" } }, required: ["name", "year"] }, execute({ name, year, imageUrl }, agent) { // Implementation โ updates UI and app state return { content: [{ type: "text", text: `Stamp "${name}" added.` }] }; } }
Invoking Tools
When connected as an agent, send a tool call by name with parameters matching inputSchema. The execute callback runs on the page's main thread, can update the UI, and returns a structured response: // Response format from execute(): { content: [ { type: "text", text: "Result description" } ] } Tools run sequentially on the main thread (one at a time). execute may be async (returns a Promise). The second parameter agent provides agent.requestUserInteraction() for user confirmation flows.
User Interaction During Tool Execution
Tools can request user confirmation before sensitive actions: async function buyProduct({ product_id }, agent) { const confirmed = await agent.requestUserInteraction(async () => { return confirm(`Buy product ${product_id}?`); }); if (!confirmed) throw new Error("Cancelled by user."); executePurchase(product_id); return { content: [{ type: "text", text: `Product ${product_id} purchased.` }] }; } Always respect user denials โ do not retry cancelled tool calls.
Agent Workflow
Navigate to the target website. Check "modelContext" in window.navigator to confirm WebMCP support. Discover registered tools (names, descriptions, schemas). Select the appropriate tool based on the user's goal and the tool description. Invoke with correct parameters matching inputSchema. Read the structured response and relay results to the user. After SPA navigation or state changes, re-discover tools โ the set may have changed. If no WebMCP tool fits the task, fall back to DOM-based interaction.
Important Constraints
Browser context required โ tools only exist in a live browsing context (tab/webview), not headlessly. Sequential execution โ tool calls run one at a time on the main thread. No cross-origin tool sharing โ tools are scoped to the page that registered them. Permission-gated โ the browser may prompt the user before allowing tool access. Tools are dynamic โ SPAs may register/unregister tools based on UI state.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md