Name: cockroachdb
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

cockroachdb

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

Quality

61%

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/cockroachdb/SKILL.md

Quality

Content

61%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 largely actionable with concrete Membrane CLI commands and a solid connection-state feedback loop. It is held back by an unnecessary 'what is CockroachDB' intro, filler lines, and the absence of validation steps for the destructive/database action-execution workflow.

Suggestions

Remove or trim the introductory paragraph explaining what CockroachDB is and delete filler like 'Use action names and parameters as needed.' to improve token efficiency.

Add a validation/verification checkpoint after running actions or proxy requests (e.g. check the `output`/`error` fields, confirm row counts) to satisfy the database-operations feedback-loop requirement.

Provide at least one fully-worked action-run example with real-looking parameters and expected output so the guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but the opening paragraph explains what CockroachDB is (a concept Claude already knows) and filler like 'Use action names and parameters as needed.' adds padding, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a flag table; minor gaps such as placeholders (CONNECTION_ID) and no worked action-run example keep it at 4 rather than 5.	4 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear with a good polling/feedback loop for connection state, but the data-operation steps (action run, proxy requests) lack validation/verification; per the database-operations cap, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	No bundle files exist; content is a single well-sectioned file with clear headers and only an external docs link, giving good structure and easy navigation with minor organization gaps (e.g. the proxy flag table inline) rather than a 5.	4 / 5
	Total	14 / 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 correctly uses third-person voice and includes both a 'what' and a 'when' clause with the product name as the primary trigger. It is weakened by generic action verbs ('manage data, records, automate workflows') and a thin set of trigger variations.

Suggestions

Replace generic verbs with concrete CockroachDB-specific actions (e.g. 'Run SQL queries, manage databases and tables, inspect cluster health') to lift specificity.

Expand the 'Use when' clause with natural trigger phrases and synonyms (e.g. 'CockroachDB, CRDB, distributed SQL database, cluster, SQL queries').

Add file-format or object-level terms users actually say (e.g. 'tables', 'indexes', 'queries') to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ('CockroachDB integration') and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete; it does not reach the 'several specific actions' bar of 4.	3 / 5
Completeness	Both 'what' (CockroachDB integration; manage data/records; automate workflows) and 'when' ('Use when the user wants to interact with CockroachDB data') are present; the 'when' is explicit but could be more specific with additional trigger phrases, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	The main natural keyword 'CockroachDB' is present in the trigger clause, but common variations/synonyms (e.g. 'distributed SQL', 'CRDB', 'cluster') are missing, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The CockroachDB product name gives it a clear niche, but the generic 'manage data, records' phrasing leaves minor overlap risk with other database-integration skills, fitting 'mostly distinct; minor overlap risk'.	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/cockroachdb/SKILL.md
Commit: f484c82

Reviewed: ~14 hours 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.