zhihu-publisher
Skill244 starsChanged 5 days agoMITView on GitHub
Prepare or publish eunomia.dev Markdown articles on Zhihu. Use when asked to create, import, paste, publish, QA, or record a Zhihu draft or article from repository Markdown. Preserves a syndicated long-form source title and body apart from mechanical rendering fixes, with browser-editor workflow, Zhihu formatting checks, publication authorization, and media ledger updates.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- lug88866/openclaw-skillstheir own version, first seen Jul 30, 2026
- ArchAIHarness/agent-workflowstheir own version, first seen Jun 23, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ArchAIHarness/agent-workflows★ 1same name
- lug88866/openclaw-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- app/AGENTS.mdAGENTS.md
- app/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- blog-writerSkill
- blog-writing-styleSkill
- content-launch-plannerSkill
- devto-publisherSkill
- eunomia-community-radarSkill
- eunomia-content-patrolSkill
- eunomia-research-reportSkill
- eunomia-social-radarSkill
- hackernews-publisherSkill
- juejin-publisherSkill
- linkedin-publisherSkill
- lobsters-publisherSkill
- medium-publisherSkill
- reddit-publisherSkill
- seo-geoSkill
- xiaohongshu-publisherSkill
- x-publisherSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 9 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
If the source path is missing, inspect .github/publisher/posts_queue.txt, .github/publisher/media/not-published.md, and recent …
- Distinctive: line 28
Use a browser surface with the logged-in session when UI work is required.
- Distinctive: line 29
Never bypass authentication with search results or alternate sources.
- Distinctive: line 40
Do not directly access Zhihu APIs, internal endpoints, or background HTTP interfaces under any circumstances.
- Distinctive: line 49
Read the canonical Chinese source and extract title, summary, tags, images, code blocks, source URL for the ledger, GitHub links, and paper …
- Distinctive: line 52
remove YAML front matter
- Distinctive: line 61
Keep the opening, section order, claims, examples, and conclusion unchanged.
- Distinctive: line 62
If the source needs a content fix, update it first or skip syndication.
- Very specific: line 68
Before opening the Zhihu editor, write or update the Zhihu draft record under draft/media/YYYY-MM-DD/<source-slug>/zhihu.md using the local …
- Distinctive: line 83
Avoid post-paste surgical repair in the Zhihu editor.
- Very specific: line 92
Treat visible public-page DOM inspection as sufficient QA.
- Very specific: line 149
After a confirmed publish, update .github/publisher/media/published.md with title, source path, Zhihu URL, date, tags or column, and …
- Distinctive: line 153
Before closing the publishing task, run a platform-lessons pass.
- Very specific: line 157
Keep screenshots and observed UI notes under .github/publisher/media/.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Zhihu Publisher
Prepare or publish a reviewed Zhihu article from the canonical repository source. Publication authorization follows CLAUDE.md's Precedence Rule and Publishing section.
Inputs
- Source Markdown path or topic.
- Intended language and title, if the user specifies them.
- Optional target column, cover, tags, source URL, GitHub link, or paper link.
If the source path is missing, inspect .github/publisher/posts_queue.txt,
.github/publisher/media/not-published.md, and recent docs/blog/posts/
entries before asking the user.
Platform Entry Points
- Editor: https://zhuanlan.zhihu.com/write
- Creator center: https://www.zhihu.com/creator
- Observed profile: https://www.zhihu.com/people/yun-wei-64-11
Use a browser surface with the logged-in session when UI work is required. Never bypass authentication with search results or alternate sources.
References
Load references/platform-preferences.md when choosing Zhihu-native framing,
title, opening, "想法" format, or promotion/link balance. Load
references/ai-works.md for Zhihu AI Works fields, campaign notes, project
material, and reusable copy.
Browser-Only Platform Boundary
Do not directly access Zhihu APIs, internal endpoints, or background HTTP interfaces under any circumstances. All verification, drafting, QA, screenshots, and ledger evidence must come from normal browser interactions that a regular logged-in user can perform: navigating pages, scrolling profile/article lists, clicking visible controls, reading rendered page content, using the editor UI, and capturing screenshots.
Draft Preparation
- Read the canonical Chinese source and extract title, summary, tags, images, code blocks, source URL for the ledger, GitHub links, and paper links.
- Build a Zhihu copy in canonical syndication mode:
- remove YAML front matter
- preserve the article body by default
- preserve the source title and first paragraph exactly
- convert relative images to checked public URLs or prepare manual image upload
- convert tables, formulas, Mermaid, footnotes, or complex HTML only when the target editor cannot render them faithfully
- Preserve links already present in the source. A visible eunomia.dev original/canonical note is optional and is not added by default.
- Keep the opening, section order, claims, examples, and conclusion unchanged. If the source needs a content fix, update it first or skip syndication. Rewrite, translate, shorten, expand, reorder, or split only when the user explicitly asks for that specific publication.
Draft Archive
Before opening the Zhihu editor, write or update the Zhihu draft record under
draft/media/YYYY-MM-DD/<source-slug>/zhihu.md using the local date. For
unchanged Chinese canonical syndication, the file may reference the source body
instead of duplicating it, but it must record the exact title, source URL for
the ledger if known, GitHub/paper links, column/tags if known, source/project
note if useful, media choices, and QA state.
Editor Workflow
- Open https://zhuanlan.zhihu.com/write.
- Fill the title field, observed as
请输入标题(最多 100 个字). - For long-form posts, prefer a local
.mdor.docxartifact prepared before opening the editor. Use Zhihu's visible document import path when available (toolbar more/menu import); paste only for short text or when import is not available. - Avoid post-paste surgical repair in the Zhihu editor. If a long draft needs structural fixes, regenerate the local artifact and re-import into a fresh draft when practical.
- Verify visually:
- heading hierarchy is preserved
- code blocks are readable
- tables do not collapse
- images render
- links point to intended GitHub, docs, project, or paper sources
- Treat visible public-page DOM inspection as sufficient QA. If
Page.captureScreenshottimes out, do not retry it; verify the title, structure, code blocks, tables, image loading, and links through the visible DOM/page instead.
- In the publish/settings flow, choose a relevant question when Zhihu offers a question selector. Verify the selected question is topical before final publish; do not leave an unrelated default question selected.
- Set cover and column inclusion only when the user requested them or the choice is obvious from prior posts.
- Complete the visible
发布action when the task requests publication or the queue item is marked排队; do not ask for duplicate confirmation. Stop at preview only for a draft or preview task.
Content Strategy
Zhihu works best when the article reads like an explanatory essay rather than a release note. For existing Chinese long-form eunomia.dev posts, preserve the source title exactly and keep the body substantively unchanged. Platform work is limited to rendering, cover, column, tags, question selection, and preview quality. If the source is not already a usable Chinese essay, skip it or improve the source before syndication.
Optimize for the maintainer's personal technical account brand: clear taste, useful explanation, research and engineering credibility, and discussion from readers who care about eBPF systems, AI agents, and runtime observability. Keep GitHub, docs, project, or paper links as sources or extended reading. Use an eunomia.dev link only when it helps the reader, not as a default canonical requirement.
Safety Boundary
Do not automate:
- final
发布when the task is limited to a draft or preview - direct Zhihu API access, internal endpoint reads, or browser-hidden data fetches
- column submission unless the user names the exact column
- deleting drafts or changing account settings
- security, privacy, phone-verification, or CAPTCHA prompts
- likes, comments, follows, reposts, or private messages
Session Recovery
- The 知乎 login lives in the
z_c0cookie. The persistent visible profile's jar can hold anonymous identifiers (d_c0,_xsrf,_zap,__zse_ck, and the mountedSESSIONID/JOID/osd/crystal) with noz_c0, in which case bothhttps://www.zhihu.com/creatorandhttps://zhuanlan.zhihu.com/writeredirect to/signin. - Unlike Juejin, importing the mounted
/run/social-manager-session/browser-state.jsoncookies through the page-target CDPStorage.setCookiesdoes NOT recover the session when the mounted state itself carries noz_c0(verified 2026-10-30: 11 知乎 cookies imported,/creatorstill landed on/signin). Treat that result as proof the recovery needs a real user login in the visible profile — do not loop on cookie re-imports, and never solve the CAPTCHA/verification prompt automatically.
Ledger Update
After a confirmed publish, update .github/publisher/media/published.md with
title, source path, Zhihu URL, date, tags or column, and formatting fixes. Remove
or update the matching row in .github/publisher/media/not-published.md.
Before closing the publishing task, run a platform-lessons pass. Add any new, reproducible editor failure and its verified workaround to this skill or its references so the next publish does not repeat it.
Keep screenshots and observed UI notes under .github/publisher/media/.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

