CtrlK
BlogDocsLog inGet started
Tessl Logo

postgresql-development-cloudbase

Use when building, debugging, or evaluating CloudBase PostgreSQL / CloudBase PG / PG mode apps, including Postgres schema setup, queryPgDatabase/managePgDatabase, JS SDK v3 app.rdb() CRUD/RPC, PG HTTP API fallback, RLS-style permissions, username-password auth, and Web CMS/admin CRUD flows backed by CloudBase PG.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is postgresql-development-cloudbase in TencentCloudBase/CloudBase-AI-Toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 exceptionally actionable and well-sequenced with strong validation feedback loops and a clean one-level reference structure. Its main weakness is verbosity — duplicated API-mismatch tables and restated rules — that inflates the context cost without adding guidance.

Suggestions

Collapse the two near-identical 'NoSQL/ORM vs PG' method tables (lines ~49–58 and ~203–210) into a single canonical table; the second copy adds no new information.

Trim repeated guardrails — e.g. 'auth.uid() returns text not uuid' and 'do not use current_user in RLS' each appear multiple times — keep one authoritative statement and cross-reference it.

Move the full migration-action enumeration (planMigration/fetchMigration/rollbackMigration/repairMigration) into a reference file, leaving only the core apply/verify loop inline, to reduce the SKILL.md token footprint.

DimensionReasoningScore

Conciseness

Mostly efficient and genuinely high-signal, but the body is long (~280 lines) with several padded/ reiterated sections — the NoSQL-vs-PG table appears twice near-identically, migration actions are re-listed, and some guardrails restate rules already covered — so it could be tightened without losing substance.

3 / 5

Actionability

Fully executable guidance throughout: copy-paste CRUD shapes, real MCP tool calls with named parameters (queryPgDatabase(action=...)), exact documented HTTP base URLs, and concrete SQL bundles for GRANT/RLS — covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

A numbered Required Flow (steps 0–12) sequences environment confirmation through DDL/migration, auth, CRUD, and verification, with explicit validation checkpoints (envQuery gate, column-name inspection before CREATE, read-back verification after DDL, RLS error inspection) and feedback loops (MIGRATION_TASK_TIMEOUT → describeMigrationTask, retry-twice-then-inspect).

5 / 5

Progressive Disclosure

SKILL.md acts as a concise overview pointing to eight well-signaled one-level-deep references (references/index.md plus topic files), all of which exist as real files, with a Reference index section and a sibling-skill routing map; detail is appropriately split out and navigation is explicit.

5 / 5

Total

18

/

20

Passed

Description

100%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 a model trigger clause: it leads with 'Use when', enumerates concrete PG-specific capabilities, packs in natural synonyms and exact API names, and is clearly distinguishable from sibling NoSQL/MySQL skills. It earns top marks on all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities spanning setup through verification — 'Postgres schema setup', 'queryPgDatabase/managePgDatabase', 'JS SDK v3 app.rdb() CRUD/RPC', 'PG HTTP API fallback', 'RLS-style permissions', 'username-password auth', and 'Web CMS/admin CRUD flows' — giving comprehensive action coverage.

5 / 5

Completeness

Opens with an explicit 'Use when building, debugging, or evaluating' trigger and immediately enumerates the concrete 'what' (schema setup, CRUD/RPC, HTTP fallback, RLS, auth, CMS flows), explicitly answering both what and when with concrete phrases.

5 / 5

Trigger Term Quality

Dense natural trigger terms and synonyms — 'CloudBase PostgreSQL / CloudBase PG / PG mode', 'Postgres', 'PostgreSQL', 'RLS', 'app.rdb()', 'queryPgDatabase', 'managePgDatabase' — covering both lay names and the exact API tokens a user or task would cite.

5 / 5

Distinctiveness Conflict Risk

Tightly scoped to CloudBase PG-specific APIs and explicitly contrasts with MySQL (queryMysqlDatabase/manageMysqlDatabase) and NoSQL siblings, carving a clear niche with minimal conflict risk against adjacent CloudBase skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
TencentCloudBase/CloudBase-AI-Toolkit
Reviewed

Table of Contents

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.