cover-art SKILL.md skillA
cover-art 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/cover-art@git:20261114.cd7501fPins git:20261114.cd7501f 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/cover-art/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261114.cd7501f, committed Nov 14, 2026
- Size
- 11,700 bytes
- Repository stars
- 3
- License
- CC0-1.0
記事の見出し画像(カバー)の生成プロンプトを作り、できた画像を点検する。『見出し画像を作って』『カバー画像』で使う。図は mono-figure、題とサムネの文字は headline-craft。.
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
# cover-art — 記事の見出し画像 見出し画像は、読者が記事を開く前の期待を作る。画像を添えるだけで見出しは「正しそう」に見え、 誤った期待は本文を読んだ後も残る。だから本文が回収しないものを絵で足さない。 この skill の目的はクリック率ではない。題と画像だけを見た人の期待が本文と一致することを目指す。 ## 入力と完了条件 入力は、内容 GO とタイトル確定が済んだ原稿の path と、出す媒体。作るのはこの後で、題と命題が 動くと画像の主題も動くからである。 画像は、Codex で案ごとに 1 枚ずつ並列に生成して著者が 1 枚を選ぶ(下の「生成」)か、著者が自分の生成ツールで 作る。この skill は主題の案・プロンプト・生成・点検を受け持つ。 完了は、媒体ごとの画像ファイルが下の「点検」を全部通り、alt が決まった状態。 headline-craft が見出し画像の構図メモ(焦点の対象・要素の数)を出していれば、主題を決める材料に使う。記事の 見出し画像には文字を入れないので、構図メモの文字の位置は使わない。 ## 媒体の仕様 | 媒体 | 寸法・容量 | 切れ方 | 置き場 | |---|---|---|---| | note | 推奨 1280×670(約 1.91:1)、最大 10MB | 推奨と違う比率はトリミングされ、ブラウザとアプリで見え方が違う | `images/covers/<slug>-note.png` | | Substack | post / social preview は 1200×630 以上 | Center か Smart で自動に切り抜く。公式ページは同じ箇所に「14:10」とも書いていて、数値どうしが合わない | note と同じ 1 枚 | | DEV | cover は 1000×420(約 2.38:1) | 上下が切れる | `images/covers/<slug>.png`(GitHub raw URL で参照する) | | Zenn | 見出し画像の欄がない(emoji が担う) | — | 作らない | as-of: note は noteヘルプ「登録画像の推奨サイズ一覧」(2026-10-01 閲覧)。Substack と DEV は 2026-11-02 の調査で、 Substack の 1200×630 は第三者の解説とも一致する。 原版は 1 枚、1280×670 で作る。主題と意味を担う部分は中央の 60% に収める。Substack の小さいリンクカードが一番 きつく切り、DEV は上下が切れるので、周辺は切れても意味を失わない余白にする。DEV 用は原版から切り出す。 ```sh …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7tx3aro2z33ii6gp/e27c68e009927fcb9b5464b7459eaf696b9fbb67e5b5473a97c3ce38c6164591.json
Then /plugin install cover-art@markdownregistry-7tx3aro2z33ii6gp in Claude Code. It installs git:20261114.cd7501f, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add shimo4228/writing/cover-art@sha256:e27c68e009927fcbThe line at the top of this page pins the label git:20261114.cd7501f, 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_7tx3aro2z33ii6gp)
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/cover-art 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 cover-art from somewhere else? Ask it: where did my cover-art 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 14, 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/cover-art/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 (11700 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_7tx3aro2z33ii6gp GET https://markdownregistry.com/api/v1/resolve?ref=shimo4228/writing/cover-art GET https://markdownregistry.com/api/v1/blob/e27c68e009927fcb9b5464b7459eaf696b9fbb67e5b5473a97c3ce38c6164591
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.