Install
$ agentstack add skill-kelpi-ai-meta-ads-skills-catalog-commerce ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Catalog & Commerce
Doctrine
Commerce plumbing is unglamorous and decisive: dynamic product ads cannot run without a healthy catalog, and a catalog wired to a broken pixel just automates showing people the wrong products. Order matters: pixel first (see pixel-conversions), catalog second, product sets third. Product sets are angles for inventory: "best sellers", "under $50", "new arrivals" are different promises to different buyers.
When to use
- Ecom stores with enough SKUs that per-product creative is impractical.
- Before any retargeting play that shows people what they browsed.
- Needs a Meta Ads MCP with write access; creation steps are confirmed before running.
Run it
Catalog setup, step by step, confirm with me before each write:
1. List my existing catalogs and their product counts. If a catalog already exists, audit it instead of duplicating: how many products, how many rejected or missing images/prices?
2. Check the pixel link: is the catalog connected to my pixel, and are the product IDs in my purchase events matching catalog IDs? If not, stop and tell me; nothing downstream works until this does.
3. Propose 2-3 product sets that match my angles (for example: best sellers, entry-price items, the category my ads target). Show the filter logic.
4. On my approval, create the sets and tell me exactly which ad type they unlock (dynamic product ads, advantage+ catalog ads) and what a $20/day test on the best set would look like.
Guardrails
- Audit before create: duplicate catalogs are how accounts end up advertising stale prices.
- The pixel-to-catalog ID match is a hard gate. Skipping it produces ads for out-of-stock products at wrong prices.
- Product sets mirror angles: a set nobody wrote an angle for is inventory, not a campaign.
Good output looks like
One healthy catalog, 2-3 named product sets tied to angles, and a clear go/no-go on whether dynamic ads are ready to test.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kelpi-ai
- Source: kelpi-ai/meta-ads-skills
- License: MIT
- Homepage: https://kelpi.ai/skills
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.