Agent skill · Databases

langchain4j-vector-stores-configuration

Provides configuration patterns for LangChain4J vector stores in RAG applications. Use when building semantic search, integrating vector databases (PostgreSQL/pgvector, Pinecone, MongoDB, Milvus, Neo4j), implementing embedding storage/retrieval, setting up hybrid search, or optimizing vector database performance for production AI applications.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill langchain4j-vector-stores-configuration-giuseppe-trisciuogli-dev-giuseppe-trisciuogli-developer-kit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 10 KB
Bundled scripts: none
Allowed tools: ReadWriteEditBashGlobGrep
Path: skills/ai-llm/langchain4j-vector-stores-configuration-giuseppe-trisciuogli-dev-giuseppe-trisciuogli-developer-kit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# LangChain4J Vector Stores Configuration Configure vector stores for Retrieval-Augmented Generation applications with LangChain4J. ## Overview LangChain4J provides a unified abstraction for vector stores (PostgreSQL/pgvector, Pinecone, MongoDB Atlas, Milvus, Neo4j) with builder-based configuration, metadata filtering, and hybrid search support. ## When to Use - Configuring vector stores for semantic search and RAG applications - Setting up embedding storage with metadata filtering and hybrid search - Optimizing vector database performance for production AI workloads ## Instructions ### Set Up Basic Vector Store Configure an embedding store for vector operations: ```java @Bean public EmbeddingStore<TextSegment> embeddingStore() { return PgVectorEmbeddingStore.builder() .host("localhost") .port(5432) .database("vectordb") .user("username") .password("password") .table("embeddings") .dimension(1536) // OpenAI embedding dimension .createTable(true) .useIndex(true) .build(); } ``` ### Validation Workflow Follow this workflow to ensure correct vector store setup: 1. **Configure**: Build the embedding store with required dimensions and connection parameters 2. **Test connection**: Verify

What's inside
Steps it walks through
  1. Overview
  2. When to Use
  3. Instructions
  4. Set Up Basic Vector Store
  5. Validation Workflow
  6. Configure Multiple Vector Stores
  7. Implement Document Ingestion
  8. Set Up Metadata Filtering
  9. Configure Production Settings
  10. Implement Health Checks
  11. Examples
  12. Basic RAG Application Setup
  13. Semantic Search Service
  14. Production Setup with Monitoring
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the langchain4j-vector-stores-configuration skill do?

Provides configuration patterns for LangChain4J vector stores in RAG applications. Use when building semantic search, integrating vector databases (PostgreSQL/pgvector, Pinecone, MongoDB, Milvus, Neo4j), implementing embedding storage/retrieval, setting up hybrid search, or optimizing vector database performance for production AI applications.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill langchain4j-vector-stores-configuration-giuseppe-trisciuogli-dev-giuseppe-trisciuogli-developer-kit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going