social-media-scheduling
Skill1 starsChanged 7 months agoMITView on GitHub
Manage the scheduling state of a social-media campaign — post status lifecycle, per-network pre-schedule windows and frontiers, and keeping the cronograma/agenda derived views in sync with the posts. Use when scheduling, re-scheduling, or reconciling post status. Domain-agnostic.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- fajrisilmi12-cyber/hermes-socmed-functiontheir own version, first seen Aug 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- fajrisilmi12-cyber/hermes-socmed-function★ 20same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- readme-generatorSkill
- add-react-i18nSkill
- band-album-campaignSkill
- band-music-reflectionSkill
- band-streaming-launchSkill
- ckm:banner-designSkill
- ckm:brandSkill
- deploy-prodSkill
- ckm:designSkill
- ckm:design-systemSkill
- docker-compose-configSkill
- doc-managerSkill
- dotnet-architectureSkill
- dotnet-doc-controllerSkill
- dotnet-envSkill
- dotnet-fluent-validationSkill
- dotnet-graphqlSkill
- dotnet-multi-tenantSkill
- dotnet-test-apiSkill
- dotnet-testSkill
- frontend-designSkill
- gitversionSkill
- maui-architectureSkill
- mermaid-chartSkill
- nauth-guideSkill
- nnews-guideSkill
- react-alertSkill
- react-architectureSkill
- react-archSkill
- react-modalSkill
- readme-generatorSkill
- ckm:slidesSkill
- social-media-assetsSkill
- social-post-authoringSkill
- ckm:ui-stylingSkill
- ui-ux-pro-maxSkill
- wsl-dockerSkill
- ztools-guideSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 40
Never publish: After the user reports what was published or changed, update each post's Status and the derived views.
- Very specific: line 59
When the user reports "agendado no <rede> até <data>", record that
- Distinctive: line 65
When today's date moves forward and a frontier slips below the respective cutoff (today + window), surface a reminder so the user knows …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Social Media Scheduling
Owns the time/state layer of a campaign under social-media/: the post status
lifecycle, the per-network scheduling windows, and the synchronization between the
posts (single source of truth) and their derived views (cronograma.md /
agenda.md). It is platform mechanics only — the folder tree of a specific
campaign is defined by the domain pack (e.g. an album pack), but the status
semantics and the derived-view sync rules here apply to any campaign.
The literal status tokens and artifact section labels are kept verbatim (the generated files target a PT-BR audience). The documentation is in English.
Status lifecycle — 6 values
falta-conteudo → planejado → agendado → publicado (happy path)
+ cancelado (excluded by a rule)
+ aguardando (posts with no date yet)falta-conteudo— the slot's date exists (slot reserved) but the post has no theme/material/caption defined yet. Frontmatter has the date and item, butTipo,Material,Legendaand post-specific hashtags are "a definir". Counts as ⚠️ FALTANTE non-blocking in cronograma/agenda.planejado— ready in this repo (Material, copy, hashtags) but not yet queued in the network's composer.agendado— the user has queued the post in the network's composer; the network will publish on the scheduled date.publicado— the post is live.cancelado— excluded by some rule.aguardando— ready but waiting for a trigger external to the calendar (post with no fixed date). See the domain pack that defines dateless posts.
Never publish. After the user reports what was published or changed, update
each post's Status and the derived views.
Per-network pre-schedule windows
Each network has its own rolling pre-queue limit. The calendar can plan posts far into the future, but the actual queuing inside each platform's composer happens in chunks as time progresses.
| Network | Pre-schedule window |
| Instagram (Meta Business Suite) | 29 days |
| Threads (mirrors Instagram) | 29 days (inherited) |
| TikTok | 30 days |
| X.com | no practical limit — accepts > 30 days, track the frontier |
| YouTube | no practical limit — accepts long windows, track the frontier |
Per-network scheduling frontier
- When the user reports "agendado no
<rede>até<data>", record that frontier inconfig.mdand in the mastercronograma.md/agenda.md, and flip every active post on<rede>with date≤ <data>fromplanejadotoagendado. The frontier is the date-level marker;Statusis the per-post marker — they must stay in sync. Skip posts alreadypublicado,canceladooraguardando. - When today's date moves forward and a frontier slips below the respective cutoff (today + window), surface a reminder so the user knows it's time to queue more posts on that network.
- For networks whose window is TBD, plan without a frontier until the user gives the constraint.
Derived-view synchronization (hard rule)
The posts in posts/ are the single source of truth. cronograma.md (the
by-date view) and agenda.md (the by-network view) are derived views —
they must never lag behind the post state. Whenever you create, edit, cancel or
re-allocate a post — or mark it ⚠️ FALTANTE não-bloqueante — propagate the change
to:
- The "Pendência de mídia" column of that date's
cronograma.md: the cell becomes⚠️if any post on the date is marked,⛔if any is blocking,✅only if all posts on the date are clean. - The "Material" column of that post's
agenda.md(✅ / ⚠️ / ⛔ summary). - The aggregated counts and Pendência column of the master
cronograma.md.
agenda.md — content & maintenance
agenda.md is the index of posts grouped by network, each section listing the
posts chronologically with a clickable link to the post file (the by-network
scheduling view, used to queue platform by platform). Sections in order: YouTube,
Instagram, TikTok, X.com, Threads. Each section holds a chronological table with
columns: Data, Tipo, Status (planejado / agendado / publicado / cancelado /
aguardando), Material (short summary: ✅ ready / ⚠️ FALTANTE / ⛔ blocking), and
Arquivo (relative Markdown link to the <rede>.md). The Threads section lists
each date that has an instagram.md flagged "replicar no Threads", linking the
instagram.md. Cancelled dates go to a "Canceladas" sub-table at the end of the
network's section. Do not duplicate caption content — index rows only.
The concrete folder layout (
albuns/<x>/<faixa>/...vs another structure) and the mastercronograma.mdare defined by the campaign's domain pack. This skill only guarantees that, whatever the layout, the views stay in sync with the posts per the rules above.
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.

