{"id":48284,"plugin_id":"plugin_asdk_app_6abce2d24d4c819194be3d24718f161a","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:35:56.181Z","digest":"eb2da49ff009831d20a95fac35fbd436e4f0bb7650f560334a453799b0758b9b","against":null,"payload":{"description":"Create or update a LeadJourney dashboard with report cards (channel, campaign, creative, or custom reports) so the user has a recurring view of marketing performance.","included_files":[],"name":"dashboard-builder","skill_md_contents":"---\nname: dashboard-builder\ndescription: Create or update a LeadJourney dashboard with report cards (channel, campaign, creative, or custom reports) so the user has a recurring view of marketing performance.\n---\n\nUse this skill when the user wants a dashboard, wants a report \"saved\" or \"pinned\", asks for a weekly/monthly overview they can return to, or wants to add a chart to an existing dashboard.\n\n## Inputs to establish\n\n1. **Workspace.** `get_current_workspace`; switch if needed.\n2. **New or existing dashboard.** Call `list_dashboards`. If a dashboard with a matching name exists, add to it rather than creating a duplicate. Confirm with the user when the match is only approximate.\n3. **Which reports.** Each card is a report. Clarify the date range behaviour (rolling last 30 days vs fixed period) and the metric the user cares about.\n\n## Steps\n\n1. Call `describe_report_builder` once to get the valid metric and dimension ids. A card takes the same arguments as `run_report`, so every id must come from this response.\n2. For each requested card, call `run_report` first and check that it returns rows. A card built from a report that returns nothing renders as an empty tile; fix the arguments before adding it.\n3. If creating: call `create_dashboard` with a clear name. If adding: use the existing dashboard id.\n4. Call `add_dashboard_report` once per card, with the verified `run_report` arguments and a card title the user will understand.\n5. Only call `remove_dashboard_report` or `delete_dashboard` when the user explicitly asks to remove or delete, and confirm the target by name before doing so. Deletion cannot be undone.\n\n## Output\n\n- Dashboard name and a list of the cards added, each as `title — metric by dimension, date range`.\n- If any requested card could not be built (metric not available, empty results), say which one and why, and suggest the closest alternative from `describe_report_builder`.\n\n## Do not\n\n- Do not guess metric or dimension ids.\n- Do not delete or remove anything without an explicit instruction naming the dashboard or card.\n- Do not add more than the user asked for; suggest extra cards in one line instead of creating them.\n\nExplicit user instructions override these defaults.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}