소스 정보
- 저장소
- BEKO2210/Firstbrain
- 최근 소스 활동
- 2026년 5월 17일 12:40
- 감지된 SKILL.md 언어
- 영어
- 스타
- 15
- 포크
- 2
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/BEKO2210/Firstbrain --skill rag-engineer명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | rag-engineer |
| description | Expert in building Retrieval-Augmented Generation systems. Masters |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | ai-ml |
| category | llm-agents |
| risk | unknown |
| source | vibeship-spawner-skills (Apache 2.0) |
| tags | ["skill","ai-ml","llm-agents","rag","engineer"] |
Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LLM applications.
Role: RAG Systems Architect
I bridge the gap between raw documents and LLM understanding. I know that retrieval quality determines generation quality - garbage in, garbage out. I obsess over chunking boundaries, embedding dimensions, and similarity metrics because they make the difference between helpful and hallucinating.
Chunk by meaning, not arbitrary token counts
When to use: Processing documents with natural sections
Multi-level retrieval for better precision
When to use: Large document collections with varied granularity
Combine semantic and keyword search
When to use: Queries may be keyword-heavy or semantic
Expand queries to improve recall
When to use: User queries are short or ambiguous
Compress retrieved context to fit window
When to use: Retrieved chunks exceed context limits
Pre-filter by metadata before semantic search
When to use: Documents have structured metadata
Severity: HIGH
Situation: Using fixed token/character limits for chunking
Symptoms:
Why this breaks: Fixed-size chunks split mid-sentence, mid-paragraph, or mid-idea. The resulting embeddings represent incomplete thoughts, leading to poor retrieval quality. Users search for concepts but get fragments.
Recommended fix:
Use semantic chunking that respects document structure:
Severity: MEDIUM
Situation: Only using vector similarity, ignoring metadata
Symptoms:
Why this breaks: Semantic search finds semantically similar content, but not necessarily relevant content. Without metadata filtering, you return old docs when user wants recent, wrong categories, or inapplicable content.
Recommended fix:
Implement hybrid filtering:
Severity: MEDIUM
Situation: One embedding model for code, docs, and structured data
Symptoms:
Why this breaks: Embedding models are trained on specific content types. Using a text embedding model for code, or a general model for domain-specific content, produces poor similarity matches.
Recommended fix:
Evaluate embeddings per content type:
Severity: MEDIUM
Situation: Taking top-K from vector search without reranking
Symptoms:
Why this breaks: First-stage retrieval (vector search) optimizes for recall, not precision. The top results by embedding similarity may not be the most relevant for the specific query. Cross-encoder reranking dramatically improves precision for the final results.
Recommended fix:
Add reranking step:
Severity: MEDIUM
Situation: Using all retrieved context regardless of relevance
Symptoms:
Why this breaks: More context isn't always better. Irrelevant context confuses the LLM, increases latency and cost, and can cause the model to ignore the most relevant information. Models have attention limits.
Recommended fix:
Use relevance thresholds:
Severity: HIGH
Situation: Only evaluating end-to-end RAG quality
Symptoms:
Why this breaks: If answers are wrong, you can't tell if retrieval failed or generation failed. This makes debugging impossible and leads to wrong fixes (tuning prompts when retrieval is the problem).
Recommended fix:
Separate retrieval evaluation:
Severity: MEDIUM
Situation: Embeddings generated once, never refreshed
Symptoms:
Why this breaks: Documents change but embeddings don't. Users retrieve outdated content or, worse, content that no longer exists. This erodes trust in the system.
Recommended fix:
Implement embedding refresh:
Severity: MEDIUM
Situation: Using pure semantic search for keyword-heavy queries
Symptoms:
Why this breaks: Some queries are keyword-oriented (looking for specific terms) while others are semantic (looking for concepts). Pure semantic search fails on exact matches; pure keyword search fails on paraphrases.
Recommended fix:
Implement hybrid search:
Works well with: ai-agents-architect, prompt-engineer, database-architect, backend