feat(harness): discover skills progressively
This commit is contained in:
@@ -0,0 +1,21 @@
|
||||
---
|
||||
name: ads-analysis
|
||||
description: Use when analyzing the bundled mock advertising account, identifying campaign anomalies, or recommending budget and creative actions from mock ad metrics.
|
||||
---
|
||||
|
||||
# Ads Analysis
|
||||
|
||||
Call `mock_ads_metrics` before calculating, comparing, or explaining any account or campaign metric.
|
||||
|
||||
Treat every returned value as fixture data. Never describe it as live, connected, or sourced from a real advertising platform. State the available date range when presenting results.
|
||||
|
||||
Base all numeric claims on the tool response. Images may provide supporting creative context, but never use an image to invent or override spend, impressions, clicks, conversions, or revenue.
|
||||
|
||||
Analyze the account in this order:
|
||||
|
||||
1. Summarize spend, impressions, clicks, conversions, and revenue.
|
||||
2. Compare campaigns using derived efficiency metrics such as CTR, CPC, CPA, CVR, and ROAS when their denominators are non-zero.
|
||||
3. Flag meaningful outliers and explain the evidence for each flag.
|
||||
4. Recommend concrete budget, targeting, or creative actions, separating evidence from inference.
|
||||
|
||||
If the requested range is unavailable, explain the limitation instead of extrapolating beyond the fixture.
|
||||
Reference in New Issue
Block a user