> For the complete documentation index, see [llms.txt](https://help.meetmadison.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meetmadison.ai/social/post-health.md).

# Post health

**Post health** is a quick visual check on your [Social calendar](/social/social-posts.md). Each day carries a small marker that tells you, at a glance, whether that day has content scheduled, so you can spot quiet days and fill them before they arrive.

## What the markers mean

Look at the top of each day on the calendar:

* **Green thumbs-up**: fully covered, every account has content for that day.
* **Grey thumbs-up**: partly covered, some content is scheduled, but not for everything.
* **No thumbs-up**: nothing is scheduled that day.
* **Sparkles ✨**: there are draft posts waiting for your approval that day. Open the day to review and approve them.

A green thumbs-up across your calendar means you're all set. Grey or empty days are the ones worth a look.

{% hint style="success" %}
The easiest way to keep every day covered is to turn on **daily campaigns**, which let Madison create posts for you automatically. See [Daily campaigns](/social/daily-campaigns.md).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.meetmadison.ai/social/post-health.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.