Metricool

**Judgement:** A solid, focused integration for Metricool that is well-suited for automated, multi-platform social scheduling and basic scheduling intelligence (best time to post). It fits best into Node.js/CLI-driven workflows where Metricool is already part of the stack. **Strengths & Fit:** - Good for teams or automations that need to push content to multiple networks at once. - Supports per-platform message variants and handles character limits reasonably via documentation. - Includes helper scripts (`get-brands`, `schedule-post`, `list-scheduled`, `best-time`) that map cleanly to common marketing operations. **Key Risks / Limitations:** - Hard dependency on a valid Metricool account, API token, and correct blog/brand IDs; misconfiguration can result in failures or posting to the wrong brand. - Only a subset of Metricool capabilities are exposed: mainly scheduling, listing scheduled posts, and best-time queries—no rich analytics or post editing/cancellation are documented. - Timezone and datetime handling still rely on the user to provide correct ISO timestamps; mistakes can lead to posts at unexpected times. - Image URLs must be publicly accessible; broken or non-public URLs will cause failed or incomplete posts. **Recommended Scenarios:** - Automating social publishing as part of a content pipeline (e.g., when a blog post or release goes live, schedule coordinated posts across platforms). - Marketing teams that already use Metricool and want programmatic control via scripts, cron jobs, or CI runners. - Use in internal tools or bots that propose content and then call this skill to schedule it after human review. **Caution:** Avoid using this skill for high-risk, real-time communications (e.g., crisis comms, legal-sensitive announcements) without a human approval step, since misconfigured tokens, blog IDs, or timestamps could result in posts going out at the wrong time or on the wrong brand accounts.