cockroachdb-sql
Use when writing, generating, or optimizing SQL for CockroachDB, designing CockroachDB schemas, or when the user asks about CockroachDB-specific SQL patterns, type mappings, and distributed database best practices. Also use when encountering CockroachDB anti-patterns like missing primary keys, sequential ID hotspots, or incorrect type usage.
81
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/query-and-schema-design/cockroachdb-sql/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger coverage and completeness. It clearly specifies when to use the skill with an explicit 'Use when...' clause and includes CockroachDB-specific terminology that makes it highly distinctive. The main weakness is that the 'what' portion could be more concrete with specific actions rather than broad categories like 'writing, generating, or optimizing SQL'.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'Generates CockroachDB-compatible DDL, converts PostgreSQL queries to CockroachDB syntax, recommends UUID-based primary keys, optimizes queries for distributed execution.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (CockroachDB SQL) and mentions several actions like writing/generating/optimizing SQL, designing schemas, and identifying anti-patterns, but these are somewhat general categories rather than multiple concrete, specific actions like 'extract text, fill forms, merge documents'. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (writing/optimizing SQL, designing schemas, CockroachDB-specific patterns and anti-patterns) and 'when' with clear 'Use when...' triggers covering multiple scenarios including writing SQL, schema design, and encountering anti-patterns. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'SQL', 'CockroachDB', 'schemas', 'type mappings', 'distributed database', 'primary keys', 'sequential ID hotspots', 'anti-patterns'. These are terms users would naturally use when seeking CockroachDB help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific focus on CockroachDB rather than generic SQL. The mention of CockroachDB-specific concerns like 'sequential ID hotspots' and 'distributed database best practices' clearly distinguishes it from general SQL or other database skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has a well-structured workflow with a strong validation feedback loop (EXPLAIN mandate), which is its greatest strength. However, it is moderately verbose with sections like 'When to Use This Skill' that add little value for Claude, and it lacks concrete executable SQL examples that would make it more actionable. The progressive disclosure to reference files is reasonable but cannot be fully verified without bundle files.
Suggestions
Add 2-3 concrete, executable SQL examples (e.g., a CREATE TABLE with UUID primary key, a SELECT with EXPLAIN output) to improve actionability.
Remove or significantly trim the 'When to Use This Skill' section — this information is already captured in the YAML description and Claude doesn't need trigger-phrase examples to understand when to apply the skill.
Include at least one complete input→output example showing natural language input, generated SQL, and expected EXPLAIN validation flow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the 'When to Use This Skill' section which largely restates what the YAML description already covers, and the bullet list of trigger phrases is verbose. However, the core workflow and rules are reasonably efficient. | 2 / 3 |
Actionability | Provides concrete commands like `cockroach sql --url` and `SHOW TABLES;`, and specifies the EXPLAIN validation loop, but lacks executable SQL examples. The references to rule files provide structure but the skill itself doesn't include copy-paste-ready code patterns or example outputs. | 2 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced (parse intent → gather context → apply rules → validate against DB), with an explicit validation checkpoint (EXPLAIN loop with fix-and-retry feedback) marked as MANDATORY. The connection detection sequence is also well-ordered with clear fallback logic. | 3 / 3 |
Progressive Disclosure | References to `references/cockroachdb-rules/` and `references/EXAMPLES.md` are clearly signaled and one level deep, which is good. However, no bundle files were provided to verify these exist, and the main skill inlines substantial content (like the full 'When to Use' section and response behavior details) that could be more concisely organized. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%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
- cockroachlabs/cockroachdb-skills
- Commit
84bc1e4
- 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.