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.

74

Quality

92%

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

85%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 highly actionable with executable code, precise MCP signatures, explicit validation checkpoints, and well-organized one-level-deep references. Its main weakness is conciseness: a duplicated comparison table and repeated auth.uid()/RLS warnings across several sections could be consolidated.

Suggestions

Consolidate the two NoSQL/ORM-vs-PG comparison tables (lines 49-58 and 203-209) into a single table in the JS SDK Patterns section, linking to it from the Required Flow instead of repeating it.

Centralize the auth.uid()/RLS helper guidance (currently repeated in step 9, Data Model Rules, and reference pointers) into one location and point other sections to references/auth-and-rls.md or references/rls-patterns.md.

Remove the stray Chinese fragments inside the second comparison table (lines 205-211: '或', '通过 select 的 count 参数获取总数', '注意 range 是包含两端的分页') to keep the skill in a single consistent language.

DimensionReasoningScore

Conciseness

Mostly efficient and information-dense, but the NoSQL/ORM-vs-PG comparison table is duplicated verbatim (Required Flow lines 49-58 and JS SDK Patterns lines 203-209) and the auth.uid()/RLS guidance is repeated across step 9, Data Model Rules, and the reference pointers — clear tightening candidates.

3 / 5

Actionability

Provides copy-paste-ready TypeScript (imports, CRUD shapes, auth.getSession helper, storage upload) plus exact MCP call signatures like 'managePgDatabase(action=applyMigration, migrationName=..., migrationVersion=..., sql=..., confirm=true)' and concrete error-code fixes.

5 / 5

Workflow Clarity

The Required Flow (steps 0-12) and migration workflow (1-6) have explicit validation checkpoints ('Verify: listMigrations', 'After DDL, re-query the schema and compare', 'Verify both layers before claiming done') plus feedback loops for MIGRATION_TASK_TIMEOUT and RLS failures, and a Quick Checks checklist.

5 / 5

Progressive Disclosure

A Reference index lists all 8 bundle files (each verified present in references/) with well-signaled one-level-deep pointers inline ('See references/auth-and-rls.md', 'read references/app-workflow.md'); the overview stays inline while detail is split into references.

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 exemplary: it states explicit trigger conditions, enumerates concrete capabilities, includes multiple natural synonyms, and carves out a distinct niche with minimal conflict risk. It uses the standard third-person 'Use when...' trigger form with no first/second-person voice issues.

DimensionReasoningScore

Specificity

Lists multiple 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' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both: when ('Use when building, debugging, or evaluating CloudBase PostgreSQL / CloudBase PG / PG mode apps') and what (the enumerated capability list), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural synonyms and product-specific tokens users would actually say — 'CloudBase PostgreSQL / CloudBase PG / PG mode', 'Postgres', 'app.rdb()', 'queryPgDatabase', 'RLS', 'Web CMS/admin CRUD' — with strong synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (CloudBase PG mode) with distinct triggers like 'app.rdb()', 'queryPgDatabase', and 'PG mode' that are unlikely to fire for NoSQL/MySQL 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.