CtrlK
BlogDocsLog inGet started
Tessl Logo

postgres

Use this skill for any PostgreSQL database work — table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations. **Trigger when user asks to:** - Design or modify PostgreSQL tables, schemas, or data models - Choose data types, constraints, indexes, or partitioning strategies - Work with pgvector embeddings, semantic search, or RAG - Set up full-text search, hybrid search, or BM25 ranking - Use PostGIS for spatial/geographic data - Set up TimescaleDB hypertables for time-series data - Migrate tables to hypertables or evaluate migration candidates - Plan or execute safe schema migrations with zero downtime - Create, fork, or manage databases with Ghost **Keywords:** PostgreSQL, Postgres, SQL, schema, table design, indexes, constraints, pgvector, PostGIS, TimescaleDB, hypertable, semantic search, hybrid search, BM25, time-series, migration, Ghost

76

Quality

95%

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

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-architected hub skill: concise, clearly navigable, with each reference described and triggered appropriately and all referenced paths resolving to real files. No significant weaknesses in the evaluated body.

DimensionReasoningScore

Conciseness

The body is a lean index: every line is either a labeled reference pointer with a one-sentence description or a short workflow step, with no padding or explanation of concepts Claude already knows; each token earns its place.

3 / 3

Actionability

For an index/routing skill, the guidance is concrete and actionable: each reference lists what it covers and a '**Use for…**' trigger, and 'How to Use' gives a specific 3-step procedure (identify, load, load multiple as needed).

3 / 3

Workflow Clarity

Although it is a simple routing skill rather than a destructive multi-step process, the 'How to Use' section sequences the work clearly (identify matching reference → load it → load multiple for cross-area tasks), which the rubric allows to score 3 for simple single-purpose skills.

3 / 3

Progressive Disclosure

Content is appropriately split into one-level-deep reference files (design-postgres-tables.md, pgvector-semantic-search.md, etc.), all of which exist as real symlinked files in references/, each clearly signaled with a description and usage trigger, giving easy navigation.

3 / 3

Total

12

/

12

Passed

Description

90%Weight 40%Scale 1-3

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, well-structured description with explicit triggers and excellent keyword coverage. Its only real weakness is the second-person 'Use this skill for…' opening, which violates the third-person voice rule and caps specificity.

Suggestions

Rewrite the opening in third person to avoid the voice penalty, e.g. 'Provides PostgreSQL expertise for table design, indexing, data types, constraints, extensions, search, and migrations.'

Keep the 'Trigger when user asks to:' clause as-is — it is the strongest part of the description.

DimensionReasoningScore

Specificity

The description lists many concrete actions ('table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations'), which would warrant a 3, but it opens with the second-person voice 'Use this skill for any PostgreSQL database work,' which the rubric penalizes by reducing specificity by 1.

2 / 3

Completeness

It explicitly answers both what ('any PostgreSQL database work — table design, indexing…') and when ('**Trigger when user asks to:**' followed by nine explicit triggers), matching the top anchor.

3 / 3

Trigger Term Quality

The '**Keywords:**' line plus trigger bullets give broad coverage of natural terms users would say — 'PostgreSQL, Postgres, SQL, schema, table design, indexes, constraints, pgvector, PostGIS, TimescaleDB, hypertable, semantic search, hybrid search, BM25, time-series, migration, Ghost'.

3 / 3

Distinctiveness Conflict Risk

The PostgreSQL niche is clearly scoped with distinct triggers tied to specific extensions and tasks, making it unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
timescale/pg-aiguide
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.