blog-content-publish

What This Skill Does

The blog-content-publish skill serves as the primary interface for publishing content to editorial and dynamic blog sections using the @leeguoo/blog-publish package. It acts as an orchestrator for ensuring high-quality, source-grounded, and bilingual-compliant content distribution. The skill enforces rigid quality gates for dynamic sections (hot, news, and ai_news), ensuring that every entry provides consistent depth, verifiable evidence, and actionable insights. It also handles the synchronization of repository skills to ClawHub, keeping your local environment in sync with global project standards.

Installation

To integrate this skill into your environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/leeguooooo/blog-content-publish

Use Cases

• Editorial Publishing: Easily publish standard blog posts and editorial content with metadata support.
• Dynamic Briefs: Automatically generate structured, bilingual-paired news or tech trend updates that maintain high information density.
• Repository Syncing: Execute batch updates across the ClawHub infrastructure using the clawhub sync --all command.
• Quality Enforcement: Ensure all published content meets strict standards regarding source grounding, evidence anchors, and forbidden language patterns.

Example Prompts

1. "Publish this editorial post to the blog with the slug 'q3-updates', title 'Quarterly Growth Report', and my markdown content."
2. "Create a dynamic news brief for 'ai_news' with pairId 'ai-summit-2024'. Ensure the zh and en versions are ready for publication with 5 topics each."
3. "Synchronize all repository skills to the latest versions on ClawHub."

Tips & Limitations

• Evidence Anchors: Always provide concrete links to PRs, issues, or official documentation. General homepage links are rejected by the quality gate.
• Bilingual Parity: When publishing dynamic content, ensure your zh and en versions share the same pairId. Failure to match topic counts or risk interpretations across languages will result in a blocked publication.
• Producer Privacy: Never include internal identity or placeholder text. The system automatically scrubs internal producer labels to ensure a professional, clean public output.
• Topic Depth: Aim for 4-8 topics per dynamic brief. Avoid shallow entries (1-2 topics) as the system is designed to favor comprehensive, multi-angle summaries.