article-bilingual-translation-publisher

Translate Chinese articles into English Markdown and write bilingual summaries back to LanceDB.

2|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/zero-yx/static_flow --skill article-bilingual-translation-publisher-zero-yx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: article-bilingual-translation-publisher
Source: https://github.com/zero-yx/static_flow/tree/main/skills/article-bilingual-translation-publisher
Command: npx skills add https://github.com/zero-yx/static_flow --skill article-bilingual-translation-publisher-zero-yx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Publishing bilingual content requires translating full Chinese articles into render-safe English Markdown and regenerating structured summaries, then persisting both to the LanceDB articles table without corrupting unrelated fields or breaking Markdown structure. ## Core Features & Use Cases - Whole-article English translation: Generates content_en in one coherent LLM-native pass while preserving headings, code fences, tables, links, and formulas. - Bilingual detailed summaries: Produces aligned detailed_summary.zh/en following the article-summary-architect structure (opening sentence, 3-5 sections, concise bullets). - Safe LanceDB write-back: Updates only articles.content_en and articles.detailed_summary via sf-cli update-article-bilingual, with backups, structure validation, and rollback support. - Use Case: Given an article id, fetch the Chinese source from LanceDB, translate it, regenerate both summaries, validate table and code-fence parity, and write the results back with a full backup trail under tmp/article_translate/. ## Quick Start Translate article with id 42 into English, regenerate its bilingual detailed summaries, and write the results back to LanceDB using sf-cli.

Frequently Asked Questions about article-bilingual-translation-publisher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate a Chinese article to English and store it in LanceDB?▼

Provide the article id or Markdown file path, generate the English translation and bilingual summaries in one pass, then run sf-cli db update-article-bilingual with the content and summary files. Only articles.content_en and articles.detailed_summary are updated.

How are bilingual detailed summaries generated for articles?▼

Summaries follow the article-summary-architect method: classify the article type first, then produce an opening sentence, 3-5 sections, and 2-4 bullets per section in both Chinese and English. Raw table markdown must not appear inside summary bullets.

Does the translation preserve Markdown tables and code blocks?▼

Yes, the workflow validates that fenced code block counts, table block counts and column shapes, and link or image URLs match between source and translation before any write-back occurs. Code logic stays unchanged while comments may be translated.

What happens if the LanceDB write-back fails or quality is poor?▼

If structure checks fail, nothing is written. If write-back fails, tmp artifacts and reproducible commands are kept, and unsatisfactory results can be rolled back from the row backup stored under tmp/article_translate/<article_id>/.

Which fields in the LanceDB articles table get updated?▼

Only articles.content_en and articles.detailed_summary (a JSON object with zh and en keys) are overwritten. Fields such as title, content, tags, category, and date are never mutated.