agentleFS
Marky-TeamMarky-Team/marky-skills/skills/create-post-countdown/SKILL.md

create-post-countdown

Skill5 starsChanged 4 months agoApache-2.0View on GitHub

Build a countdown campaign for an upcoming event through the Marky API: a series of on-brand posts, each with a different angle, scheduled at the right intervals leading up to the date. Use this when you have an event (launch, sale, webinar, opening, holiday promo) and want a sequence of posts that build anticipation and end with a final reminder. Reads auth and endpoints from the marky-api skill. Also triggers on "countdown to my event", "posts leading up to the launch", "build hype for my webinar". For a single event post, see schedule-posts.

  • Sends data out

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Marky wants your feedback: If anything breaks or is confusing while you run this skill — and again once you finish — send Marky a quick …

    line 21
  2. Distinctive:

    Ask the user for whatever is missing:

    line 25
  3. Very specific:

    Only target platforms whose status is valid.

    line 43
  4. Distinctive:

    Keep the final reminder short and direct with a clear next step.

    line 126
  5. Very specific:

    If the user gives you photos or video for the event, upload them first with POST /businesses/{id}/media and pass the returned original_url …

    line 127

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Event Countdown Posts

Turn one event into a sequence of posts that build excitement over time. Each post takes a different angle (announce, tease details, build anticipation, final reminder) and gets scheduled at a sensible interval before the event.

Read the marky-api skill first for the base URL, your mk_live_ key, and the full endpoint list. Everything below uses https://api.mymarky.ai/api and the header Authorization: Bearer mk_live_YOUR_KEY.

Marky wants your feedback. If anything breaks or is confusing while you run this skill — and again once you finish — send Marky a quick note with the submit_feedback MCP tool. See the "Marky wants your feedback" section in the marky-api skill for when and how.

Step 1 — gather the event details

Ask the user for whatever is missing:

  • What is the event? (launch, sale, webinar, opening, etc.)
  • The exact date and time, and the timezone.
  • The key details to highlight (offer, location, link, who it is for).
  • How many posts they want (a 5-post countdown is a good default).
  • Which connected platforms to post to.

Step 2 — find the workspace and platforms

curl https://api.mymarky.ai/api/workspaces \
  -H "Authorization: Bearer mk_live_YOUR_KEY"

curl https://api.mymarky.ai/api/businesses/BIZ_ID/integrations \
  -H "Authorization: Bearer mk_live_YOUR_KEY"

Only target platforms whose status is valid.

Step 3 — plan the schedule

Work backward from the event date. A 5-post countdown usually lands like this:

PostAngleWhen to publish
1Announce it exists~7 days before
2Tease the details / the offer~4 days before
3Build anticipation (why it matters)~2 days before
4"Tomorrow!" reminder1 day before
5"Today / last chance" final reminderday of, a few hours before

Adjust the spacing to how far out the event is. Confirm the plan with the user before creating anything.

Step 4 — create each post

You can write each caption yourself (full control) or let Marky draft on-brand copy from the event description. Either way you end up with a post you then schedule.

Write it yourself:

curl -X POST https://api.mymarky.ai/api/businesses/BIZ_ID/posts \
  -H "Authorization: Bearer mk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "caption": "Announce-angle caption for the event.",
    "restrict_publish_to": ["instagram", "facebook", "linkedIn"]
  }'

Or let Marky draft on-brand copy (brand voice, colors, and logo are applied automatically). You choose target platforms later when you schedule, so generate only needs the idea:

curl -X POST https://api.mymarky.ai/api/businesses/BIZ_ID/posts/generate \
  -H "Authorization: Bearer mk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "custom_idea": "Announce our Spring Sale, 20% off, this Saturday only.",
    "count": 1
  }'

generate returns a job_id. Poll GET /businesses/BIZ_ID/jobs/{job_id} until it is completed, then list the new drafts with GET /businesses/BIZ_ID/posts?status=NEW to get each new post_id.

Step 5 — schedule each post at its interval

For each post, schedule it at the time you planned in Step 3 (ISO 8601, in the future):

curl -X POST https://api.mymarky.ai/api/businesses/BIZ_ID/posts/POST_ID/schedule \
  -H "Authorization: Bearer mk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "scheduled_publish_time": "2026-04-10T09:00:00Z",
    "restrict_publish_to": ["instagram", "facebook", "linkedIn"]
  }'

Convert the user's local event time to UTC for scheduled_publish_time. Double-check the math so a 9am-local reminder does not go out in the middle of the night.

Step 6 — confirm

List the scheduled posts back to the user so they can see the full countdown:

curl "https://api.mymarky.ai/api/businesses/BIZ_ID/posts?status=SCHEDULED" \
  -H "Authorization: Bearer mk_live_YOUR_KEY"

Show the sequence (each angle + its publish time) and confirm it is ready.

Tips

  • Vary the angle on every post. Five "don't miss our event!" posts is noise. Announce, tease, explain the value, remind, last-call.
  • Keep the final reminder short and direct with a clear next step.
  • If the user gives you photos or video for the event, upload them first with POST /businesses/{id}/media and pass the returned original_url in each post's media_urls.

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.