Google ads for OpenClaw

v1.0.0

Управление кампаниями Google Ads. Используйте этот навык, когда пользователь хочет просмотреть статистику, изменить бюджет, включить или выключить кампании в...

1· 546·0 current·0 all-time
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
Name/description claim management (view, change budgets, enable/disable). The repository includes helper scripts for Google Ads but the package metadata declares no required credentials or primary credential despite the SKILL.md and code requiring Google Ads credentials (developer_token, client_id, client_secret, refresh_token). This mismatch is disproportionate to the stated purpose.
!
Instruction Scope
SKILL.md instructs the agent to check for ~/.google-ads.yaml and to use scripts for listing/updating. The python script, however, only implements the 'list' flow — the update-budget and update-status CLI branches are defined but not implemented. That means runtime behavior will not match the instructions and could mislead users or agents into believing updates will occur when they won't.
Install Mechanism
There is no install spec (instruction-only plus bundled scripts), which is lower risk for arbitrary code installs. However the scripts import google.ads.googleads (Google Ads client library) and no dependency or installation instructions are declared in metadata — the runtime will fail unless that library is present. setup_ads.py will write a config template to ~/.google-ads.yaml if run.
!
Credentials
The skill requires Google Ads credentials (explicit in SKILL.md and setup template) but the registry metadata lists no required environment variables or primary credential. Requesting developer_token/client_id/client_secret/refresh_token is proportionate to Google Ads use, but the lack of declared required env vars is an incoherence and a practical risk (users may provide secrets without realizing).
Persistence & Privilege
always is false and the skill does not request elevated persistent privileges. The only persistence behavior is setup_ads.py creating ~/.google-ads.yaml (its own config file). The skill does not modify other skills or system-wide configs.
What to consider before installing
This skill is not clearly coherent: it needs Google Ads credentials but doesn't declare them, and the main script only implements listing (not updating budgets/statuses) despite advertising full management. Before installing or running it: 1) Inspect/verify the code yourself (or have a developer do so) and confirm update operations are correctly implemented; 2) Do not supply your primary production Google Ads credentials until you trust the code — consider testing with a limited-access test Ads account; 3) Ensure the google-ads-python library will be installed in a controlled environment; 4) Be aware running setup_ads.py will create ~/.google-ads.yaml containing tokens on disk; if you proceed, add explicit required-env declarations and a dependency spec, or ask the publisher for a corrected release. If you cannot validate these points, avoid granting credentials or running the scripts.

Like a lobster shell, security has layers — review code before you run it.

Any user can simply place the ClawAds folder into their .agent/skills/ directory. Open Source: All scripts are written in Pythonvk972zbd80rgmdekb8bhvj2qcd581zamzand instructions are provided in Markdown. Any developer can easily add new featuresvk972zbd80rgmdekb8bhvj2qcd581zamzlatestvk972zbd80rgmdekb8bhvj2qcd581zamzsuch as keyword management or advanced analytics. Important Note for Users: To get the skill up and runningvk972zbd80rgmdekb8bhvj2qcd581zamzthere are two steps required (detailed instructions are included inside the folder): Install the Google Ads library: pip install google-ads. Use your own configuration file: Ensure you have a ~/.google-ads.yaml file containing your personal API tokens.vk972zbd80rgmdekb8bhvj2qcd581zamz
546downloads
1stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Google Ads Manager

Инструмент для управления контекстной рекламой Google.

Возможности

  1. Мониторинг: Получение списка кампаний и их текущих метрик (показы, клики, CTR, затраты).
  2. Управление: Изменение статуса кампаний (ENABLE, PAUSED) и обновление дневных бюджетов.
  3. Отчеты: Генерация базовых отчетов за определенный период.

Настройка

Для работы требуются учетные данные в файле google-ads.yaml или переменные окружения. Файл конфигурации должен находиться по пути: ~/.google-ads.yaml или в корне проекта.

Использование скриптов

Основной интерфейс взаимодействия реализован через Python-скрипт scripts/google_ads_tool.py.

Примеры команд

  • Список кампаний: python3 scripts/google_ads_tool.py list
  • Изменение бюджета: python3 scripts/google_ads_tool.py update-budget --id <ID> --amount <VALUE>
  • Остановка кампании: python3 scripts/google_ads_tool.py update-status --id <ID> --status PAUSED

Инструкции для агента

При получении запроса на работу с рекламой:

  1. Проверьте наличие конфигурационного файла.
  2. Используйте google_ads_tool.py для выполнения соответствующего действия.
  3. Всегда подтверждайте критические изменения (изменение бюджета, остановка кампаний) перед выполнением, если пользователь не указал иное.

Comments

Loading comments...