zenn-format SKILL.md skillA
zenn-format 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/zenn-format@git:20261113.01f04a3Pins git:20261113.01f04a3 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/zenn-format/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261113.01f04a3, committed Nov 13, 2026
- First version recorded
- Oct 3, 2026
- Size
- 6,744 bytes
- Repository stars
- 3
- License
- CC0-1.0
Zenn記事のfrontmatter、emoji/topics、Zenn固有Markdown記法の正本。Use when — Zenn原稿を作成・検証するとき、著者の内容GO後にtopics/emoji候補を提示するとき。NOT for — 執筆構成・voice・タイトル判定・公開可否・Dev.to/note/Substack形式。.
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
# Zenn Format Skill 文体と執筆プロセスはproject-local `writing-ecosystem`、titleは`headline-craft`、channel値は `.claude/rules/publishing-channels.md`、公開操作は`publish-article`が持つ。 ## Frontmatter draft template: ```markdown --- title: "Your Article Title" emoji: "📚" type: "tech" topics: ["claudecode", "mcp", "python"] published: false --- ## 最初の見出し ``` 本文見出しはH2から始める。公開時は`published: true`と`published_at`を設定する。 | Field | Requirement | |---|---| | `title` | required。文字数はchannel contract | | `emoji` | required、single emoji | | `type` | required、`tech`または`idea`。voice分岐には使わない | | `topics` | required、lowercase 1〜5件 | | `published` | required、boolean | | `published_at` | `published: true`でrequired。`YYYY-MM-DD HH:MM` JST | ## Emoji and topics emojiは記事の主対象を示す一つを選ぶ。 | Theme | Candidates | |---|---| | AI / LLM | 🤖, 🧠, 💬 | | Learning | 📚, 🎓, 📝 | | Testing | 🔬, ✅, 🧪 | | Development | ⚙️, 🛠️, 💻 | | Performance | ⚡, 📊 | | Architecture | 🏛️, 🧩, 🌐 | topics: - 1〜5件。具体性があるなら5件まで使う - 主題に最も近い製品名・技術名・手法名を選ぶ。各 topic は、その語で検索した読者がこの記事に届く語にする - `ai` / `llm` / `generativeai` は入れない — 主題を問わず付く広い語で、その語で探す読者の関心が記事の主題と合わない。空いた枠は本文が正面から扱う手法名(例: `llmasajudge`)で埋めるか、空けたままにする …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jpse2fdbso7xb6iz/dd4e9ad2bfcef3f517d032866ab632bad8e251ccdca38cf42c985d6195f3924b.json
Then /plugin install zenn-format@markdownregistry-jpse2fdbso7xb6iz in Claude Code. It installs git:20261113.01f04a3, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add shimo4228/writing/zenn-format@sha256:dd4e9ad2bfcef3f5The line at the top of this page pins the label git:20261113.01f04a3, 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_jpse2fdbso7xb6iz)
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/zenn-format 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 zenn-format from somewhere else? Ask it: where did my zenn-format 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 Oct 3, 2026 and Nov 13, 2026, about one every 10 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.01f04a3 latest | 2026-11-13 | 01f04a3 | 6,744 B | A | view · diff |
| git:20261102.28f20a9 | 2026-11-02 | 28f20a9 | 6,734 B | A | view · diff |
| git:20261012.bef9f2a | 2026-10-12 | bef9f2a | 6,747 B | A | view · diff |
| git:20261003.ee42589 | 2026-10-03 | ee42589 | 6,430 B | A | view · diff |
| git:20261003.7636d9e | 2026-10-03 | 7636d9e | 6,208 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/zenn-format/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 (6744 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_jpse2fdbso7xb6iz GET https://markdownregistry.com/api/v1/resolve?ref=shimo4228/writing/zenn-format GET https://markdownregistry.com/api/v1/blob/dd4e9ad2bfcef3f517d032866ab632bad8e251ccdca38cf42c985d6195f3924b
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.