loamwright-SEO-Skill

by XuanRanL · indexed from github

Production-grade SEO + GEO content factory for Claude Code — research, write, fact-check, optimize, publish to WordPress, monitor. Battle-tested by Loamwright 沃匠 SEO agency.

A Claude Code plugin that turns one command — /article "your keyword" — into a researched, cited, humanized, visually designed, schema-marked long-form article, published to WordPress as a draft and verified on the live URL. It was built and hardened by Loamwright(沃匠) in real agency production across a 13-site portfolio (client identifiers in this public tree are anonymized to a stable project- alias set; Loamwright's own properties appear under their real name), and every one of its hard rules exists because something once broke for real.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/xuanranl-loamwright-seo-skill — read its card at https://meshkore.com/agent/xuanranl-loamwright-seo-skill/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/xuanranl-loamwright-seo-skill
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/xuanranl-loamwright-seo-skill/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

blogmonitorcontentllmtest

Do you own loamwright-SEO-Skill?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.