Add studio report skill reference#86
Merged
Merged
Conversation
andrewjensen
approved these changes
Jun 4, 2026
|
|
||
| Supported tile `chart_type` values are `line`, `pie`, `stacked_bar`, `scatter`, and `table`. | ||
|
|
||
| `line`, `stacked_bar`, and `scatter` chart configs require `xAxis` and `yAxes`; `pie` chart configs require `labelColumn` and `valueColumn`; `table` chart configs can be `{}`. |
Collaborator
There was a problem hiding this comment.
NB: Chart information looks a little sparse. Have agents done a good job setting the axes and labels correctly during development? If not, we might want to fill out some explicit examples.
Collaborator
Author
There was a problem hiding this comment.
Yeah I haven't seen any issues.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ticket
https://www.loom.com/share/31b76d8ede4a4fadb2a1359c694ea204
Summary
This adds Studio report creation guidance to the dx-cli skill so agents know how to create and update reports through the CLI without trying to assemble large payloads directly in shell arguments.
The report create and update commands take YAML payloads that include report metadata, access settings, SQL, chart types, and chart configuration. Without dedicated skill documentation, agents would have to infer the workflow from the command help or prior context, which makes it easier to miss the intended init/edit/create flow or the supported access and chart config values.
The root cause was that the dx-cli skill had references for catalog and scorecard management, but no comparable reference for Studio report creation. I added a new Report creation reference that mirrors the existing reference-doc pattern and moved the report-specific guidance out of the top-level skill file.
Changes
skills/dx-cli/references/report-creation.mdwith Studio report list, info, init, create, update, and stdin workflows.skills/dx-cli/SKILL.mdalongside the existing catalog and scorecard references.Validation
pnpm format:check.