Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

commerce-protocol-readiness

Estrellas1

Forks1

Actualizado15 de junio de 2026 a las 21:34

Audit an ecommerce storefront for agentic commerce protocols and action readiness. Use when checking ACP, UCP, AP2, x402, MPP, MCP, A2A, OAuth, checkout, order, and payment readiness.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

wakqasahmed

wakqasahmed/agentic-commerce-skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	commerce-protocol-readiness
description	Audit an ecommerce storefront for agentic commerce protocols and action readiness. Use when checking ACP, UCP, AP2, x402, MPP, MCP, A2A, OAuth, checkout, order, and payment readiness.

Commerce Protocol Readiness

Workflow

Classify the commerce goal: discovery only, assisted checkout, native agent checkout, account linking, order support, paid API/tool access, or machine-to-machine payment.
Check public discovery signals: documented API catalog, .well-known endpoints, MCP server card, A2A agent card, WebMCP, Agent Skills, link headers, and developer docs.
Check checkout readiness: cart creation, pricing/tax/shipping recalculation, inventory reservation, checkout session handoff, order confirmation, returns/refunds, and support escalation.
Map protocols to the goal:
- ACP: agent-initiated checkout where the merchant remains merchant of record.
- UCP: broader lifecycle coverage across search, cart, identity linking, checkout, order, and post-purchase support.
- AP2: cryptographic payment authorization and user-consent proof.
- x402 or MPP: paid API requests, content access, tool calls, or machine-to-machine payments.
- MCP: exposing merchant tools, catalog lookup, policy lookup, support tools, or order tools to agents.
- A2A: delegating work between agents using explicit capabilities.
Score each protocol as not applicable, missing, partial, ready, or verified, with evidence.
Recommend the smallest next implementation that improves buyer value and merchant control.

Guardrails

Do not treat a protocol as required just because it exists. Tie it to a concrete customer or agent workflow.
See ../references/guardrails.md for shared cross-skill guardrails (autonomous action safety, evidence provenance, internal runtime disclosure).

Más de este repositorio

mismo repositorio

skills-marketplace-readiness

wakqasahmed/agentic-commerce-skills

Prepare an agent skills repository for discovery, installation, and marketplace listings. Use when publishing skills to skills.sh, Agent Skills clients, Claude plugins, Codex, Cursor, Copilot, and related skill directories.

2026-07-171

agent-readiness

wakqasahmed/agentic-commerce-skills

Check whether AI agents can discover, read, cite, and safely act on an ecommerce storefront. Use for agentic commerce readiness reviews.

2026-07-171

custom-agent-remediation-plan

wakqasahmed/agentic-commerce-skills

Convert Agentic Commerce audit findings into a custom-agent implementation checklist. Use after readiness, SEO/AEO/GEO, product knowledge, or policy gaps are known.

2026-07-171

readiness-audit

wakqasahmed/agentic-commerce-skills

Route an ecommerce storefront through an Agentic Commerce readiness audit. Use when assessing whether a store should move to Custom Agent, Verified Audit, Forward Deployed Engineering, or Not Qualified.

2026-07-171

llms-txt-and-crawler-access

wakqasahmed/agentic-commerce-skills

Review crawler and AI-agent access files for ecommerce sites, including robots.txt, sitemap, llms.txt, and AI bot rules.

2026-07-101

ecommerce-policy-readiness

wakqasahmed/agentic-commerce-skills

Assess whether ecommerce policies are clear enough for AI answers, support drafts, and supervised order workflows.

2026-06-151

name	commerce-protocol-readiness
description	Audit an ecommerce storefront for agentic commerce protocols and action readiness. Use when checking ACP, UCP, AP2, x402, MPP, MCP, A2A, OAuth, checkout, order, and payment readiness.

Commerce Protocol Readiness

Workflow

Classify the commerce goal: discovery only, assisted checkout, native agent checkout, account linking, order support, paid API/tool access, or machine-to-machine payment.
Check public discovery signals: documented API catalog, .well-known endpoints, MCP server card, A2A agent card, WebMCP, Agent Skills, link headers, and developer docs.
Check checkout readiness: cart creation, pricing/tax/shipping recalculation, inventory reservation, checkout session handoff, order confirmation, returns/refunds, and support escalation.
Map protocols to the goal:
- ACP: agent-initiated checkout where the merchant remains merchant of record.
- UCP: broader lifecycle coverage across search, cart, identity linking, checkout, order, and post-purchase support.
- AP2: cryptographic payment authorization and user-consent proof.
- x402 or MPP: paid API requests, content access, tool calls, or machine-to-machine payments.
- MCP: exposing merchant tools, catalog lookup, policy lookup, support tools, or order tools to agents.
- A2A: delegating work between agents using explicit capabilities.
Score each protocol as not applicable, missing, partial, ready, or verified, with evidence.
Recommend the smallest next implementation that improves buyer value and merchant control.

Guardrails

Do not treat a protocol as required just because it exists. Tie it to a concrete customer or agent workflow.
See ../references/guardrails.md for shared cross-skill guardrails (autonomous action safety, evidence provenance, internal runtime disclosure).