data-integration

Getting data into Luzmo from any source. Use whenever connecting a database, pushing files, or modeling data. Triggers on: "connect data source", "upload CSV", "import data", "sync from database", "push data via API", "data not loading", createDataprovider. Provides ready-to-use scripts. Covers data modeling, Warp acceleration, and custom connectors. Use eagerly for any data-source or schema question. Essential before charts can display anything. Not for chart rendering (use data-visualization) or per-tenant access control (use multitenancy).

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.

A well-structured, highly actionable integration skill with clear sequenced workflows, validation gates, and clean one-level-deep progressive disclosure. Its main weakness is redundancy across the routing and pitfall sections, which inflates length without adding guidance.

Suggestions

Collapse the "Quick Decision Tree" and "Choose the Right Path" table into a single routing aid to remove duplicated routing logic.

Merge the "Avoid" list into "Common Mistakes" (or vice versa) since they restate the same pitfalls (client-side execution, hardcoded credentials, 10k-row limit, skipping native connectors).

Trim the prose around the security checkpoint — the checkbox list already conveys the rules, so the surrounding explanatory sentences can be shortened.

Dimension	Reasoning	Score
Conciseness	Largely high-signal and avoids teaching Claude basics, but carries real redundancy: the "Quick Decision Tree" and "Choose the Right Path" table cover the same routing, and the "Avoid" section restates the "Common Mistakes" entries and security checkpoint — it could be tightened without losing clarity.	2 / 3
Actionability	Provides copy-paste-ready, fully executable commands (e.g. the connect-datasource.js invocations with all flags), concrete API call JSON shapes, and ready-made scripts for both flows.	3 / 3
Workflow Clarity	The connect flow is a clearly numbered createAccount → getDataprovider → createDataprovider sequence with an explicit pre-code security checklist ("STOP and fix before proceeding"), account-existence validation, and a destructive-replace confirmation gate for batch operations.	3 / 3
Progressive Disclosure	SKILL.md acts as an overview pointing one level deep to real, content-bearing files (references/data-modeling.md, references/connection-types.md) and scripts, with a dedicated "Bundled References" section and clear navigation; verified the references do not nest further.	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.

A strong, third-person description that states concrete capabilities, gives explicit natural-language triggers, and draws clear boundaries against adjacent skills. It answers what, when, and what-not with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "connecting a database, pushing files, or modeling data" and "data modeling, Warp acceleration, and custom connectors" plus "Provides ready-to-use scripts" — rather than vague language.	3 / 3
Completeness	Clearly answers both what ("Getting data into Luzmo from any source") and when with explicit trigger guidance ("Use whenever...", "Use eagerly for any data-source or schema question", "Triggers on:").	3 / 3
Trigger Term Quality	Explicit "Triggers on:" list covers natural user phrasings ("connect data source", "upload CSV", "import data", "sync from database", "push data via API", "data not loading") plus the technical term createDataprovider.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche and explicitly disambiguates from siblings — "Not for chart rendering (use data-visualization) or per-tenant access control (use multitenancy)" — so it is unlikely to trigger for 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.