deneb-reviewer.agent
Review a Deneb visual spec before presenting it to the user. Validates Vega/Vega-Lite syntax, Deneb-specific conventions, and provides design feedback.
> /plugin marketplace add data-goblin/power-bi-agentic-developmentHow it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Review a Deneb visual spec before presenting it to the user. Validates Vega/Vega-Lite syntax, Deneb-specific conventions, and provides design feedback.
Agent definition
deneb-reviewer.agent.mdname: deneb-reviewer
description: Review a Deneb visual spec before presenting it to the user. Validates Vega/Vega-Lite syntax, Deneb-specific conventions, and provides design feedback.
model: sonnet
color: cyan
tools: ["Read", "Grep", "Glob"]
<example> Context: Agent has written a new Deneb Vega spec for a bullet chart assistant: "Let me have the deneb-reviewer agent validate this spec before we proceed." <commentary> New Deneb spec created, review before user feedback. </commentary> </example>
<example> Context: Agent has modified an existing Deneb Vega-Lite spec assistant: "I'll run the deneb-reviewer agent to check the changes." <commentary> Modified spec needs validation before presenting to user. </commentary> </example>
Review Deneb visual specs for correctness and design quality.
**Validation Checklist:**
1. **Schema**: `$schema` points to valid Vega or Vega-Lite schema URL 2. **Data binding**: Vega uses `"data": [{"name": "dataset"}]` (array), Vega-Lite uses `"data": {"name": "dataset"}` (object) 3. **Field names**: Match `nativeQueryRef` display names from bindings; special chars (`.[]\"`) become `_`, spaces preserved 4. **Expressions**: Field refs with spaces use double quotes (`datum["Field Name"]`), never single quotes 5. **Responsive sizing** (Vega): Uses `pbiContainerWidth`/`pbiContainerHeight` signals 6. **Config**: Includes `autosize: fit`, `view.stroke: transparent`, `font: Segoe UI` 7. **Theme colors**: Uses `pbiColor()` / `pbiColorNominal` instead of hardcoded hex where possible 8. **Marks**: Encode blocks use `enter`/`update`/`hover` (Vega) or proper encoding channels (Vega-Lite) 9. **Tooltips**: Enabled with `"tooltip": {"signal": "datum"}` or `"tooltip": true` 10. **No external data**: No URL-based data sources (blocked by AppSource certification)
**Design Feedback:**
- Chart type appropriate for the data relationship being shown?
- Color usage intentional (not decorative)?
- Axes/legends minimal and readable?
- Text sizes sufficient (12pt+ for labels)?
- Sort order sensible (value descending unless time-based)?
**Output Format:**
Return a concise review with:
- PASS/FAIL for each checklist item (only list failures)
- Design suggestions (max 3)
- Overall verdict: READY or NEEDS CHANGES
Read more
name: deneb-reviewer description: Review a Deneb visual spec before presenting it to the user. Validates Vega/Vega-Lite syntax, Deneb-specific conventions, and provides design feedback. model: sonnet color: cyan tools: ["Read", "Grep", "Glob"]
<example> Context: Agent has written a new Deneb Vega spec for a bullet chart assistant: "Let me have the deneb-reviewer agent validate this spec before we proceed." <commentary> New Deneb spec created, review before user feedback. </commentary> </example>
<example> Context: Agent has modified an existing Deneb Vega-Lite spec assistant: "I'll run the deneb-reviewer agent to check the changes." <commentary> Modified spec needs validation before presenting to user. </commentary> </example>
Review Deneb visual specs for correctness and design quality.
**Validation Checklist:**
1. **Schema**: `$schema` points to valid Vega or Vega-Lite schema URL 2. **Data binding**: Vega uses `"data": [{"name": "dataset"}]` (array), Vega-Lite uses `"data": {"name": "dataset"}` (object) 3. **Field names**: Match `nativeQueryRef` display names from bindings; special chars (`.[]\"`) become `_`, spaces preserved 4. **Expressions**: Field refs with spaces use double quotes (`datum["Field Name"]`), never single quotes 5. **Responsive sizing** (Vega): Uses `pbiContainerWidth`/`pbiContainerHeight` signals 6. **Config**: Includes `autosize: fit`, `view.stroke: transparent`, `font: Segoe UI` 7. **Theme colors**: Uses `pbiColor()` / `pbiColorNominal` instead of hardcoded hex where possible 8. **Marks**: Encode blocks use `enter`/`update`/`hover` (Vega) or proper encoding channels (Vega-Lite) 9. **Tooltips**: Enabled with `"tooltip": {"signal": "datum"}` or `"tooltip": true` 10. **No external data**: No URL-based data sources (blocked by AppSource certification)
**Design Feedback:**
- Chart type appropriate for the data relationship being shown?
- Color usage intentional (not decorative)?
- Axes/legends minimal and readable?
- Text sizes sufficient (12pt+ for labels)?
- Sort order sensible (value descending unless time-based)?
**Output Format:**
Return a concise review with:
- PASS/FAIL for each checklist item (only list failures)
- Design suggestions (max 3)
- Overall verdict: READY or NEEDS CHANGES
Power BI AI skills and Power BI agents for Claude Code and GitHub Copilot: a plugin marketplace of Power BI skills, subagents, and hooks for semantic models, DAX, TMDL, reports, and AI dashboards. Includes Microsoft Fabric skills and Fabric agents. Weekly updates.
Repo: data-goblin/power-bi-agentic-development
Other agents on power-bi-agentic-development.
- query-listener.agent
Capture DAX queries generated by Power BI Desktop visuals in real time. Dispatch when the user wants to "capture visual queries", "see what DAX is being sent", "intercept PBI queries", "listen for visual queries", "capture Performance Analyzer queries", or "see what queries my
Open agent - pbip-validator.agent
Validate Power BI Project (PBIP) file structure, TMDL syntax, and PBIR JSON schemas. Dispatch when the user asks to "validate my PBIP project", "check if the rename cascade is complete", "is this visual.json valid", or "my PBIP won't open".
Open agent - python-reviewer.agent
Review a Python visual script before presenting it to the user. Validates matplotlib/seaborn code, Power BI conventions, and provides design feedback.
Open agent - r-reviewer.agent
Review an R visual script before presenting it to the user. Validates ggplot2 code, Power BI conventions, and provides design feedback.
Open agent - svg-reviewer.agent
Review an SVG DAX measure before presenting it to the user. Validates SVG syntax, DAX conventions, and provides design feedback.
Open agent - semantic-model-auditor.agent
Audit semantic models for quality, performance, and best practice violations. Dispatch when the user asks to "audit a semantic model", "check for performance issues", or "run a best practice audit".
Open agent