llm-integration

Integrate LLMs with a unified API client, streaming, and guardrails.

3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/bipinks/ghost-office --skill llm-integration-bipinks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-integration
Source: https://github.com/bipinks/ghost-office/tree/main/.claude/skills/llm-integration
Command: npx skills add https://github.com/bipinks/ghost-office --skill llm-integration-bipinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently integrating LLMs across production systems to provide reliable, scalable, and secure AI capabilities.

Core Features & Use Cases

  • Unified API client design for multiple providers
  • Streaming, function calling, and tool use patterns
  • Cost tracking, retry, fallback, rate limiting, and safety guardrails

Quick Start

Create a small service that wraps providers behind a single API and demonstrates streaming responses with token/cost accounting.

Frequently Asked Questions about llm-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate LLMs into a production application safely?

You can integrate LLMs into production using a unified API client design that wraps multiple providers. This approach ensures reliable deployments by incorporating safety guardrails, validation, error handling, and clear cost accounting.

What is the best way to manage LLM API costs and handle rate limiting?

Managing LLM API costs and rate limiting requires a client design with built-in cost tracking, retry logic, and fallback mechanisms. This provides clear token and cost accounting to maintain scalable AI capabilities across your production systems.

How do I implement streaming responses and function calling with LLMs?

Implementing streaming responses and function calling involves applying specific tool use patterns within your LLM API client. This architecture enables efficient data streaming and external tool execution while maintaining observability and safety checks.

Can I use a single API interface for multiple LLM providers?

Yes, a unified API client design allows interfacing with multiple LLM providers behind a single API. This requires a well-defined interface and model selection logic to ensure maintainable deployments while applying robust routing across different use cases.

When do I need safety guardrails and validation for LLM integrations?

Safety guardrails and validation are essential whenever deploying LLMs in production environments. They ensure safe, maintainable deployments by validating outputs and applying safety checks across use cases requiring RAG, embeddings, and robust tool use.