When you want to bring an existing service (a third-party API, a library, an in-house microservice) into an iii system without rewriting it, wrap it in a thin worker that exposes the service's capabilities as iii functions. The worker translates between the existing service's interface and the iii function-call shape.
Installs into .claude/skills of the current project.
Are you the author of Patterns?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/iii-hq-patterns)
<!-- generated by iii-skill-render. DO NOT EDIT (changes here are overwritten on the next render). Edit docs/0-12-0/patterns/adapter-pattern.mdx. -->
# Adapter Pattern
When you want to bring an existing service (a third-party API, a library, an in-house microservice)
into an iii system without rewriting it, wrap it in a thin worker that exposes the service's
capabilities as iii functions. The worker translates between the existing service's interface and
the iii function-call shape.
## When to use this pattern
When you have an existing service you want to use from iii without rewriting it, and you want
callers to address it the way they address every other worker (by function ID, not by HTTP or
library-specific call shapes).
## Structure
A thin iii worker that:
1. Connects to the engine.
2. Registers one function per operation you want to expose.
3. Inside each handler, calls the existing service and returns the result as the function's
response.
{/* TODO: full worked example wrapping a real third-party API (e.g. Stripe, OpenAI, internal REST service) as an iii worker. Include the function ID conventions, error mapping from the wrapped service to iii function errors, and how to handle authentication / secrets. */}
