custom-charts

Build a brand-new Luzmo chart component when no built-in chart type (and Flex) is sufficient. Triggers on: "custom chart", "build a custom chart", "no built-in chart type fits", "chart plugin", "manifest", "render/resize/buildQuery", "custom chart not in picker", "upload custom chart", "org release". Rare advanced path (~95% of users never need this). Not for Flex charts with built-in types (use data-visualization), embedding saved dashboards (use core), self-service chart editors (use analytics-studio), or auth setup (use core).

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

The body is well-structured, concise, and uses progressive disclosure with a verified reference file and explicit validation checkpoints. Its main weakness is actionability on the authoring path, where executable manifest/render examples are deferred to external docs rather than shown inline.

Suggestions

Add a minimal executable manifest snippet (a slot definition with a localized label) so the authoring workflow is actionable without leaving SKILL.md.

Show a minimal render/resize function skeleton inline rather than only naming the functions, to make the core implementation step concrete.

Move the duplicated 'When to Use', 'Rules', 'Troubleshooting', and 'Using a Released Custom Chart' sections out of SKILL.md into the reference to reduce redundancy with references/chart-development.md.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no explanation of basic concepts; every section adds information Claude would not already infer.	3 / 3
Actionability	It provides an executable HTML embed snippet and concrete rules (localized { en: "Label" }, explicit dimensions), but the core authoring workflow mostly defers to docs and the bundled reference rather than giving executable manifest/render code, leaving key implementation details incomplete.	2 / 3
Workflow Clarity	A clear 7-step development sequence is paired with a Security Checkpoint that halts on unchecked items and an explicit 'validate before production release' step, providing a real validation feedback loop.	3 / 3
Progressive Disclosure	The SKILL.md is an overview that signals one real, one-level-deep reference (references/chart-development.md, verified present) and external docs, with a dedicated 'Bundled References' section for navigation.	3 / 3
	Total	11 / 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.

The description is concise, specific, and well-differentiated, with explicit trigger terms and clear exclusions to sibling skills. Voice is consistently third person with no over-claims.

Dimension	Reasoning	Score
Specificity	It names a concrete action ('Build a brand-new Luzmo chart component') and enumerates the supporting concepts (manifest, render/resize/buildQuery), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly answers what ('Build a brand-new Luzmo chart component') and when (explicit 'Triggers on:' list), plus a 'Not for...' exclusion clause, satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	An explicit 'Triggers on:' list gives natural user phrases ('custom chart', 'build a custom chart', 'upload custom chart', 'custom chart not in picker') with good coverage of how a user would actually phrase the need.	3 / 3
Distinctiveness Conflict Risk	The 'Not for...' clause routes overlapping cases to data-visualization, core, and analytics-studio, establishing a clear niche unlikely to trigger the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: luzmo-official/agent-skills
Commit: 5ee6b03

Reviewed: 10 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.