- Home
- Skills
- Workflow Automation
- multi platform post scheduler
Works with the AI Agents you already use
multi platform post scheduler
Maintain and extend a Python Playwright scheduler for X, LinkedIn, Bluesky, and Meta platforms.
$8
/moSubscription · cancel anytime
Secure checkout via Stripe
- Always the latest version
- Delivered live to your agent via MCP
- Cancel anytime, access ends at period end
multi platform post scheduler
Example session with this skill installed
Fix the X adapter to handle a new selector for the post button and update the project notes.
- Read your context and instructions
- Compiled the multi platform post
- Generated the data export
I have updated x_adapter.py to reflect the new selector for the post button and synchronized the verification details in project_notes.md.
X Adapter Update
The selector for the final schedule button in x_adapter.py has been updated from [data-testid="tweetButton"] to [data-testid="SideNav_NewTweet_Button"] based on the latest DOM inspection. The project_notes.md now records this verified flow.
# x_adapter.py
def schedule_post(page, post_data):
# ... navigation logic ...
# Updated selector for the final schedule click
schedule_button_selector = '[data-testid="SideNav_NewTweet_Button"]'
try:
page.wait_for_selector(schedule_button_selector, timeout=5000)
if not dry_run:
page.click(schedule_button_selector)
return "posted"
else:
print(f"[Dry Run] Would have clicked {schedule_button_selector}")
return "pending"
except Exception as e:
print(f"Error finding X schedule button: {e}")
return "error"
| File | Change Type | Description |
|---|---|---|
x_adapter.py | Bug Fix | Updated CSS selector for the schedule button. |
project_notes.md | Documentation | Added timestamped entry for verified X browser flow. |
main.py | Verification | Confirmed routing to x_adapter remains intact. |
Next steps
- Run
python -m py_compile x_adapter.pyto verify the syntax. - Execute the scheduler with
--dry-runto confirm the element is found without posting. - Review
posts.csvto ensure the status field is correctly updated after the run.
posts.csv
CSV · data export
Example file from a real run - the skill writes it into your workspace.
Subscription · always the latest version
- Secure checkout via Stripe
- Cancel anytime
- Delivered live via MCP
About this skill
Managing social media across multiple platforms often results in brittle automation scripts and broken browser selectors. This skill maintains a Python-based scheduler that coordinates posts to X, LinkedIn, Bluesky, Facebook, and Instagram via a CSV-driven workflow.
What it does
- Platform adapters manages browser automation logic for X, LinkedIn, Bluesky, Facebook, and Instagram.
- CSV orchestration processes posts based on platform, datetime, caption, and status fields.
- Image handling selects and persists media state across sessions, supporting platform-specific rules like LinkedIn multi-image posts.
- Meta integration utilizes the Meta Graph API and Business Suite for Facebook and Instagram publishing.
- State persistence tracks posted and pending rows to prevent duplicate content delivery.
How it works
- Analyze adapters by reviewing platform-specific files like
x_adapter.pyorlinkedin_adapter.pyfor current selector logic. - Review CSV contract to ensure
statusandimage_pathfields correctly trigger or skip rows. - Validate code using
py_compileto ensure Python changes are syntactically correct before deployment. - Update documentation by syncing
project_notes.mdwith any verified browser flow or selector changes.
Frameworks & tools
The project is built with Python and utilizes Playwright for browser automation. It integrates with the Meta Graph API and handles local filesystem state via CSV and JSON.
Why this beats prompting it yourself
Generic prompts often ignore the specific "dry-run" behaviors that differ between X and LinkedIn, leading to accidental live posts. This skill understands the unique CSV contract and image-selection persistence required to keep a multi-platform scheduler running without manual intervention.
Use cases
- Debug failing browser selectors on X or LinkedIn.
- Extend the
stub_adapters.pyto implement new platforms like Threads. - Refactor the image picker logic to support new media formats.
- Modify the CSV processing loop in
main.pyto add custom scheduling logic.
Known limitations
Does not include a dedicated test suite. Threads is currently only a stub. LinkedIn dry-run behavior still clicks the final schedule button.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.
No built-in test suite; relies on py_compile. Threads is a stub. LinkedIn dry-run does not prevent scheduling. Requires manual selector updates when social platforms change their UI.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 1 day ago
- Accounts
Facebook
- Software
Python
Git
Permissions
Allowed Hosts