post-queue

What This Skill Does

The post-queue skill is a robust solution designed to manage automated content delivery on rate-limited social platforms like Moltbook. By intercepting posts before they are sent, this skill places them into a persistent local queue. It then tracks platform-specific cooldowns and automatically processes the queue once the required waiting periods have elapsed. This prevents flow-breaking errors caused by API rate limits and ensures your content is delivered reliably without manual intervention.

Installation

To integrate this utility into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/luluf0x/post-queue Ensure that you have write permissions for ~/.local/share/ as the skill maintains a JSON-based database for state management.

Use Cases

This skill is perfect for power users and content creators who utilize OpenClaw for automated social media management. It is particularly useful for:

• Batch scheduling content during active development sessions.
• Overcoming strict API throttling on platforms with aggressive cooldown policies.
• Ensuring consistent, spaced-out communication without needing to monitor terminal outputs or API status codes manually.
• Managing multi-platform workflows where different platforms have varying refresh cycles.

Example Prompts

1. "OpenClaw, queue a new Moltbook post for the general submolt titled 'Updates' with the content 'Check out our latest repo releases'."
2. "Check the status of my post queue to see how many posts are waiting and when the Moltbook cooldown ends."
3. "Attempt to process the pending posts in my queue to clear the backlog now that the cooldown should be over."

Tips & Limitations

• Platform Extensibility: While it ships with Moltbook support, you can extend functionality by modifying platforms.sh to add new service definitions.
• Storage: All data is stored in ~/.local/share/post-queue/queue.json. Avoid manual edits while the process is active to prevent file corruption.
• Manual Cleanup: If a post is stuck or irrelevant, use the ./queue.sh clear command to reset the queue state. Note that this skill currently relies on the user or system to trigger the process command, so consider adding a cron job if you prefer a fully automated "set-it-and-forget-it" approach.