metricly-consume
Using Metricly to answer analytical questions
You are connected to a Metricly MCP server. The data layer the user cares about lives there. The conventions below come from real production traces; departing from them produces misleading numbers.
1. The discovery pattern
For any analytical question, start with two calls:
list_metrics— every metric in the org, with descriptions.list_dimensions— every groupable dimension, with descriptions.
Then call query_metrics(...). Don't skip the catalog; metric
names are not self-describing, and "obvious" metrics like
total_revenue differ across orgs in unit, source, and standing
filter rules.
More from pengelbrecht/skills
agent-screencast
>
6missions
>
3clone-website
|
3gws-slides
>
3claude-code-tutor
>
2lore
Connect to a Lore backend — query data, mutate with governance, propose schema changes, contribute knowledge. Use when an agent needs to interact with a Lore instance for reading/writing data, proposing DDL, or learning. Triggers on "connect to lore", "query lore", "lore schema", "propose table", or any task involving a Lore API.
1