← LighthouseCONTENT HISTORY

Update to Lighthouse

Snapshot Nov 18, 2026 · 06:17 UTC · version 1.0.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Lighthouse and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Build a new Lighthouse metric (a scheduled check on the user's data that alerts in Slack or email when a threshold is met) from a plain-language goal, test it, backtest it and take it live. Use when the user asks to monitor, track, watch or alert on something in their data with Lighthouse.",
  "included_files": [],
  "name": "build-metric",
  "skill_md_contents": "---\nname: build-metric\ndescription: Build a new Lighthouse metric (a scheduled check on the user's data that alerts in Slack or email when a threshold is met) from a plain-language goal, test it, backtest it and take it live. Use when the user asks to monitor, track, watch or alert on something in their data with Lighthouse.\n---\n\n# Build a metric\n\nA metric runs a query on a data source on a schedule, compares the result with a threshold and notifies people when it is met. Build it as a DRAFT, prove it works, then go live only when the user says so.\n\nIf a tool named here is missing, the user's key or role does not allow it. Say which one and that it can be changed in Lighthouse under Settings, API & Agents.\n\n## Steps\n\n1. **Pin down the goal.** What number, per what (segments such as country or customer), how often, what counts as bad, and who should hear about it. Ask only for what you cannot find.\n2. **Find the data.**\n    - `list_data_sources` and `list_data_sets` for what exists; `get_data_set` for column ids and which columns can be a metric, filter, segment or date.\n    - Prefer a CUSTOM metric on a data set: it gets trend and threshold options and can be backtested. Use RAW_SQL only when no data set fits and one should not be made.\n    - If no data set fits, follow the explore-data-and-model-datasets skill (`list_data_source_tables`, `list_data_source_columns`, `query_data_source`, `create_data_set`).\n3. **Start from an example.** Call `search_metric_configuration_examples` with words from the goal (for example \"count\", \"segments\", \"trend max\", \"calculation window\", \"slack\"), then peek at up to 5 example ids for the full JSON. Copy the closest shape; do not invent fields.\n4. **Assemble the configuration** with real ids only:\n    - data source and data set ids from step 2;\n    - a schedule (every metric needs one);\n    - notifications: `list_communication_sources`, then `get_communication_source` for Slack channel or user ids. Email recipients must be members of the organization;\n    - KPI tags if the user wants them (`list_kpis`);\n    - who may edit and view it. Ask the user; do not assume. For editing: everyone (`editAccessLevel` `EVERYONE`, \"Everyone\" in the web app) or only them (`ADMINS`, shown as \"Owner\"). For viewing, the same choice with `viewAccessLevel`. For specific people or groups, use `SELECTED_USERS` with editorUserIds, viewerUserIds, editorBusinessGroupIds or viewerBusinessGroupIds (ids from `search_users_and_groups`, which anyone who can write metrics may use). Pass the choice in the configuration.\n5. **Test.** Call `test_metric` with the full configuration. Fix every error and repeat until valid is true. Show the user the preview rows and check they look like the number they meant.\n6. **Save as a draft.** `create_metric` with status DRAFT. A draft never runs on its schedule and sends nothing.\n7. **Backtest.** For a CUSTOM metric with a calculation function, call `preview_metric_history` with the new metric id. Report how often the threshold would have been met per day. If it would fire too often or never, adjust the threshold with `test_metric` and `preview_metric_history` (pass metricId and only the changed fields), then save with `update_metric`. See the tune-alert-noise skill for more.\n8. **Go live, with consent.** Summarize what will run, who will be notified and who can edit and view it, and ask. Only after a clear yes, set status LIVE with `update_metric`. LIVE counts toward the plan's live metric limit.\n\n## Safety rules\n\n- Ask before `run_metric`: a run can send the metric's real notifications and actions, like a scheduled run. `test_metric` and `preview_metric_history` never notify anyone.\n- Never call `send_test_notification` unless the user asked for a test message. It sends a real message to real people; call it once.\n- `test_metric` and `preview_metric_history` query the customer's warehouse, which can cost money and is rate limited. Do not loop on them; change something between calls.\n- Do not set a metric LIVE or PAUSED without the user's yes.\n\n## Report back\n\n- Metric name and id, status, data source or data set, schedule.\n- The threshold in plain words, the segments, who is notified and where, and who can edit and view it.\n- The test preview and the backtest result (hits per day, days with hits).\n- What is still open (for example \"still a DRAFT, say the word to go live\").\n"
}

SHA-256 of public snapshot: 70f42444c4795dd50b349b2a1573b1ac388fe3fa2cc4cb0ef730bae19e403e6a