relational-database-mcp-cloudbase

[Deprecated] This is the required documentation for agents operating on the CloudBase Relational Database through MCP. It defines the canonical SQL management flow with `queryMysqlDatabase`, `manageMysqlDatabase`, `queryPermissions`, and `managePermissions`, including MySQL provisioning, destroy flow, async status checks, safe query execution, schema initialization, and permission updates. New environments should use PostgreSQL — see postgresql-development skill instead.

Quality

78%

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/relational-database-mcp-cloudbase/SKILL.md

Quality

Content

81%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.

A highly actionable, well-sequenced body with strong validation feedback loops for destructive operations; its main weakness is redundant trigger/tool-selection sections and a monolithic single-file structure that could benefit from splitting out the API reference.

Suggestions

Collapse the overlapping Activation Contract, 'When to use this skill', and 'How to use this skill' sections into a single trigger + tool-selection block to remove redundancy.

Move the detailed 'Available MCP tools' reference into a separate references/ file, leaving SKILL.md as a concise overview that points to it.

De-duplicate the tool-picking guidance that appears both in 'How to use this skill' step 2 and in the per-tool sections.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the Activation Contract, 'When to use this skill', and 'How to use this skill' sections overlap noticeably, and tool-selection guidance is restated later in 'Available MCP tools', so the body could be tightened.	3 / 5
Actionability	Provides concrete tool names, action parameters, call shapes, and copy-pasteable JSON/SQL examples (runQuery payload, _openid column DDL, queryPermissions/managePermissions shapes) covering the common cases.	5 / 5
Workflow Clarity	Five sequenced scenarios with explicit checkpoints: provisioning polls until READY, and the destructive destroy flow requires confirmation, verifies via getInstanceInfo, and recovers from failed tasks via describeTaskStatus.	5 / 5
Progressive Disclosure	Sibling-skill references are one-level-deep and clearly signaled, and sections are well organized, but the full tool reference and all lifecycle flows are inlined in one ~200-line file rather than split into separate bundle files.	4 / 5
	Total	17 / 20 Passed

Description

75%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.

A specific, well-scoped, third-person description with strong action coverage and low conflict risk, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness score.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when an agent must manage CloudBase MySQL via MCP tools') to raise completeness above 3.

Pair the tool-name jargon with the natural phrasings users would actually say ('run SQL', 'check MySQL status', 'set table permissions').

Move the deprecation note to the end so the opening sentence leads with the skill's purpose and trigger, not its replacement.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'MySQL provisioning, destroy flow, async status checks, safe query execution, schema initialization, and permission updates' — alongside specific tool names, giving comprehensive coverage.	5 / 5
Completeness	The 'what' is clearly stated ('defines the canonical SQL management flow...') but there is no explicit 'Use when...' clause; 'for agents operating on...' is only a weakly implied trigger, so completeness caps at 3 per the rubric.	3 / 5
Trigger Term Quality	Good keyword coverage (MySQL, SQL, permissions, provisioning, schema, PostgreSQL, CloudBase) but leans on tool-name jargon like queryMysqlDatabase that users would not naturally say, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	Targets a narrow niche (CloudBase Relational Database via MCP) with distinct tool names and an explicit deprecation pointer to PostgreSQL, giving minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/relational-database-mcp-cloudbase/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.