Whichllm Wrap
Paste the following prompt into your AI chat to install this skill:
Please install @user_922b1001/whichllm-wrap according to https://skillhub.cn/install/skillhub.md.
About this skill
What It Addresses
Whichllm Wrap positions itself as a wrapper repository around Whichllm. If a project is already handling model selection, invocation parameters, or result propagation, directly depending on the external component can scatter entry points, configuration, and error handling across multiple places. A wrapper layer provides a maintainable boundary so upper-level code interacts with one integration point.
How It Works and Where It Fits
Based on the confirmed metadata, the skill is a wrapper repository for Whichllm, version 1.0.0. Its likely usage is integration-layer oriented:
- treat Whichllm as the wrapped dependency
- connect it from application code as needed
- isolate external component changes behind one entry point
It fits scenarios that need centralized dependencies, isolated external changes, or a unified integration path. It should not be assumed to provide authentication, retries, streaming, evaluation, or multi-model routing unless the repository implementation says otherwise. For quick validation of basic Whichllm behavior, review the repository examples and interface definitions before treating it as a production dependency.
Use Cases
- When evaluating a Whichllm integration, isolate the external dependency in a wrapper repository before writing minimal call code.
- When adding Whichllm to an existing agent repo, use a wrapper repository to manage where the dependency is introduced.
- When refactoring an old call chain, move Whichllm-related code into a wrapper repository to make later replacement easier.
- When introducing Whichllm for a team, start with a wrapper repository to create an independent layer and check the integration point.
Best For
- AI integration engineers who need to clarify the Whichllm repository dependency before wiring it into business logic.
- Backend maintainers of multi-component projects who want a wrapper repository to isolate Whichllm changes.
- Framework engineers organizing third-party AI dependencies and want Whichllm in a separate wrapper repository for later replacement.
- Architects evaluating integration boundaries and need to see how a wrapper repository wraps the Whichllm dependency.
Related Skills
Turn vague requests into structured prompts with role, task, context, and constraints, outputting only usable prompts without executing the task.
A skill for game NPC and enemy AI that separates decision, steering, and pathfinding, covering FSMs, behavior trees, A*, path caching, and pitfalls.
Provides multi-turn emotional companion chat through a third-party Agent API and supports continuing sessions via session_id.
An evaluation-driven workflow for diagnosing, optimizing, validating, and logging Agent Skills based on design patterns and anti-patterns.