KymiraCertified BI

The 22 skills · Craft skill · Core Pack and Everything

AGENT SKILL

report-design: what it makes your agent do, and what it refuses.

report-design is what your agent brings to the first conversation so nobody starts from a blank page. It arrives with three or four archetypes, asks what decision the report supports, and then subtracts. Certification is a mandatory section of every archetype, not a feature of the expensive one.

The job report-design does

The blank page is the failure mode that kills conversational tools: a buyer who has never heard of weeks of supply will never ask for it, and ends up with a worse dashboard than one they were handed. This skill holds the archetypes worth proposing, what question each answers, the grain each needs, and the slots it fills. It opens with opinions and lets the user delete what they do not want, which is faster than an interview and leaves a record of what that tenant cares about. Four rules outrank every archetype, covering certification, masthead identity, what to do when the file spills past its claimed period, and the shape of a KPI tile.

What report-design refuses

A skill is worth what it stops as much as what it produces. These are the refusals written into report-design, taken from the rules and limits in its own file.

9 lines from the report-design skill file, verbatim

From skills/report-design/SKILL.md, unedited. Kymira skills are plain text you can read in full before you install them, which is the point of shipping a method rather than a binary.

**Certification is a mandatory section of every archetype.** Product detail,
then validation and lineage — checks run, anchors tied, flags with stakes,
open rulings — and finally data notes. It is not an archetype-2 feature; a
certified report with its evidence amputated is a styled report.

**Masthead identity follows doctrine 4 exactly as period does.** Only what the
file internally evidences goes on the masthead. A filename-derived name
renders as "source file: <name>" with an explicit "issuer not evidenced in
data" note, never as a company title.

The failure modes report-design addresses

No entry in the catalogue of 51 observed failure modes names report-design as the thing that addresses it. The catalogue records failures we have watched happen, so a skill appears there once a failure it covers has actually been observed and written up. Read the catalogue.

The tier report-design ships in

TierPriceWhat the tier holdsreport-design
Free$0honest-dataviz and the eleven doctrine principles, published in fullNot in this tier
Core Pack$199the thirteen craft skills, one-time purchase, lifetime updatesIncluded
Everything$349all 22 skills, both libraries, the template bank, one-time purchase, lifetime updatesIncluded

Both paid tiers are a one-time purchase with lifetime updates, and all sales are final: the files are plain text you keep the moment they arrive, so judge the quality on the free skill and the published doctrine first. The pricing section states exactly what each tier contains.

Installing report-design

A skill is a folder with a SKILL.md file in it. Installing one is copying that folder where your agent looks for skills, with no build step and no dependencies.

mkdir -p ~/.claude/skills
cp -R Kymira/skills/report-design ~/.claude/skills/

Or open the unzipped pack in Claude Code and say install Kymira, which installs every skill in your tier, or double-click the installer for your system. Cursor reads the same skill as a rule file: copy report-design.mdc into .cursor/rules/. Skills are read at startup, so start a new session and ask your agent which skills it has available.

Not for

It does not choose your metrics or compute anything. It proposes shapes and grains, and it cannot tell you whether the definition behind a figure is the one your team argues about. That conversation belongs to contested-metrics and the metric store.

Last updated 2026-08-29 · Dylan, founder · one of 22 packaged skills, each one a method written down, not a product tour.

See the tiers → All 22 skills The doctrine The failure catalogue