vector-databases
Guides retrieval-store design, indexing, and query behavior for embedding-backed systems without confusing storage with application truth.
소스 정보
- 저장소
- agentic-in/elephant-agent
- 최근 소스 활동
- 2026년 5월 15일 07:09
- 감지된 SKILL.md 언어
- 영어
- 스타
- 584
- 포크
- 63
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- Vector Databases
- skill_id
- vector-databases
- description
- Guides retrieval-store design, indexing, and query behavior for embedding-backed systems without confusing storage with application truth.
- version
- 1.0.0
- source_kind
- elephant-builtin
- aliases
- ["vector db","vector database","embedding store"]
- trigger_phrases
- ["set up a vector database","design the retrieval store","index embeddings for search"]
- keywords
- ["vector database","retrieval","embeddings","index","chunking","filtering"]
- category
- mlops
# Vector Databases
Use this built-in skill when the user needs an embedding-backed retrieval store, semantic search index, or hybrid filtering design.
## Core rules
- Define the retrieval task before selecting an index or vendor.
- Make chunking, metadata, freshness, and filter behavior explicit.
- Keep canonical application truth outside the vector index unless the system is designed that way.
- Evaluate retrieval quality, not just index build success.
## Default workflow
1. Identify the query patterns, corpus shape, and update frequency.
2. Choose the embedding and indexing strategy that matches that workload.
3. Design metadata filters, ids, and refresh behavior intentionally.
4. Test retrieval quality with representative queries before scaling up.
## Guardrails
- Do not equate a working index build with a good retrieval system.
- Do not hide stale-data or reindex costs.
- Do not use the vector store as a vague substitute for product data modeling.
GitHub에서 보기