substack-publishing SKILL.md skillB
substack-publishing 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/substack-publishing@git:20261114.761a86cPins git:20261114.761a86c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shimo4228/writing
- Path
.claude/skills/substack-publishing/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261114.761a86c, committed Nov 14, 2026
- First version recorded
- Sep 16, 2026
- Size
- 15,804 bytes
- Repository stars
- 3
- License
- CC0-1.0
完成・レビュー済みのhuman essayをSubstackへHTML pasteで公開し、project corpusへmirrorするlocal workflow。執筆の原理は writing-principles rule、Title / 出典は project-local writing-ecosystem、翻訳はprose-translationにdefer。Use when — Substackへ手動投稿・mirror・配信運用するとき。NOT for — note投稿(note-publishing)、執筆、翻訳、quality判定。.
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
# substack-publishing — Substack 公開 + LLM corpus ミラー レビュー済みの human essay を Substack に公開し、LLM に発見されるよう corpus へミラーするまでの手順。執筆・レビュー・翻訳は別 skill が担い、本 skill は **Substack 固有の公開機構** と **公開後のミラー / cross-link** だけを扱う。 ## いつ使うか project-local `quality-gate` PASSと著者GOの後に使う。noteの投稿操作は`note-publishing`が所有する。日本語正本は`note/`(Zenn転載は`articles/`)、Substackへは `prose-translation`で訳したEN版を出す。 ## defer 先(本 skill では再掲しない) - Voice / AI-slop / Title 規約 / 出典編入(Citation & Sources Workflow)→ `writing-ecosystem` - JA→EN 翻訳 → `prose-translation` ## 1. Substack は raw Markdown を変換しない エディタに Markdown を貼っても `##` や `[](url)` は literal のまま残る。経路は2つ: - **入力時ショートカット**(短い編集向け): `#`/`##`/`###`+space=見出し、`>`+space=引用、`---`=区切り線、`*`/`-`+space=リスト、cmd+B/I、cmd+K=リンク。**貼り付けでは変換されない**(タイプ時のみ効く)。 - **MD→HTML→リッチテキスト貼り付け**(全文向け・推奨): ```bash scripts/render_note_assets.sh substack/<slug>-en.md # note/<slug>.md も同じ ``` 先頭 h1 の除外(タイトル欄に別入力するため)と `-f gfm` をスクリプトが持つ。pandoc の既定方言は 「blank line なしで段落直後に始まるリスト」を段落に潰す(GitHub 上のレンダリングと乖離する)。 **手打ちの `pandoc` を書かない** — `-f gfm` を落とすとこの段落潰れを起こす。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hn73k7j73rwphb54/7069a55896ffa06d457121608bf27648519828b2a64dd3777e388b517ddaa7c6.json
Then /plugin install substack-publishing@markdownregistry-hn73k7j73rwphb54 in Claude Code. It installs git:20261114.761a86c, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add shimo4228/writing/substack-publishing@sha256:7069a55896ffa06dThe line at the top of this page pins the label git:20261114.761a86c, 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_hn73k7j73rwphb54)
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/substack-publishing 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 substack-publishing from somewhere else? Ask it: where did my substack-publishing 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 16, 2026 and Nov 14, 2026, about one every 15 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261114.761a86c latest | 2026-11-14 | 761a86c | 15,804 B | B | view · diff |
| git:20261114.81fd010 | 2026-11-14 | 81fd010 | 14,419 B | B | view · diff |
| git:20261102.ea199f1 | 2026-11-02 | ea199f1 | 14,827 B | B | view · diff |
| git:20260929.12b4c12 | 2026-09-29 | 12b4c12 | 14,532 B | B | view · diff |
| git:20260916.bf8561b | 2026-09-16 | bf8561b | 14,490 B | B | 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/substack-publishing/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
- fail: No link to a raw IP address (matched: http://127.0.0.1)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15804 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 script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
shimo4228/writing · 3 stars · license CC0-1.0 · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hn73k7j73rwphb54 GET https://markdownregistry.com/api/v1/resolve?ref=shimo4228/writing/substack-publishing GET https://markdownregistry.com/api/v1/blob/7069a55896ffa06d457121608bf27648519828b2a64dd3777e388b517ddaa7c6
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.