add-composer-platform

Coordinate state, placement, and messaging changes when adding a social platform to the composer.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/promobase/openpromo --skill add-composer-platform
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-composer-platform
Source: https://github.com/promobase/openpromo/tree/main/.claude/skills/add-composer-platform
Command: npx skills add https://github.com/promobase/openpromo --skill add-composer-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The composer currently lacks a standardized, repeatable process for introducing new social platforms. This skill provides a structured checklist to ensure all required code areas and messaging are consistently updated when integrating a platform.

Core Features & Use Cases

  • Unified integration checklist: coordinates changes across initial state, placement registries, and platform-specific messaging.
  • Cross-file consistency: ensures type unions, default specs, and registry updates stay in sync when a new platform is added.
  • Use Case: when adding a platform like LinkedIn or Mastodon, the skill guides the exact files and handlers to modify to support placements, messages, and attachments.

Quick Start

Update the composer by implementing the required state, placement, and messaging changes as outlined in the checklist.

Frequently Asked Questions about add-composer-platform

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

FAQPage Schema
How do I add a new social media platform to a shared composer engine?

Adding a new social media platform to a composer requires coordinating changes across initial state, placement registries, and platform-specific messaging handlers. This ensures the UI and data layers correctly process platform placements and messages.

What files need to be updated when integrating a new platform into the composer?

Integrating a new platform requires updating initial state configurations, placement specs, and platform-specific message handlers. You must also update type unions and default specs to maintain type safety and cross-file consistency.

Why do platform-specific message fields break when adding a new social media platform?

Platform-specific message fields break when type unions and registry updates fall out of sync during integration. Maintaining consistent messaging across platforms requires coordinating state and placement changes across all affected files.

Does adding a platform to the composer require updating placement registries?

Yes, adding a platform requires updating placement registries to wire the new platform into the shared composer engine. Placement specs must be defined alongside initial state and messaging handlers to support the new platform.

Can I use a checklist to wire a platform like LinkedIn or Mastodon into the composer?

Yes, a structured integration checklist guides engineers through the exact files and handlers to modify when adding platforms like LinkedIn or Mastodon. It coordinates state, placement, and messaging changes to ensure consistent integration.