publish-article SKILL.md skillA
publish-article 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/publish-article@git:20261114.525f78fPins git:20261114.525f78f 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/publish-article/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261114.525f78f, committed Nov 14, 2026
- First version recorded
- Sep 29, 2026
- Size
- 5,415 bytes
- Repository stars
- 3
- License
- CC0-1.0
quality-gate PASS済みの対象稿1本について、Zennのfrontmatter・preview・予約またはDev.toのdry-run・予約、公開索引、push確認を扱うproject-local公開skill。Use when — 対象となるZenn稿またはEN稿自身のproject-local quality-gate PASSと著者GOの後。NOT for — 翻訳生成、prose review、security/quality判定、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
# Publish Article Skill このskillは公開操作だけを持つ。文章品質とpublic-safetyはproject-local `quality-gate`、Zenn形式は `zenn-format`、channel値は `.claude/rules/publishing-channels.md` が正本。 ## Usage ```text /publish-article articles/<slug>.md /publish-article articles-en/<slug>.md ``` 引数なしなら `published: false` のZenn原稿を列挙する。 ## Preconditions - 引数で指定した対象稿自身のproject-local `quality-gate`がPASS - 著者が最終タイトルと本文を通読済み - 著者が公開GOを出している 不足していれば公開操作を始めず、欠けた証跡を返す。 最初に対象pathをchannel contractの1行へ解決する。JP稿のPASSをEN稿へ流用しない。 ## Zenn / Dev.to publish flow ### 1. Validate target ```bash npm run evidence -- articles/<slug>.md --online # 構造・書式・実在・一致 + 外部URLの生死 npm run validate ``` `deviations`が1件でもあれば公開操作を始めない。`grandfathered`は検査導入前の既公開分なので blockしない。目視で数え直さず、scriptの出力をそのまま扱う。 Zenn稿のtitle、emoji、type、topics、slug、`published_at`は`zenn-format`とchannel contractに従う。 EN稿は`devto-translator` self-check済みであることを確認する。 ### 2. Preview or dry-run ```bash npm run preview ``` Zenn稿は`http://localhost:8000`でコードblock、画像、message/details、内部linkを確認する。 EN稿は実POSTせずdry-runする。 ```bash cd scripts && uv run python devto_crosspost.py post <slug> --dry-run ``` ### 3. Schedule the resolved target 通常はfrontmatterを次の形にする。 ```yaml …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_l6xqt7c7kjfkwe4j/ca32f81573ee44e88881a27c3c7fbd50ce530816422b1d4c6ee00d53c639f112.json
Then /plugin install publish-article@markdownregistry-l6xqt7c7kjfkwe4j in Claude Code. It installs git:20261114.525f78f, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add shimo4228/writing/publish-article@sha256:ca32f81573ee44e8The line at the top of this page pins the label git:20261114.525f78f, 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_l6xqt7c7kjfkwe4j)
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/publish-article 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 publish-article from somewhere else? Ask it: where did my publish-article 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 Sep 29, 2026 and Nov 14, 2026, about one every 11 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261114.525f78f latest | 2026-11-14 | 525f78f | 5,415 B | A | view · diff |
| git:20261102.ea199f1 | 2026-11-02 | ea199f1 | 5,396 B | A | view · diff |
| git:20261012.f7bf0f2 | 2026-10-12 | f7bf0f2 | 5,116 B | A | view · diff |
| git:20261003.5f083a9 | 2026-10-03 | 5f083a9 | 5,061 B | A | view · diff |
| git:20260929.12b4c12 | 2026-09-29 | 12b4c12 | 4,503 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/publish-article/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 (5415 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_l6xqt7c7kjfkwe4j GET https://markdownregistry.com/api/v1/resolve?ref=shimo4228/writing/publish-article GET https://markdownregistry.com/api/v1/blob/ca32f81573ee44e88881a27c3c7fbd50ce530816422b1d4c6ee00d53c639f112
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 shimo4228/writing
Every file in shimo4228/writing