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

88%

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.

A thorough, highly actionable skill body with a well-sequenced validated workflow and clean reference navigation. Its main weakness is verbosity from duplicated comparison tables and repeated warnings, plus some bulk cookbook content inlined in SKILL.md that could be deferred to references.

Suggestions

Deduplicate the NoSQL/ORM-vs-PG API comparison table — keep it in one location (e.g. the Required Flow or the SDK Patterns section) and cross-reference it from the other, to recover meaningful tokens.

Move the full CRUD cookbook (count/pagination/upsert/join/RPC examples, lines ~218-250) into a dedicated reference file and keep only the minimal canonical shapes inline in SKILL.md.

Consolidate the repeated auth.uid()-returns-text and CREATE TABLE IF NOT EXISTS warnings into a single authoritative callout in the RLS / schema sections to avoid restating the same caveat three times.

DimensionReasoningScore

Conciseness

The body is platform-specific with no basic-concept padding, but the NoSQL-vs-PG API comparison table is duplicated (lines 50-59 and 252-263) and the auth.uid()-returns-text and CREATE TABLE IF NOT EXISTS warnings repeat, so it could be meaningfully tightened.

3 / 5

Actionability

Provides copy-paste-ready, executable code for SDK init, CRUD, count, pagination, upsert, joins, RPC, and storage uploads, alongside concrete MCP action calls with parameters — fully executable guidance covering common cases.

5 / 5

Workflow Clarity

A numbered 0-12 required flow with explicit validation checkpoints (env confirmation, listMigrations version verify, RLS test-row insert/read-back, dual-layer project+E2E verify) and feedback loops for migration timeouts and RLS failures.

5 / 5

Progressive Disclosure

Clear 'Then also read' pointers and a Reference index, with all eight references real and one level deep; however the body inlines a large CRUD cookbook and duplicate comparison tables that could reasonably live in the referenced files.

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, specific description that names concrete actions, tools, and natural trigger terms while explicitly covering both what the skill does and when to use it. The only weakness is minor overlap with sibling CloudBase auth/web skills, which the body (not the description) disambiguates.

DimensionReasoningScore

Specificity

Enumerates many concrete actions and named tools — 'Postgres schema setup, queryPgDatabase/managePgDatabase, JS SDK v3 app.rdb() CRUD/RPC, PG HTTP API fallback, RLS-style permissions, username-password auth' — giving comprehensive, specific coverage rather than vague language.

5 / 5

Completeness

Explicitly opens with 'Use when building, debugging, or evaluating...' (the when) and follows with an enumerated capability list (the what) with concrete trigger phrases, answering both clearly.

5 / 5

Trigger Term Quality

Covers natural terms users would say with synonyms — 'CloudBase PostgreSQL / CloudBase PG / PG mode' plus 'queryPgDatabase', 'app.rdb()', 'RLS', 'Web CMS/admin CRUD' — comprehensive keyword coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

A clear PG niche with distinct triggers (PG mode, app.rdb(), queryPgDatabase), but 'username-password auth' and 'Web CMS/admin CRUD flows' overlap with sibling CloudBase auth/web skills, giving minor 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.

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.