Skill request: AdMob API reporting and inventory
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- google-cloud
- Domain
- api, documentation
Research direction
This asks for a new skill for the AdMob API, so there is no existing code path to change; the work is authoring a skill document that covers OAuth setup with the admob.report and admob.readonly scopes, paginated app and ad unit listing, and reporting guidance. Use the linked kmshack/skills#1 walkthroughs and the AdMob reporting guide as references, and check the existing Google Mobile Ads skills in the repo to match format. Done when the skill covers the three listed areas and follows the repository's skill conventions.
Written by the indexing model from the issue text.
Description
Could Google Skills add an AdMob API skill for publisher reporting and inventory? The existing Google Mobile Ads SDK skills cover app integration. This skill would help developers retrieve and interpret publisher data from the AdMob API.
Proposed scope
- Set up OAuth with the narrowest scope for the task. Use
admob.reportfor publisher details and reports, andadmob.readonlyfor app and ad unit inventory. - Resolve the publisher account and retrieve paginated app and ad unit listings.
- Generate network or mediation reports for common questions, such as estimated earnings and impressions by app or ad source. Include guidance on reporting time zones, monetary units, and incomplete results.
An example implementation with OAuth and REST walkthroughs is available in kmshack/skills#1. The AdMob API reporting guide describes the underlying API.
- Dominant language
- Python
- Stars
- 23.1k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/skills
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
namespace
Difficulty 1/5 Under an hour Newbie friendliness 68/100
EclipseFdn/open-vsx.org#15604 ·
Maintainers usually reply within 1 day
-
app: scripts severity: low status: backlog type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netbox-community/netbox-scripts#164 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 5 days
-
Public function to read participants.tsvPossibly taken @bruAristimunha claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
huggingface/tau#799 ·
Maintainers usually reply within 2 days