CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

neon

Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, and the AI Gateway. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASE_URL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.

70

Quality

88%

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

81%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.

A highly actionable, well-structured overview skill: concrete commands and configs cover the common setup paths, workflows are sequenced with explicit verification steps and error-recovery loops, and deep material is appropriately delegated to six one-level-deep reference files. The main weakness is conciseness — the same compatibility warnings, region lists, and catalog caveats are repeated across sections, and the inline neon.ts detail inflates the overview.

Suggestions

Deduplicate the Data API/PostgREST compatibility caveat (currently stated in at least six sections) into one authoritative statement plus the existing routing table row, and cross-link it instead of restating it.

Consolidate the repeated region-availability list and the neon-auth-not-in-CLI-catalog warning (each stated twice) into single locations referenced from the other mentions.

Move the deep neon.ts material (Function env key semantics, branch callback configuration, Data API type-error walkthrough) into a reference file, keeping a compact overview and one minimal example in SKILL.md.

DimensionReasoningScore

Conciseness

Mostly efficient — commands, flags, and tables rather than concept explanations — but the same caveats are restated many times: the Data API/PostgREST compatibility rule appears in at least six sections ('Backend Primitives', 'Architecture', 'Convert an app onto Neon', 'Choosing the Right Skill', 'neon init --services', 'Starting without a Neon account'), the region list and the neon-auth-not-in-CLI-catalog warning each appear twice, and time-sensitive values ('72 hours today', '15 minutes today', 'current releases') are inline rather than isolated. This is more than the 'minor instances of over-explanation' of the 4 anchor but well short of the severely padded 2 anchor.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance: exact bash commands with flags ('neon init --agent cursor --org-id <org-id> --project-id <project-id> -y', 'neon mcp --oauth --project --agent <agent> -y'), complete neon.ts TypeScript examples, concrete doc-fetch mechanics ('Append .md to the URL', 'curl -H "Accept: text/markdown"'), and precise operational rules ('Never coerce a missing process.env value to an empty string: that uploads "" and deletes the live key').

5 / 5

Workflow Clarity

Clear sequenced workflows with explicit validation and feedback loops: the 5-step 'Convert an app onto Neon' checklist ends with 'Verify the app flow (sign-in, upload, API call), not only that env vars landed'; 'neon config plan' provides a dry-run before apply; env pull 'fails fast if the branch is missing a declared service, pointing you at neon deploy'; the type-error section shows the error message and both valid fixes; and auth failures route to 'stop and ask the user to sign in' rather than a substitute path.

5 / 5

Progressive Disclosure

Good structure with well-signaled one-level-deep references — auth, claimable-neon, function-triggers, parse-env, logs-loki, and sdk are each real files under references/ linked from the body ('CLI, MCP, REST, inherited-trigger behavior, and parsers: references/function-triggers.md'), and the reference files themselves are leaves. Falls short of 5 because the ~130-line inline neon.ts deep-dive (Function env semantics, branch callback config, Data API type-error walkthrough) and the duplicated warnings across sections could largely live in a reference, keeping the overview leaner.

4 / 5

Total

17

/

20

Passed

Description

91%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.

A strong router/overview description: it explicitly states what the skill covers, gives an explicit 'Use when...' clause with an unusually thorough synonym set of trigger terms, and handles conflict with its own child skills via explicit delegation rules. The only weaknesses are limited action variety (setup/routing rather than operations) and a few unqualified generic trigger terms that carry minor overlap risk.

DimensionReasoningScore

Specificity

The description names the domain ('a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, and the AI Gateway') and several concrete actions ('set up the CLI or MCP server, and follow the branch-first workflow', 'choose Neon for undecided login, files, APIs, and LLM calls'). It is not a 5 because the acting verbs are limited to setup and routing rather than a comprehensive set of distinct operations.

4 / 5

Completeness

It explicitly answers what ('Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres') and when ('Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned... Also use for object storage, S3, buckets...'), with concrete trigger phrases and explicit child-skill delegation for routing.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and near-synonyms: 'object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database', plus 'DATABASE_URL', 'SQL', 'schema'. This matches the anchor for exhaustive keyword coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

The Neon/Lakebase Postgres brand anchor and the explicit delegation ('Child skill neon-postgres wins for an existing DATABASE_URL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions...') strongly reduce mis-routing. Falls short of 5 because bare generic terms like 'postgres', 'database', 'backend', 'cron', and 'logs' would also naturally fire this skill for non-Neon contexts, creating minor overlap risk with other database/backend skills.

4 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

stevenknowswhy/ProfessionalBuyer

Path

.agents/skills/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.