cli-anything-chromadb

Command-line interface for ChromaDB - A stateless CLI for managing vector database collections, documents, and semantic search. Designed for AI agents and automation via the ChromaDB HTTP API v2.

Quality

73%

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 ./chromadb/agent-harness/cli_anything/chromadb/skills/SKILL.md

Quality

Content

87%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 content is lean, well-organized, and highly actionable with concrete executable CLI examples, but destructive/batch operations lack validation checkpoints, capping workflow clarity.

Suggestions

Add a brief validation/verification step for destructive commands (e.g. confirm collection exists before 'collection delete', verify document count after 'document delete') to lift workflow clarity above 3.

Clarify return-code/error-handling expectations inline with the delete commands rather than only in the general 'For AI Agents' section.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — installation, prerequisites, commands, and output modes are presented without explaining concepts Claude already knows — so every token earns its place, matching the 'lean and efficient' anchor.	5 / 5
Actionability	It provides copy-paste-ready executable commands covering common cases (--help, heartbeat, list, search) and concrete flag usage, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	Commands are clearly listed, but destructive and batch operations ('collection delete', 'document delete') have no validation or verification checkpoints, and the guideline caps workflow clarity at 3 for such skills; it does not reach the explicit-checkpoint anchors.	3 / 5
Progressive Disclosure	The skill is under 50 lines, has no external bundle files, and is organized into clear sections (Installation, Usage, Command Groups, Output Formats, For AI Agents), so the simple-skill exception applies and progressive disclosure scores 5.	5 / 5
	Total	18 / 20 Passed

Description

58%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 clearly states what the skill does and names a specific niche, but it omits any explicit 'when to use' trigger guidance and lacks natural user phrasings and synonyms, which limits its completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when managing ChromaDB collections, adding or querying documents, or running semantic search from the command line.'

Include common synonyms and concrete artifacts a user might mention (e.g. 'vector store', 'embeddings', 'ChromaDB server', '.json output') to improve trigger term quality.

Tighten specificity toward a comprehensive action list (create/list/delete collections, add/get/delete/count documents, semantic search) to approach the top anchor.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'managing vector database collections, documents, and semantic search' — covering multiple capabilities with only minor gaps, matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.	4 / 5
Completeness	Provides a clear 'what' (CLI for managing ChromaDB collections/documents/search) but has no 'Use when...' clause or explicit trigger guidance, which per guidelines caps completeness at 3; it does not reach the both-what-and-when anchors at 4-5.	3 / 5
Trigger Term Quality	Contains relevant keywords like 'vector database collections', 'documents', 'semantic search' but lacks synonyms, file extensions, or natural trigger phrases a user would say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct — 'ChromaDB', 'HTTP API v2', 'stateless CLI' — with only minor overlap risk against generic database CLIs, matching 'mostly distinct; minor overlap risk' rather than the fully-distinct 5.	4 / 5
	Total	14 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HKUDS/CLI-Anything
Path: chromadb/agent-harness/cli_anything/chromadb/skills/SKILL.md
Commit: 34f5195

Reviewed: 1 day 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.