geo-software-deploy SKILL.md skillA
geo-software-deploy 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-deploy@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-deploy/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261113.0d9593d, committed Nov 13, 2026
- First version recorded
- Nov 12, 2026
- Size
- 6,966 bytes
- Repository stars
- 12
- License
- Apache-2.0
実装とテストの済んだ地図プロダクトを、人間を呼ばずに公開し、本番で確かめる。昼に準備した認証と権限の範囲で、DB のマイグレーション、デプロイ、独自ドメインの割り当て、本番の URL での確認、リポジトリの公開までを行い、許可の検査に拒まれたら承認の要らない方法で成果物を残す。「デプロイして」「公開して」「本番に出して」「ドメインを割り当てて」「GitHub に公開して」と言われたとき、ダークファクトリーの夜の段階で geo-software-build のあとに使う。.
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-deploy geo-software-build で完成の条件を満たしたものを、本番に出して確かめる。何をどこに置くかは geo-software-arch で決まっている。ここでは、昼に与えられた権限の範囲で出し、本番の URL で完成の条件を確かめ直すところまでを行う。 | reference | 読むとき | 中身 | |---|---|---| | [preflight](references/preflight.md) | 夜に入る前 (昼の準備) と、デプロイの直前 | 人間に先回りして頼むもの、値を出さずに確かめる方法 | | [cloudflare-workers](references/cloudflare-workers.md) | Cloudflare Workers と D1 に出すとき | マイグレーション、デプロイ、独自ドメイン、確かめ方、実際に踏んだ挙動 | | [cloud-deploy](references/cloud-deploy.md) | AWS、Google Cloud、Microsoft Azure、Vercel、Netlify、Render に出すとき | CLI 認証、プレビュー先行デプロイ、ロールバック、台帳記録の比較と共通手順 | | [airgap-onprem](references/airgap-onprem.md) | LGWAN・閉域網・オンプレ VM/IIS へ納品するとき | 外部通信ゼロ確認、イメージ/wheel/タイル同梱バンドル、IIS/systemd 配備要点 | | [verify](references/verify.md) | デプロイの後 | 本番の URL での確かめ方 | | [scripts/deploy_gate.py](scripts/deploy_gate.py) | デプロイの直前とロールバックのとき | 未コミットの変更、評価した版との不一致、公開を止める監査指摘、破壊的な SQL をプログラムで拒み、出した版とコミットを対で台帳に記録して前の版を返す | | [scripts/smoke.py](scripts/smoke.py) | デプロイの直後に | 本番の URL に GET だけで当て、疎通、状態コード、応答時間、`.git` や `.env` の露出、セキュリティのヘッダ、source map を判定する | | [publish-repo](references/publish-repo.md) | リポジトリを公開するとき | 公開前の履歴の点検、公開するブランチ、説明文 | ## 入力 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lj2p5oiwlhscrfnx/bd2e63d95c7d318fdabcfc0ee55c053110082c86bad1a03f9b8ac3e4c091aa51.json
Then /plugin install geo-software-deploy@markdownregistry-lj2p5oiwlhscrfnx 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-deploy@sha256:bd2e63d95c7d318fThe 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_lj2p5oiwlhscrfnx)
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-deploy 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-deploy from somewhere else? Ask it: where did my geo-software-deploy 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 5 versions of this file, between Nov 12, 2026 and Nov 13, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.0d9593d latest | 2026-11-13 | 0d9593d | 6,966 B | A | view · diff |
| git:20261113.2f9f217 | 2026-11-13 | 2f9f217 | 6,750 B | A | view · diff |
| git:20261113.a912aab | 2026-11-13 | a912aab | 6,511 B | A | view · diff |
| git:20261112.c495e9a | 2026-11-12 | c495e9a | 6,186 B | A | view · diff |
| git:20261112.298bd4e | 2026-11-12 | 298bd4e | 5,828 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-deploy/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 (6966 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_lj2p5oiwlhscrfnx GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/geo-software-factory/geo-software-deploy GET https://markdownregistry.com/api/v1/blob/bd2e63d95c7d318fdabcfc0ee55c053110082c86bad1a03f9b8ac3e4c091aa51
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.