threads-context

Loads, validates, and updates Threads post context to prevent duplicate topics and conflicts.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/zdpk/skills --skill threads-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: threads-context
Source: https://github.com/zdpk/skills/tree/main/dotfiles/skills/custom/threads/threads-context
Command: npx skills add https://github.com/zdpk/skills --skill threads-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before writing posts for Threads, load the account context, verify consistency across posts and stances, and update the archive to prevent duplicates and conflicts.

Core Features & Use Cases

  • Load account context (profile, posts, stances, topics history)
  • Validate consistency and detect potential conflicts before drafting
  • Update posts archive after publishing to reflect new topics and stances
  • Produce a structured context summary for drafting

Quick Start

Load the account context with threads-context load <account-id> to prepare a consistent drafting base.

Frequently Asked Questions about threads-context

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

FAQPage Schema
How do I prevent duplicate topics and stance conflicts before drafting Threads posts?

You can prevent duplicate topics by loading and validating account context before drafting. This process parses profile, posts, stances, and topics-history data to detect conflicts and output a structured summary.

How do I update my Threads post archive after publishing new content?

Update your posts archive after publishing by applying context validation to harmonize new topics and stances. This reflects recent posts in your topics-history and stances data to maintain consistency across multiple accounts.

What is the best way to maintain posting consistency across multiple Threads accounts?

Maintain posting consistency across multiple Threads accounts by loading and validating context data for each account before drafting. This checks profile metadata and topics-history files to prevent stance conflicts and ensure alignment.

Do I need specific data files to validate Threads context before drafting?

Yes, validating Threads context requires access to threads-account data. The process parses profile.yaml, posts metadata, stances.yaml, and topics-history.yaml files to verify consistency and produce a structured drafting summary.

Can I use automation to archive and harmonize Threads topics and stances after posting?

Yes, you can automate archiving and harmonizing Threads topics and stances after posting. The context update process applies after publishing to reflect new topics and stances in history files across multiple accounts.