ads-publish
Skill102 starsChanged 6 months agoMITView on GitHub
Publish generated ad creatives to 14+ social networks via the Zernio API. Optional paid layer that closes the loop after /ads generate or /ads photoshoot. Use when user says publish, schedule, post, ship, Zernio, distribute, send to socials, push to Instagram/Facebook/LinkedIn/TikTok/Twitter, or auto-publish.
- Reads credentials
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillsedited, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- oivanfelipe/claude-skills★ 0100% same
Wrote their own version · 0
None found.
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 repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adsSkill
- ads-auditSkill
- ads-budgetSkill
- ads-competitorSkill
- ads-concienciaSkill
- ads-createSkill
- ads-creativeSkill
- ads-dnaSkill
- ads-generateSkill
- ads-googleSkill
- ads-landingSkill
- ads-mathSkill
- ads-metaSkill
- ads-nextSkill
- ads-photoshootSkill
- ads-planSkill
- ads-startSkill
- ads-testSkill
- ads-tiktokSkill
- ads-updateSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
After /ads generate (image ad creatives) or /ads photoshoot (product photography) produces an ad-assets/ directory, /ads publish takes …
- Very specific: line 35
Call
scripts/zernio_publish.py: Use Bash with the user's selected platforms and the optional --schedule flag. - Distinctive: line 36
Report results: Read the JSON output, show what was published vs.
- Very specific: line 93
If campaign-brief.md exists, the script parses sections like ## Instagram caption, ## TikTok caption, etc.
- Distinctive: line 118
Use it to verify what landed and what didn't.
- Very specific: line 122
Never publish without explicit user confirmation unless --yes was passed.
- Very specific: line 123
If --schedule is in the past, refuse and prompt for a future timestamp.
- Distinctive: line 124
If the caption exceeds the platform's limit (X: 280, LinkedIn: 3000, etc.), show a warning before posting.
≈ “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.
Files
<!-- Portions Copyright (c) 2026 Enrique Rocha (@soyenriquerocha) - see LICENSE for original authors · tododeia.com · id er-fd4fa55b -->/ads publish — Push creatives to socials via Zernio
Pricing: Zernio is free for the first 2 connected social accounts (no credit card). Solo users posting to Instagram + Facebook = $0/mo forever. Agencies pay $1–$6/mo per additional account (see "Pricing tiers" below). X/Twitter API costs are metered pass-through even on the free tier; all other 13 networks are fully included up to your account quota.
When to use this
After /ads generate (image ad creatives) or /ads photoshoot (product
photography) produces an ad-assets/ directory, /ads publish takes those
files and schedules them as posts on every social network you've connected
in Zernio. Supported: Twitter/X · Instagram · Facebook · LinkedIn · TikTok ·
YouTube · Pinterest · Reddit · Bluesky · Threads · Google Business ·
Telegram · Snapchat · WhatsApp · Discord.
Process
- Verify prerequisites. Confirm:
ZERNIO_API_KEYis set (see "Auth setup" below).ad-assets/exists or the user passed--assets <dir>.- Optionally,
campaign-brief.mdexists (the script will extract per-platform captions from it).
- Discover assets. List images and videos in the assets directory. For each, infer compatible platforms from the filename aspect-ratio hint (
9x16,1x1,16x9,1.91x1). - Plan the publication. Show the user a table: per asset, which platforms it would go to, the caption length, and the scheduling time. Ask the user to confirm before calling Zernio (unless
--dry-run). Iftwitterorxis in the target platforms list, surface the X/Twitter pass-through cost note before posting — those posts incur metered Twitter API charges on top of any Zernio tier; the other 13 networks are free up to the account quota. - Call
scripts/zernio_publish.py. Use Bash with the user's selected platforms and the optional--scheduleflag. - Report results. Read the JSON output, show what was published vs. errored, and surface any rate-limit or auth issues clearly. If anything was scheduled (vs. posted immediately), remind the user of when posts will go live.
Auth setup
- Sign up at https://zernio.com — first 2 accounts are always free, no credit card. Confirm at https://zernio.com/pricing.
- Dashboard → API Keys → create a key (
sk_<64-hex-chars>). Keys are shown once. - For each social network you want to publish to, complete the OAuth flow in Zernio's dashboard at
/connect/<platform>. Zernio handles the per-network OAuth — you don't need to manage Twitter/Meta/LinkedIn tokens yourself. Each social network you connect counts as one of your "accounts" toward the free quota. - Export:
export ZERNIO_API_KEY='sk_...'
Pricing tiers
| Accounts connected | Price per account / month |
| First 2 | $0 (free forever) |
| 3–10 | $6 |
| 11–100 | $3 |
| 101–2,000 | $1 |
| 2,001+ | Custom |
Important caveat: X/Twitter API costs are metered pass-through at X's published rates regardless of your Zernio tier. All other 13 platforms (Instagram, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Reddit, Bluesky, Threads, Google Business, Telegram, Snapchat, WhatsApp, Discord) are fully included.
Without Zernio (alternative for 3+ accounts)
The free 2-account quota covers the typical solo user. If you manage
3+ social accounts (an agency setup) and don't want to pay Zernio's
per-account fee, run /ads publish --dry-run to get the plan
(which asset goes to which network with which caption) and then
publish manually using each platform's native scheduler:
- Meta Business Suite: free, supports Facebook + Instagram scheduling.
- LinkedIn Page Posts → schedule from the composer.
- TikTok Business Suite: free scheduling for organic posts.
- Buffer / Hootsuite free tiers: limited but functional.
Same plan, zero recurring cost — just more clicks per post.
Asset-to-platform matching
| Aspect | Platforms |
| 9:16 (vertical) | Instagram Stories/Reels, TikTok, YouTube Shorts, Snapchat, Facebook Stories |
| 1:1 (square) | Instagram Feed, Facebook Feed, LinkedIn, Pinterest, X/Twitter |
| 16:9 (horizontal) | YouTube, X/Twitter, LinkedIn, Facebook |
| 1.91:1 (landscape) | LinkedIn Single Image, Facebook link previews |
The script reads the filename's aspect token (e.g. hero_9x16.png,
product_1x1.jpg) to decide. Override with --platforms <list>.
Caption extraction from brief
If campaign-brief.md exists, the script parses sections like
## Instagram caption, ## TikTok caption, etc. and uses each as the
caption for that platform. A ## Default caption section is used as
fallback for any platform without a specific one.
Output
/ads publish writes a JSON report (publish-results.json) with:
{
"tool": "zernio_publish",
"dry_run": false,
"assets_found": 5,
"captions_parsed": ["instagram", "facebook", "linkedin", "default"],
"planned": [
{"asset": "ad-assets/hero_9x16.png", "platform": "instagram", "scheduled_at": "..."}
],
"published": [
{"asset": "...", "platform": "instagram", "post_id": "...", "status": "scheduled"}
],
"errors": []
}Use it to verify what landed and what didn't.
Quality gates
- Never publish without explicit user confirmation unless
--yeswas passed. - If
--scheduleis in the past, refuse and prompt for a future timestamp. - If the caption exceeds the platform's limit (X: 280, LinkedIn: 3000, etc.), show a warning before posting.
- Per asset: cap to ≤5 platforms per
/ads publishinvocation by default (avoids burning Zernio quota on large directories accidentally).
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.

