52 Account Structure Global

What it does

When your agent uses it

• An ad account HIERARCHY needs designing
• Cleaning up — campaign
• Ad structure by objective
• A naming convention that keeps data readable

Example prompts

• “account structure”
• “campaign structure”
• “naming convention”
• “/52-account-structure-global”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

1. 1Hierarchy overview
2. 2Naming convention
3. 3Consolidation check
4. 4CBO vs ABO
5. 5Structure by stage
6. 6Budget allocation by campaign type
7. 7Minimum daily budget per ad set

What it can do on your machine

Read from SKILL.md and the folder at commit 0360adc. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

52 Account Structure Global loads about 2.8k tokens when it runs. Until then it costs about 184 tokens; SKILL.md has 1,079 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~184

When it runs · the whole SKILL.md, loaded when a task matches

~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from minhnv0807/ai-business-skills at commit 0360adc, republished under its MIT licence (© minhnv0807). 1,079 words, ~2,761 tokens.

name

52-account-structure-global

description

Use when an ad account HIERARCHY needs designing or cleaning up — campaign, ad set, and ad structure by objective, a naming convention that keeps data readable, CBO versus ABO by stage, how many ad sets and creatives to run, and the minimum daily budget an ad set needs to exit learning. Trigger on 'account structure', 'campaign structure', 'naming convention', 'how many ad sets should I run', 'CBO or ABO', 'our account is a mess of duplicated campaigns'. Not for — scoring an existing account against 84 checkpoints, see `21-ads-audit-global`; pixel and conversion setup, see `53-tracking-setup-global`; budget across channels, see `54-media-plan-global`; scaling a winner, see `55-scaling-ads-global`.

metadata.version

1.0.1

metadata.category

performance

license

MIT

triggers

account structure, campaign structure, naming convention, set up campaign, how many ad sets, CBO or ABO, restructure ad account, ad account setup

output

File .md — full campaign structure by stage, naming convention, budget allocation, minimum ad set budget math, and a pre-launch checklist

related

product-marketing-context-global, 51-audience-research-global, 53-tracking-setup-global, 54-media-plan-global, 05-ad-copy-global, 19-ab-test-setup-global…

Account
|-- Campaign 1 — [Objective] — [Product/Offer] (Cold Testing)
|   |-- Ad Set 1.1 — [Broad / Advantage+]      -> Ad A (hook 1) / Ad B (hook 2)
|   |-- Ad Set 1.2 — [Interest theme A]        -> Ad A / Ad B
|   |-- Ad Set 1.3 — [Interest theme B]        -> Ad A / Ad B
|   \-- Ad Set 1.4 — [Lookalike 1-3%]          -> Ad A / Ad B
|-- Campaign 2 — [Objective] — Scale winner (split out once a winner is proven)
\-- Campaign 3 — Retargeting
    \-- Ad Set 3.1 — [Warm 7-30 days] — objection-handling creative

Daily floor per ad set = (50 optimization events x target CPA) / 7 days
Quick sanity check     = daily budget >= 5x target CPA

# Account Structure — [Product] — [Platform]
Stage: [Testing/Scaling/Maintaining] · Monthly budget: [amount] · Markets: [list]

## 1. Campaign tree
[Full hierarchy using the naming convention]

## 2. Ad set table
| Campaign | Ad set (named) | Audience | Daily budget | ABO/CBO | Ads inside |

## 3. Naming convention applied
| Level | Format | Real example from this project |

## 4. Budget allocation
| Campaign type | % | Daily amount | Monthly amount |

## 5. Learning-phase math
| Ad set | Target CPA | Derived floor | Planned budget | Passes? |

## 6. Pre-launch checklist
- [ ] Pixel/CAPI fires correctly on landing and confirmation pages (see 53-tracking-setup-global)
- [ ] Correct conversion event selected (Lead / Purchase), no duplicates
- [ ] Consent mode and CMP live in EU/UK and California traffic
- [ ] UTMs on every link; utm_content matches the ad name exactly
- [ ] Test events all green — NOT GREEN MEANS DO NOT LAUNCH
- [ ] Naming format applied across campaigns, ad sets, and ads
- [ ] Every ad set budget clears the derived learning floor
- [ ] Exclusions applied: cold excludes purchasers and warm audiences

© minhnv0807, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/en/52-account-structure-global of minhnv0807/ai-business-skills.

Open the folder on GitHubat commit 0360adc