CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

using-neon

Neon is a serverless Postgres platform that separates compute and storage to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/using-neon/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 SKILL.md body is a well-structured, token-efficient routing index: it gives executable doc-fetch commands, explicit anti-guessing rules, and cleanly organized one-level-deep reference tables. Its main weaknesses are the verbatim duplication of the frontmatter description, generic when-to-use bullets, an implicit rather than explicit workflow sequence, and reference files that could not be verified in the bundle as provided.

Suggestions

Remove the opening paragraph that duplicates the frontmatter description verbatim, and tighten or drop the generic 'When to Use This Skill' bullets — the routing tables already convey this more concretely.

Make the docs workflow explicit, e.g. '1. Pick the resource file from the tables below; 2. Fetch live docs via llms.txt only when the reference file lacks the answer', and include one worked curl example with a real docs path instead of the `<path>` placeholder.

Fix the small copy errors ("additonal" → "additional", "support you find" → "help you find") to match the skill's otherwise polished presentation.

DimensionReasoningScore

Conciseness

The body is dominated by lean routing tables that earn their tokens, but the opening paragraph repeats the frontmatter description verbatim, the 'When to Use This Skill' bullets are generic (e.g. "Questions about Neon best practices"), and there are minor typos ("additonal", "support you find"). This matches anchor 4 — efficient with minor instances that could be trimmed — rather than 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete executable commands are provided: `curl https://neon.com/llms.txt` and `curl -H "Accept: text/markdown" https://neon.com/docs/<path>`, plus the explicit rule "Don't guess docs pages. Use the llms.txt index". The `<path>` placeholder is unfilled and no worked fetch example is given, so it is 'mostly executable with minor gaps' (anchor 4) rather than fully copy-paste ready for the common case.

4 / 5

Workflow Clarity

The routing workflow is unambiguous: each resource table pairs a file with a 'When to Use' column, and the docs-fetch path is prescribed via llms.txt. No destructive or batch operations exist, so the validation cap does not apply, but the reference-then-fetch-docs sequence is implicit rather than explicitly sequenced with checkpoints — anchor 4, not 5's explicit step/checkpoint structure.

4 / 5

Progressive Disclosure

The body is a genuine overview that routes to 13 well-signaled, one-level-deep reference files organized in labeled tables with per-file 'When to Use' guidance — close to anchor 5's structure. However, none of the referenced `references/*.md` files exist in the provided bundle, so the referenced paths could not be verified as real files, keeping it at anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

61%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 clear and factually specific about what Neon is, with a distinct niche and good keyword coverage, but it reads as a product description rather than a skill capability description: it never states what the skill does and omits any explicit 'Use when...' trigger guidance. Adding a trigger clause and concrete skill actions would raise completeness and specificity substantially.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when working with Neon databases, setting up serverless Postgres, choosing connection methods, or managing branches via the Neon API/CLI' — the missing trigger clause currently caps completeness at 3.

State concrete skill actions instead of only platform features, e.g. 'Sets up Neon projects and connection strings, chooses drivers/ORMs, and manages Neon branches via CLI and Platform API' to complement the feature list.

Include additional natural trigger terms users would say, such as 'Neon database', 'connection string', and 'serverless database', to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("serverless Postgres platform") and several concrete platform features ("autoscaling, branching, instant restore, and scale-to-zero"), but states no actions the skill itself performs — there is no 'set up', 'connect', or 'manage' verb describing capability. Anchor 4 requires several specific actions, which are absent, so it sits at anchor 3: domain named with concrete but non-comprehensive action coverage.

3 / 5

Completeness

"Neon is a serverless Postgres platform that separates compute and storage to offer autoscaling, branching, instant restore, and scale-to-zero" clearly answers 'what', but 'when' is entirely absent — there is no 'Use when...' clause or equivalent explicit trigger guidance (compatibility with Postgres stacks only weakly implies it). Per the judging guidelines this caps completeness at 3, matching anchor 3 ('has a clear what but when is missing or only weakly implied') and not anchor 4, which requires an explicit 'when'.

3 / 5

Trigger Term Quality

Natural terms a user would say are present: "Neon", "serverless Postgres", "Postgres", "autoscaling", "branching", "ORM". Common variations like "Neon database", "connection string", or "set up a Postgres database" are missing, matching anchor 4 (good keyword coverage, a few natural terms missing) rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Neon" and "serverless Postgres" establish a clear niche with minimal conflict risk, but "fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres" broadens the trigger surface toward generic Postgres/database skills — minor overlap risk with closely related skills, matching anchor 4 rather than 5's minimal conflict risk.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 14 missing

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/using-neon/SKILL.md

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.