AdKit CLI

Agent interface for managing ads via the terminal. Draft-first — nothing publishes until explicitly confirmed.

First: check setup

1. Search the project for a file named

   ad-process.md

   . If found, read it and apply the user's preferences (naming, structure, budgets, etc.) to all commands. If the user shares preferences but no file exists, offer to create one. Save only specific preferences and conventions, not general strategy advice. Use

   ## General

   for cross-platform preferences,

   ## Meta

   /

   ## Google

   etc. for platform-specific ones.
2. Run

   adkit status

   . If it works, proceed to the command routing table.
3. If

   adkit

   is not found:

   npm i -g adkit-cli

   , then

   adkit setup manage

   .
4. If not authenticated:

   adkit setup manage

   opens a browser for login and Meta Ads account connection in one step.

Command routing

adkit setup

adkit status

adkit projects use <id>

adkit manage meta campaigns create

adkit manage meta adsets create

adkit manage meta ads create

adkit manage meta media upload

adkit manage meta interests search

adkit manage drafts list

adkit manage drafts publish <id>

adkit manage meta {entity} list

Core commands

Campaign

adkit manage meta campaigns create --name "..." --objective sales --budget-daily 50

--objective

sales

leads

engagement

awareness

app_promotion

sales

leads

--budget-daily

--budget-total

--name

campaign YYYY-MM-DD

--bid-strategy

lowest_cost

cost_cap

bid_cap

min_roas

--abo

Ad set

adkit manage meta adsets create --campaign <id> --optimization conversions --event-type purchase --countries US,CA

--campaign

--optimization

conversions

lead_generation

link_clicks

impressions

reach

--event-type

purchase

lead

subscribe

start_trial

add_to_cart

contact

--countries

US,CA,GB

--interest

interests search

--pixel

--budget-daily

--abo

*Required when

--optimization

conversions

Ad

adkit manage meta ads create --adset <id> --media ./image.jpg --primary-text "..." --headline "..." --cta learn_more --url "https://..."

--adset

--media

--primary-text

--headline

--cta

learn_more

shop_now

sign_up

download

book_now

apply_now

--url

--page

Flexible Creatives: pass multiple

--media

--primary-text

--headline

Interests search

adkit manage meta interests search "digital marketing" "social media"

Multiple queries in one call. Returns IDs for

--interest

Run

adkit <command> --help full

Draft-first workflow

All create/update commands produce a draft by default:

1. Create campaign → draft ID
2. Create ad set → draft ID
3. Create ad → draft ID
4. Review:

   adkit manage drafts list

5. Publish each:

   adkit manage drafts publish <id>

Add

--publish

Key behaviors

• AdKit API, not Meta API. All commands go through AdKit's simplified API. Flags like

  --objective

  ,

  --budget-daily

  ,

  --event-type

  are AdKit's abstraction — friendlier than Meta's raw fields.
• Smart defaults. AdKit applies defaults settings (matching Business Manager defaults + improvements like scheduling, etc). Most campaigns only need a few flags — omitted settings are handled automatically. If user needs something specific, they can override the defaults.

• --platform-overrides <json>

  : escape hatch for raw Meta API fields not covered by AdKit flags. Merged directly onto the platform payload. Use when a specific Meta option isn't available as a named flag.

• --json

  : auto-enabled in non-TTY. Force with

  --json

  flag.

• --data <json>

  : bypasses named flags — pass the full AdKit API request body as JSON.
• Account resolution: auto-resolved if only one Meta account connected. Otherwise use

  --account <id>

  .
• Media handling:

  --media

  auto-uploads files and detects image vs video from extension.

With meta-ads

The meta-ads skill provides Meta advertising strategy: campaign structure, budget management, creative best practices, audience targeting, and performance analysis. Use it to decide what to build, then use this CLI skill to execute it.