Name: neon
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

neon

Neon integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Neon data.

Quality

65%

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

Fix and improve this skill with Tessl

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

Quality

Content

67%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 concrete CLI commands and a well-structured connection workflow including state-based checkpoints. It is held back by an unnecessary introductory explanation of what Neon is and templated placeholders that prevent fully copy-paste-ready examples.

Suggestions

Remove the opening paragraph explaining what Neon is ('Neon is a fully managed serverless Postgres database...') since Claude already knows this.

Add at least one fully-resolved worked example (real connection id and action id) so users can copy-paste without substituting placeholders.

Tighten explanatory prose around authentication and connection setup to reduce padding like 'so you can focus on the integration logic rather than auth plumbing'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows ('Neon is a fully managed serverless Postgres database...') and mild padding like 'so you can focus on the integration logic rather than auth plumbing'.	3 / 5
Actionability	Provides concrete, executable commands (install, login, connection ensure, action run, request) with a full flag table, but examples rely on placeholders like CONNECTION_ID and <actionId> requiring substitution rather than being fully copy-paste ready.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop after user action; falls short of a full validate-fix-retry checklist.	4 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no bundle files to reference; minor gaps as some inlineable reference material (proxy flag table) stays in SKILL.md.	4 / 5
	Total	15 / 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 covers both what the skill does and when to use it, anchored to a specific product niche. Its main weakness is a generic 'Manage' verb and limited trigger-term coverage lacking Postgres/database synonyms.

Suggestions

Replace the generic verb 'Manage' with concrete actions per entity (e.g. 'Create and list Organizations, invite Users, set Goals, apply Filters').

Broaden trigger terms to include natural synonyms users say, such as 'Postgres', 'database', or 'serverless Postgres'.

Make the 'when' clause more specific than 'interact with Neon data', e.g. 'Use when the user wants to query or manage a Neon Postgres database'.

Dimension	Reasoning	Score
Specificity	Names the Neon domain and concrete entities ('Manage Organizations, Users, Goals, Filters') but the single generic verb 'Manage' applied to a noun list is not comprehensive concrete action coverage.	3 / 5
Completeness	Both 'what' ('Neon integration. Manage Organizations, Users, Goals, Filters') and an explicit 'when' ('Use when the user wants to interact with Neon data') are present, though the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes the natural product name 'Neon' and the phrase 'interact with Neon data', but misses common synonyms a user might say such as 'Postgres', 'database', or 'serverless Postgres'.	3 / 5
Distinctiveness Conflict Risk	'Neon integration' is a clear, product-specific niche with a distinct trigger; minor overlap risk only because 'interact with Neon data' is somewhat broad.	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/neon/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.