> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/ai-solutions/mcp-skills/brand-skills/brand-program-health-check-skill.md).

# Brand Program Health Check Skill

Use this skill to get a fix-it list for a brand program, ranking what needs attention across concentration, mix, quality, efficiency, and partner momentum. It delivers a markdown health check with up to seven severity-ranked findings, each pointing to the right sibling skill for a deeper dive, and exactly three next actions.

For a full partner leaderboard, use the [Brand Partner Performance Scorecard](/ai-solutions/mcp-skills/brand-skills/brand-partner-performance-scorecard-skill.md) instead.

### Prerequisites

* MCP access enabled on your impact.com brand account.
* Client connected per [MCP Quick Start](/ai-solutions/mcp-quick-start.md).

### Install the skill

{% file src="/files/yGoCBO5TjRxM7CTExnc6" %}

1. Download or copy the skill package above.
2. Install it in Claude, Cursor, or VS Code using [Install an MCP Skill](/ai-solutions/mcp-skills/install-an-mcp-skill.md).
3. Use this package's frontmatter when the AI client asks for metadata:
   * Name: `Brand program health check`
   * Description: `Rank a Brand program's fix-it list across concentration, mix, quality, efficiency, and partner slippage from live MCP data. Use for what is wrong with a program, a health check, or where to look first.`
   * Folder name (Cursor / VS Code): `brand-program-health-check`
4. With impact.com MCP connected, prompt: "Run a health check on \[program]."


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.impact.com/ai-solutions/mcp-skills/brand-skills/brand-program-health-check-skill.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.