Name: relational-database-mcp-cloudbase
Rating: 62.4 (1 reviews)
Author: TencentCloudBase

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

74%

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

The canonical home for this skill is relational-database-mcp-cloudbase in TencentCloudBase/CloudBase-AI-Toolkit

Quality

Content

73%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 delivers actionable, well-sequenced workflows with strong validation for destructive operations, but it is hampered by duplicated guidance across the activation, use, and tool sections and inlines material that could be split into reference files.

Suggestions

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

Move the per-tool reference ('Available MCP tools') and 'Compatibility' notes into a separate references file, keeping SKILL.md as a lean overview with a clear pointer.

Add one complete end-to-end example call for provisioning (provisionMySQL) and destroy (destroyMySQL) showing all required parameters, not just the action name.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the 'Activation Contract', 'When to use this skill', and 'How to use this skill' sections restate overlapping tool-selection and use-case guidance that appears again in 'Available MCP tools', introducing noticeable duplication that could be tightened.	3 / 5
Actionability	Provides concrete call shapes (e.g., 'queryPermissions(action="getResourcePermission", resourceType="sqlDatabase", resourceId="<tableName>")') and a JSON runQuery example, but lacks a complete end-to-end provisioning/destroy invocation showing all parameters, leaving minor gaps.	4 / 5
Workflow Clarity	Five numbered lifecycle scenarios each sequence steps with explicit validation checkpoints (poll until 'READY', read-only check before writes, confirm before destroy, query describeTaskStatus until completion) and feedback loops for failure recovery on destructive operations.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep sibling-skill references (e.g., '../relational-database-web-cloudbase/SKILL.md'); no bundle files exist so all content is inlined, and the detailed tool reference could arguably live in a separate file, leaving a minor organization gap.	4 / 5
	Total	16 / 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.

The description is specific, well-scoped, and clearly distinct from sibling skills, but it omits any explicit 'Use when...' trigger guidance, which caps completeness. Trigger-term coverage is good but lacks natural synonyms.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations (e.g., 'Use when an agent must provision, query, or destroy CloudBase MySQL, or manage SQL table permissions via MCP').

Include natural synonyms and variations users might say (e.g., 'CloudBase MySQL', 'SQL permissions', 'security rules') to broaden trigger-term coverage.

Lead with the active capability statement before the deprecated notice so the 'what' is immediately visible.

Dimension	Reasoning	Score
Specificity	Names four concrete MCP tools and enumerates multiple specific actions ('MySQL provisioning, destroy flow, async status checks, safe query execution, schema initialization, and permission updates'), giving comprehensive coverage of capabilities.	5 / 5
Completeness	The 'what' is detailed and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance; per the guideline a missing explicit 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural domain terms a user would say ('CloudBase Relational Database', 'MySQL', 'MCP') plus tool names, but lacks synonyms/common variations and has no plain-language trigger phrasing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	It targets a clear niche (CloudBase Relational Database via specific MCP tools) and explicitly redirects new environments to PostgreSQL, minimizing overlap with sibling 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: config/.claude/skills/relational-database-mcp-cloudbase/SKILL.md
Commit: 3ce25cd

Reviewed: ~13 hours 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.