Name: plugin-bundle-size
Rating: 80 (1 reviews)
Author: grafana

plugin-bundle-size

Optimise Grafana app plugin bundle size using React.lazy, Suspense, and webpack code splitting. Use when the user asks to reduce plugin bundle size, optimise module.js, add code splitting, improve initial plugin load performance, split plugin chunks, lazy load plugin pages, or help implement lazy loading in a Grafana app plugin. Triggers on phrases like "optimise plugin bundle size", "module.js is too large", "plugin is slow to load", "code split the plugin", "reduce initial JS payload", or "help me with Suspense in my plugin".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, executable workflow with strong sequencing, validation checkpoints, and well-organised external references. Content earns its tokens with domain-specific guidance rather than generic explanation.

Dimension	Reasoning	Score
Conciseness	Lean and domain-specific — no padding about what React.lazy or webpack are; every section delivers executable guidance or hard targets (e.g. 'module.js under ~200 KB', '15-25 chunks').	3 / 3
Actionability	Fully executable bash snippets and copy-paste TSX examples across all four priorities, plus concrete CI workflow YAML for both root and subdirectory plugins.	3 / 3
Workflow Clarity	Eight clearly sequenced steps with explicit validation checkpoints: baseline measurement (Step 2), build verification (Step 7), and runtime testing of every route (Step 8).	3 / 3
Progressive Disclosure	Body is an overview that defers datasource-specific and troubleshooting detail to real, clearly-signalled one-level-deep references (references/datasource-plugins.md, references/troubleshooting.md), both present in the bundle.	3 / 3
	Total	12 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description that clearly states capabilities and use conditions for Grafana app plugin bundle-size optimisation. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'optimise module.js', 'add code splitting', 'split plugin chunks', 'lazy load plugin pages' — via React.lazy, Suspense, and webpack code splitting.	3 / 3
Completeness	Explicitly answers what (optimise bundle size via React.lazy/Suspense/webpack) and when ('Use when the user asks...'), with concrete trigger phrases.	3 / 3
Trigger Term Quality	Natural phrases users would say are well covered: 'optimise plugin bundle size', 'module.js is too large', 'plugin is slow to load', 'reduce initial JS payload'.	3 / 3
Distinctiveness Conflict Risk	Narrowly scoped to Grafana app plugin bundle size with distinct triggers; unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: grafana/skills
Commit: 7155edc

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.