skills.rest
organvm-i-theoria
organvm-i-theoriaOFFICIAL
Explore all skills by this author →
GitHub

posse-distribution-architecture

Implement POSSE content syndication with canonical URLs, platform adapters, and retry queues.

Updated May 16, 2026
Search Tags:#syndication#content distribution#cross-platform publishing#canonical url#indieweb#posse#backfeed
One-click install
npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill posse-distribution-architecture-organvm-i-theoria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: posse-distribution-architecture
Source: https://github.com/organvm-i-theoria/_agent-ontology/tree/main/.agents/skills/posse-distribution-architecture
Command: npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill posse-distribution-architecture-organvm-i-theoria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing content across multiple platforms manually is error-prone, and platform-first publishing risks losing your canonical archive when platforms change or shut down. This Skill provides a complete architecture for publishing on your own site first and syndicating copies everywhere else. ## Core Features & Use Cases - Canonical-First Distribution: Publish content on your own site as the single source of truth, then syndicate adapted copies to Bluesky, Dev.to, newsletters, and other platforms with links back to the canonical URL. - Resilient Delivery: Per-platform circuit breakers, exponential-backoff retry queues, and status tracking (pending, published, failed, retrying) handle rate limits and platform outages. - Backfeed Collection: Aggregate likes, reposts, and comments from syndicated copies back into a syndication manifest that enriches the canonical record. - Use Case: You publish a long-form essay on your blog and want it automatically adapted and posted to Bluesky (300-char limit), Dev.to (full markdown with canonical_url), and your email newsletter, with failures retried and engagement metrics collected overnight. ## Quick Start Ask the AI to design a POSSE distribution pipeline that publishes my blog posts to Bluesky, Dev.to, and a newsletter with retry handling and a syndication manifest.

Frequently Asked Questions about posse-distribution-architecture

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

FAQPage Schema
How do I implement POSSE content syndication across multiple platforms?▼

Publish content on your own site first to establish the canonical URL, then use platform adapters to adapt and publish copies to each target. Each syndicated copy links back to the canonical URL, and statuses are tracked per platform.

What is the difference between POSSE and platform-first publishing?▼

POSSE publishes on your own site first, making your URL canonical and preserving your archive if platforms change. Platform-first publishing gives the platform ownership of the original, risking content loss and splitting SEO value.

How do I handle rate limits and platform outages when syndicating content?▼

Use a retry queue with exponential backoff for rate-limited requests and a per-platform circuit breaker that opens after repeated failures. Failed syndications are requeued up to a maximum attempt count before being abandoned and logged.

Should syndicated content be identical on every platform?▼

No, content should be adapted per platform. For example, Bluesky posts are truncated to 300 characters with a link, Dev.to receives full markdown with a canonical_url field, and newsletters use an HTML email template.

What is backfeed in POSSE and how is it collected?▼

Backfeed is engagement data (likes, reposts, comments) from syndicated copies collected back to the canonical record. Adapters query each platform's metrics for the syndication URL, and results are aggregated into the syndication manifest on a best-effort basis.

Related Skills

Explore More Content & Communication Skills→
HeadyAIHeadyAI
1

heady-cms

Publish and synchronize content across Heady CMS sites via MCP tools.

Official
Advanced
Veloxia-agencyVeloxia-agency

social-media-analyzer

Analyze social media campaign metrics for engagement, reach, CTR, and ROI.

Community
Advanced
RogerGimbelRogerGimbel

late-api

Integrate with the Late API to manage posts across 13 platforms.

Community
Advanced
lapc506lapc506
4

Platform Channels & Native Integration

Facilitate bidirectional Flutter-native communication via MethodChannel, EventChannel, and FFI.

Community
Advanced