Name: couchbase
Rating: 58.4 (1 reviews)
Author: membranedev

couchbase

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/couchbase/SKILL.md

Quality

Content

68%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 highly actionable with real CLI commands and a sensible workflow, but loses points for explaining Couchbase basics Claude already knows and for lacking validation/verification checkpoints around destructive database operations.

Suggestions

Remove the introductory paragraph explaining what Couchbase is and who uses it; Claude already knows this and it adds padding.

Add a validation/verification step before destructive operations, e.g. 'Before DELETE/PUT via proxy or destructive actions, confirm the target with the user or run a read-only action first to verify scope.'

Fix the dangling 'Step 2' reference (the body says 'skip to Step 2' but no Step 2 header exists) by labeling the Searching/Running sections as explicit numbered steps.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Couchbase is and who uses it (concepts Claude already knows) and phrases like 'When to use which actions: Use action names and parameters as needed' are filler, but the bulk is efficient CLI commands, landing at 'mostly efficient with some unnecessary explanation'.	3 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a complete flags table, covering the common cases with real CLI invocations rather than pseudocode.	5 / 5
Workflow Clarity	A clear install→auth→connect→poll→search→run→proxy sequence exists with a polling feedback loop for connection state, but this is a database skill with destructive-capable operations (proxy DELETE/PUT, action runs) and no validation/verification steps before such operations, so workflow clarity is capped at 3 per the destructive/batch guideline.	3 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Working with Couchbase, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested or buried references and no bundle files present; good structure, though at ~140 lines some reference-worthy detail (proxy flags, state handling) is inlined rather than split out, keeping it just below the ideal split level.	4 / 5
	Total	15 / 20 Passed

Description

66%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 concise, third-person, and includes an explicit 'Use when...' trigger with both what and when answered. Its main weakness is generic action verbs and limited keyword synonyms, which keep specificity and trigger coverage at mid-range.

Suggestions

Replace generic verbs with concrete Couchbase actions, e.g. 'Query buckets with N1QL, manage documents and collections, automate workflows' to lift specificity.

Add natural synonyms users say — 'N1QL queries', 'buckets', 'collections', 'documents', 'NoSQL' — to broaden trigger coverage.

Make the 'when' clause more specific, e.g. 'Use when the user wants to query, read, or modify Couchbase buckets, documents, or N1QL data.'

Dimension	Reasoning	Score
Specificity	Names the domain ("Couchbase integration") and lists a few action areas ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete like 'extract text' or 'fill forms', so it sits at the 'names domain and 1-2 actions but not comprehensive' anchor rather than above.	3 / 5
Completeness	Answers both 'what' ("Manage data, records, and automate workflows") and 'when' ("Use when the user wants to interact with Couchbase data") with an explicit trigger clause, but the 'when' is somewhat generic and could be more specific, matching the 'both present, when could be more explicit' anchor rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Couchbase", "data", "records", "interact with Couchbase data") but misses common variations and synonyms a user might say (N1QL, buckets, documents, NoSQL, .json), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Names the specific product Couchbase, giving it a clear niche with distinct triggers and minimal conflict risk with other skills; the generic action verbs do not undermine the product-specific anchoring.	5 / 5
	Total	15 / 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/couchbase/SKILL.md
Commit: f484c82

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