agentleFS
fajrisilmi12-cyberfajrisilmi12-cyber/hermes-socmed-function/skills/social-media-scheduling/SKILL.md

social-media-scheduling

Skill20 starsChanged 3 months agoMITView on GitHub

Use for Postnify social-post scheduling requests. Covers IG.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. landim32/awesome-ai-skills★ 1same 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never pass local paths or foreign URLs to -m.

    line 20
  2. Distinctive:

    Free tier is 15 posts/month: When volume matters or user complains about the cap, point IG/FB scheduling to Meta Business Suite (free, …

    line 45
  3. Very specific:

    When the media is a terminal/IDE screenshot (common from Fajri), run vision analysis on it first asking specifically whether any FULL API …

    line 64
  4. Very specific:

    If any full secret is visible: warn and ask before posting.

    line 66

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Social Media Scheduling via Postnify

Fajri schedules Instagram posts through chat ("upload ini jam 6 sore, caption X"). The tool is Postnify CLI (/usr/bin/postnify, OAuth2 already valid in ~/.postnify/credentials.json). Load this skill before running any postnify command — it carries the account IDs, the gotchas that actually bit us, and a ready verification script.

Workflow

  1. Identify target time — Fajri speaks WIB (UTC+7): "jam 6 sore" = 18:00 WIB = 11:00Z. Confirm with date -u if the current UTC time is near or past the requested slot.
  2. Check auth + integration (skip only if used earlier same session): postnify auth:status then postnify integrations:list.
  3. Upload media FIRST — postnify upload <file> → use returned .path URL in -m. Never pass local paths or foreign URLs to -m.
  4. Create post — -s date is REQUIRED and must be ISO8601 Zulu:
    postnify posts:create -c "<caption>" -m "<uploaded-url>" -s "<YYYY-MM-DDTHH:MM:SSZ>" \
      --settings '{"post_type":"post"}' -i "$IG_ID"
  5. Verify — run scripts/verify_ig_schedule.sh <post-id> (or read its inline logic): confirm state=QUEUE and publishDate matches the request; report both to the user.

Gotchas learned the hard way (do not rediscover)

  • post_type is REQUIRED for instagram-standalone or posts:create returns 400 (settings.post_type should not be null). Always pass --settings '{"post_type":"post"}' (or "story"). This error is NOT mentioned as required in integrations:settings output. Stories: use "story" + a space " " as caption when the user says "tanpa caption" (empty -c "" fails with "Either --content or --json is required").
  • Instagram rejects WebP uploads at PUBLISH time, not create time. The post shows state=QUEUE and only fails later with ERROR. Convert to JPEG first: ffmpeg -y -i in.webp out.jpg. After any ERROR, delete + recreate with converted media; do not just reschedule the broken post.
  • Deleting a queued post: postnify posts:delete <id> works cleanly while state=QUEUE/ERROR.
  • Pin order: schedule earlier-requested posts earlier even if asked in reverse order, so the queue matches how Fajri thinks about them.
  • Time math: Fajri speaks WIB = UTC+7 ("jam 8:40 malam" → 13:40Z same day). Confirm with date -u right before scheduling; he schedules near-current-time slots often.
  • Free tier is 15 posts/month. When volume matters or user complains about the cap, point IG/FB scheduling to Meta Business Suite (free, unlimited) instead of upgrading; keep Postnify for multi-platform pushes.

Delivering longer content via chat (not Postnify-specific)

  • Discord caps a message at 2000 chars. Any reply longer than that must be split into consecutive send chunks (or condensed); the API hard-rejects overlong posts.
  • WhatsApp long-message delivery (working pattern): cronjob create with no_agent=true, deliver=whatsapp, a one-shot schedule, and a python script whose stdout is print(open(path).read()). Pitfalls hit this way:
    • script must be a resolvable file — a bash one-liner (cat /path) was mis-parsed as the path (/root/.hermes/scripts/cat /path → "Script not found").
    • One-shot schedule must be >120s in the future; earlier times are rejected.
    • A one-shot job that already fired is disabled/completed — run/update-then-run will NOT re-fire it; remove and create a fresh job instead.

Safety check before publishing screenshots

When the media is a terminal/IDE screenshot (common from Fajri), run vision analysis on it first asking specifically whether any FULL API key/token/password is visible unmasked. If any full secret is visible: warn and ask before posting. Truncated keys (ending in …) and bare UUIDs are acceptable.

References

  • references/postnify-ig.md — account/integration IDs, command transcript patterns, analytics notes for this user's connected accounts.
  • references/zernio.md — parallel multi-platform scheduler (16 platforms, 2 free accounts forever, no Postnify cap). Use when Postnify's 15-post/month limit or single-platform scope blocks the request.
  • references/ig-data-access.md — verified facts for IG data-access questions (Graph API limits, dead Basic Display API, scraping constraints on this server, anti-bot reality). Consult before answering "can we scrape IG".

Planned extension (not yet wired)

Facebook Page posting for the FB-Shopee dropshipping project — connect the Page as a second integration, then reuse the same flow (likely needs different settings keys; check integrations:settings <fb-page-id> first).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.