Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
zenn
Publish Zenn articles by managing Markdown in a GitHub-connected repository (push/PR -> merge) and previewing with Zenn CLI.
skill openclawclawhub Free
Publish Zenn articles by managing Markdown in a GitHub-connected repository (push/PR -> merge) and previewing with Zenn CLI.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.0.1
Provenance
- Publisher
- tachi-koma-x
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Overview
Zenn publishes by syncing a GitHub repository. Articles/books are Markdown files placed in specific directories, and Zenn CLI helps you preview and scaffold content locally. This skill defines an operational workflow that is both fast and safe: Draft in PRs (published: false) Review with local preview (zenn preview) Publish by flipping published: true once the PR is ready
Inputs to collect
Repo path (local clone) and GitHub remote Publishing branch (the branch connected to Zenn) Article metadata: title, emoji, type (tech or idea), topics, published Slug / filename for the Markdown file (kebab-case recommended) Assets (images) location strategy (recommended: images/<slug>/...)
File placement rules (Zenn)
Articles must be placed under articles/ as individual .md files. (Optional) Books are placed under books/. Recommended repo layout: . โโ articles/ โ โโ 20260216-openclaw-to-zenn.md โโ books/ # optional โโ images/ # optional, recommended โโ openclaw-to-zenn/ โโ cover.png โโ diagram.png
Install / init (one-time per repo)
If Zenn CLI is not set up yet in the repo: npm init --yes npm install zenn-cli npx zenn init
Preview locally
npx zenn preview
Create new content
npx zenn new:article npx zenn new:book
List existing content
npx zenn list:articles npx zenn list:books
Article template (copy/paste)
- Create articles/<slug>.md:
- ---
- title: "่จไบใฟใคใใซ"
- emoji: "๐งฉ"
- type: "tech" # tech or idea
- topics: ["ruby", "rails", "ai"]
- published: false
- ---
- ## TL;DR
- ...
- ...
- ...
- ## ่ๆฏ
- ...
- ## ๅฎ่ฃ / ๆค่จผ
- ...
- ## ๅญฆใณ
- ...
- ## ๅ่
- ...
- Notes:
- Title is in front matter, so body headings should generally start at ##.
- Keep topics to a small, consistent set for series-building.
1) Draft in a feature branch
Create or edit articles/<slug>.md (keep published: false) Add images (if any) under images/<slug>/... Preview locally: npx zenn preview
2) Open a PR
git checkout -b article/<slug> git add articles/<slug>.md images/<slug>/ git commit -m "Add draft: <title>" git push -u origin article/<slug> Open a PR into the Zenn publishing branch.
3) Publish safely
Option A (safest): publish in a second tiny PR/commit Merge the draft PR (still published: false) Flip to published: true and merge a small PR Option B (fast): publish in the same PR Keep published: false during writing/review Flip to true right before merging
Quality gate checklist (minimum)
Before setting published: true, verify: No confidential info (customer names, internal URLs, unreleased metrics) Code blocks are runnable or clearly labeled as pseudo-code Images render and paths are correct Links are correct Spelling / headings / formatting are acceptable
Troubleshooting
Preview differs from Zenn web or CLI shows update notice: npm install zenn-cli@latest Images not showing: Ensure they are committed and pushed Ensure references look like /images/<slug>/... (not ./images/...) Article not appearing: File is under articles/ published: true The branch synced to Zenn is the one being updated
When does this not work?
Skipping PR review (direct publish) increases risk of accidental leaks. Relying on UI/browser automation instead of GitHub sync is brittle to UI changes. Mixing multiple articles in one file or placing files outside articles/ will not publish as expected.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md