Name: postgrest
Rating: 61.6 (1 reviews)
Author: membranedev

postgrest

PostgREST integration. Manage data, records, and automate workflows. Use when the user wants to interact with PostgREST data.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/postgrest/SKILL.md

Quality

Content

82%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 content is highly actionable with concrete, copy-paste-ready CLI commands and a well-sequenced connection workflow. It is held back from the top band by minor verbosity, broken step-label references, and a lack of validation checkpoints on the data-operation steps.

Suggestions

Add explicit validation/error-recovery guidance for data operations, e.g. how to confirm an `action run` or `request` succeeded and what to do on non-2xx responses or `CONFIGURATION_ERROR`.

Fix the broken step numbering: the body references "Step 2" and "1b" but never defines a "Step 1" or "Step 2" section — renumber the Connecting/Search/Run sections into a coherent labeled sequence or drop the dangling references.

Trim the introductory PostgREST definition and merge the redundant "Popular actions" section into "Searching for actions" to recover token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the introductory explanation of what PostgREST is and a redundant "Popular actions" section duplicating "Searching for actions" are minor trims that keep it just below fully lean.	4 / 5
Actionability	It provides fully executable, copy-paste-ready bash commands across install, auth, connection, action search/run, and proxy, plus a complete proxy-flag table covering the common cases.	5 / 5
Workflow Clarity	The connection setup is clearly sequenced with a real poll-and-branch feedback loop, but step labels reference an undefined "Step 2" and the actual data-operation steps (run/proxy) lack explicit validation or error-recovery checkpoints.	4 / 5
Progressive Disclosure	The single file is organized into clear section headers with no external references needed, but at ~140 lines some detailed inline content (the clientAction state machine, the proxy flag table) could be split into a reference file.	4 / 5
	Total	17 / 20 Passed

Description

62%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 well-formed with an explicit Use-when clause and a clear, niche domain anchor (PostgREST). Its main weakness is generic action phrasing ("manage data, records, automate workflows") that limits specificity, trigger-term breadth, and distinctiveness.

Suggestions

Replace generic verbs with concrete PostgREST operations, e.g. "Query, insert, update, and delete records via a PostgREST API; call database functions and views."

Broaden trigger terms to cover natural variations users would say, e.g. "Use when the user wants to query or modify PostgREST data, call PostgREST endpoints, or interact with a PostgREST API."

Tighten the "what" so it reads as specific capabilities rather than broad categories, which would also raise distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the PostgREST domain and lists multiple action phrases ("Manage data, records, and automate workflows"), but each action is generic rather than concrete, matching the anchor for naming a domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	It answers both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with PostgREST data") with an explicit trigger clause, but the "what" is generic so it falls short of the fully concrete anchor 5.	4 / 5
Trigger Term Quality	The phrase "interact with PostgREST data" provides a relevant natural keyword ("PostgREST"), but coverage is limited to a single phrase and misses common synonyms or variations a user might say.	3 / 5
Distinctiveness Conflict Risk	The "PostgREST" keyword anchors a distinct niche with minimal conflict risk, but the generic action verbs ("manage data, records, automate workflows") create minor overlap with general data/database skills.	4 / 5
	Total	14 / 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: membranedev/application-skills
Path: skills/postgrest/SKILL.md
Commit: f484c82

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