agentsclimarketplace

Notion dashboard

Skill NovateStudioGit/novate-studio-skills/knowledge-ops/notion-dashboard

57 agent skills for Claude Code — creative production, paid growth, copywriting, ecommerce, email marketing & knowledge ops. By Novate Studio.

Install
npx -y skills add NovateStudioGit/novate-studio-skills --skill notion-dashboard

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Compose a dashboard for an existing Notion database — chart number tiles for key totals, grouped views for slicing, and a clean heading layout. Use when the user says "build a dashboard for this database", "Notion dashboard from X", "summary view in Notion", or pastes a Notion DB URL and asks for an executive view. Reads the DB schema, proposes the dashboard structure, then creates views + (optionally) a parent page that embeds them. Stops at a preview gate before any mutation.

SKILL.md

4.0 KB, 870 tokens by cl100k_base, as published. Nobody here has run it

/notion-dashboard

Build an executive dashboard for an existing Notion database. Reuses what's already there — never duplicates the underlying data.

Inputs

  • Database URL or ID (required). Always run notion-fetch on it first to read the schema and existing views before proposing anything.
  • Intent (optional but useful): "OPEX by category", "leads by stage and source", "revenue YTD vs target". If not given, infer 1–3 plausible dashboard candidates from the schema and ask the user to pick.
  • Target page (optional): where the dashboard should live. If omitted, add views as new tabs on the existing database. If a parent page is given, create linked-database views there instead.

Steps

  1. Read. notion-fetch the DB. Note: title, schema (property types + options), existing views (names + configs), parent page.
  2. Propose. Output a compact plan to the user:
    • 1–3 chart number tiles (which property, which aggregation — sum / count / average — and optional FILTER for "active only").
    • 1–2 board or table views grouped by the most-informative select/multi-select (Category, Status, Workstream, etc.).
    • Optional: a "Heads-up" filtered table (e.g. renewal date ≤ 30 days, status = trial, blank required fields).
    • If a target page was specified, propose the page layout (heading → number tiles row → grouped views).
  3. Preview gate. Wait for user confirmation. Do not mutate yet.
  4. Build.
    • For each chart/table view: notion-create-view with the right DSL (CHART number AGGREGATE sum/count/etc., GROUP BY, FILTER, SORT BY, SHOW). For chart-number titles that include a live value, hardcode the current value in the name AND tell the user it'll go stale.
    • If a parent page was specified: notion-create-pages with a heading + embedded <view> references.
  5. Confirm. Print each created view's URL and ID. Highlight any manual one-clicks needed (the Calculate footer is UI-only).

Hard-won gotchas

These are the Notion MCP procedural issues this skill must route around:

  • No Calculate footer in view DSL. To show a total at the bottom of a table, the user must click Calculate → Sum manually (one-time, per view). If they want a fully automated "Total = $X", use a CHART number AGGREGATE sum ON "Property" view instead. State both options when relevant.
  • View names are static strings. They don't interpolate live aggregate values. If user wants a value baked into the title (e.g. "Total = $250"), flag staleness once then comply.
  • Property must be the right type for AGGREGATE sum/avg/min/max. Text columns won't aggregate as numbers. If the property is text but the user wants math, propose ALTER COLUMN ... SET NUMBER FORMAT 'dollar' first (lossless if values are clean numerics; lossy if values contain "$" or "/mo" — preview and confirm).
  • To enumerate all rows in a data source, there's no query_data_sources tool exposed; use notion-search with data_source_url set and a few broad single-letter queries ("a", "e", "o", "s") and union the results.

Output

  • A short summary of what was created with URLs.
  • Any manual one-clicks the user needs to make (Calculate footer toggle).
  • Updated Admin/<tracker-name>.md in Obsidian if the dashboard maps to an existing tracker doc.

Output format

Terse. Sub-150-words for the build confirmation. The proposal step can be longer since it's a design conversation.

Reverts / non-destructive

This skill never deletes existing views. If a proposed view name collides, append " (v2)" or ask.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.