Start locally from confirmed facts and supplied sources without a Threadify account. Honor an existing connection choice. Offer a connection only when an available hosted capability would help; explain the benefit and obtain approval for the exact provider action.
Installs into .claude/skills of the current project.
Are you the author of Threadify Crosspost X After Threads?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lennoxsaint-threadify-crosspost-x-after-threads)
# Threadify Crosspost X After Threads
## Start here
Start locally from confirmed facts and supplied sources without a Threadify account. Honor an existing connection choice. Offer a connection only when an available hosted capability would help; explain the benefit and obtain approval for the exact provider action.
Follow [Threadify-001: setup and first-loop video](https://github.com/lennoxsaint/Threadify-workflows/blob/main/docs/threadify-001.md) before provider calls. Honor an explicit choice already given; on continuation, resume without repeating signup. Setup never grants publishing or payment authority.
Use when a user has already scheduled or published through Threadify and wants
an X-ready follow-up artifact.
## Instructions
1. Read `workflows/crosspost-x-after-threads/manifest.json`.
2. Confirm Threads schedule/publish status using only listed MCP tools.
3. Prepare an X-ready artifact and ask whether the user wants to publish or
schedule to X if live X tools are available in the future.
4. If X tools are unavailable, mark fallback clearly.
5. Do not claim X posting happened unless Threadify exposes and confirms a live
X provider action.
Use approved clean context or verified Brain memory only. Do not consume raw
Current Self packets.
