P
paid-traffic-architect
About paid-traffic-architect
A planning skill for paid-traffic campaigns, covering campaign structure, audience hypotheses, landing-page requirements, UTM conventions, and creative briefs. It does not access or modify ad accounts by default and requires approval before actions that could spend money or change tracking.
Key features
- 01Campaign structure and audience hypotheses
- 02Landing-page requirements
- 03UTM conventions and reporting alignment
- 04Ad creative briefs
- 05Cross-team handoff requirements
- 06Safety checks for account actions
Use cases
- 01Drafting a paid campaign plan
- 02Standardizing UTM tags and reporting
- 03Briefing ad creative production
- 04Handing landing and tracking needs to teams
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sergekostenchuk/ ui-ux-agent-skill-system --skill paid-traffic-architectAfter installing, type/paid-traffic-architectin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlassets/paid-traffic-plan.template.mdevals/evals.jsonreferences/paid-traffic-safety-contract.mdDetails
From the project READMEPaid Traffic Architect
This skill prepares paid traffic plans and landing requirements. It does not access or change ad accounts by default.
Operating Modes
campaign-plan: define campaign structure, audience hypotheses, and landing-page requirements.utm-map: create UTM conventions and reporting alignment.creative-brief: define ad angles and asset requirements.handoff: send landing and tracking requirements to UI/SEO/analytics owners.
Required Workflow
- Read references/paid-traffic-safety-contract.md.
- Use assets/paid-traffic-plan.template.md.
- Keep budgets, bids, and audiences as planning assumptions unless the user provides approved values.
- Require
analytics-setup-architectfor tracking andseo-llm-site-architectwhen landing content and organic pages overlap.
Safety Rules
- Do not launch campaigns, spend money, edit pixels, upload audiences, or change ad accounts without approval.
- Do not store ad account tokens, customer lists, cookies, or private audience exports.
- Do not make prohibited, discriminatory, medical, financial, legal, or false claims.
Validation
python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/paid-traffic-architect
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/paid-traffic-architect
python3 -m json.tool $CODEX_HOME/skills/paid-traffic-architect/evals/evals.json >/dev/null
Comments
Markdown supported