geo-publish SKILL.md skillA
geo-publish from fangx-ai/geo-doctor is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fangx-ai/geo-doctor/geo-publish@v1.8.0Pins v1.8.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fangx-ai/geo-doctor
- Path
skills/geo-publish/SKILL.md- Versions recorded
- 1
- Latest version
- v1.8.0, committed Nov 16, 2026
- Size
- 4,453 bytes
- Repository stars
- 610
- License
- MIT
Plan and run multi-platform publishing for GEO content: the official site publishes directly, third-party platforms get a packaged outbox that a human posts. Use when the user asks where to publish so AI cites them, wants one article shipped to a blog plus social platforms, needs drafts converted into each platform format, or wants a publish log of what went out and when. Publishes only confirmed drafts and never claims a post succeeded on a platform without a URL. For the writing itself, see…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 发布与分发 只做一件事:**把已经审过的稿子发出去,并记清楚发了什么、发到哪、链接是什么。** 不代发第三方平台,不伪造发布成功。 用用户的语言交流;本文件是中文的,读懂后用用户的语言转述。 ## 什么时候用 - "这篇稿子该发哪几个平台?" - "一次发到官网、知乎、公众号、小红书" - "发完了,怎么记录?" / 想知道哪些平台真的被 AI 读到 - 已经有一批 `geo/drafts/`,要按平台转格式 不接的活:还没写稿 → `ai-content-writer`;发布后要测效果 → `ai-visibility`;站点文件 → `llms-txt`。 ## 两条铁律 1. **只发 `status: confirmed` 的草稿。** 没审过的稿子进不了发布和打包流程,这是硬门槛,不要为了"先发出去"手改状态。 2. **发布成功只以"有可访问的 URL"为证据。** 打包生成、粘贴完成、平台提示"已提交"都不是发布成功;被 AI 提及、被 AI 引用更是另外两件事,不能混着说。 ## 流程 以本 `SKILL.md` 所在目录为技能根,说明见 `references/publishing.md`,脚本 `scripts/geo-publish.mjs`(零依赖)。 ### 1. 检查 ```bash node scripts/geo-publish.mjs check geo/drafts node scripts/geo-publish.mjs check geo/drafts --json ``` 逐篇报:缺事实来源、缺平台适配、状态不合格、标题/摘要长度超限。**先清零再发。** ### 2. 官网 / 自有站 ```bash node scripts/geo-publish.mjs site geo/drafts --to static --out dist --base-url https://example.com node scripts/geo-publish.mjs site geo/drafts --to wordpress --site https://blog.example.com --user me --status draft node scripts/geo-publish.mjs site geo/drafts --to http --endpoint https://api.example.com/posts --token-env MY_TOKEN ``` WordPress 用应用密码,从环境变量 `GEO_WP_APP_PASSWORD` 读,**不要写在命令或文件里**。先 `--status draft` 发成草稿,人看一眼再发布,比直接 publish 安全。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7cljtp3ixnh3llc5/514f128944cae90704cf5110166cd543b2b1750ee594275e735c4626096525a9.json
Then /plugin install geo-publish@markdownregistry-7cljtp3ixnh3llc5 in Claude Code. It installs v1.8.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add fangx-ai/geo-doctor/geo-publish@sha256:514f128944cae907The line at the top of this page pins the label v1.8.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7cljtp3ixnh3llc5)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in fangx-ai/geo-doctor/geo-publish since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of geo-publish from somewhere else? Ask it: where did my geo-publish come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 16, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/geo-publish/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4453 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
fangx-ai/geo-doctor · 610 stars · license MIT · pushed 2026-11-17 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_7cljtp3ixnh3llc5 GET https://markdownregistry.com/api/v1/resolve?ref=fangx-ai/geo-doctor/geo-publish GET https://markdownregistry.com/api/v1/blob/514f128944cae90704cf5110166cd543b2b1750ee594275e735c4626096525a9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.