- Home
- Skills
- Kriscard
- Kriscard Claude Plugins
- Ai Engineer
ai-engineer_skill
- Shell
1
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill kriscard/kriscard-claude-plugins --skill ai-engineer- SKILL.md5.0 KB
Overview
This skill helps engineers design and deploy production-grade LLM applications, retrieval-augmented generation (RAG) pipelines, and multi-agent orchestration. It focuses on practical choices: model selection, embedding strategies, vector stores, and operational trade-offs. Use it when you need repeatable patterns and hardened practices for LLM systems rather than general backend work.
How this skill works
The skill inspects architectural choices and prescribes concrete pipelines: document chunking, embedding selection, vector database layout, and retrieval strategies. It lays out agent orchestration patterns, memory handling, tool-use flows, and production hardening steps like logging, fallbacks, and monitoring. Outputs include recommended components, trade-offs, and step-by-step integration guidance.
When to use it
- Building RAG pipelines to answer questions from documents
- Choosing embeddings and vector stores for semantic search
- Integrating managed or local LLMs into applications
- Designing multi-agent systems and tool-use orchestration
- Optimizing retrieval, reranking, and generation for accuracy
Best practices
- Match embedding model and dimensionality to your retrieval needs and cost constraints
- Chunk documents using semantic or hierarchical strategies for complex sources
- Combine vector similarity with keyword filters (hybrid search) and reranking for precision
- Cache embeddings and monitor retrieval quality to reduce latency and cost
- Implement streaming responses, rate-limit handling, and graceful fallbacks in production
Example use cases
- Customer support knowledge base with semantic search and RAG answers
- Internal document assistant: chunk, embed, and query policy or legal corpora
- Agent system that chains tools, maintains memory, and falls back to safe defaults
- Local development with ChromaDB or pgvector before migrating to managed stores like Pinecone
- A/B testing prompt templates and retrieval parameters to optimize answer quality
FAQ
For quick local development use ChromaDB or pgvector; for scalable managed service choose Pinecone or Weaviate depending on hybrid search needs.
How do I choose an embedding model?
Match the embedding model to the domain and retrieval precision required; prefer smaller, cheaper models for high-volume approximate search and higher-quality models for precision-sensitive tasks.