admapix
Ad intelligence & app analytics assistant. Search ad creatives, analyze apps, view rankings, track downloads/revenue, and get market insights via api.admapix.com.
Install / Use
npx skills add LeoYeAI/openclaw-master-skills --skill admapix-iceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Data & AnalyticsSupported Platforms
Our assessment of admapix
admapix scores 90/100 on our quality scale, 304th of 604 Data & Analytics skills we index.
Its SKILL.md is 17 KB long, well organised into 29 sections with 11 code examples: a thorough specification that gives an agent plenty to work with.
With 2,149 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
- Our last check on 2026-10-30 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
admapix compared with similar skills
All 4 of these similar skills score higher than admapix; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| admapix (this skill)by LeoYeAI | 90 | 2.1k | 4mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
| crawl4aiby unclecode | 100 | 87.4k | 3d ago | MCP Server |
Frequently asked questions
- How do I install admapix?
- Run
npx skills add LeoYeAI/openclaw-master-skills --skill admapix. The install tabs above show the steps for each supported agent. - Which AI agents does admapix work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is admapix safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is admapix still maintained?
- The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
Skill content
View source on GitHubname: admapix description: "Ad intelligence & app analytics assistant. Search ad creatives, analyze apps, view rankings, track downloads/revenue, and get market insights via api.admapix.com. Triggers: 找素材, 搜广告, 广告素材, 竞品分析, 广告分析, 排行榜, 下载量, 收入分析, 市场分析, 投放分析, App分析, 出海分析, search ads, find creatives, ad spy, ad analysis, app ranking, download data, revenue, market analysis, app intelligence, competitor analysis, ad distribution." metadata: {"openclaw":{"emoji":"🎯","primaryEnv":"ADMAPIX_API_KEY"}}
AdMapix Intelligence Assistant
You are an ad intelligence and app analytics assistant. Help users search ad creatives, analyze apps, explore rankings, track downloads/revenue, and understand market trends — all via the AdMapix API.
Data disclaimer: Download/revenue figures are third-party estimates, not official data. Always note this when presenting such data.
Language Handling / 语言适配
Detect the user's language from their first message and maintain it throughout the conversation.
| User language | Response language | Number format | H5 keyword | Example output | |---|---|---|---|---| | 中文 | 中文 | 万/亿 (e.g. 1.2亿) | Use Chinese keyword if possible | "共找到 1,234 条素材" | | English | English | K/M/B (e.g. 120M) | Use English keyword | "Found 1,234 creatives" |
Rules:
- All text output (summaries, analysis, table headers, insights, follow-up hints) must match the detected language.
- H5 page generation: When using
generate_page: true, pass the keyword in the user's language so the generated page displays in the matching language context. - Field name presentation:
- Chinese → use Chinese labels: 应用名称, 开发者, 曝光量, 投放天数, 素材类型
- English → use English labels: App Name, Developer, Impressions, Active Days, Creative Type
- Error messages must also match: "未找到数据" vs "No data found".
- Data disclaimers: "⚠️ 下载量和收入为第三方估算数据" vs "⚠️ Download and revenue figures are third-party estimates."
- If the user switches language mid-conversation, follow the new language from that point on.
API Access
Base URL: https://api.admapix.com
Auth header: X-API-Key: $ADMAPIX_API_KEY
All endpoints use this pattern:
# GET
curl -s "https://api.admapix.com/api/data/{endpoint}?{params}" \
-H "X-API-Key: $ADMAPIX_API_KEY"
# POST
curl -s -X POST "https://api.admapix.com/api/data/{endpoint}" \
-H "X-API-Key: $ADMAPIX_API_KEY" \
-H "Content-Type: application/json" \
-d '{...}'
Interaction Flow
Step 1: Check API Key
Before any query, run: [ -n "$ADMAPIX_API_KEY" ] && echo "ok" || echo "missing"
Never print the key value. If missing, output:
🔑 You need an AdMapix API Key.
1. Go to https://www.admapix.com to register
2. Configure: openclaw config set skills.entries.admapix.apiKey "YOUR_KEY"
3. Try again 🎉
Step 1.5: Complexity Classification — 复杂度分类
Before routing, classify the query complexity to decide the execution path:
| Complexity | Criteria | Path | Examples | |---|---|---|---| | Simple | Can be answered with exactly 1 API call; single-entity, single-metric lookup | Skill handles directly (Step 2 onward) | "Temu排名第几", "搜一下休闲游戏素材", "Temu下载量", "Top 10 游戏" | | Deep | Requires 2+ API calls, any cross-entity/cross-dimensional query, analysis, comparison, or trend interpretation | Route to Deep Research Framework | "分析Temu的广告投放策略", "Temu和Shein对比", "放置少女的投放策略和竞品对比", "东南亚手游市场分析" |
Classification rule — count the API calls needed:
Simple (exactly 1 API call):
- Single search: "搜一下休闲游戏素材" → 1× search
- Single ranking: "iOS免费榜Top10" → 1× store-rank
- Single detail: "Temu的开发者是谁" → 1× unified-product-search
- Single metric: "Temu下载量" → 1× download-detail (after getting ID, but that's lookup+query=2, so actually Deep)
Deep (2+ API calls):
- Any query requiring entity lookup + data fetch: "Temu下载量" needs search→download = 2 calls → Deep
- Any analysis: "分析XX" → always multi-call → Deep
- Any comparison: "对比XX和YY" → always multi-call → Deep
- Any market overview: "XX市场分析" → always multi-call → Deep
- Any trend: "XX趋势" → always multi-call → Deep
In practice, only these are Simple:
- Direct keyword search with no analysis: "搜XX素材", "找XX广告"
- Direct ranking with no drill-down: "排行榜", "Top 10"
- Filter-options or param lookups
Default: If unsure, classify as Deep (prefer thorough over incomplete).
Execution paths:
→ Simple path: Continue to Step 2 (existing routing logic). At the end of the response, append a hint in the user's language:
- Chinese:
💡 需要更深入的分析?试试说"深度分析{topic}" - English:
💡 Want deeper analysis? Try "deep research on {topic}"
→ Deep path: Call the Deep Research Framework.
This is a 3-step process. Do NOT use [[reply_to_current]] until Step 3.
Step 1 — Submit the research task (returns instantly):
Run this exact command (only replace {user_query} and {additional_context}):
curl -s -X POST "https://deepresearch.admapix.com/research" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer test-local-token-2026" \
-d '{"project": "admapix", "query": "{user_query}", "context": "{additional_context}", "api_key": "'"$ADMAPIX_API_KEY"'"}'
projectis always"admapix"— do NOT change this.queryis the user's research question (in the user's language).contextis optional — add useful context such as "用户是游戏公司,关注二次元赛道" if relevant. Omit or set tonullif not needed.api_keypasses the user's API key to the framework — always include it as shown above.
This returns immediately with:
{"task_id": "dr_xxxx-xxxx-xxxx", "status": "pending", "created_at": "..."}
Extract the task_id value for Step 2.
Step 2 — Poll until done (use this exact script, do NOT modify):
Run this exact command, only replacing {task_id}:
while true; do r=$(curl -s "https://deepresearch.admapix.com/research/{task_id}" -H "Authorization: Bearer test-local-token-2026"); s=$(echo "$r" | grep -o '"status":"[^"]*"' | head -1 | cut -d'"' -f4); echo "status=$s"; if [ "$s" = "completed" ] || [ "$s" = "failed" ]; then echo "$r"; break; fi; sleep 15; done
This script polls every 15 seconds and exits only when the task is done. It may take 1-5 minutes. Do NOT interrupt it, do NOT add a loop limit, do NOT abandon it.
- When it finishes, the last line contains the full JSON result. Proceed to Step 3.
Step 3 — Format and reply to the user with the framework's report.
CRITICAL RULES:
- Do NOT send
[[reply_to_current]]before Step 2 completes — it will stop execution. - NEVER fall back to manual analysis. The framework WILL complete — just wait for it.
- NEVER write your own polling loop. Use the exact script above.
Processing the response JSON:
The completed response has this structure:
{
"task_id": "dr_xxxx",
"status": "completed",
"output": {
"format": "html",
"files": [{"name": "report.html", "url": "https://deepresearch.admapix.com/files/{task_id}/report.html", ...}],
"summary": "- Temu近30天广告投放以拉美和东南亚为核心\n- 视频素材占比超过95%\n- ..."
},
"usage": {"model": "gpt-5.4", "total_tokens": 377289, "research_time_seconds": 125.2}
}
Do NOT paste the full report into the chat. Instead:
- Take
output.summary(already formatted as bullet points) and present it directly as the key findings - Append the report link from
output.files[0].url:[📊 查看完整报告]({url}) - Add follow-up hints based on the summary content
If the task failed (status="failed"):
- The response will contain
"error": {"message": "..."}with a user-friendly reason - Present the error to the user and suggest they try again or simplify their query
- Do NOT try to manually replicate the analysis
Example output (Chinese):
📊 深度分析完成!
**核心发现:**
- AFK Journey 近30天投放覆盖全球,美国、墨西哥、巴西为Top3市场
- 视频素材占比约90%,图片约10%
- 投放媒体位以休闲游戏和工具类App为主(Blockudoku、Backgammon等)
- 2/18-2/23 与 3/14-3/16 出现投放峰值,可能对应版本更新或活动
👉 [查看完整报告](https://deepresearch.admapix.com/files/dr_xxxx/report.html)
💡 试试:"和RAID对比" | "看看素材" | "日本市场详情"
If Step 1 returns an error with "code": "api_key_required": The user's API key is missing or not configured. Output the same API key setup instructions from the "Check API Key" section above and stop.
If the framework is unreachable (connection refused/timeout on Step 1): Fall back to the existing Deep Dive logic (Step 2 → Deep Dive intent group).
Step 2: Route — Classify Intent & Load Reference
Read the user's request and classify into one of these intent groups. Then read only the reference file(s) needed before executing.
| Intent Group | Trigger signals | Reference file to read | Key endpoints |
|---|---|---|---|
| Creative Search | 搜素材, 找广告, 创意, 视频广告, search ads, find creatives | references/api-creative.md + references/param-mappings.md | search, count, count-all, distribute |
| App/Product Analysis | App分析, 产品详情, 开发者, 竞品, app detail, developer | references/api-product.md | unified-product-search, app-detail, product-content-search |
| Rankings | 排行榜, Top, 榜单, 畅销, 免费榜, ranking, top apps, chart | references/api-ranking.md | store-rank, generic-rank |
| Download & Revenue | 下载量, 收入, 趋势, downloads, revenue, trend | references/api-download-revenue.md | download-detail, revenue-detail |
| Ad Distribution | 投放分布, 渠道分析, 地区分布, 在哪投的, ad distribution, channels | references/api-distribution.md | app-distribution |
| Market Analysis | 市场分析, 行业趋势, 市场概况, market analysis, industry | references/api-market.md | market-search |
| Deep Dive | 全面分析, 深度分析, 广告策略, 综合报告, full analysis, strategy | Multiple files as needed | Multi-endpoint orchestration |
Rules:
- If uncertain, default to Creative Search (most common use case).
- For Deep Dive, read reference files incrementally as each step requires them — do NOT load all files upfront.
- Always read
references/param-mappings.mdwhen the user mentions regions, creative types, or sort preferences.
Step 3: Classify Action Mode
| Mode | Signal | Behavior |
|---|---|---|
| Browse | "搜一下", "search", "find", vague exploration | Single query, generate_page: true, return H5 link + summary |
| Analyze | "分析", "哪家最火", "top", "趋势", "why" | Query + structured analysis, generate_page: false |
| Compare | "对比", "vs", "区别", "compare" | Multiple queries, side-by-side comparison |
Default to Analyze when uncertain.
Step 4: Plan & Execute
Single-group queries: Follow the reference file's request format and execute.
Cross-group orchestration (Deep Dive): Chain multiple endpoints. Common patterns:
Pattern A: "分析 {App} 的广告策略" — App Ad Strategy
POST /api/data/unified-product-search→ keyword search → getunifiedProductIdGET /api/data/app-detail?id={id}→ app infoPOST /api/data/app-distributionwithdim=country→ where they advertisePOST /api/data/app-distributionwithdim=media→ which ad channelsPOST /api/data/app-distributionwithdim=type→ creative format mixPOST /api/data/product-content-search→ sample creatives
Read api-product.md for step 1-2, api-distribution.md for step 3-5, api-creative.md for step 6.
Pattern B: "对比 {App1} 和 {App2}" — App Comparison
- Search both apps → get both
unifiedProductId app-detailfor each → basic infoapp-distribution(dim=country)for each → geographic comparisondownload-detailfor each (if relevant) → download trendsproduct-content-searchfor each → creative style comparison
Pattern C: "{行业} 市场分析" — Market Intelligence
POST /api/data/market-searchwithclass_type=1→ country distributionPOST /api/data/market-searchwithclass_type=2→ media channel sharePOST /api/data/market-searchwithclass_type=4→ top advertisersPOST /api/data/generic-rankwithrank_type=promotion→ promotion ranking
Pattern D: "{App} 最近表现怎么样" — App Performance
- Search app
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
crawl4ai
87.4kOfficial Crawl4AI Cloud: a hosted web scraping, extraction, and search API for AI agents. Free API key, 1,000 credits a month, no card. Fully open source: this repo is the Apache-2.0 crawler that powers it, and you can self-host it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
