agency-agentic-search-optimizer

Audit WebMCP readiness and agentic task capabilities across sites.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/anavvanzin/Research --skill agency-agentic-search-optimizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-agentic-search-optimizer
Source: https://github.com/anavvanzin/Research/tree/main/cowork/integrations/antigravity/agency-agentic-search-optimizer
Command: npx skills add https://github.com/anavvanzin/Research --skill agency-agentic-search-optimizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits whether AI browsing agents can actually complete real user tasks on your site (book, buy, register, subscribe) and tracks task completion rates across multiple agents.

Core Features & Use Cases

  • WebMCP readiness audits across domains and pages
  • Declarative and imperative pattern guidance for agent exposure
  • Task-flow friction mapping and success-rate measurement
  • Discovery endpoint reporting (mcp-actions.json) and agent compatibility checks
  • Cross-agent compatibility tracking (Claude in Chrome, Edge Copilot, Perplexity, etc.)

Quick Start

Run a WebMCP readiness audit on a target site to assess declarative and imperative action readiness.

Frequently Asked Questions about agency-agentic-search-optimizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is WebMCP readiness and how does it affect AI browsing agents?

WebMCP readiness measures whether AI browsing agents can discover and complete user tasks on a site by checking for declarative markup (data-mcp-*), navigator.mcpActions registrations, and a discovery endpoint (mcp-actions.json).

How do I audit if AI agents can complete booking or purchasing flows on my site?

You can audit agent task completion by running a friction-map workflow that measures whether AI browsing agents can discover, initiate, and complete flows like booking, purchasing, registering, or subscribing across your pages.

Do I need a discovery endpoint for agentic task compatibility across browsers?

Yes, providing a discovery endpoint (mcp-actions.json) is required for cross-agent compatibility tracking, ensuring AI agents like Claude in Chrome, Edge Copilot, and Perplexity can successfully discover and initiate site actions.

How do I measure task completion rates across multiple AI browsing agents?

You measure task completion rates by applying a friction-map workflow for evaluation that tracks success rates across domains and pages, verifying that declarative WebMCP markup and imperative navigator.mcpActions registrations exist.

What's the difference between declarative and imperative patterns for agent exposure?

Declarative patterns use WebMCP markup (data-mcp-*) for static action discovery, while imperative patterns involve optional navigator.mcpActions registrations for dynamic exposure, both required to fully enable AI browsing agents to complete real user tasks.