Przejdź do treści
Biblioteka skilli
Marketing i treści · Automatyzacja

ads-setup

/ads-setup

Podłącza reklamy AdSense lub AdMob, dodaje ads.txt albo app-ads.txt i identyfikatory jednostek, sprawdza politykę i zgodę.

Repozytorium
agent-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
6
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
3
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Podłącza reklamy AdSense lub AdMob, dodaje ads.txt albo app-ads.txt i identyfikatory jednostek, sprawdza politykę i zgodę.

Wyzwalacze z opisu

set up adsподключи рекламунастрой AdSenseдобавь AdMob
Oryginalny opis (EN)

Use when the user asks to add ads, set up AdSense or AdMob, add ads.txt or app-ads.txt, the consent message, ad unit IDs, or the Play Console ads and data safety answers, in any language: "set up ads", "подключи рекламу", "настрой AdSense", "добавь AdMob". Checks ad policy, picks AdSense for sites and AdMob for Android, goes through the dashboards with the user logged in, wires the IDs with test ads in debug, writes TODO.md.

Jak działa

  1. Logins and keys
  2. 1. Read the project
  3. 2. Pick the ad product per surface
  4. 3. Check the site can pass review
  5. 4. Set up the site
  6. 5. Set up the app
  7. 6. Consent and privacy
  8. 7. Play Console declarations
  9. 8. Commit, deploy, record
  10. 9. Write TODO.md
Sekcje z nagłówków SKILL.md, w oryginale · 203 linii, 1 576 słów
Podgląd SKILL.md
---
name: ads-setup
description: 'Use when the user asks to add ads, set up AdSense or AdMob, add ads.txt or app-ads.txt, the consent message, ad unit IDs, or the Play Console ads and data safety answers, in any language: "set up ads", "подключи рекламу", "настрой AdSense", "добавь AdMob". Checks ad policy, picks AdSense for sites and AdMob for Android, goes through the dashboards with the user logged in, wires the IDs with test ads in debug, writes TODO.md.'
---

# Set up ads for a site and an Android app

The agent MUST get AdSense to approve the site and connect the app to AdMob,
with each ad policy kept on the way.

## Logins and keys

- **Browser** the agent SHOULD drive whatever browser tool it has: the VS
  Code browser tools, or the `agent-browser` skill. Without one, it MUST hand
  the user the link and the clicks as numbered steps, one per line, and wait.
- **API first** when an AdMob, AdSense or Google Play MCP server is connected,
  the agent MUST read the accounts, apps, units and sites through it. The
  browser SHOULD serve only the pages the API lacks, such as a new app, a
  consent message or payments. Browser tools hang on the Google consoles when
  the machine is busy.
- **Login screen** the user MUST log in inside that window, and the agent
  MUST wait for "done". A password, a 2FA code, a bank account or a tax ID
  MUST NOT be typed by the agent.
- **Payments and tax forms** the user MUST fill them. The agent MUST name the
  page and wait.
- **Public IDs** `ca-pub-...`, `ca-app-pub-...~...` and the ad unit IDs MAY
  sit in the code. Each visitor can read them in the page or the app.
- **Secrets** an API token or a service account key MUST stay out of commits
  and out of the chat.

## 1. Read the project

The repo rules MUST beat this skill. The agent MUST start with `AGENTS.md`,
`CLAUDE.md` and the README, then look for ads code with these:

```bash
git grep -nE 'adsbygoogle|ca-pub-|google-adsense-account|ca-app-pub-|play-services-ads|google_mobile_ads|user-messaging-platform' -- ':!*.lock'
ls android app 2>/dev/null; ls pubspec.yaml capacitor.config.* android/twa-manifest.json 2>/dev/null
```

1. **The site** the agent MUST find the domain, how the pages are made, and
   where head tags belong.
2. **The app** it MUST tell native Kotlin or Java, Flutter, React Native,
   Capacitor, a WebView, or a Trusted Web Activity (TWA) that shows the site
   in Chrome.
3. **The work already there** it MUST note IDs in the code, `ads.txt`, a
   README section on ads.

## 2. Pick the ad product per surface

Each surface MUST get its ads from the product in this table, set up by the
reference in its row:

| Surface                                           | Ads from                                                            | Read                                           |
| ------------------------------------------------- | ------------------------------------------------------------------- | ---------------------------------------------- |
| A website in a browser                            | AdSense                                                             | [references/adsense.md](references/adsense.md) |
| A native app: Kotlin, Java, Flutter, React Native | AdMob                                                               | [references/admob.md](references/admob.md)     |
| A Capacitor or WebView app                        | AdMob, plus the WebView API for Ads when the web page shows AdSense | [references/admob.md](references/admob.md)     |
| A TWA showing the site                            | AdSense off inside the app                                          | [references/twa-ads.md](references/twa-ads.md) |

AdSense code MAY run on web pages and approved WebView setups, and only there.
A TWA counts as neither, so the site MUST hide AdSense when the app opens it.

## 3. Check the site can pass review

Most first AdSense attempts fail for the same handful of reasons. Before
applying, each of these MUST be true:

- **Own domain** the site MUST be served over https, with no "coming soon"
  page.
- **Content** it MUST hold original text, enough to judge the site by: the
  `seo-setup` skill sets the bar.
- **Trust pages** it MUST have About, Contact with a working email, a privacy
  policy.
- **Crawlers let in** `robots.txt` and the Cloudflare bot settings MUST pass
  `Mediapartners-Google` and `Googlebot`.
- **Navigation** a menu MUST lead to each page.

When something is missing, the agent MUST load the `seo-setup` skill, fix the
gap, deploy, then return here.

### Design an app site so the reviewer sees text

The reviewer opens the home page and judges the site by what it shows. A map,
a fretboard or a landing with a button and 2 lines gets "insufficient
content", and the whole account is refused. The rules below MUST hold on each
site before it goes into AdSense:

- **Home page is a text page** the home page MUST show at least 300 words
  of visible text: what the tool does, who it is for, how to use it, and
  links to the content pages. An app screen MAY sit above the text, and the
  text MUST follow it on the same page, in plain view. An `sr-only` or
  `noscript` block does not count.
- **Text in view-source** the text MUST be in the HTML the server sends, so
  a client-only app MUST prerender or statically render its home and content
  pages.
- **Content pages** the site MUST hold at least 5 pages of original text of
  300 words or more: guides, explainers, the data behind the tool. The
  `seo-setup` content guide sets the bar for each page.
- **One site per application** the account MUST apply with its strongest
  site alone. The other sites go in one at a time after the first approval,
  and each one passes the checks above first. 4 sites at once got one refusal
  for all of them on 2026-11-03.
- **Check before the request** the agent MUST run the check below on each
  page the menu links to. A page under 300 words MUST get its text first.
  The check MUST go through `perl`, since a one-line HTML page makes `sed`
  strip from the first `<script>` to the last one.

```bash
curl -sL "https://$d/" | perl -0pe 's/<script.*?<\/script>//gs; s/<style.*?<\/style>//gs; s/<[^>]+>/ /g' | wc -w
```

## 4. Set up the site

The agent MUST work through [references/adsense.md](references/adsense.md):
account, verification code in the head, `ads.txt`, review request, consent
message, ad units.

An AdSense review lasts anywhere from a few days to 4 weeks. The agent MUST
stop once the request is in, note the date, and tell the user to run this
skill again when the approval email arrives.

## 5. Set up the app

The agent MUST work through [references/admob.md](references/admob.md):
account, the app and its ad units, the SDK with test ads in debug builds, the
consent form, `app-ads.txt`.

- A debug build MUST NOT load real ad unit IDs. One click on a real ad from a
  developer's phone gets the account flagged.
- The app MUST hide its ads on the developer's own device, with a "Show test
  ads" switch in Settings that only that device sees. The agent MUST read
  [references/dev-device.md](references/dev-device.md) and build it with the
  ad code.
- The app SHOULD go to Play internal testing with test ads before anything
  else. The `play-release` skill MUST handle the upload.

## 6. Consent and privacy

1. The agent MUST publish a GDPR message in Privacy & messaging: in AdSense
   for the site, in AdMob for the app. It reaches the EEA, the UK and
   Switzerland. Visitors there see limited ads when it is missing.
2. A US states message SHOULD be added as well, from the same tool.
3. The privacy policy MUST mention Google ads cookies and link to
   `https://policies.google.com/technologies/partner-sites`. The agent MUST
   change it in the repo and deploy.

## 7. Play Console declarations

An app that shows ads, or a TWA that shows a site with ads, MUST declare it.
The agent MUST read
[references/play-declarations.md](references/play-declarations.md) and fill
in each page in the browser.

## 8. Commit, deploy, record

- A change SHOULD get a commit of its own, in the repo's commit style: the
  IDs, `ads.txt`, the consent code, the privacy policy.
- Before each commit, the agent MUST run the repo checks. It MUST deploy,
  then fetch the live `ads.txt` and `app-ads.txt` with `curl`.
- The agent MUST add or update the README section on ads, written per
  `writing-style`: the account, where each ID lives, what is under review and
  from what date.

## 9. Write TODO.md

`TODO.md` at the target repo root MUST hold each task this run leaves for the
user. The agent MUST touch only the `## ads-setup` section, adding or
updating it.

- **One task per line** each line MUST hold a checkbox, the task, the place,
  and a date for a wait.
- **Done tasks** they MUST come off once the user says so or the dashboard
  shows it.
- **No tasks left** the section MUST be removed.
- **Secrets** passwords, bank details and tax IDs MUST be left out.

The section SHOULD read like this:

```markdown
## ads-setup

- [ ] Fill in the tax form in AdSense, Payments: https://adsense.google.com
- [ ] Run `ads-setup` again when the approval email comes, review sent <date>
```

The agent MUST commit it together with the README record.

## 10. Report back

1. The report MUST give each surface: the ad product, its state (code in,
   under review, approved, serving), its dashboard link.
2. It MUST list the commits, a line for each.
3. It MUST say what is waiting on Google, and the date to look again.
4. It MUST list the `TODO.md` tasks: payments, tax form, ID check.

## Guardrails

- A live ad MUST NOT be clicked by the agent, on any device.
- Ads MUST stay clear of buttons and look unlike the site content or the
  menu. Placements that lead to misclicks get the account banned.
- The page MUST carry no text that asks people to click ads or to support the
  site through them.
- An ad slot MUST hold its height until the ad loads, so the page stays still.
- After a rejection, the review SHOULD be read in full and fixed before it goes
  in again.
Pliki w paczce (6)
  • SKILL.md 10 KB
  • references/admob.md 4 KB
  • references/adsense.md 4 KB
  • references/dev-device.md 2 KB
  • references/play-declarations.md 2 KB
  • references/twa-ads.md 3 KB

Wersje

W bazie nie ma innych skilli o nazwie ads-setup.

Migawka bazy z 13.11.2026 · wersja paczki 82ed0cdc5634 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100adsense-site-auditor
    Audytuje strony pod kątem gotowości do wniosku o AdSense i zgodności z zasadami: własność witryny, jakość treści, nawigacja, dostęp robotów, ads.txt, polityka prywatności oraz zasady Google Publisher Policies.
  • 100seo-setup
    Ustawia SEO strony: rejestruje ją w Search Console i Bing, dodaje sitemap, robots.txt i metadane, a potem zapisuje listę zadań w TODO.md.
  • 100admob
    Rejestruje aplikacje i tworzy jednostki reklamowe w AdMob z wiersza poleceń przez API, a potem przekazuje identyfikatory do kodu aplikacji.
  • 100admob-ads-and-consent
    Buduje reklamy AdMob za portem aplikacji: banery, interstitiale, nagradzane, zgodę UMP przed ATT, odstępy między reklamami i testowe identyfikatory ADS_MODE.
  • 100adsense-site-builder
    Buduje i sprawdza strony niszowe gotowe do AdSense: walidację niszy, plan słów kluczowych, strukturę, strony zaufania i SEO techniczne.
  • 100store-media
    Wysyła zrzuty, wideo, grafikę i ikony aplikacji do Google Play i innych miejsc, a przed wysłaniem do recenzji pyta o zgodę.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.