geo-software-research-competitor SKILL.md skillA
geo-software-research-competitor 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-research-competitor@git:20261112.67cc76ePins git:20261112.67cc76e 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-research-competitor/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261112.67cc76e, committed Nov 12, 2026
- First version recorded
- Nov 12, 2026
- Size
- 8,070 bytes
- Repository stars
- 12
- License
- Apache-2.0
作りたい地図プロダクトと似たサービス (競合、先行例、代わりになる既存の手段) を探して実際に開き、価値、データ、機能を並べて比べ、本人が「使う」「貢献する」「違いを決めて作る」のどれを選ぶかを選択肢で確かめる。geo-software-product-grilling で価値の芯が決まったあと、技術選定に入る前に使う。「〇〇だけの地図を作りたい」「似たものはあるか」「車輪の再発明にならないか」と言われたときにも使う。.
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-research-competitor 作る前に、似たサービスを探して開き、本人が作るかどうか、何で違いを出すかを決める材料にする。似たものがあることは、作らない理由にならない。既存のもので満足できないところ、既存にない情報や機能があるなら、そこが作る理由になる。決めるのは本人で、エージェントは探して、開いて、並べる。 | reference | 読むとき | 中身 | |---|---|---| | [search-channels](references/search-channels.md) | 似たサービスを探すとき | 探す経路ごとの得手不得手と、2026-11-11 に「全国の本屋の地図」で試した結果 | | [comparison](references/comparison.md) | 見つけたものを並べるとき | 比べる観点、表の形、「全国の本屋の地図」の比較の実例 | 観測済みの地図サービスは [assets/services/](assets/services/README.md) (ウェブ、ウェブとアプリの両方) と [assets/apps/](assets/apps/README.md) (ストアのアプリが本体のもの) に 1 サービス 1 枚のカードで置いてある (一行で、提供する価値、想定する利用者、商用か非商用か、推定の売上、運営、推定の運用費と、描画、背景の地図、保存先、配信)。探す前に、[scripts/find_cards.py](scripts/find_cards.py) で、一行の説明の語と、その言い換え、上位の語、英語を渡してカードを引く (例: `python3 scripts/find_cards.py 電源 Wi-Fi Web会議 作業場所 カフェ 通話 coworking`)。カードを全部読み込んで目で探さない。100 枚を超えるカードの中では、当てはまる 1 枚が埋もれて見落とされる (評価で実際に起きた)。一致したカードは、一致した語が少なくても全部、比べる対象の候補に入れ、手順 4 で開いて確かめる。同じサービスを調べ直さない。新しく開いたサービスは、同じ形のカードにして足す。 ## 入口と出口 - 入口: プロダクト概要の「一行で」と「提供する価値」(本人が並べた順位) が埋まっていること。埋まっていなければ geo-software-product-grilling に戻る - 出口: プロダクト概要の「似たサービスと違い」の節。本人が選んだ進め方 (下の手順 6)。作る場合は、違いを生む機能を Must に入れ直したかどうか ## 手順 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_z3dovp7iocqvfu6o/8945633a4120815b58a0715f4225a40130e8677230e5c67972fa56e35ace42fc.json
Then /plugin install geo-software-research-competitor@markdownregistry-z3dovp7iocqvfu6o in Claude Code. It installs git:20261112.67cc76e, 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-research-competitor@sha256:8945633a4120815bThe line at the top of this page pins the label git:20261112.67cc76e, 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_z3dovp7iocqvfu6o)
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-research-competitor 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-research-competitor from somewhere else? Ask it: where did my geo-software-research-competitor 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, all committed on Nov 12, 2026.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261112.67cc76e latest | 2026-11-12 | 67cc76e | 8,070 B | A | view · diff |
| git:20261112.c078140 | 2026-11-12 | c078140 | 7,369 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-research-competitor/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 (8070 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_z3dovp7iocqvfu6o GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/geo-software-factory/geo-software-research-competitor GET https://markdownregistry.com/api/v1/blob/8945633a4120815b58a0715f4225a40130e8677230e5c67972fa56e35ace42fc
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.