riverside-short-social-schedule
Skill1 starsChanged 17 days agoMITView on GitHub
Use this skill when finished vertical clips from a Riverside recording are approved and need scheduling to YouTube Shorts, TikTok and Instagram. Produces one scheduled post per clip and platform, each read back and checked. Uses Riverside's MCP server. "Schedule the shorts", "post the clips this week", "fix the shorts schedule".
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- client-win-backSkill
- late-payment-chaseSkill
- network-path-mappingSkill
- rate-increase-planSkill
- sales-call-debriefSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- ceo-exec-assistantSkill
- og-image-from-templateSkill
- weekly-site-and-ad-reportSkill
- icp-reviewSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- kondo-owed-reply-sweepSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- linkedin-shoutout-postSkill
- plain-language-copy-checkSkill
- revenue-goal-funnel-mathSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Read what is already scheduled, then build the expected-state matrix before any write: one row per clip, platform and account.
- Distinctive: line 23
Check the matrix. Every caption carries the approved call to action, usually the full-episode link rather than a hosting or bio page, and …
- Very specific: line 24
Create each row with social_upload_create.
- Very specific: line 26
Read every row back with social_get_upload and social_get_upload_status.
- Distinctive: line 37
MUST have approval for copy, accounts and times before the first write.
- Distinctive: line 38
MUST read back every post.
- Distinctive: line 39
NEVER retry a write whose outcome is unknown.
- Distinctive: line 40
NEVER cancel and recreate a scheduled post to fix it.
- Distinctive: line 41
NEVER run two scheduling sessions against the same Riverside account at once.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Applies after clips are finished and approved, when they need to go out on a schedule. Produces scheduled posts, one per clip and platform, each verified by reading it back.
Riverside's MCP server (OAuth, signed in once by the human) exposes the social scheduling tools. Five clips on three platforms is fifteen writes, so the procedure is built around never doubling or losing one.
The play
- Get approval for everything that goes out: captions, titles, accounts, visibility and times. Scheduling is publishing.
- Read what is already scheduled, then build the expected-state matrix before any write: one row per clip, platform and account. The columns are listed in
references/expected-state-matrix.md. - Check the matrix. Every caption carries the approved call to action, usually the full-episode link rather than a hosting or bio page, and every time is converted to UTC for that date. Daylight saving moves the UTC hour.
- Create each row with
social_upload_create. IncludecomposeSettings: {}on the first create. Without it, Riverside rejects an exported clip as "not exported yet". - Journal each write as it returns. If a write's result is unknown (timeout, dropped connection), don't retry it. Read the schedule once, then stop and ask.
- Read every row back with
social_get_uploadandsocial_get_upload_status. Check account, UTC time, visibility, caption, title and source clip against the matrix. A create can return "waiting for greenlight" and read back as "scheduled". Only the read-back counts. - Repair only what failed: keep verified rows, write only the missing ones.
What good looks like
- First check: the caption link. A Short without the full-episode link is reach that leads nowhere.
- The mediocre version fires fifteen creates in a loop, retries the ones that time out, and finds duplicate posts on TikTok two days later.
- The output is right when every matrix row reads back "scheduled" with the right account, UTC time and caption, and the journal shows exactly one create per row.
Rules
- MUST have approval for copy, accounts and times before the first write.
- MUST read back every post; NEVER report a create response as success.
- NEVER retry a write whose outcome is unknown.
- NEVER cancel and recreate a scheduled post to fix it; edit it, or ask.
- NEVER run two scheduling sessions against the same Riverside account at once; parallel callers hit its rate limit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

