Ads report
Render Markdown, HTML, or PDF paid-advertising reports from a validated Claude Ads JSON run bundle. Use for ads report, client report, audit PDF, executive audience reporting, or exporting prior audit and plan results.From its SKILL.md
npx -y skills add AgriciDaniel/claude-ads --skill ads-reportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.1 KB, 158 tokens by cl100k_base, as published. Nobody here has run it
Render Paid Media Reports
- Accept a validated versioned report bundle, never loose worker prose.
- Confirm run completeness, evidence coverage, privacy class, branding choice, requested audience, and output formats.
- Render all formats from the same canonical data and deterministic templates.
- Preserve findings, confidence, evidence references, contradictions, missing inputs, actions, owners, and measurement windows.
- Run structural checks, then visual/layout checks for HTML and PDF.
- Write atomically inside the run directory and update its manifest.
Do not include credentials, customer lists, private paths, raw research, internal agent transcripts, or promotional copy unless the operator explicitly enabled branding. Never hide partial or insufficient-evidence status in an executive summary.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most docs writing skills give in 158 tokens
Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06
- Use third-person for skill descriptionsin 54 of 1951, across 35 files
- Start descriptions with Use whenin 43 of 1951, across 29 files
- Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
- Use active voicein 40 of 1951, across 36 files
- Map file responsibilities before defining tasksin 36 of 1951, across 29 files
- Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
- Ask one question at a timein 35 of 1951
- Offer execution options after saving the planin 33 of 1951, across 24 files
- Include complete code in every stepin 33 of 1951, across 27 files
- Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
- Announce the skill usage at the startin 30 of 1951
- Verify agent compliance after adding the skillin 29 of 1951, across 17 files
Said here and by no other author read
- Accept a validated versioned report bundle
- Confirm run completeness and evidence coverage
- Render formats from canonical data and templates
- Preserve findings and evidence references
- Run structural and visual layout checks
- Write atomically inside the run directory
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.