一键在 Manus 中运行任何 Skill

blog-publisher

星标71

分支4

更新时间2026年3月27日 03:32

Write blog posts for the Pareto documentation site and create external platform versions for 掘金 (Juejin), Medium, and Dev.to. Handles bilingual content (English + Chinese), updates the blog listing pages, verifies internal links, and builds to confirm. Use when the user says "write a blog post", "发布文章", "写博客", "new blog post", "publish article", "blog about X", or wants to announce a feature/release. Also use when the user asks to prepare content for external platforms like Juejin, Medium, or Dev.to.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

childrentime

childrentime/pareto

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Blog Publisher

Write blog posts for the Pareto website and prepare versions for external publishing platforms.

Context

The Pareto documentation site uses Astro + Starlight. Blog posts live in the docs content collection but use template: splash to render without the documentation sidebar. The site is bilingual (English + Chinese). External platform versions strip internal links and add canonical URLs.

File Locations

website/src/content/docs/blog/          # English blog posts
website/src/content/docs/blog/index.mdx # English blog listing
website/src/content/docs/zh/blog/       # Chinese blog posts
website/src/content/docs/zh/blog/index.mdx # Chinese blog listing
blog-external/                           # External platform versions

Workflow

1. Write the blog post

Create the English version first at website/src/content/docs/blog/<slug>.md:

---
title: Post Title
description: One-line description for SEO and social sharing.
template: splash
---

Post content here...

Key points:

Always use template: splash — this removes the docs sidebar from blog pages
Write in the Pareto brand voice: precise, confident, technical but approachable
Include code examples inline — they make the content more concrete and AI-citable
Use tables for feature comparisons and convention file listings
End with a clear call-to-action (try it, install it, read more)

2. Write the Chinese translation

Create at website/src/content/docs/zh/blog/<slug>.md with the same frontmatter structure. Translate naturally — don't transliterate. Technical terms (Vite, React, SSR, loader) stay in English. Code examples stay identical. Only translate prose and UI strings in code comments.

3. Update blog listing pages

Add an entry to BOTH listing pages (blog/index.mdx and zh/blog/index.mdx).

English entry format:

<article class="blog-entry">

### [Post Title](/blog/<slug>/)

One-line description matching the frontmatter description.

<span class="blog-date">Month Day, Year</span>

</article>

Chinese entry format — same structure, translated text, link path prefixed with /zh/.

Add new entries at the TOP of the <div class="blog-list"> block (newest first).

4. Create external platform versions

Create two files in blog-external/:

<slug>-medium-devto.md — For Medium and Dev.to:

Start with # Title (H1 heading, no frontmatter)
Add a TL;DR block at the top (1-2 sentences + install command)
Replace ALL internal doc links (like [API reference](/api/core/)) with full URLs (https://paretojs.dev/api/core/)
End with a Links section: GitHub, Docs, Full post URL
End with a line encouraging GitHub stars

<slug>-juejin.md — For 掘金:

Same structure as Medium version but in Chinese
Technical terms stay in English
Links section uses Chinese labels (GitHub, 文档, 完整发布说明)

5. Verify links

Scan all new and modified .md/.mdx files for internal links. For each link like (/concepts/routing/), verify the target file exists:

/concepts/routing/ → website/src/content/docs/concepts/routing.md
/zh/concepts/routing/ → website/src/content/docs/zh/concepts/routing.md
/blog/<slug>/ → website/src/content/docs/blog/<slug>.md

Report any broken links before proceeding.

6. Build and verify

Run npx astro build in the website directory. The build must complete with no errors. Check that the page count increased (new blog pages should appear in the build output).

Writing Guidelines

Blog post structure

For release announcements:

Opening paragraph — what changed and why it matters
Major changes — one H2 section per feature, with code examples
Migration guide — numbered steps for upgrading
Call to action — npx create-pareto@latest or link to docs

For technical deep-dives:

Problem statement — what pain point this addresses
How it works — with progressive code examples
When to use / when not to use — practical guidance
Related concepts — links to relevant docs

Code examples

Always include the file path as a comment: // app/dashboard/loader.ts
Use TypeScript with proper type imports
Keep examples minimal — show the pattern, not a full app
For pareto.config.ts examples, always include the full file structure with imports and export default

SEO considerations

Title should include the primary keyword naturally
Description should be actionable (not just descriptive)
Include a comparison table if comparing with other tools
Add links to relevant documentation pages (cross-linking helps SEO)

External platform differences

Medium/Dev.to readers may not know Pareto. Add 1-2 sentences of context at the top explaining what Pareto is before diving into what changed.

掘金 readers are familiar with the Chinese frontend ecosystem. You can reference Next.js, Remix, Vite directly without explanation, but briefly explain what Pareto is.

同仓库更多 Skills

同仓库

pareto-seo-blog

childrentime/pareto

Write a new Pareto blog post targeting a specific long-tail SEO keyword and prepare its three external-platform copies (Medium, dev.to, 掘金). Use when the user says "写一篇博客", "写一篇 SEO 博客", "针对 X 关键词写博客", "新增一篇博客", "create a new pareto blog post", "publish a new blog post", "write SEO content", or names a slug from blog-external/SEO-KEYWORDS.md and asks to draft it. Generates the bilingual website canonical post (EN + ZH), updates both blog index pages, and produces medium.md / devto.md / juejin.md ready to publish through the existing flow (curl for dev.to, /medium-push, manual copy for 掘金).

2026-05-0671

medium-push

childrentime/pareto

将 Markdown 文件推送到浏览器中打开的 Medium 编辑器。当用户说"发布到 medium"、"推送到 medium"、"paste to medium"、"push to medium"或在完成文章生成后要求发送到 Medium 时触发。

2026-03-2971

content-strategy

childrentime/pareto

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.

2026-03-2671

email-sequence

childrentime/pareto

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

2026-03-2671

free-tool-strategy

childrentime/pareto

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

2026-03-2671

lead-magnets

childrentime/pareto

When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tool-strategy. For writing the actual content, see copywriting. For the email sequence after capture, see email-sequence.

2026-03-2671

name

blog-publisher

description

Blog Publisher

Write blog posts for the Pareto website and prepare versions for external publishing platforms.

Context

File Locations

website/src/content/docs/blog/          # English blog posts
website/src/content/docs/blog/index.mdx # English blog listing
website/src/content/docs/zh/blog/       # Chinese blog posts
website/src/content/docs/zh/blog/index.mdx # Chinese blog listing
blog-external/                           # External platform versions

Workflow

1. Write the blog post

Create the English version first at website/src/content/docs/blog/<slug>.md:

---
title: Post Title
description: One-line description for SEO and social sharing.
template: splash
---

Post content here...

Key points:

Always use template: splash — this removes the docs sidebar from blog pages
Write in the Pareto brand voice: precise, confident, technical but approachable
Include code examples inline — they make the content more concrete and AI-citable
Use tables for feature comparisons and convention file listings
End with a clear call-to-action (try it, install it, read more)

2. Write the Chinese translation

3. Update blog listing pages

Add an entry to BOTH listing pages (blog/index.mdx and zh/blog/index.mdx).

English entry format:

<article class="blog-entry">

### [Post Title](/blog/<slug>/)

One-line description matching the frontmatter description.

<span class="blog-date">Month Day, Year</span>

</article>

Chinese entry format — same structure, translated text, link path prefixed with /zh/.

Add new entries at the TOP of the <div class="blog-list"> block (newest first).

4. Create external platform versions

Create two files in blog-external/:

<slug>-medium-devto.md — For Medium and Dev.to:

Start with # Title (H1 heading, no frontmatter)
Add a TL;DR block at the top (1-2 sentences + install command)
Replace ALL internal doc links (like [API reference](/api/core/)) with full URLs (https://paretojs.dev/api/core/)
End with a Links section: GitHub, Docs, Full post URL
End with a line encouraging GitHub stars

<slug>-juejin.md — For 掘金:

Same structure as Medium version but in Chinese
Technical terms stay in English
Links section uses Chinese labels (GitHub, 文档, 完整发布说明)

5. Verify links

Scan all new and modified .md/.mdx files for internal links. For each link like (/concepts/routing/), verify the target file exists:

/concepts/routing/ → website/src/content/docs/concepts/routing.md
/zh/concepts/routing/ → website/src/content/docs/zh/concepts/routing.md
/blog/<slug>/ → website/src/content/docs/blog/<slug>.md

Report any broken links before proceeding.

6. Build and verify

Run npx astro build in the website directory. The build must complete with no errors. Check that the page count increased (new blog pages should appear in the build output).

Writing Guidelines

Blog post structure

For release announcements:

Opening paragraph — what changed and why it matters
Major changes — one H2 section per feature, with code examples
Migration guide — numbered steps for upgrading
Call to action — npx create-pareto@latest or link to docs

For technical deep-dives:

Problem statement — what pain point this addresses
How it works — with progressive code examples
When to use / when not to use — practical guidance
Related concepts — links to relevant docs

Code examples

Always include the file path as a comment: // app/dashboard/loader.ts
Use TypeScript with proper type imports
Keep examples minimal — show the pattern, not a full app
For pareto.config.ts examples, always include the full file structure with imports and export default

SEO considerations

Title should include the primary keyword naturally
Description should be actionable (not just descriptive)
Include a comparison table if comparing with other tools
Add links to relevant documentation pages (cross-linking helps SEO)

External platform differences

Medium/Dev.to readers may not know Pareto. Add 1-2 sentences of context at the top explaining what Pareto is before diving into what changed.

掘金 readers are familiar with the Chinese frontend ecosystem. You can reference Next.js, Remix, Vite directly without explanation, but briefly explain what Pareto is.