geo-software-product-grilling SKILL.md skillA
geo-software-product-grilling 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-product-grilling@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-product-grilling/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261113.0d9593d, committed Nov 13, 2026
- First version recorded
- Nov 12, 2026
- Size
- 9,317 bytes
- Repository stars
- 12
- License
- Apache-2.0
作りたい地図プロダクトについて、誰にどんな価値を届けたいのか、その価値のためにどの機能を実装すべきかが十分に明確になるまで、選択肢で答えられる質問を 1 問ずつ重ねて問い詰める。「地図アプリを作りたい」「地図サービスを企画している」「地図を使って何かしたい」のように目的や要件が曖昧な依頼、または技術選定を頼まれたが要件が聞き出せていないときに使う。.
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-product-grilling 作りたい地図プロダクトを、本人への選択肢つきの質問を 1 問ずつ重ねて明確にし、プロダクト概要にまとめる。本人の頭の中の答えを当てにいくのではなく、エージェントが材料から選択肢を作り、本人が選ぶか書き換えることで、2 人で概要を形にしていく。 | reference | 読むとき | 中身 | |---|---|---| | [question-bank](references/question-bank.md) | 質問を組み立てるとき | 観点ごとの質問と選択肢の作り方、2026-11-10 の聞き取りの実例 | | [enterprise-contract](references/enterprise-contract.md) | 業務用・受託・自治体案件のとき | 検収条件、納入物、既存台帳連携、閉域網、SLA、アクセシビリティの追加質問 | ひな形は [assets/product-brief-template.md](assets/product-brief-template.md)。夜に渡す前に [scripts/check_brief.py](scripts/check_brief.py) で、価値の芯、Must、シナリオの置き場所、判断の方針が埋まり、「準備したもの」の鍵の名前が設定済みで CLI があるかを確かめる (値は読まない)。 ## 目的 次がそろったら問い詰めを終え、プロダクト概要にまとめて確認をとる。 - 一行の説明: 誰の、どんな困りごとを、地図で何をすることで解くか - 価値の順位: 届ける価値を、本人が重要な順に並べたもの (最重要、重要、副次的) - 機能: Must / Should / Could。最初の版の期限があれば、その期限までの Must - 後の段階の入口の条件 (リポジトリ直下の AGENTS.md の表): geo-software-arch の 4 項目 (要る機能、データの大きさと対象範囲、ルールの強制、対象端末) と、geo-software-infra の 3 項目 (利用形態、規模、対象地域)。分からない項目は「未定」と書けるが、推測では埋めない ## 進め方 1. 依頼と、本人が示した材料 (参考の URL、過去の記録、似たサービス) を読む。材料は質問と選択肢を作るためだけに使い、読んだ結果の要約や、エージェントの見立てを本人に先に見せない。見せると、本人が自分の答えではなく見立てに寄せてしまう 2. 1 回に 1 問だけ聞く。質問の頭に「N 問目です」と番号を付ける …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_mbsnjfz52y37enmq/fa013651191010f5531a466b992e8a576b4beb34f26c590555dfb3ea8fbdd93c.json
Then /plugin install geo-software-product-grilling@markdownregistry-mbsnjfz52y37enmq 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-product-grilling@sha256:fa013651191010f5The 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_mbsnjfz52y37enmq)
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-product-grilling 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-product-grilling from somewhere else? Ask it: where did my geo-software-product-grilling 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 | 9,317 B | A | view · diff |
| git:20261112.e30bb8e | 2026-11-12 | e30bb8e | 9,100 B | A | view · diff |
| git:20261112.df5079c | 2026-11-12 | df5079c | 8,831 B | A | view · diff |
| git:20261112.b377d97 | 2026-11-12 | b377d97 | 8,324 B | A | view · diff |
| git:20261112.c078140 | 2026-11-12 | c078140 | 8,221 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-product-grilling/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 (9317 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_mbsnjfz52y37enmq GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/geo-software-factory/geo-software-product-grilling GET https://markdownregistry.com/api/v1/blob/fa013651191010f5531a466b992e8a576b4beb34f26c590555dfb3ea8fbdd93c
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.