repost-global-dedupe

Maintain a centralized JSONL ledger to prevent duplicate cross-platform reposts.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/EthanSK/Repost-with-agent --skill repost-global-dedupe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repost-global-dedupe
Source: https://github.com/EthanSK/Repost-with-agent/tree/main/skills/repost-global-dedupe
Command: npx skills add https://github.com/EthanSK/Repost-with-agent --skill repost-global-dedupe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It prevents duplicate content from being posted across multiple platforms by maintaining a global content ledger, reducing redundancy and ensuring content uniqueness.

Core Features & Use Cases

  • Cross-pair Deduplication: Tracks content to ensure the same item isn't reposted on different platform pairs, avoiding double-posting.
  • Global State Management: Uses a centralized JSONL state file for tracking posted content and duplicates.
  • Use Case: When reposting the same article from LinkedIn to X and Bluesky, this Skill identifies duplicates and skips redundant posts, saving time and maintaining content integrity.

Quick Start

Use the repost-global-dedupe skill to check for existing content before posting a new item across platforms.

Frequently Asked Questions about repost-global-dedupe

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

FAQPage Schema
How do I prevent duplicate content when reposting across multiple social media platforms?

Preventing duplicate content during cross-platform reposting requires a global deduplication system that maintains a centralized ledger, associating content keys with platform-specific posts to track lineages and skip redundant posts automatically.

What is the best way to track content state for social media automation workflows with multiple content hops?

Tracking content state across multiple content hops is best handled via centralized JSONL global state management, which records posted items and their duplicates to maintain cross-pair deduplication and ensure content uniqueness.

How does cross-pair deduplication work for articles reposted between LinkedIn, X, and Bluesky?

Cross-pair deduplication works by inheriting lineage from previous posts and checking a centralized ledger before posting, so when reposting from LinkedIn to X and Bluesky, the system identifies duplicates and skips redundant posts to maintain content integrity.

Do I need any external dependencies to set up a global content ledger for platform integration?

No external dependencies are required to set up a global content ledger for platform integration, as the deduplication system operates independently using centralized JSONL state files and scripts to manage content keys and track duplicates.

Why does the same post keep appearing on different platform pairs during automated social media reposting?

The same post keeps appearing during automated social media reposting because a global content ledger is missing or not checking content keys, causing the system to fail at inheriting lineage from previous posts and allowing duplicate posts to slip through.