writing-ecosystem SKILL.md skillA
writing-ecosystem 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/writing-ecosystem@git:20261115.7a8a990Pins git:20261115.7a8a990 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/writing-ecosystem/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261115.7a8a990, committed Nov 15, 2026
- First version recorded
- Nov 13, 2026
- Size
- 29,177 bytes
- Repository stars
- 3
- License
- CC0-1.0
人間向け記事・エッセイ・ブログポスト・ニュースレターの唯一の執筆 orchestrator。project の publication channel contract を読み、中心命題 1 つの editorial brief、因果線、証拠の選択と除外、構成、執筆、観点別レビュー、著者の内容 GO、タイトル、quality-gate までを統括する。Use when — 「この記事を書いて」「このテーマでエッセイにして」「原稿の論点を一つに絞って構造改稿して」のような新規執筆・全体改稿・全文の別 channel 展開。NOT for — 一文や段落だけの翻訳(→ prose-translation)、title だけ(→ headline-craft)、SNS の告知・断片(→ social-post)、公開 thread 返信(→ public-comment)、AI 向け docs、README、paper、媒体固有の公開操作。.
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
# writing-ecosystem — 人間向け執筆の手順 人間読者向けコンテンツ(記事・エッセイ・ブログポスト・ニュースレター)を書く手順と、関わる skill・agent の 役割分担の正本。 **書き始める前に `~/MyAI_Lab/writing/.claude/rules/writing-principles.md`(執筆の背骨: 著者の方針と原理 6 本)を読む。** この repo で作業していれば rules として常駐しているが、別 repo からの `--add-dir` や他 skill からの参照では載っていない。 判断は背骨から導き、本 skill は手順・役割・受け入れの規律だけを持つ。 ## Scope **人間 primary のコンテンツのみ扱う**。AI-facing ドキュメント(`llms.txt` / `llms-full.txt` / FAQ ページ等)には `llms-txt-writer` skill を使う。audience 判定と役割分担は `llms-txt-writer` skill の SKILL.md の「Audience Separation: Human vs AI」節を読む。 媒体名・語尾・frontmatter・文字数・reviewer 構成・公開 command は channel contract が持つ。記事全体を 扱う task では最初に `<project>/.claude/rules/*.md` の **publication channel contract** を読み、対象 path を 1 channel へ解決する。contract が無い、または複数 channel に一致する場合は推測せず停止する。 執筆時の規範は、背骨の rule・local contract・本 skill の手順だけである。ADR と memory は経緯と事例の記録で、 規範は背骨に一本化してある。過去セッションを素材にするときは `session-theme-mining` が選んだ一次 pointer、`collect-context` が作る evidence dossier の順に限定して受け取る。 --- ## Ecosystem Map 執筆関連コンポーネントの役割分担。どの phase で誰が何を持つか。 | フェーズ | コンポーネント | 軸 | トリガー | |---------|---------------|-----|----------| …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qjkjelwytsullvyk/c6a7b821c8aa59c4985e70d554c745b5737ccceb9be9f0bdb522dcd192d5c490.json
Then /plugin install writing-ecosystem@markdownregistry-qjkjelwytsullvyk in Claude Code. It installs git:20261115.7a8a990, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add shimo4228/writing/writing-ecosystem@sha256:c6a7b821c8aa59c4The line at the top of this page pins the label git:20261115.7a8a990, 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_qjkjelwytsullvyk)
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/writing-ecosystem 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 writing-ecosystem from somewhere else? Ask it: where did my writing-ecosystem 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 Nov 13, 2026 and Nov 15, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261115.7a8a990 latest | 2026-11-15 | 7a8a990 | 29,177 B | A | view · diff |
| git:20261114.761a86c | 2026-11-14 | 761a86c | 29,182 B | A | view · diff |
| git:20261114.fabd271 | 2026-11-14 | fabd271 | 29,045 B | A | view · diff |
| git:20261114.525f78f | 2026-11-14 | 525f78f | 30,339 B | A | view · diff |
| git:20261113.01f04a3 | 2026-11-13 | 01f04a3 | 28,848 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/writing-ecosystem/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 (29177 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_qjkjelwytsullvyk GET https://markdownregistry.com/api/v1/resolve?ref=shimo4228/writing/writing-ecosystem GET https://markdownregistry.com/api/v1/blob/c6a7b821c8aa59c4985e70d554c745b5737ccceb9be9f0bdb522dcd192d5c490
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.