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

96%

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

Quality

Content

92%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 expert, highly operational skill body with excellent actionability, strong validation-laced workflows, and a clean one-level reference structure. The main weakness is redundancy: the NoSQL/ORM comparison table and its critical warning are restated in a second section, lightly inflating the body.

Suggestions

Remove the duplicate NoSQL/ORM-vs-PG comparison table and "CRITICAL" warning in the "JS SDK v3 PostgreSQL Patterns" section, keeping a single authoritative version in Required Flow and cross-referencing it.

Resolve the language inconsistency in the second table (lines with Chinese annotations such as "或", "通过 select 的 count 参数获取总数") so the skill is consistently in one language.

Consider moving the storage error-code cheat sheet and the full migration-action list into references/ (e.g. storage-pg.md / a migrations reference) to further slim the main SKILL.md toward an overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, high-signal CloudBase-specific guidance Claude would not already know, but it repeats the NoSQL/ORM-vs-PG comparison table and the "CRITICAL: PG mode API is NOT the same as NoSQL" warning in two separate sections (Required Flow and JS SDK Patterns), which is trimmable redundancy.	4 / 5
Actionability	Copy-paste-ready TS snippets (init, getSession, canonical CRUD shapes, storage upload), exact MCP action signatures (applyMigration with named params), concrete file paths, and an error-code cheat sheet mapping codes to fixes leave no execution gap.	5 / 5
Workflow Clarity	The numbered Required Flow (steps 0–12) includes explicit validation checkpoints (envQuery RuntimeBackends check, listMigrations verify, post-DDL schema re-query, build+E2E before claiming done) and feedback loops (RLS insert/read-back/fix, DDL retry-then-query-objects), satisfying the destructive-ops validation bar rather than capping at 3.	5 / 5
Progressive Disclosure	A clear Reference Index plus a "Then also read" section signal one-level-deep references; all eight referenced files exist and resolve exactly one level, with references/index.md providing an explicit read order, so navigation is easy and content is appropriately split.	5 / 5
	Total	19 / 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.

A dense, well-constructed description that names a specific platform niche, enumerates concrete capabilities with real API names, and opens with an explicit "Use when" trigger covering multiple synonyms. It reads like the rubric's good examples and has no fluff or voice issues.

Dimension	Reasoning	Score
Specificity	The description lists many concrete actions and named 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" — which is comprehensive coverage rather than the minor-gaps profile of a 4.	5 / 5
Completeness	An explicit "Use when building, debugging, or evaluating CloudBase PostgreSQL / CloudBase PG / PG mode apps" clause supplies the WHEN, while the capability list supplies the WHAT, so it clears the "Use when"-clause cap and hits the explicit-both anchor.	5 / 5
Trigger Term Quality	It supplies natural synonyms a user would actually say ("CloudBase PostgreSQL / CloudBase PG / PG mode", "Postgres") plus concrete API trigger tokens (app.rdb(), queryPgDatabase, RLS), matching the comprehensive-synonyms anchor rather than the good-but-incomplete 4.	5 / 5
Distinctiveness Conflict Risk	The PG-specific API surface (app.rdb(), queryPgDatabase, managePgDatabase, PG mode) carves a clear niche distinct from the MySQL/NoSQL sibling skills, giving minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
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
Commit: f07c33c

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