@keemakr/tools
v0.2.0
Published
Ready-made eve tools for keemakr marketplace agents — drop-in capabilities (Hunter find-email, …) that run on the @keemakr/agent-sdk floor, plus an `add` CLI that scaffolds editable tool templates.
Readme
@keemakr/tools
Ready-made eve tools for keemakr marketplace agents — drop-in capabilities that run on the @keemakr/agent-sdk floor. The tenant, the capability grant, and the connection credential are all handled for you: a tool here calls back into keemakr-core through the SDK, and the secret never reaches your agent.
Install
npm install @keemakr/tools @keemakr/agent-sdkPeer dependencies (match your eve agent): [email protected], zod@^4.4.3. Configure the SDK's environment (KEE_CORE_JWKS_URL, KEE_AGENT_AUDIENCE, KEE_CORE_URL) — see the @keemakr/agent-sdk README.
Use a tool
An eve agent discovers tools from agent/tools/**.ts, naming each by its file path. Re-export a ready tool in one line:
export { findEmail as default } from "@keemakr/tools/hunter";That's a working Hunter find-email tool — the agent can now find a person's work email, and the tenant's Hunter key stays in keemakr-core.
Configure with the factory
import { findEmailTool } from "@keemakr/tools/hunter";
export default findEmailTool({
minScore: 80, // only treat a hit with confidence >= 80 as "found"
});What's included
| Import | Tool | Requires (in entry.json) |
|---|---|---|
| @keemakr/tools/hunter → findEmail / findEmailTool | Find a work email at a domain by name (Hunter.io) | a connection dependency on hunter |
The tool calls useKee(ctx).connections.hunter.call("email-finder", …) under the hood — it never hand-rolls grant, tenant, or credential logic. That layering is the point: the plumbing lives once in @keemakr/agent-sdk; these tools just use it.
License
MIT
