openclaw-content-ops

Coordinate image hosting, blog publishing, and Blinko writing via a centralized dispatcher.

1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/tangchunwu/skill-hub --skill openclaw-content-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-content-ops
Source: https://github.com/tangchunwu/skill-hub/tree/main/skills/custom/content/openclaw-content-ops
Command: npx skills add https://github.com/tangchunwu/skill-hub --skill openclaw-content-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw Content Ops coordinates three existing capabilities to streamline content workflows: uploading images to an image bed, publishing blog posts, and writing to Blinko.

Core Features & Use Cases

  • Unified orchestration across image hosting, blog publishing, and Blinko writing.
  • Reuse of existing subsystems by delegating tasks to the corresponding skills (openclaw-image-bed-uploader, openclaw-personal-blog-publisher, openclaw-blinko-writer).
  • Use Case: Upload images to the image bed, assemble a blog post JSON, publish the post, and optionally push content to Blinko for further organization.

Quick Start

Coordinate content by uploading images to the image bed, compiling a blog post, and publishing it to your personal blog, while routing content to Blinko when needed.

Frequently Asked Questions about openclaw-content-ops

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

FAQPage Schema
How do I coordinate image hosting and blog publishing in a single workflow?

Content ops orchestration unifies image hosting, blog publishing, and Blinko writing by delegating tasks to corresponding sub-skills through a centralized dispatcher that enforces handoffs and reports status.

How do I upload images to an image bed and publish a blog post end to end?

To publish a blog post end to end, upload images to the image bed, compile the blog post JSON, and publish it through the orchestrator which delegates to the image hosting and blog publishing sub-skills.

Can I use this content workflow orchestration in both Codex and Claude environments?

Yes, the content operations dispatcher applies across both Codex and Claude environments, allowing you to route items to Blinko for task tracking and coordinate content workflows seamlessly.

What is the best way to route content to Blinko for task tracking after publishing a blog?

Use the centralized dispatcher to optionally push published blog content to Blinko for task tracking, ensuring content is organized and handoffs are clearly enforced across the workflow.

Does this content ops dispatcher require separate sub-skills for image hosting and publishing?

Yes, the dispatcher reuses existing subsystems by delegating tasks to corresponding sub-skills for image hosting, blog publishing, and Blinko writing rather than implementing those features natively.