geo-software-ops SKILL.md skillA
geo-software-ops 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-ops@git:20261113.0d9593dPins git:20261113.0d9593d 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-ops/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261113.0d9593d, committed Nov 13, 2026
- First version recorded
- Nov 12, 2026
- Size
- 10,466 bytes
- Repository stars
- 12
- License
- Apache-2.0
地図プロダクトを運用する。地図 API のキーの管理 (公開キー、Origin や referrer、アプリの識別子の制限、漏洩したときの対処、入れ替え)、利用量と予算の監視とアラート、上限で止まるか課金が続くかの提供元ごとの違い、地図データとタイルの更新の手順 (PMTiles の作り直しと切り替え、CDN のキャッシュの無効化、帰属表示の日付)、提供元の障害や無料枠の超過で地図が出なくなったときの切り替えを扱う。「API キーの制限をどうする」「キーが漏れた」「地図 API の請求が急に増えた」「予算の上限を掛けたい」「タイルの更新手順」「地図が出なくなった」「障害時の備え」と言われたら使う。提供元の選定は geo-software-infra、置き場所は geo-software-arch で行う。.
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-ops 地図プロダクトを公開した後の運用を決める。キーの制限、利用量と予算の歯止め、データの更新、障害時の切り替えの 4 つを、使っている提供元ごとに手順にする。提供元ごとの料金、無料枠、規約の事実は geo-software-infra の provider の reference にあり、ここでは運用に効く違い (止まるか課金が続くか、何で制限できるか、どこで障害を知るか) を扱う。 | reference | 読むとき | 中身 | |---|---|---| | [api-key-management](references/api-key-management.md) | 地図 API のキーを発行・公開するとき、キーが漏れたとき | 提供元ごとにできる制限 (referrer、Origin、アプリの識別子、API の種類)、入れ替えと漏洩時の手順 | | [usage-monitoring](references/usage-monitoring.md) | 予算を決めるとき、請求が急に増えたとき | 提供元ごとの利用量の見え方、通知、ハードキャップの有無、超過時の振る舞い | | [data-update](references/data-update.md) | 地図データやタイルを更新するとき | 生成と取得、版ごとの別名での配置、ETag、CDN のキャッシュの消し方、帰属表示の日付 | | [fallback](references/fallback.md) | 障害に備えるとき、地図が出なくなったとき | ステータスページの一覧、原因の見分け方、予備のスタイル、キャッシュの規約、利用者への見せ方 | | [handover-sla](references/handover-sla.md) | 受託開発や自治体案件で引き渡すとき | SLA・RPO/RTO 定義、バックアップ・DR、1 次切り分けフロー、引き渡し文書一式 | | geo-software-infra の [providers](../geo-software-infra/references/providers/) | 提供元の単価、無料枠、規約を確かめるとき | 提供元ごとの事実 (2026-11-10 確認) | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_4t2qf4ah3ploidm5/e78633447807b6cfc4a419e2c869f87b18aec78147135bb3d4a2cd3d8356cf95.json
Then /plugin install geo-software-ops@markdownregistry-4t2qf4ah3ploidm5 in Claude Code. It installs git:20261113.0d9593d, 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-ops@sha256:e78633447807b6cfThe line at the top of this page pins the label git:20261113.0d9593d, 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_4t2qf4ah3ploidm5)
1 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-ops 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-ops from somewhere else? Ask it: where did my geo-software-ops 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 13, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.0d9593d latest | 2026-11-13 | 0d9593d | 10,466 B | A | view · diff |
| git:20261112.c078140 | 2026-11-12 | c078140 | 10,260 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-ops/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 (10466 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_4t2qf4ah3ploidm5 GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/geo-software-factory/geo-software-ops GET https://markdownregistry.com/api/v1/blob/e78633447807b6cfc4a419e2c869f87b18aec78147135bb3d4a2cd3d8356cf95
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.