geo-software-migrate SKILL.md skillA
geo-software-migrate from yuiseki/geo-software-factory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yuiseki/geo-software-factory/geo-software-migrate@git:20261114.05b9cc4Pins git:20261114.05b9cc4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yuiseki/geo-software-factory
- Path
.agents/skills/geo-software-migrate/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261114.05b9cc4, committed Nov 14, 2026
- First version recorded
- Nov 12, 2026
- Size
- 10,042 bytes
- Repository stars
- 12
- License
- Apache-2.0
既存の地図プロダクトを、別の地図サービスやライブラリへ乗り換える計画を立てる。Google Maps Platform、Mapbox、Leaflet とラスタタイルからの移行で、今の地図が使っているものの棚卸し、API の対応、移行元の規約で持ち越せないデータ (キャッシュ、プレイス ID、ジオコーディングの結果、Studio のスタイル) と併用の可否、費用の変化、段階的な切り替えと戻し方、移行後の見た目と機能の比べ方を扱う。「Google Maps から乗り換えたい」「Mapbox の料金が高い」「Mapbox GL JS から MapLibre に移りたい」「Leaflet からベクトルタイルに移りたい」「地図 SDK を入れ替える計画を立てて」と言われたら使う。.
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
# geo-software-migrate 既存の地図プロダクトを、別の地図サービスやライブラリへ乗り換える計画を立てる。乗り換え先の選定は geo-software-infra (地図データ) と geo-software-library (ライブラリ) で行い、検索とルート検索の置き場所は geo-software-arch で決める。ここでは、今の地図の棚卸し、移行元の規約による制約、切り替えの段階と戻し方、移行後の比べ方を扱う。 | reference | 読むとき | 中身 | |---|---|---| | [from-google-maps](references/from-google-maps.md) | Google Maps Platform から移るとき | Google Maps JavaScript API、Places、Geocoding、Directions から MapLibre GL JS、OpenLayers、Leaflet などへの API の対応と、併用とデータの持ち越しの規約 | | [from-mapbox](references/from-mapbox.md) | Mapbox から移るとき | Mapbox GL JS v1 / v2 以降から MapLibre GL JS への置き換え (パッケージ、トークン、`mapbox://`、スタイル仕様の違い、プラグイン) と、Studio のスタイルとタイルの規約 | | [from-leaflet-raster](references/from-leaflet-raster.md) | ラスタタイルと Leaflet から移るとき | Leaflet に残してベクトルの層を足すか、MapLibre GL JS や OpenLayers に移るかの目安と、プラグインの対応 | | [legacy-rewrite-and-upgrade](references/legacy-rewrite-and-upgrade.md) | 既存ソフトの改修、依存関係の更新、モダン構成への全面作り直しのとき | 旧ソフトを正本とする特性テスト、新環境への厳密なテスト移植、新旧突合による TDD 移行 | | [migration-plan](references/migration-plan.md) | どの移行でも、計画を立てるとき | 棚卸しの項目、機能フラグや段階的な公開、比較、戻し方、移行元を止める手順 | ## 入力 計画の前に、次のことをそろえる。プロダクト概要があればそこから読み、無ければ依頼から読み取る。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xrxwertmgmfy2dpo/9cdcd625aeb3b141aa584eb8f9cc3bf2e0feadd05699f3f6330fad06a25377c2.json
Then /plugin install geo-software-migrate@markdownregistry-xrxwertmgmfy2dpo in Claude Code. It installs git:20261114.05b9cc4, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add yuiseki/geo-software-factory/geo-software-migrate@sha256:9cdcd625aeb3b141The line at the top of this page pins the label git:20261114.05b9cc4, 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_xrxwertmgmfy2dpo)
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 yuiseki/geo-software-factory/geo-software-migrate 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-software-migrate from somewhere else? Ask it: where did my geo-software-migrate 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 2 versions of this file, between Nov 12, 2026 and Nov 14, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261114.05b9cc4 latest | 2026-11-14 | 05b9cc4 | 10,042 B | A | view · diff |
| git:20261112.c078140 | 2026-11-12 | c078140 | 9,740 B | A | view |
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-software-migrate/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 (10042 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
yuiseki/geo-software-factory · 12 stars · license Apache-2.0 · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xrxwertmgmfy2dpo GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/geo-software-factory/geo-software-migrate GET https://markdownregistry.com/api/v1/blob/9cdcd625aeb3b141aa584eb8f9cc3bf2e0feadd05699f3f6330fad06a25377c2
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.
More from yuiseki/geo-software-factory
Every file in yuiseki/geo-software-factory
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.