pinecone

Managed vector DB for production RAG and search.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/mlops/pinecone/SKILL.md

Quality

Content

65%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 highly actionable with comprehensive executable examples, but it is padded with time-sensitive pricing/performance sections, lacks validation checkpoints around destructive and batch operations, and fails to wire its existing deployment.md reference into the body.

Suggestions

Add verification steps before destructive calls (e.g. confirm index name, dry-run describe_index_stats, print affected vector counts) and gate delete/delete_all behind an explicit confirmation.

Link references/deployment.md from the body and move duplicated deployment, hybrid, and namespace detail there to avoid inlining content that already lives in the bundle.

Move pricing, version numbers, and the performance table into a clearly marked, easily-updatable section or the deployment reference so time-sensitive data does not bloat the skill body.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, executable code, but it carries time-sensitive material ("Pricing (as of 2025)", "current 9.x", a performance table) outside any deprecated/old-patterns section, plus a padded 10-item best-practices list. It is not a 4 because the pricing/performance/marketing-style sections are clearly trimmable padding.	3 / 5
Actionability	It provides copy-paste-ready, executable examples for the common cases (init, create index, upsert, query, metadata filters, namespaces, delete) and even a real hybrid_score_norm helper with a corrective note about the alpha kwarg. It is not a 4 because coverage of common cases is comprehensive rather than having minor gaps.	5 / 5
Workflow Clarity	Operations are organized into clear sections, but destructive and batch operations (delete index, delete_all, delete-by-filter, batch upsert) have no validation or verification checkpoints, so per the rubric cap workflow clarity cannot exceed 3. It is not a 2 because the sections do give a coherent sequence rather than rough gaps.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but the bundled references/deployment.md is never linked or signaled from the body, and deployment/hybrid/namespace content is duplicated between the two files rather than split. It is not a 4 because a provided reference file is completely unlinked and content that belongs in it is inlined.	3 / 5
	Total	14 / 20 Passed

Description

48%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 a concise noun phrase that clearly identifies the domain but omits concrete actions and any "Use when" trigger guidance. It is distinctive within the vector-DB/RAG niche yet under-specified on when Claude should reach for it.

Suggestions

Add concrete action verbs, e.g. "Store, query, and filter vectors for production RAG and similarity search."

Append an explicit trigger clause such as "Use when building RAG pipelines, semantic search, or vector similarity workloads."

Include common synonyms users say (embeddings, semantic search, similarity search) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Managed vector DB for production RAG and search" names the domain and a use case but contains no concrete action verbs (e.g. store, query, upsert), matching the anchor that names the domain with minimal/generic actions. It is not a 3 because no specific concrete actions are listed at all.	2 / 5
Completeness	The description gives a clear "what" (managed vector DB) but no "Use when..." or equivalent trigger guidance, so per the rubric completeness is capped at 3. It is not a 2 because the "what" is clear rather than vague, and not a 4 because "when" is entirely absent rather than merely weak.	3 / 5
Trigger Term Quality	It surfaces "vector DB", "RAG", and "search", which are relevant natural terms, but misses common variations users say such as "embeddings", "similarity search", or "semantic search". It is not a 4 because keyword coverage is thin rather than merely missing a few terms.	3 / 5
Distinctiveness Conflict Risk	The managed-vector-DB-for-RAG framing carves a fairly distinct niche with only minor overlap risk against other vector-database skills. It is not a 5 because it does not name Pinecone or concrete trigger phrases that would minimize conflict, and not a 3 because it is more specific than a generic "works with documents"-level overlap.	4 / 5
	Total	12 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/mlops/pinecone/SKILL.md
Commit: 6680afb

Reviewed: about 3 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.