CtrlK
BlogDocsLog inGet started
Tessl Logo

pinecone

Managed vector database for production AI applications. Fully managed, auto-scaling, with hybrid search (dense + sparse), metadata filtering, and namespaces. Low latency (<100ms p95). Use for production RAG, recommendation systems, or semantic search at scale. Best for serverless, managed infrastructure.

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with abundant executable code, but the body is verbose and duplicates content already in references/deployment.md, which itself is never linked. Destructive operations lack validation checkpoints.

Suggestions

Move deployment, hybrid-search, and namespace detail into references/deployment.md and replace the inline duplicates with a clearly signaled link (e.g., 'See [deployment.md](references/deployment.md)').

Reframe the 'Pricing (as of 2025)' section as deprecated/time-sensitive or move it to a reference file, since dated pricing penalizes conciseness.

Add a validation/confirmation step before destructive operations (delete index, delete_all, delete by filter) to lift workflow clarity above 2.

DimensionReasoningScore

Conciseness

The ~340-line body repeats content found in references/deployment.md (hybrid search, namespaces, metadata filtering) and carries a time-sensitive 'Pricing (as of 2025)' section outside any deprecated/old-patterns block, which the guidelines penalize.

2 / 3

Actionability

Provides fully executable, copy-paste-ready code for init, index creation, upsert, query, filtering, hybrid search, and integrations with concrete parameters.

3 / 3

Workflow Clarity

Quick start gives a rough sequence but lacks validation checkpoints, and destructive operations (delete index, delete by filter, delete_all) have no verification steps — capping this dimension at 2.

2 / 3

Progressive Disclosure

A references/deployment.md file exists but is never linked or signaled in the body, while its deployment/hybrid/namespace content is duplicated inline — references are present but not clearly signaled and content that should be separate is inline.

2 / 3

Total

9

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities and gives an explicit 'Use for...' trigger clause covering natural user terms. It clearly answers both what the skill does and when to apply it.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'hybrid search (dense + sparse), metadata filtering, and namespaces', 'auto-scaling', and 'Low latency (<100ms p95)' — rather than vague language, and uses third-person voice.

3 / 3

Completeness

Explicitly answers both what it is ('Managed vector database...hybrid search...metadata filtering...namespaces') and when to use it via the explicit 'Use for production RAG, recommendation systems, or semantic search at scale' trigger.

3 / 3

Trigger Term Quality

Includes natural terms a user would actually say — 'production RAG', 'recommendation systems', 'semantic search', 'vector database' — giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (managed Pinecone vector DB) with distinct triggers ('serverless, managed infrastructure', 'production RAG'), making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.