CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

90%

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

SKILL.md
Quality
Evals
Security

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.

An exceptionally actionable, well-sequenced operating manual with real validation checkpoints and feedback loops for database and migration work. Its weaknesses are redundancy (a duplicated comparison table and warnings repeated 3+ times) and inlining detail that belongs in the existing reference files, which hurts token efficiency.

Suggestions

Remove the second, partly-Chinese copy of the NoSQL-vs-PG method table in 'JS SDK v3 PostgreSQL Patterns' (including its 'Golden rule' paragraph) — the table in Required Flow plus the 'Common query helpers' list already covers it.

State each repeated warning once — 'auth.uid() returns text not uuid', 'use auth.getSession() not auth.getUser()', and 'bucket must exist before upload' each appear 3+ times — and point to the relevant reference file (auth-and-rls.md, storage-pg.md) instead of repeating.

Move the storage failure-mode cheat sheet and the extended migration-action details (fetchMigration/repairMigration, out-of-order versions) into references/storage-pg.md and a migration-focused reference, keeping SKILL.md to the core flow.

DimensionReasoningScore

Conciseness

The body is mostly dense, non-obvious platform guidance, but the NoSQL-vs-PG method table appears twice (in "Required Flow" and again in "JS SDK v3 PostgreSQL Patterns", the second copy partly in Chinese), and warnings like "auth.uid() returns text, not uuid" and "only use auth.getSession(), never auth.getUser()" each repeat 3+ times across sections. This is more than anchor 4's "minor instances" of over-explanation, but the bulk still earns its place, so it does not fall to anchor 2's padded level.

3 / 5

Actionability

Provides copy-paste-ready TS snippets (SDK init, CRUD shapes, count/pagination/upsert/RPC), exact MCP call signatures with parameters (e.g. managePgDatabase(action=applyMigration, migrationName=..., confirm=true)), a full SQL owner-table template, exact CLI commands, and a failure-mode table keyed on real error codes. Fully executable and covering the common cases, matching anchor 5.

5 / 5

Workflow Clarity

The Required Flow is a clearly numbered 0-12 sequence with explicit validation (step 0 environment probe with STOP conditions, "Verify: managePgDatabase(action=listMigrations)", post-DDL schema re-query with column comparison, "Verify both layers before claiming done"), feedback loops ("retry SQL at most twice" then query objects; MIGRATION_TASK_TIMEOUT handled via describeMigrationTask before any re-push), and a Quick Checks checklist — the anchor 5 pattern for database operations.

5 / 5

Progressive Disclosure

All 10 referenced files exist in references/, are one level deep, clearly signaled with purpose (e.g. "MUST read before writing any bucket / upload / URL code"), and backed by a genuine routing index (references/index.md with a read order). However, substantial detail is inlined in SKILL.md — the storage failure-mode cheat sheet (duplicated by references/storage-pg.md), extended migration-action details, and the second copy of the API comparison table — so anchor 4's "minor organization gaps" fits better than anchor 5's "content appropriately split".

4 / 5

Total

17

/

20

Passed

Description

96%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 strong, highly specific description with an explicit "Use when" trigger clause, synonym coverage ("CloudBase PostgreSQL / CloudBase PG / PG mode"), and a concrete capability list tied to named APIs. Its only weakness is a minor overlap risk with sibling CloudBase auth skills via the "username-password auth" clause.

DimensionReasoningScore

Specificity

Enumerates concrete capabilities — "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" — naming specific APIs rather than vague actions. Matches the anchor-5 breadth (setup, data access, permissions, auth, and app flows all covered); anchor 4 would require minor coverage gaps that are not present.

5 / 5

Completeness

"Use when building, debugging, or evaluating CloudBase PostgreSQL... apps" explicitly answers when, and the "including..." clause explicitly answers what with concrete capabilities. The trigger guidance is explicit and leading, matching anchor 5; anchor 4 would require the 'when' to be less explicit or specific, which it is not.

5 / 5

Trigger Term Quality

"CloudBase PostgreSQL / CloudBase PG / PG mode" provides explicit synonyms, alongside natural developer terms like "Postgres", "app.rdb()", "queryPgDatabase", and "RLS". A user needing this skill would naturally say these; no common variation is missing, so it fits anchor 5 rather than anchor 4's "a few natural terms missing".

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (CloudBase PG mode) with platform-specific triggers like "queryPgDatabase" and "app.rdb()" that minimize conflict with generic skills. However, "username-password auth" is also a natural trigger for the sibling auth skill, so a non-PG CloudBase auth question could route here — minor overlap with a closely related skill, fitting anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

19

/

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.

Validation — 15 / 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

Path

plugin/cloudbase/skills/postgresql-development-cloudbase/SKILL.md

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.