geo-software-build SKILL.md skillA
geo-software-build 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-build@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-build/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261114.05b9cc4, committed Nov 14, 2026
- First version recorded
- Nov 12, 2026
- Size
- 9,112 bytes
- Repository stars
- 12
- License
- Apache-2.0
技術選定の済んだ地図プロダクトを、人間を呼ばずに実装してテストし、実装と別の評価者 (geo-software-eval) の評価に通るまで直す。技術選定の結果から、テストを先に書いて小さく積み、地図に載せるデータを出典つきで組み立て、画面と同期の配線までテストし、ブラウザで画面を開いて目で確かめる。「実装して」「作って」「TDD で進めて」「この概要どおりに作って」と言われたとき、ダークファクトリーの夜の段階で、技術選定が終わったあとに使う。公開は geo-software-deploy で行う。.
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-build geo-software-eval の評価に通るまで、実装とテストを人間を呼ばずに進める。完成かどうかを決めるのは実装者ではなく、実装から切り離した評価である。実装者が書くテストは、作りながら壊さないための道具で、完成の判定には使わない。技術の選定はここでは行わない (geo-software-arch、geo-software-infra、geo-software-data、geo-software-library の結果に従う)。手順は、地図アプリ 1 本を企画から公開まで通したときの記録から作った。その記録では、実装の合意から公開まで約 25 分、初めのコミットから公開まで 22 分だった。 | reference | 読むとき | 中身 | |---|---|---| | [order](references/order.md) | 作り始める前に | 小さく積む順番と、各段で書くテスト | | [testing](references/testing.md) | テストの置き場所と道具を決めるとき | 本番と同じ実行環境でのテスト、配線のテスト、認証を通した通しの確認、画面の確かめ方 | | [data](references/data.md) | 地図に載せるデータを組み立てるとき | 出典を固定した取得、行ごとの出典、ビルドで落とす検査、正本の決め方 | | geo-software-tdd | 試験の種類と CI を決めるとき | 地図のライブラリと OSS の地図アプリの作法に沿った、試験の種類、試験のデータと通信、CI の組み立て、不安定な試験の扱い | | [pitfalls](references/pitfalls.md) | 詰まったとき、終わる前に | 実際に踏んだ失敗と、その見つけ方 | ## 入力 - プロダクト概要 (`product-brief.md`): 一行の説明、機能 (Must / Should / Could)、完成の条件の大枠、判断の方針、技術選定の結果、準備したもの。評価のシナリオの本文は読まない (置き場所だけ知っていればよい)。 - 評価のシナリオが無ければ、昼なら geo-software-eval で人間と作る。夜なら、実装者とは別の文脈の評価者に、Must から geo-software-eval の手順で書き起こさせ、「夜に決めたこと」に書く。実装者が自分でシナリオを書かない。 - 技術選定の結果が無ければ、先に技術選定のスキルを使う。 ## 進め方 1. 評価のシナリオの置き場所と、評価者を立てる方法 (別のエージェント、別のセッション) を確かめる。シナリオの本文は開かない。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_nl2lqve3vwncqmzi/60761dba44b3d7e4152927494f678b2aebc98447dc3dc24b4e405a71d7f00ade.json
Then /plugin install geo-software-build@markdownregistry-nl2lqve3vwncqmzi 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-build@sha256:60761dba44b3d7e4The 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_nl2lqve3vwncqmzi)
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-build 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-build from somewhere else? Ask it: where did my geo-software-build 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 14, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261114.05b9cc4 latest | 2026-11-14 | 05b9cc4 | 9,112 B | A | view · diff |
| git:20261112.632dcee | 2026-11-12 | 632dcee | 8,714 B | A | view · diff |
| git:20261112.df5079c | 2026-11-12 | df5079c | 8,697 B | A | view · diff |
| git:20261112.637d57d | 2026-11-12 | 637d57d | 8,260 B | A | view · diff |
| git:20261112.298bd4e | 2026-11-12 | 298bd4e | 8,023 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-build/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 (9112 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_nl2lqve3vwncqmzi GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/geo-software-factory/geo-software-build GET https://markdownregistry.com/api/v1/blob/60761dba44b3d7e4152927494f678b2aebc98447dc3dc24b4e405a71d7f00ade
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.