Skill instructions
ai-visibility-setup1.77 KB
View saved version →
---
name: ai-visibility-setup
description: Set up or change what Maxed tracks in AI assistants. Use to draft a new tracked topic, to add, edit, pause, resume or archive tracked prompts and audiences (personas), to plan tracking for a new product, service or location in AI assistant answers, or to review the current tracking setup before changing it. Examples include "what should I track for plumbing in Denver," "add a prompt," "pause these prompts," "who are my personas."
---
# AI visibility setup
This skill covers changes to Maxed's AI visibility tracking. To read results instead, use the search-and-ai-visibility skill.
## Steps
1. If you don't have an account id, call `list_accounts`. Call `get_business_context` so topics and personas fit the business.
2. Read the current setup before changing anything: `aeo_list_topics`, `aeo_get_topic`, `aeo_list_audiences`, `aeo_list_prompts`. Never assume what exists.
3. Before planning more than one new topic, check `aeo_plan_limits` so the plan fits the account's allowance.
4. For a new topic, call `list_playbooks` and follow the playbook for starting to track a topic. Starting, pausing or archiving a whole existing topic is done in the Maxed app, under AI Visibility > Topics: tell the user where.
5. For prompts and audiences, call the matching tool (`aeo_create_prompt`, `aeo_update_prompt`, `aeo_set_prompt_status`, `aeo_create_audience`, `aeo_update_audience`, `aeo_archive_audience`), passing only what changes. Updates replace the saved wording, so confirm the new text with the user first.
6. Afterwards, say what changed and when the next readings arrive.
## Don't
- Don't create audiences or prompts the user hasn't seen and agreed to.
- To retire a tracked item, archive or pause it. Never discard anything except an unused draft topic.
getting-started2.28 KB
View saved version →
---
name: getting-started
description: First steps with Maxed, and the fallback for any marketing request no other Maxed skill covers. Use when someone connects Maxed, asks what Maxed can do, asks "what should I look at," wants a tour of their connected marketing data, or asks a broad marketing question about their own business ("how is my marketing doing," "what should I know," "why did sales change," "what's working"). Loads the business profile and connected platforms, finds the matching Maxed playbook and follows it.
---
# Getting started with Maxed
Maxed holds this business's real marketing data (ads, analytics, search, social, store, AI visibility) and a library of expert playbooks. The playbooks change often, so they are never copied into this skill. Always fetch them live.
## Steps
1. Call `get_business_context` and `list_playbooks` together. If you don't have an account id, call `list_accounts` first. When the user has only one account, use it without asking.
2. Read the playbook summaries and pick the one that fits the request. For a broad "how am I doing" question, pick the cross-channel analyst playbook. For a first look around the account, pick the orientation playbook.
3. Call `get_playbook` with that playbook's exact key and follow it. The playbook's method overrides this skill. The user's explicit instructions override both.
4. Ground every claim in this account's numbers from the marketing data and AI visibility tools. Never give generic advice instead.
## When the user is new
- Say briefly what's connected (from `get_business_context`) and what Maxed can do with it.
- Offer two or three of the playbooks' `starterPrompts` as next asks. Pick ones that need platforms the user has connected.
- If the business profile is incomplete (`complete: false`), mention that filling it in at Maxed sharpens every answer.
- Maxed can notify you when new data lands: new AI-visibility readings, a finished scheduled report, a newly connected platform or its first import. When the user wants to keep an eye on something, offer to watch for it.
## Don't
- Don't answer marketing questions from general knowledge before checking `list_playbooks`.
- Don't name or guess playbook keys. Always use the keys `list_playbooks` returns.
- Don't trigger for requests unrelated to the user's marketing.
paid-ads1.5 KB
View saved version →
---
name: paid-ads
description: Paid advertising on Google Ads, Meta (Facebook and Instagram ads) and other connected ad platforms. Use for ad performance, spend, budget, ROAS, CPA, conversions, campaigns, ad sets, keywords and search terms, negative keywords, Performance Max, creative fatigue, wasted spend and where to scale. Examples include "how are my ads doing," "why did my ROAS drop," "which campaigns should I pause," "which search terms waste money," "where should I spend more." Routes to the matching live Maxed playbook.
---
# Paid ads
The method for paid-ads work lives in Maxed's playbooks, which are updated often. This skill only routes to them.
## Steps
1. Call `list_playbooks` and `get_business_context`. If you don't have an account id, call `list_accounts` first.
2. Pick the paid-ads playbook whose summary best fits the request: a broad review, a sweep for problems, a scan for opportunities, a single campaign, or search terms. If it's about writing new ads rather than reading performance, pick the ad creative playbook.
3. Call `get_playbook` with its exact key and follow it. Use `list_marketing_tables`, `describe_marketing_table` and `query_marketing_data` for the numbers.
4. If no ad platform is connected (check `list_accounts`), say so and suggest connecting Google Ads or Meta in Maxed. Don't invent figures.
## Don't
- Don't recommend budget or campaign changes without this account's numbers behind them.
- Don't name or guess playbook keys. Always use the keys `list_playbooks` returns.
reports-and-strategy1.77 KB
View saved version →
---
name: reports-and-strategy
description: Marketing reports and big-picture decisions. Use for performance summaries for a boss, client or team, for daily, weekly or monthly scheduled reports that Maxed writes and emails automatically (set up, change, pause, run now, read past runs), for cross-channel "how is everything doing" analysis, and for strategic decisions that benefit from several expert perspectives ("which direction is stronger," "challenge my thinking," "what am I missing," "ask my Marketing Council"). Routes to the matching live Maxed playbook.
---
# Reports and strategy
The method for this work lives in Maxed's playbooks, which are updated often. This skill only routes to them.
## Steps
1. Call `list_playbooks` and `get_business_context`. If you don't have an account id, call `list_accounts` first.
2. Pick the playbook whose summary best fits the request:
- A one-off summary for someone else calls for the performance report playbook.
- A report that should repeat on a schedule calls for the recurring report playbook.
- Understanding results across channels calls for the analyst playbook.
- A decision between directions calls for the Marketing Council.
3. Call `get_playbook` with its exact key and follow it.
## Scheduled reports
- Draft a real first report with the user before saving anything.
- Save it with `create_report_template` only after the user agrees.
- Read existing reports with `list_report_templates` before creating a new one, so you don't duplicate one.
- Each run uses part of the account's monthly report allowance, so mention it when it matters.
## Don't
- Don't email a report to anyone the user hasn't named. Recipients must be members of the account.
- Don't name or guess playbook keys. Always use the keys `list_playbooks` returns.
search-and-ai-visibility1.76 KB
View saved version →
---
name: search-and-ai-visibility
description: How people find the business on Google and in AI assistants. Use for organic search and SEO (Search Console clicks, impressions, rankings, branded vs non-branded queries, pages close to page one), for AI visibility (how often AI assistants mention the brand, which sites they cite, which prompts miss the brand, competitors in AI answers), and for website content and FAQs built to win those searches. Routes to the matching live Maxed playbook.
---
# Search and AI visibility
The method for this work lives in Maxed's playbooks, which are updated often. This skill only routes to them.
## Steps
1. Call `list_playbooks` and `get_business_context`. If you don't have an account id, call `list_accounts` first.
2. Pick the playbook whose summary best fits the request:
- Google search performance calls for the organic search playbook.
- Brand mentions and citations in AI answers call for the AI visibility playbook.
- Starting to track AI visibility, or an AI visibility question on an account with no topics yet, calls for the topic setup playbook.
- Writing FAQs or site content calls for the FAQ / content playbook.
3. Call `get_playbook` with its exact key and follow it.
4. Use the `aeo_` tools for AI visibility numbers and the marketing data tools for Search Console.
## Reading AI visibility
- AI answers vary day to day. Look for sustained patterns over several days, not one day's change.
- A platform that failed to answer is not the same as a zero. Report the two separately.
## Changing what Maxed tracks
If the user wants to add, edit or pause tracked topics, audiences or prompts, use the ai-visibility-setup skill instead.
## Don't
- Don't name or guess playbook keys. Always use the keys `list_playbooks` returns.
social-and-content1.39 KB
View saved version →
---
name: social-and-content
description: Social media and marketing content. Use for organic Instagram, Facebook and TikTok performance (breakout posts, what's working, account trends), for writing ad copy and new ad concepts based on what already performs, and for drafting LinkedIn posts grounded in the business's real results. Examples include "which posts took off and why," "write new ad variations from my best ad," "turn this month's results into a LinkedIn post." Routes to the matching live Maxed playbook.
---
# Social and content
The method for this work lives in Maxed's playbooks, which are updated often. This skill only routes to them.
## Steps
1. Call `list_playbooks` and `get_business_context`. If you don't have an account id, call `list_accounts` first.
2. Pick the playbook whose summary best fits the request:
- Reading social performance calls for the organic social review.
- Writing ads calls for the ad creative playbook.
- Writing LinkedIn posts calls for the LinkedIn post builder.
3. Call `get_playbook` with its exact key and follow it.
4. Base content on the account's real performance and verified business facts from `get_business_context`. Never invent results, testimonials or personal experiences.
## Don't
- Don't post or publish anything. Maxed drafts content; the user publishes it.
- Don't name or guess playbook keys. Always use the keys `list_playbooks` returns.
website-and-sales1.47 KB
View saved version →
---
name: website-and-sales
description: Website conversion and online sales. Use for GA4 traffic and conversion rate by source, device or page, for Shopify revenue, orders, average order value, refunds, new vs returning customers and product mix, and for reconciling what ad platforms claim against GA4 and Shopify (attribution gaps, true ROAS, blended return across channels). Examples include "why did my store revenue drop," "is my website converting worse," "do my ads really drive these sales." Routes to the matching live Maxed playbook.
---
# Website and sales
The method for this work lives in Maxed's playbooks, which are updated often. This skill only routes to them.
## Steps
1. Call `list_playbooks` and `get_business_context`. If you don't have an account id, call `list_accounts` first.
2. Pick the playbook whose summary best fits the request:
- Website conversion calls for the conversion diagnostic.
- Store revenue and orders call for the ecommerce momentum playbook.
- Comparing what ad platforms claim with business results calls for the cross-channel reconciliation playbook.
3. Call `get_playbook` with its exact key and follow it. Use the marketing data tools for the numbers.
4. If GA4 or Shopify isn't connected, say which one the question needs. Don't estimate the missing figures.
## Don't
- Don't declare one data source "correct" when sources disagree. Explain why they differ.
- Don't name or guess playbook keys. Always use the keys `list_playbooks` returns.