analytics-studio

Build a self-service analytics environment inside your application. Two approaches - out-of-the-box Embedded Dashboard Editor (editMode) or custom Analytics Components Kit (ACK). Use for letting end-users create/edit dashboards, white-label studios, editMode, designer/owner token roles, and ACK configuration. Triggers on: "self-service analytics", "let users edit dashboards", "embedded studio", "analytics components kit", "ACK", "designer role", "dashboard editor". Critical pattern: ACK configures -> your app stores state -> separate renderer displays. Not for view-only embedding of saved dashboards (use core), building charts in code (use data-visualization), data connection (use data-integration), or AI queries (use ai-analytics).

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 highly actionable, clearly sequenced, and well-structured with one-level-deep references that exist on disk. Its main weakness is conciseness: several core points (ACK-as-renderer, license requirement) are repeated across multiple sections and could be consolidated.

Suggestions

Consolidate the 'ACK components do not render' guidance: present it once in the Configure→Store→Render / Configuration vs Rendering section and reference it from Common Mistakes and Key Facts rather than restating the same [ERROR]/[OK] code blocks three times.

Merge the License Requirements section and the license bullet in Key Facts to avoid duplicating the 'ACK addon' message and the support@luzmo.com pointer.

Trim the two near-identical 'mismatched item-type' code blocks in Keep Types Synchronized and Common Mistakes into a single canonical example with a cross-reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, useful technical guidance and avoids explaining concepts Claude already knows, but it is verbose through repetition: the 'ACK does not render' point and its [ERROR]/[OK] code blocks are restated across the Configure→Store→Render, Configuration vs Rendering, Common Mistakes, and Key Facts sections, and license guidance is repeated twice. It could be tightened to preserve the same clarity with fewer tokens, so it sits at the 'mostly efficient but could be tightened' anchor rather than the lean top anchor.	2 / 3
Actionability	Provides fully executable code (JSX, Vue, JavaScript API calls), exact component names, import paths for utilities like switchItem/loadDataFieldsForDatasets, and precise developer.luzmo.com doc URLs — copy-paste ready guidance matching the top anchor.	3 / 3
Workflow Clarity	The configure→store→render flow is laid out as an explicit numbered 1-2-3 sequence, the Security Checkpoint is a checklist with a 'STOP' gate, and handleChartTypeChange is a sequenced 4-step routine with symptoms+cause+fix given for each common mistake — clear sequencing with validation checkpoints and feedback, with no destructive/batch operation that would cap the score.	3 / 3
Progressive Disclosure	SKILL.md acts as an overview with well-signaled one-level-deep references — the 'Choose the Right Path' table routes to references/embedded-editor.md and references/dashboard-api.md (both verified present), plus a 'Doc Retrieval' section and 'Bundled References' list — matching the top anchor for clear, easy 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 precise, uses third-person/infinitive voice, and explicitly covers what it does, when to use it (with a trigger list), and what it is NOT for. It is a strong, well-scoped skill description.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions and components — 'Build a self-service analytics environment', 'Embedded Dashboard Editor (editMode)', 'Analytics Components Kit (ACK)', 'create/edit dashboards', 'white-label studios', 'ACK configuration', 'designer/owner token roles' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers both what ('Build a self-service analytics environment inside your application') and when (an explicit 'Use for...' clause plus a 'Triggers on:' line), satisfying the top anchor for both what and when.	3 / 3
Trigger Term Quality	An explicit 'Triggers on:' line lists natural user phrasings — 'self-service analytics', 'let users edit dashboards', 'embedded studio', 'analytics components kit', 'ACK', 'designer role', 'dashboard editor' — giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	A 'Not for...' clause explicitly disambiguates from core (view-only embedding), data-visualization (charts in code), data-integration, and ai-analytics, giving it 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.