data-model-creation

[Deprecated] Optional advanced tool for complex data modeling. For simple MySQL table creation, use relational-database-tool directly; for PostgreSQL / CloudBase PG schema work, use postgresql-development. New environments should use PostgreSQL DDL via queryPgDatabase/managePgDatabase — see postgresql-development skill instead.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugin/cloudbase/skills/data-model-creation/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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 and actionable, with a concrete Mermaid example, a type-mapping table, and named modeling tools. Its main weaknesses are repeated routing content that could be tightened and the absence of an explicit validation feedback loop around the publish step.

Suggestions

Consolidate the MySQL/PostgreSQL routing guidance into a single section to remove repetition across Overview, Quick routing, and Best practices.

Add an explicit validate->fix->retry feedback loop for the publish step (e.g., re-run manageDataModel(action='get') to confirm fields/constraints before publishing) to lift workflow clarity.

Provide fuller tool signatures or a short parameter table for modifyDataModel and manageDataModel so the guidance is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the MySQL-vs-PostgreSQL routing guidance is repeated across 'Overview', 'Quick routing', and 'Best practices', which could be consolidated.	3 / 5
Actionability	It provides a copy-paste-ready Mermaid example, a concrete business-to-Mermaid type mapping table, and named tools with parameters (manageDataModel action='list'\|'get'\|'docs', modifyDataModel with action='create'), with only minor gaps around full tool signatures.	4 / 5
Workflow Clarity	The 4-step 'How to use' sequence is clear and mentions validation ('Validate names, field types, and relationships before calling modeling tools', 'Publish only after checking...'), but publishing is a batch/irreversible operation with no explicit validate->fix->retry feedback loop, so workflow clarity is capped at 3 per the destructive/batch rule.	3 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and one-level-deep pointers to sibling skills via relative paths; no nested references or monolithic API dump, and no bundle files are needed, so organization is good with only minor gaps.	4 / 5
	Total	14 / 20 Passed

Description

36%Weight 40%Scale 1-5

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

This is a deprecation/routing description more than a capability description: it spends most of its text telling the reader to use other skills instead of stating what this skill concretely does or when to trigger it. It lacks explicit trigger guidance and concrete actions for the skill itself.

Suggestions

Add an explicit 'Use when...' clause naming this skill's own triggers (e.g., Mermaid classDiagram modeling, multi-entity ER design) rather than only redirecting to other skills.

List 1-2 concrete actions this skill performs (e.g., 'Generate Mermaid classDiagram models from business entities', 'Inspect and publish CloudBase data models') to lift specificity.

Include natural trigger terms users would say — 'ER diagram', 'Mermaid class diagram', 'data model' — alongside the existing PostgreSQL/MySQL routing language.

Dimension	Reasoning	Score
Specificity	The description names the domain ('complex data modeling') but lists no concrete actions for this skill — every action clause ('use relational-database-tool directly', 'use postgresql-development', 'use PostgreSQL DDL via queryPgDatabase/managePgDatabase') redirects to a different skill rather than describing what this one does.	2 / 5
Completeness	The 'what' is vague ('Optional advanced tool for complex data modeling') and there is no explicit 'Use when...' trigger for this skill — every when-style clause points the user away to another skill, so the 'when' for this skill is effectively absent.	2 / 5
Trigger Term Quality	It includes relevant terms a user might say ('complex data modeling', 'MySQL table creation', 'PostgreSQL / CloudBase PG schema'), but omits the natural terms for this skill's actual capability (Mermaid, classDiagram, ER diagram) and offers few synonyms.	3 / 5
Distinctiveness Conflict Risk	It is somewhat specific to data modeling and names distinct sibling skills, but because it spends most of its length redirecting to postgresql-development and relational-database-tool, its own niche is blurred and it could still overlap with those closely related skills.	3 / 5
	Total	10 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: TencentCloudBase/CloudBase-AI-Toolkit
Path: plugin/cloudbase/skills/data-model-creation/SKILL.md
Commit: ef9f182

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