feat(ecosystem): add Alchemy skills (CLI, MCP, API, Agentic Gateway)

[SahilAujla]

Summary

• Adds Alchemy's four first-party skills under ecosystem/ per ecosystem/CONTRIBUTING.md:
  • ecosystem/alchemy-cli/ — live agent work via the Alchemy CLI (@alchemy/cli)
  • ecosystem/alchemy-mcp/ — live agent work via the hosted Alchemy MCP server
  • ecosystem/alchemy-api/ — app code with a standard API key
  • ecosystem/alchemy-agentic-gateway/ — app code without an API key (x402 / MPP wallet-based per-request payments)
• Frontmatter matches the schema in ecosystem/CONTRIBUTING.md (homepage, repository, env, dependencies, metadata.partner: "true")
• Each SKILL.md routes NFT marketplace data, listings, offers, Seaport fulfillment, ERC20 swaps, wallet signing, and tool-sdk needs back to the first-party opensea-* skills

Scope

In: EVM JSON-RPC (100+ chains), Token API, Transfers API, Prices API, Portfolio API, Simulation API, Webhooks, Solana RPC/DAS/Yellowstone gRPC, Sui gRPC, Wallets/Account Kit/Bundler/Gas Manager, x402 + MPP wallet-based auth, Alchemy app/webhook admin.

Out (routes to first-party OpenSea):

• NFT/token data, search, collection stats → opensea-api
• Buy/sell NFTs, listings, offers, Seaport fulfillment → opensea-marketplace
• ERC20 token swaps → opensea-swaps
• Wallet signing setup → opensea-wallet
• Build/register/gate AI agent tools → opensea-tool-sdk

Notes

• Reciprocal to the OpenSea skill Alchemy added: feat(ecosystem): add OpenSea skill (NFT marketplace + Seaport trades) alchemyplatform/skills#37
• alchemy-agentic-gateway is named with the alchemy- prefix to match the ecosystem/<vendor>-<skill-name>/ convention in CONTRIBUTING.md; upstream source is agentic-gateway in alchemyplatform/skills

[ryanio]

Hey @SahilAujla — closing the loop: your ecosystem PR's content just shipped as part of opensea-skill 2.8.0, which auto-published to ClawHub (opensea/opensea-marketplace@2.8.0) at https://github.com/ProjectOpenSea/opensea-skill/releases/tag/v2.8.0. The four ecosystem/alchemy-*/ dirs are on main here with the same content you proposed, plus a small sync action wrapped around them so future updates flow automatically.

How it works going forward: a bot runs Mondays 06:00 UTC against alchemyplatform/skills@main, picks up any drift in references/ and rules/, and opens a PR for review. SKILL.md, LICENSE.txt, and agents/ stay artisan on our side — so the description, handoff table, and frontmatter you set up won't get clobbered by upstream changes. .upstream.json in each ecosystem dir records the upstream SHA so provenance is verifiable.

Pinned to main per your confirmation that those four skills/* paths are stable. If you ever rename or remove one, the bot now refuses to wipe local content and fails loud — we'll update the manifest. Same applies in reverse if Alchemy's side ever wants to flip to SHA pinning instead of branch tracking.

Closing this PR — superseded by the released version. Thanks for kicking the whole thing off!