pinecone

Managed vector DB for production RAG and search.

Quality

51%

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

57%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 a well-organized, largely executable reference for Pinecone operations with genuinely useful corrections (e.g., the explicit note that query() does not accept an alpha kwarg, with a working pre-scaling helper). Its main weaknesses are the orphaned deployment.md reference, inlined extended content, missing validation around destructive/batch operations, and time-sensitive pricing data in the main body.

Suggestions

Link the existing references/deployment.md from the body (e.g., 'For production deployment patterns, see [deployment.md](references/deployment.md)') and move extended content — LangChain/LlamaIndex integrations, index management, and delete operations — out of SKILL.md to slim the main body.

Add validation checkpoints around destructive and batch operations, e.g. verify describe_index_stats() after batch upserts and confirm the index name via pc.list_indexes() before pc.delete_index().

Move the 'Pricing (as of 2025)' section and the performance table into a clearly dated reference file (or remove them) so time-sensitive figures don't stale in the always-loaded body.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, executable code with little explanatory padding, but it includes removable elements: a redundant tagline ('The vector database for production AI applications.'), a Metrics section repeating the p95 latency claim, and time-sensitive data ('Pricing (as of 2025)' with specific dollar figures and a free-tier breakdown) placed in the main body rather than a dated/deprecated section, which the guidelines say should penalize conciseness. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than level 4.	3 / 5
Actionability	Concrete, near-executable code throughout: full create_index/upsert/query examples, a complete executable hybrid_score_norm helper with an alpha validation check, and an install command with a deprecated-package note. Minor gaps keep it below 5 — elided vectors ([0.1, 0.2, ...]) and a batch-upsert example referencing undefined 'embeddings'/'metadatas' variables — matching 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The overall sequence is present (install → create index → upsert → query → manage → delete), but batch upserts and destructive operations (pc.delete_index, index.delete(delete_all=True)) have no validation or verification steps such as checking describe_index_stats after upsert or confirming the target index before deletion. Per the guidelines, destructive/batch workflows without validation cap workflow clarity at 3.	3 / 5
Progressive Disclosure	Section structure and headers are good, but the skill ships references/deployment.md that the body never links to (an orphaned reference), while extended content that belongs in reference files — full LangChain/LlamaIndex integrations, index management, delete operations, and pricing — is inlined in SKILL.md. This matches 'references present but not clearly signaled; content that should be separate is inline' rather than level 2, since the body itself is well organized with clear sections.	3 / 5
	Total	13 / 20 Passed

Description

45%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 and names a clear domain, but it is domain-only: no concrete actions, no trigger guidance, and no distinguishing capability or product name. It would benefit most from an explicit 'Use when...' clause and a short list of concrete operations.

Suggestions

Add a 'Use when...' trigger clause, e.g. 'Use when working with Pinecone, vector databases, embedding storage, or similarity/semantic search in production RAG pipelines.'

List concrete actions to raise specificity, e.g. 'Upsert and query vector embeddings, filter by metadata, run hybrid dense+sparse search, and manage namespaced indexes.'

Include natural synonyms users would say — 'vector database' spelled out, 'embeddings', 'similarity search', 'semantic search', and the product name 'Pinecone' — to improve trigger coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Managed vector DB for production RAG and search') but lists no concrete actions such as upserting/querying vectors, metadata filtering, or hybrid search. It matches the anchor 'Names the domain but actions are minimal or generic' rather than level 3, which requires 1-2 explicit actions.	2 / 5
Completeness	There is a clear 'what' (a managed vector database for production RAG and search) but no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'RAG', 'search', and 'vector DB' are natural trigger terms, but common user phrasings are missing: 'vector database' spelled out, 'embeddings', 'similarity search', 'semantic search', and the product name 'Pinecone' itself. This matches 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Managed vector DB' identifies a specific niche, but without naming Pinecone or a distinguishing capability it could overlap with sibling vector-database skills (Weaviate, Qdrant, Chroma). This matches 'Somewhat specific but could still overlap with similar skills'.	3 / 5
	Total	11 / 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: 68fa7e9

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