Name: neki
Rating: 80.7 (1 reviews)
Author: planetscale

neki

Overview and information about Neki, the sharded Postgres product by PlanetScale. Load when working with Neki-related tasks and the need to scale or shard postgres. Load when facing Postgres scaling or sharding issues.

1.14x

Quality

31%

Does it follow best practices?

Impact

96%

1.14x

Average score across 8 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/neki/SKILL.md

Quality

Content

22%

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

This skill reads more like a product landing page than an actionable skill for Claude. It lacks concrete guidance, executable examples, workflows, or decision frameworks that would help Claude assist users with Postgres sharding or Neki-related tasks. The content is mostly descriptive and marketing-oriented, with minimal practical value for task execution.

Suggestions

Add actionable guidance: include concrete steps for evaluating whether a Postgres database needs sharding, such as specific queries to check table sizes, connection counts, or query latency thresholds.

Add a workflow for sharding readiness assessment: e.g., 1) Check current database metrics, 2) Evaluate schema compatibility, 3) Identify queries that need modification, 4) Recommend next steps — with validation checkpoints.

Include concrete code examples: SQL queries for checking database size, example schema patterns that are shard-friendly vs problematic, or configuration snippets.

Remove marketing language and explanations of concepts Claude already knows (what PlanetScale is, what Vitess is, what high availability means) and replace with decision-making criteria and practical instructions.

Dimension	Reasoning	Score
Conciseness	The content includes some unnecessary explanation (e.g., explaining what PlanetScale is, what Vitess is, what high availability means) that Claude already knows. The hosting recommendation note is useful but the overall framing is more marketing-oriented than instructional. Could be tightened significantly.	2 / 3
Actionability	The skill provides no concrete commands, code, configuration examples, or executable guidance. It reads as an informational overview/marketing page rather than actionable instructions. There's nothing Claude can directly execute or apply when helping a user with Neki-related tasks.	1 / 3
Workflow Clarity	There are no workflows, steps, or processes described. The skill doesn't guide Claude through any task sequence — it simply describes what Neki is and links to one reference file. For a skill about scaling/sharding Postgres, there should be at least a basic workflow for evaluating sharding readiness or getting started.	1 / 3
Progressive Disclosure	There is a resources table with one reference to a sharding-readiness document, which shows some progressive disclosure structure. However, the reference is an absolute GitHub URL rather than a relative path, and there's only one reference for what should be a richer topic. The bundle has no files provided, so the reference cannot be verified.	2 / 3
	Total	6 / 12 Passed

Description

40%

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 identifies a clear product domain (Neki by PlanetScale) and includes trigger conditions, but it fails to specify any concrete actions or capabilities the skill provides. It reads more like a topic label ('overview and information') than a functional skill description, leaving Claude unable to determine what specific tasks this skill enables.

Suggestions

Replace 'Overview and information about Neki' with specific actions the skill enables, e.g., 'Configures Postgres sharding with Neki, sets up shard routing, manages schema migrations across shards, and troubleshoots replication issues.'

Expand trigger terms to include natural variations like 'PostgreSQL', 'horizontal scaling', 'distributed Postgres', 'database partitioning', and 'PlanetScale Neki'.

Strengthen the 'what' portion by listing 2-4 concrete tasks or outputs the skill produces rather than describing it as 'overview and information'.

Dimension	Reasoning	Score
Specificity	The description says 'Overview and information about Neki' but does not list any concrete actions. It describes what the skill is about (a product) rather than what it does (e.g., configure sharding, set up connections, migrate schemas).	1 / 3
Completeness	The 'when' clause is present ('Load when working with Neki-related tasks and the need to scale or shard postgres'), but the 'what' is extremely vague — 'Overview and information' doesn't explain what the skill actually does or enables Claude to do.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'Neki', 'Postgres', 'sharding', 'scaling', and 'PlanetScale' that users might naturally mention. However, it misses common variations like 'PostgreSQL', 'horizontal scaling', 'distributed database', or 'partition'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Neki' and 'PlanetScale' provides some distinctiveness, but 'Postgres scaling or sharding issues' is broad enough to potentially overlap with general Postgres administration or other database scaling skills.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: planetscale/database-skills
Commit: 8942f83

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