webmcp-agent-readiness
Skill3 starsChanged 4 days agoMITView on GitHub
Build, audit, and test browser-native WebMCP tools with Chrome document.modelContext or declarative form annotations; use for Chrome WebMCP, agent-friendly web actions, journey evaluation, browser tool schemas, or modelContext integration.
In this repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hermes-mobile/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agent-automations.mdcCursor rule
- .cursor/rules/agent-device.mdcCursor rule
- .cursor/rules/agent-harness-router.mdcCursor rule
- .cursor/rules/agent-skills-overview.mdcCursor rule
- .cursor/rules/always-agent-mode.mdcCursor rule
- .cursor/rules/callstack-agent-skills-overview.mdcCursor rule
- .cursor/rules/callstack-react-native-best-practices.mdcCursor rule
- .cursor/rules/codeql-agent-hygiene.mdcCursor rule
- .cursor/rules/decision-stack.mdcCursor rule
- .cursor/rules/expo-credit-budget.mdcCursor rule
- .cursor/rules/fleet-repo-intelligence.mdcCursor rule
- .cursor/rules/hermes-mobile-prevention-july-2026.mdcCursor rule
- .cursor/rules/hermes-mobile-real-users.mdcCursor rule
- .cursor/rules/hermes-mobile-verification.mdcCursor rule
- .cursor/rules/no-desktop-hijack.mdcCursor rule
- .cursor/rules/no-manual-handoffs.mdcCursor rule
- .cursor/rules/obsidian-teammate-collaboration.mdcCursor rule
- .cursor/rules/prefer-headless-background-ops.mdcCursor rule
- .cursor/rules/react-native-best-practices.mdcCursor rule
- public/llms.txtllms.txt
- advertise-thumbgate-github-marketplaceSkill
- agent-harness-routerSkill
- agentic-pattern-selectorSkill
- agents-judgment-calls-gateSkill
- ai-native-sdlcSkill
- android-dev-summit-26-gateSkill
- anti-babysitting-mandateSkill
- anti-babysittingSkill
- background-agent-hold-gateSkill
- browseros-agent-harnessSkill
- ci-first-failSkill
- ci-pr-monitorSkill
- cloudflare-developer-stackSkill
- cloudflare-kitesurf-browserSkill
- cloudflare-monetization-gatewaySkill
- confidence-offer-gateSkill
- content-laneSkill
- context-six-blockSkill
- context-vaultSkill
- context-weight-gateSkill
- dual-model-agentic-graphragSkill
- egm-fresh-reviewSkill
- elevenlabs-voice-agentsSkill
- emeans-quant-and-instinctSkill
- explainx-trending-honestSkill
- explainx-trending-ragSkill
- future-agi-self-healing-engineSkill
- garryslist-opportunity-trackerSkill
- gemini-decisions-hold-gateSkill
- git-at-scaleSkill
- gitbutler-fleet-automationsSkill
- gitbutler-google-ssoSkill
- gitbutler-mcp-isolatedSkill
- gitbutler-session-absorbSkill
- git-hooks-no-huskySkill
- github-marketplace-action-publishSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use WebMCP as progressive enhancement: the human interface and ordinary DOM automation must still work when document.modelContext is …
- Very specific: line 21
Do not call a browser or site WebMCP-ready from its version or source code alone.
- Distinctive: line 40
Test deterministic validation and a real Chromium implementation:
- Distinctive: line 48
Add app-specific unit, browser, and evaluation cases.
- Distinctive: line 50
Read the tool and security contract before exposing tools cross-origin, auto-submitting forms, or registering write/external-action tools.
- Distinctive: line 54
After changing this skill, mirror the tested copy across agent homes:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Chrome WebMCP
Use WebMCP as progressive enhancement: the human interface and ordinary DOM automation must still work when document.modelContext is unavailable.
Start with a real capability receipt
python3 ~/.agents/skills/chrome-webmcp/scripts/probe_webmcp.py --browser allCurrent measured routing on this Mac:
- Chrome Stable 151 and Canary 154: imperative registration, discovery, and execution pass in isolated headless profiles with WebMCP test flags.
- BrowserOS Neo 148:
document.modelContextis unavailable; keep using its DOM/CDP path until a fresh probe passes.
Do not call a browser or site WebMCP-ready from its version or source code alone. Require the probe or an equivalent page-level registerTool → getTools → executeTool receipt.
Build workflow
- Choose one non-overlapping function per tool. Prefer a declarative annotated form for an existing form; use the imperative API for app logic, navigation, diagnostics, or stateful actions.
- Copy
assets/webmcp-kit.jsfor imperative tools or adaptassets/declarative-form.example.htmlfor forms. Feature-detect the API and preserve the ordinary UI fallback. - Describe the intended tools and journey evaluations in a manifest based on
assets/manifest.example.json. Static-only authoring checks are explicit:
python3 ~/.agents/skills/chrome-webmcp/scripts/lint_webmcp_manifest.py path/to/webmcp-tools.json --static-only- Produce a fresh isolated browser receipt, then run the readiness audit. A manifest without that receipt is
unverifiedand exits nonzero; static validity alone is neverready.
python3 ~/.agents/skills/chrome-webmcp/scripts/probe_webmcp.py --browser all --output /tmp/webmcp-probe.json
python3 ~/.agents/skills/chrome-webmcp/scripts/lint_webmcp_manifest.py path/to/webmcp-tools.json --probe /tmp/webmcp-probe.json- Test deterministic validation and a real Chromium implementation:
python3 ~/.agents/skills/chrome-webmcp/scripts/test_manifest_lint.py
node ~/.agents/skills/chrome-webmcp/scripts/test_webmcp_kit.mjs
python3 ~/.agents/skills/chrome-webmcp/scripts/probe_webmcp.py --browser chrome- Add app-specific unit, browser, and evaluation cases. Prove UI state changes separately from the tool return value.
Read the tool and security contract before exposing tools cross-origin, auto-submitting forms, or registering write/external-action tools.
System install
After changing this skill, mirror the tested copy across agent homes:
bash ~/.agents/skills/chrome-webmcp/test.sh
bash ~/.agents/skills/chrome-webmcp/scripts/sync_agent_homes.shRelationship to sibling capabilities
- This skill is the fleet-wide readiness gate and runtime proof source.
webmcp-instrument-siteis a Claude-side authoring reference; route its readiness claims through this skill's linter and probe.agent-mystery-shopperaudits a customer journey and stops before unauthorized external submission. It does not prove WebMCP support.- The daily funnel-truth LaunchAgent proves URL/status/body availability only, not tool discovery, execution, or journey completion.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

