DewPoint

Use the running DewPoint app to connect the source, build its reusable data model and dashboards, and query numbers live. The result is a workspace and dashboard the user can reopen in the app.

Run the bundled helper with python3 <skill-directory>/scripts/dewpoint.py <command> using the directory that contains this SKILL.md. The helper targets http://127.0.0.1:8000 by default. For a team deployment, use its approved HTTPS API origin with --api ORIGIN before the command, or set DEWPOINT_API_URL. In a Claude desktop session, check connectivity from the skill runtime with status; localhost there may differ from localhost in the user’s browser. status should report database: true and cube: true. For a fresh stack, follow the repository README's Setup section and check that the backend has a configured LLM provider. The local dashboard UI defaults to http://localhost:5173.

Select the source

Build and verify

  1. Run catalog WORKSPACE and dashboards WORKSPACE. Review measure definitions, filters, table grain, and join relationships. DewPoint usually saves a starter dashboard during workspace setup.
  2. If a saved dashboard already answers the question, run verify WORKSPACE --template DASHBOARD_ID. Otherwise use draft WORKSPACE --prompt 'Build and name a dashboard for …' > DRAFT.json. Include the approved definitions and request a layout that makes the decision easy to make. To start from a saved layout, add --template DASHBOARD_ID. A later draft can take --draft PREVIOUS.json and a new prompt. Use an agent-owned temporary directory for these files. The Designer can change the shared model through its tools. Request model changes only when the task calls for them.
  3. Run verify WORKSPACE --draft DRAFT.json to query every chart through Cube with the saved defaults. Check the numbers against the question and the catalog definitions. For join-sensitive totals, check the aggregation at the source grain or compare against an authorized read-only control query. Disclose unresolved definitions, missing values, incomplete coverage, and chart errors where they affect the answer. A successful query establishes that the chart runs. Use the business definition and a control total to establish that it answers the question.
  4. When the user has asked for a dashboard and the verified draft answers the question, run save WORKSPACE --draft DRAFT.json. This saves a new dashboard through DewPoint after verifying that every chart can load. If saving times out, check dashboards WORKSPACE before trying again.
  5. Return the app URL, workspace and dashboard names, the decision-relevant result, and the definition or check behind the main metric. Indicate whether the result is already saved or still a draft.