Vibewatch

View saved version →

---
name: use-vibewatch
description: >-
  Read a community's vibe from Vibewatch: current sentiment, the trend over
  time, the messages behind a score, daily insights, weekly reports, and the
  market backdrop — and the wider Stacks ecosystem's vibe. Use this skill
  whenever the user mentions Vibewatch, asks "what's the vibe" in their
  community, asks how community sentiment is trending or why it changed, wants
  to search what their community said, or asks for their weekly community
  report. Also use it when the user asks how the Stacks ecosystem is doing or
  how Stacks sentiment looks overall, and to check whether Vibewatch data
  collection is healthy for their organization.
---

# Use Vibewatch

Vibewatch is community intelligence for web3 teams. It reads a team's community across their
connected platforms (Discord, Telegram, X, and more), scores the vibe, surfaces daily insights,
and writes weekly reports. This plugin connects the agent to one Vibewatch organization through
the hosted Vibewatch MCP server at `https://api.vibewatch.io/mcp/`. One tool is the exception —
`get_stacks_ecosystem_sentiment` reads the Stacks ecosystem as a whole and has nothing to do with
the connected organization.

Everything here is **read-only**. The server exposes no write tools — you can read the
organization's data, plus public Stacks ecosystem data through
`get_stacks_ecosystem_sentiment`, and nothing else. Say so plainly if the user asks you to change
Vibewatch settings or data: point them at [app.vibewatch.io](https://app.vibewatch.io).

## Data model

- An **organization** connects one or more platform integrations. Messages flow in on the org's
  sync schedule.
- Each message is scored for **sentiment** and **relevance**. Org-level sentiment aggregates
  into a daily score — the vibe.
- **Daily insights** are generated highlights and lowlights: the notable things the community
  said each day.
- **Weekly reports** are narrative summaries generated on the org's report schedule.
- **Market context** (crypto market conditions, Fear & Greed) is a separate backdrop feed, not
  part of the org's score.
- **Stacks ecosystem sentiment** is public, ecosystem-wide data — the Stacks ecosystem's own
  vibe, scored across the ecosystem and unrelated to any one organization. It is the only
  non-org-scoped read on this server; the same payload is served anonymously at
  `https://api.vibewatch.io/mcp/public` and at
  [stacks.vibewatch.io](https://stacks.vibewatch.io/api/index).

## Tool routing

| Ask | Tool |
|---|---|
| "What's the vibe?" — this org's current state | `get_sentiment_overview` |
| Trend, change over time, "how was this month" | `get_sentiment_timeseries` |
| What people actually said; evidence behind a score | `search_messages` |
| Notable moments, highlights/lowlights by day | `get_daily_insights` |
| Weekly report, recap for the team | `get_reports` |
| Market backdrop | `get_market_context` |
| Plan, connected platforms, is data flowing | `get_organization` |
| "How's the Stacks ecosystem doing", "how is Stacks sentiment overall" — the ecosystem's vibe, not this org's | `get_stacks_ecosystem_sentiment` |

The last row is the only one that isn't about the connected organization. `get_sentiment_overview`
answers "how are *we* doing"; `get_stacks_ecosystem_sentiment` answers "how is *Stacks* doing".
Route on which of the two the user asked for, and never answer one with the other's numbers.

Tool parameters are self-describing; read each tool's own description for specifics.

## Workflows

**Vibe check.** `get_sentiment_overview` first. Report the actual score and what drives it —
concrete numbers from the response, never invented ones.

**Investigate a change.** `get_sentiment_timeseries` to find when the shift happened, then
`search_messages` with `start_date`/`end_date` scoped to that window to find out what the
community was reacting to. If the shift is within the last week, `get_daily_insights` adds the
generated highlight

Preview of the first 4,000 characters. Read full instructions →