article-interview SKILL.md skillA
article-interview from shimo4228/writing is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shimo4228/writing/article-interview@git:20261102.730e1f5Pins git:20261102.730e1f5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shimo4228/writing
- Path
.claude/skills/article-interview/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261102.730e1f5, committed Nov 2, 2026
- Size
- 6,312 bytes
- Repository stars
- 3
- License
- CC0-1.0
記事を書く前に、著者が何を書きたいかを一問ずつ聞き、方向を著者に選んでもらう(/article-interview).
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
# article-interview — 聞いて、著者が方向を選ぶ 記事の方向を見つけるのは聞き手の仕事で、決めるのは著者である。この skill が出してよいのは **問いと台帳だけ**。 構成・plan・題・命題は、readiness gate を通ってから writing-ecosystem が書く。AI の聞き手は数ターンで まとめに向かう強い勾配を持つ(質問の数を増やし、相手の発言に根拠のない前提を置き、早くテーマを名付ける)。 この skill は発火している間、その勾配を止める層として働く。 呼ばれ方は 2 つ。writing-ecosystem §2b がこのファイルを読んで入る(collect-context の dossier があればその path を 持って)。著者が `/article-interview` で呼ぶ(note のエッセイも同じ)。 ## 入口 1 通目は 2 文だけ書く。 1. 宣言: dossier があるときは「記録は読みました。まだ記事案も構成も作りません。何が重要かを見つけるために聞きます」。 無いときは前半を落とす 2. 最初の一問: 「この記事について、いま頭にあることを、整理しなくていいので話してください。出来事・違和感・ 言いたいこと・迷っていること、どこからでも」 ## 段階 段階は順に進む。各ターンの問いは一つで、選択肢も仮説も入れない(質問に答えの候補を入れると、聞き手がもう物語を 決めていると相手に伝わる)。 | 段階 | すること | 次へ進む合図 | |---|---|---| | 1 語り | 最初の返答には問いを足さず「ほかにありますか」だけ返す | 著者が「以上」「それくらい」と言う | | 2 出来事 | 著者の語を一つ取り、そのまま使って聞く。「その『〜』を一番感じた出来事は」「その直前に何が」「そのとき何を見た/した/考えた」。理由は「なぜ」でなく「どう至ったか」で聞く | 出来事が 1 件以上、事実・当時の考え・今の解釈に分けて書ける | | 3 意味 | 「いま振り返って何が重要だったか」「記事になるなら読者に残ってほしいのは何か」「誰に読んでほしいか」 | 著者が意味を自分の語で言った | | 4 記録からの外部質問 | dossier にあって著者が触れなかった出来事を 1 件ずつ、「記録には X もある。今回の話に入るか」の形で聞く。入らないと言われたら台帳⑤へ | dossier の主な出来事を一巡した(dossier が無ければ飛ばす) | | 5 暫定解釈 | 「私には A と B がつながって聞こえました。合っていますか。あなたならどう言いますか」。台帳には著者の修正語を書く | 著者が言い直した、または合っていると言った | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gnjsq72psfu6lgty/4c1a7062861b9cc9dbfc87fcca62f7546d6590915424e2de2f64d5c7352745f1.json
Then /plugin install article-interview@markdownregistry-gnjsq72psfu6lgty in Claude Code. It installs git:20261102.730e1f5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add shimo4228/writing/article-interview@sha256:4c1a7062861b9cc9The line at the top of this page pins the label git:20261102.730e1f5, 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_gnjsq72psfu6lgty)
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 shimo4228/writing/article-interview 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 article-interview from somewhere else? Ask it: where did my article-interview 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 1 version of this file, committed on Nov 2, 2026.
Watch this file (sign in, one email per new version)
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/article-interview/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 (6312 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
shimo4228/writing · 3 stars · license CC0-1.0 · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gnjsq72psfu6lgty GET https://markdownregistry.com/api/v1/resolve?ref=shimo4228/writing/article-interview GET https://markdownregistry.com/api/v1/blob/4c1a7062861b9cc9dbfc87fcca62f7546d6590915424e2de2f64d5c7352745f1
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.