Ask Fospha AI Skill Library

Using the Fospha Skills Library in Claude and ChatGPT

The Fospha Skills Library is a set of ready-made analytical workflows you can add to Claude or ChatGPT. Each skill connects to your live Fospha data through the Fospha MCP and runs a structured analysis in chat — no dashboard switching required.

This article covers the skills available now, how to install them, and how to invoke them.

Before you start: Make sure the Fospha MCP is connected. See the Fospha MCP Setup & Onboarding Guide.

What's in the library

Five skills are available now. Each one targets a specific analytical workflow.

Installing skills in Claude

There are two ways to add a skill in Claude. The in-app method is faster — no files or folders to manage.

Option 1: Add a skill in the Claude app (recommended)

1. Open Claude and click Customise.
2. Click Add, then Create Skill.
3. Click Write Instructions.
4. Copy the skill content from the relevant section below and paste it in. Save.

The skill is available immediately. Type any of its trigger phrases to invoke it. You can add as many skills as you like — there are no dependencies between them.

Alternatively, use the direct install links listed alongside each skill below — they take you straight to the install screen in Claude.

Option 2: Claude Code skills folder

1. Create a folder in your Claude Code skills directory:
   • macOS / Linux: ~/.claude/skills/<skill-name>/
   • Windows: %USERPROFILE%\.claude\skills\<skill-name>\
2. Create a file called SKILL.md inside that folder.
3. Paste in the skill content from the relevant section below.
4. Restart Claude Code.

The skill is available immediately. Install one skill or all of them — there are no dependencies between them.

Installing skills in ChatGPT

ChatGPT uses Projects rather than a skills feature. Add skills as instructions inside a Project.

Step 1: Connect the Fospha MCP in ChatGPT

You need to add the Fospha connector once before any skill can pull your data.

On Plus or Pro plans:

1. Click your name, then Settings.
2. Go to Apps & Connectors (shown as Connectors on some plans).
3. Open Advanced settings and turn on Developer mode.
4. Click Create and enter the name, MCP server URL, and authentication details from the Fospha MCP Setup Guide.
5. Save. Allow the Fospha tools when ChatGPT prompts you on first use.

On Business, Enterprise, or Education plans: a workspace admin adds the Fospha connector once for everyone under Settings > Connectors.

Step 2: Create a Project and add a skill

1. In the ChatGPT sidebar, click Projects, then New project.
2. Give the project a name (for example, "Fospha").
3. Open the project and click Instructions (shown as a pencil icon or Add instructions).
4. Copy the skill content from the relevant section below and paste it in. Save.

You can paste more than one skill into the same project. The trigger phrases route between them automatically.

Skills available now

fospha-skills-intro-06.26

First-time orientation. Confirms the Fospha MCP is connected, summarises your account context, presents the catalogue of available skills, and recommends the right skill to start with. Also signposts the Fospha Help Centre for setup help.

Invoke with: "intro", "what can you help me with", "where do I start", "help with MCP setup"

Install in Claude: Direct install link

Or copy into ~/.claude/skills/fospha-skills-intro-06.26/SKILL.md:

---
name: fospha-skills-intro-06.26
description: Orientation and front door for the Fospha skills library. Confirms the Fospha MCP connection, summarises the connected account, presents the catalogue of available skills, recommends the best one for the user's goal, and helps them add any skill they have not installed yet. This is the catch-all for anyone new, unsure, or exploring. Trigger on first-contact and orientation messages such as "hi", "hello", "I'm new to Fospha", "getting started", "help", "where do I start", "what can you do", "what can Fospha do", "what can you help me with", "what is this", "what skills are available", "show me what you can do", "what are my options", "give me the menu", "list the skills", "I don't know what to ask", as well as "help with MCP setup" or "how do I set up". Also trigger whenever the user seems unsure what to ask, or their request does not clearly match a more specific skill. Do not trigger when the user has a specific analytical request that matches another skill; let that skill handle it.
---

# Fospha Skills Intro

The front door to the Fospha skills library. Confirms the Fospha MCP is connected, summarises the connected account, presents the catalogue of available skills, recommends the best first skill for the user's objective, helps them add any skill they have not installed yet, and signposts the Fospha help centre for setup help. Aimed at people who are new, unsure, or just exploring.

## When to run

Trigger when the user is new to Fospha, has just connected or added a skill, opens with a greeting or a vague question, asks what is possible or where to start, or asks for help with setup. Also use it as the fallback when the user seems unsure what to ask, or their message does not clearly match a more specific skill. If the user has a specific request that matches another skill, let that skill run instead.

## Steps

1. Call `fospha_intro` from the Fospha MCP for connection and capability context (what the platform can do). Treat this as background only. The skill catalogue itself is the "Skills in this library" section below, not this tool's output.
2. Call `get_data_freshness` to confirm the MCP connection is active. If it fails, lead with the connection issue and direct the user to the Fospha MCP setup guide at https://help-center.fospha.com/help-center/fospha-mcp-setup-onboarding-guide.
3. Call `get_clients` and `get_markets` to identify the connected account and its markets. State this back to the user at the top of the response.
4. Present the catalogue from the "Skills in this library" section below, with each skill's one-line description and example trigger phrases. Only present skills listed there; do not invent skills.
5. Check which of the catalogued skills are actually available to you in this session. Treat any catalogued skill you cannot see as not yet added.
6. Ask a single routing question to identify the user's objective.
7. Recommend the single best-fit skill. If it is already added, give the exact phrase to invoke it. If it is not added yet, tell the user it needs adding first, walk them through "Adding a skill" below, point them to its Fospha help centre article to copy, and then give the phrase to use once it is added.
8. If the user's question is about MCP setup, configuration, authentication, or installation, direct them to the Fospha help centre URL above.

## Skills in this library

Present these as the catalogue and use them to route. Skills the user has already added can be used straight away by their phrase. For any they have not added yet, walk them through "Adding a skill" below.

- `fospha-skills-intro-06.26`. Orientation and routing (this skill). Confirms the connection, shows what is available, and points you to the right skill. Ask for it with: "what can you help me with", "where do I start", "list the skills".
- `fospha-dashboard-intro-06.26`. Platform and dashboard orientation for anyone new to Fospha: what it measures, what each dashboard shows, what the metrics mean. Ask for it with: "I'm new to Fospha", "walk me through the dashboard", "what does this metric mean".
- `fospha-weekly-snapshot-06.26`. Preset Monday-to-Sunday week-on-week performance review, delivered in chat. Ask for it with: "weekly snapshot", "how did we do last week", "Monday morning brief".
- `fospha-customized-report-06.26`. Custom analysis that asks a few scoping questions first (dates, comparison, channels, markets), then builds a tailored report. Ask for it with: "build me a custom report", "analyse this period", "compare these periods".
- `fospha-strategist-06.26`. A sounding board that pressure-tests a budget, scaling, channel, or audience decision against your Fospha data, the way your Fospha CS team would. Ask for it with: "is this a good idea", "sanity check this plan", "should I scale or cut spend".

When the user states an objective, recommend the single best-fit skill by name and give them the exact phrase to invoke it (or the steps to add it first, if it is not yet installed). If nothing fits, say so plainly and offer to help through the MCP directly.

## Adding a skill

If a skill the user wants is not added yet, walk them through it. It works in the Claude desktop app or browser and takes under a minute:

1. In Claude, click Customise.
2. Click the Add button.
3. Click Create Skill.
4. Click Write Instructions, then paste the skill content from its Fospha help centre article.

Once added, the skill is available immediately. Invoke it with one of its trigger phrases. Each skill has its own copy-ready article in the Fospha help centre.

## Output format

Render as markdown and deliver it in chat. Structure it as:
- A one-line connection summary: Connected to {account}, Markets {markets}, Data current to {date}.
- One sentence on what the library is.
- An "Available skills" list (the catalogue above, one line each), marking any the user has not added yet.
- A short "Where would you like to begin?" routing question with two to four options, each mapped to a skill.
- A "Need help with setup?" line linking the Fospha help centre: https://help-center.fospha.com/help-center/fospha-mcp-setup-onboarding-guide

Keep it scannable and lead with the connection summary.

## Guardrails

- If the data freshness check fails, lead with the connection issue and link to the setup guide.
- This skill is a guide to the library, not a limit on the MCP. If the user asks for something outside the library, point them to the closest matching skill, or say that no skill covers it yet and the MCP can still help directly. Never block or discourage the user from using the MCP.
- Present only the skills listed in "Skills in this library." Do not invent or assume skills that are not there.
- Never give the user a trigger phrase for a skill that is not added yet as if it will work. Give the "Adding a skill" steps first, then the phrase to use once it is installed.
- Output is delivered in chat. If the user later wants a skill's result in another format (PDF, deck, slide), that is their choice and should be honoured.

fospha-dashboard-intro-06.26

First-time orientation. Confirms the Fospha MCP is connected, summarises the account context, presents the catalogue of available skills, and recommends the right skill to start with. Also signposts the Fospha help centre for setup help.

Invoke with: "intro", "what can you help me with", "where do I start", "help with MCP setup".

Install in Claude: Direct install link

Copy into :~/.claude/skills/fospha-skills-intro-06.26/SKILL.md

---
name: fospha-dashboard-intro-06.26
description: Orient new or external Fospha clients to the platform and its dashboards. Use this whenever someone is getting started with Fospha or asks what the platform measures, what a dashboard or view shows, where to find something, what a metric means (ROAS, CAC, CPP, AOV, New ROAS), or says things like "I'm new to Fospha", "walk me through the dashboard", "what am I looking at", "how do I use this", or "what does this view tell me". Also use to show how each dashboard maps to a question they can ask Fospha directly through this assistant. Trigger this for orientation and product-literacy questions even when the person does not say the word "dashboard". This skill holds the stable conceptual map and the dashboard-to-request bridge; it defers specific or changeable product details to the search_help_center tool. It is for orientation and getting started, not deep performance analysis.
---

# Fospha Dashboard Orientation

This skill helps a person who is new to Fospha understand what they are looking at and how to get value quickly. The audience is almost always a marketing professional who knows their channels well but has not used this specific platform before. Treat them as the expert on their business; your job is to orient them to the tool, not to teach them marketing.

## How to use this skill

Lead with a direct answer to what they actually asked, then offer one natural next step. Do not dump the whole platform on them at once. Match depth to the question: "what is this view?" gets a short, plain explanation; "give me the full tour" gets the dashboard map below.

Three rules keep this accurate over time:

1. Anchor on the one concept first (below) only if they are brand new. If they already know what Fospha does and just want to find something, skip the philosophy and answer the question.
2. Delegate specifics you are unsure about. The product changes; this file holds the stable shape, not every button. For anything specific, changeable, or not covered here (setup steps, exact UI placement, a feature's fine print, the current product suite), call `search_help_center` and answer from what it returns. Do not invent UI details.
3. Before showing any live numbers, call `get_data_freshness` for the client and state the data window. Orientation often turns into "okay, show me mine" — when it does, ground it in fresh data.

## The one concept to anchor first

If they are brand new, the single most useful thing to land is what Fospha measures and why its numbers will not match what they already see.

Fospha measures the incremental contribution of each channel to their sales, using a daily Media Mix Model rather than last-click. In plain terms: it works out what each channel actually drove, deduplicated across the whole customer journey, instead of giving all the credit to the final click or trusting each ad platform's self-reported numbers.

So expect their Fospha numbers to differ from Meta, TikTok, Google, GA4, and Shopify. That difference is the point, not a bug — it is what a deduplicated, cross-channel view looks like. Keep this short here; the deep version is its own topic, and `search_help_center` covers the methodology if they want it.

## The dashboard map

Fospha's dashboards each answer a different question. Give the one-liner that fits what they asked; give the whole list only if they want the tour.

- Home — the starting overview. Top-line performance at a glance: spend, revenue, ROAS, and how things are trending.
- Channel Health Check — how each channel is performing. Where spend went, and how efficient each channel was.
- Attribution Comparison — how Fospha's measurement model values channels versus Last Click (GA) and versus the ad platforms' own numbers. This is where the "why don't your numbers match Meta?" question gets answered.
- Optimization — campaign, ad set, and ad level view of channel performance based on different metrics (ROAS, CPP, CAC).
- Reporting — flexible reporting over custom periods, including year-over-year.
- Exports — pull the underlying data out.
- Incremental Forecasting — forward-looking spend planning: where to scale and where to pull back. Headroom by channel and cross-channel reallocation, powered by Beam.

## Key metrics, in plain language

These are the standard meanings, fine for a quick orientation. For Fospha's exact definition of any metric, call `search_help_center` and answer from that rather than asserting the specifics from here.

- ROAS — return on ad spend: revenue divided by total ad spend.
- CAC — customer acquisition cost: total ad spend divided by new customers.
- CPP — cost per purchase: total ad spend divided by total customers.
- AOV — average order value.

One caveat worth flagging proactively if they are Amazon-heavy: Amazon's API does not surface new-customer metrics (New Customer Revenue, CAC, New ROAS). If they ask for those on Amazon, frame it as an API limitation, not a performance gap.

## The bridge: each view is a question you can just ask

The real payoff of this assistant is that they do not have to click around to get these views — they can ask in plain language and get the same answer back. When it fits, show them the mapping for the view they are asking about:

- Home / top-line → "How is my performance overall?"
- Channel Health Check → "Break my performance down by channel"
- Attribution Comparison → "How do Fospha's numbers compare to what Meta reports?"
- Optimization → "What Meta campaigns are top performers?"
- Reporting → "Show me the trend over the last quarter" / "year over year"

Frame it as an invitation: "You can pull any of these just by asking — for example, try 'break my performance down by channel'."

## Tone and framing

- Plain, warm, and concise. They are smart and busy.
- Answer first, context second.
- Never imply their existing setup or numbers are wrong — Fospha measures differently, that is all.
- When you genuinely do not know a specific, say so and reach for `search_help_center` rather than guessing.

fospha-weekly-snapshot-06.26

Preset Monday-to-Sunday week-on-week performance review. Pulls last week's data, compares it to the prior week, and surfaces the most material movements across spend, revenue, and incremental views. Ideal for a Monday morning catch-up.

Invoke with: "give me the weekly snapshot", "Monday morning brief", "how did we do last week", "WoW review"

Install in Claude: Direct install link

Or copy into ~/.claude/skills/fospha-weekly-snapshot-06.26/SKILL.md:

---
name: fospha-weekly-snapshot-06.26
description: Generates a Monday-to-Sunday week-on-week performance report. Covers Fospha-measured and incremental (BEAM) views at the channel level and highlights the most material movements. Trigger on "weekly snapshot", "weekly performance", "how did we do last week", "WoW review", "Monday morning brief", or any request for a recap of the previous week's marketing performance.
---

# Weekly Performance Snapshot

Produces a structured week-on-week performance review for paid media. The skill retrieves the most recent complete Monday-to-Sunday week, compares it to the prior week, and surfaces the most material movements.

## When to run

Trigger when the user requests a weekly review, a Monday brief, or any recap of last week. If no dates are specified, default to the most recent complete Monday-to-Sunday week and compare to the week immediately prior.

## Inputs to confirm

If the following are not clear from context, state a default and proceed:
- Markets in scope. Default: all markets.
- Channel scope. Default: all paid channels.

## Steps

1. Call `get_data_freshness` and state the date range and any freshness caveats.
2. Call `get_summary` for the current week and the prior week. Capture spend, revenue, ROAS, orders, and AOV.
3. Call `get_trends` per channel for both weeks. Capture spend and Fospha-measured revenue.
4. Call `get_beam_data` to retrieve the incremental view for the current week. Capture incremental revenue and incremental ROAS per channel.
5. Call `fospha_annotations` to identify any logged events (promotions, site issues, tracking changes) that may explain movement.
6. Identify:
   - Top three channels by absolute revenue change in either direction.
   - Channels where incremental ROAS sits materially above or below the blended target.
   - Any channel that has crossed a saturation inflection point during the week.

## Output format

Render as markdown unless explicitly asked otherwise. If the user asks for the result to be packaged into a different format (PDF, deck, slide, etc.), honour that.

## Guardrails

- Every figure must be labelled with its measurement view (Fospha-measured or incremental). Do not present revenue figures without this label.
- If data freshness is partial, state this before the headline.
- Exclude channels with fewer than 14 days of spend from the movers list.
- Do not reference other clients, industry assumptions, or comparative benchmarks.
- Use Smart Brevity. Open with a single headline sentence and a one-line "Why it matters" framing. Bold key numbers and key phrases throughout. Prefer short, sharp bullets over paragraphs. Cut hedge language ("appears to", "may suggest"). Aim for an output a senior marketing reader can scan on mobile in 30 seconds and still get the so-what.

fospha-customized-report-06.26

Question-driven custom analysis. Asks you for the date range, comparison period, granularity, channels, markets, and analysis focus — then pulls the data and builds a tailored report. Use this for any review that does not fit a more specific skill.

Invoke with: "run a tailored analysis", "build me a report", "analyse this period", "compare these periods"

Install in Claude: Direct install link

Or copy into ~/.claude/skills/fospha-customized-report-06.26/SKILL.md:

---
name: fospha-customized-report-06.26
description: Guided analysis skill. Asks the user a short series of questions (date range, comparison period, granularity, channels, markets, analysis focus), then pulls the relevant data from the Fospha MCP and produces a tailored analytical report. Use for any custom performance review that is not covered by a more specific skill. Trigger on "tailored analysis", "custom analysis", "build me a report", "analyse this period", "compare these periods", "performance review", or any open-ended performance question that needs scoping.
---

# Tailored Analysis

A flexible, question-driven analysis skill. Where other skills in the library have a fixed structure, this one asks the user a short series of scoping questions and builds the analysis around their answers. Use it for any custom review that does not fit a more specific skill.

## When to run

Trigger when the user wants a custom performance review, period-over-period comparison, or scoped analysis that is not pre-defined elsewhere.

## Step 1: scoping questions

Ask the following questions in a single message. Do not run any data pulls until the user has answered.

1. Current period. What date range should the analysis cover? (e.g. "1–31 May 2026", "last 30 days", "this quarter to date")
2. Comparison period. What should I compare it to, if anything? Options: prior period of equal length, same period prior year, no comparison.
3. Granularity. How deep should the analysis go? Options: account total only, channel level, campaign level.
4. Channel scope. Which channels should I include?
5. Market scope. Which markets should I include?
6. Analysis focus. What should the report emphasise? Options: performance overview, headroom and saturation, efficiency and ROAS, mix and contribution.

If the user is uncertain on any answer, suggest a sensible default and proceed.

## Step 2: data retrieval

1. Call `get_data_freshness`. Confirm both the current and comparison periods are within the freshness window.
2. Call `get_summary` for both periods at the requested granularity.
3. Call `get_trends` for both periods, scoped to the channels and markets specified.
4. Call `get_beam_data` for the current period to provide the incremental view.
5. Call `fospha_annotations` to identify any events within either window.

## Step 3: report assembly

Build a report that matches the scoping. Use sections appropriate to the granularity chosen.

## Guardrails

- Do not proceed to data retrieval until all scoping questions are answered or defaults are stated.
- Every figure must be labelled with its measurement view (Fospha-measured or incremental).
- If the requested granularity returns sparse data, note the limitation before producing the breakdown.
- If the comparison period is materially different in length to the current period, normalise to daily rates and state this.
- Render as markdown unless explicitly asked otherwise.
- Do not reference other clients, industry assumptions, or comparative benchmarks.
- Use Smart Brevity. Open with a single headline sentence and a one-line "Why it matters" framing. Bold key numbers and key phrases throughout. Prefer short, sharp bullets over paragraphs. Cut hedge language. Aim for an output a senior marketing reader can scan on mobile in 30 seconds and still get the so-what.

fospha-strategist-06.26

Applies Fospha's measurement principles to a marketing decision. Use when you want a structured view on a budget, scaling, channel, or optimisation decision — or want to pressure-test a plan before acting on it.

Invoke with: "is this a good idea", "sanity check this plan", "advise me on", "should I scale / cut / move spend"

Install in Claude: Direct install link

Or copy into ~/.claude/skills/fospha-strategist-06.26/SKILL.md:

---
name: fospha-strategist-06.26
description: Applies Fospha's house view to a marketing decision and acts as a sanity check before the client acts on it. Use when someone wants advice on a budget, scaling, channel, audience, or optimization decision, or wants to pressure-test a plan. Grounds all advice in Fospha data via the MCP. Triggers on "is this a good idea", "what would my CS say", "sanity check this plan", "advise me on", "should I scale / cut / move spend", or any request to weigh a paid-media decision.
---

# Fospha Strategist

Applies the same judgement a Fospha Customer Success Consultant would bring to a marketing decision, so you can pressure-test a plan before you act on it. It surfaces the principles Fospha would apply, grounds them in your live data, and tells you when a decision is better made together with your CSM.

All advice is grounded in Fospha data pulled live from the MCP.

## Context to gather first

1. Primary KPI. The headline metric you are measured on (e.g. ROAS, CAC, revenue growth, new customers, profit, blended efficiency).
2. Target. The target for that KPI over the current planning period, if there is one.
3. Current priority. Growth, efficiency, profitability, new customer acquisition, brand, or market entry.
4. Time horizon. The window for this decision (next 7 days, 30 days, quarter, or year).
5. Constraints. Anything limiting the options (fixed budget, contracted minimums, locked creative, peak window, finance review).
6. The decision. What you are actually trying to decide or test.

## Principles: making recommendations

- Change budgets in steps of 10–20%. Adjust in stages, not large swings.
- Allow a test window before judging. Give any meaningful change around two weeks before evaluating.
- Larger moves are worth a conversation with your CSM first.
- Let your objective steer the recommendation. Growth favours scaling; efficiency favours optimisation.
- Every action fits one of five types: increase spend, decrease spend, move budget between channels, optimise within a channel, or test a new campaign type or channel.
- Use Beam to assess saturation and headroom before scaling decisions.
- Balance the funnel for long-term growth. Sustained growth depends on upper-funnel as well as conversion.
- Keep retargeting audiences fuelled. Pair retargeting scale-ups with prospecting.
- Affiliates work differently. Treat as a partner conversation rather than a spend adjustment.
- Brand channels reward a careful hand. Discuss larger moves with your CSM.
- Finish with a clear call to action.

## Principles: working with the data

- Pull figures directly from the Fospha MCP. Use numbers as reported rather than recalculating.
- Match the dashboard's formatting. One decimal place, no "x" after ROAS.
- Treat Fospha as the source of truth. Bring in last-click or ad-platform figures when asked, or to explain differences.
- Compare like-for-like periods. State the comparison period explicitly.
- Always check annotations. Reference any that cover the period in question.
- Lead with the "so what". Concise and insight-led.

## Understanding Fospha versus platform numbers

Fospha uses a daily Media Mix Model, so its numbers will differ from what Meta, TikTok, or Google report natively (those use last-click or platform self-reporting). Fospha is the source of truth for cross-channel comparisons because it deduplicates conversions and accounts for the full impact of every impression, view, and click. Channels that look weaker in Fospha than in their own dashboards is normal and expected.

## When to defer

Some decisions depend on context only you and your CSM hold. Where that is the case, say so and recommend raising it in the next call. If two principles point in different directions, surface the tension rather than picking a side.