Agent skill

Kitaru Adapter Development

by zenml-io in zenml-io/kitaru

Add or change a Kitaru framework adapter that records native agent runs or supports bounded replay.

Apache-2.0Auto-check passedDevOps & Cloud

Install Kitaru Adapter Development

skills CLI
$ npx skills add zenml-io/kitaru --skill kitaru-adapter-development -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zenml-io/kitaru kitaru-adapter-development --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zenml-io/kitaru.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/kitaru-adapter-development .claude/skills/kitaru-adapter-development && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
kitaru-adapter-development
GitHub stars
302
Token cost
~1.7k tokens
SKILL.md length
848 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Add or change a Kitaru framework adapter that records native agent runs or supports bounded replay.

  • Python adapter distributions under plugins/packages
  • SKILL.md covers Choose the extension point, Package and documentation work, Core boundary and Validation
  • Calls pnpm and just
  • TypeScript adapter packages under packages

What it does

Kitaru Adapter Development is an agent skill from zenml-io/kitaru. Add or change a Kitaru framework adapter that records native agent runs or supports bounded replay. Use for Python adapter distributions under plugins/packages or TypeScript adapter packages under packages, not trace importers or core API work.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. It works with Python and TypeScript. The repository describes itself as: Agent traces you can run, not just read. The licence is Apache-2.0.

When your agent uses it

  • Python adapter distributions under plugins/packages
  • TypeScript adapter packages under packages
  • Not trace importers

Example prompts

  • “/kitaru-adapter-development”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit e7e55f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • just

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Kitaru Adapter Development loads about 1.7k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 848 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from zenml-io/kitaru at commit e7e55f7, republished under its Apache-2.0 licence (© zenml-io). 848 words, ~1,746 tokens.

Download SKILL.mdSave it as .claude/skills/kitaru-adapter-development/SKILL.md (or your agent's skills folder).
name
kitaru-adapter-development
description
Add or change a Kitaru framework adapter that records native agent runs or supports bounded replay. Use for Python adapter distributions under plugins/packages or TypeScript adapter packages under packages, not trace importers or core API work.

Kitaru Adapter Development

Read AGENTS.md. For Python adapters, also read plugins/AGENTS.md and plugins/DEVELOPMENT.md. For TypeScript adapters, read release/typescript.md before changing package or release metadata. Load the same-name kitaru-dev repo skill for the current host for the general command and PR workflow.

Start from the closest current adapter and the target framework's public API. Do not port a historical adapter wholesale.

Choose the extension point

Recording adapters are independent Python distributions under plugins/packages/<slug>/, with focused tests under plugins/tests/adapters/<slug>/. Importer-backed adapters are different: they live inside the provider's importer package as an ImporterBackedAdapter subclass, never intercept model or tool calls, and follow the kitaru-importer-development skill instead of this section's package rules. Agent versions running them declare runtime_capabilities with overrides: false and tool_policies: false on the run spec. TypeScript framework adapters are packages such as packages/mastra/ and packages/vercel-ai/; shared adapter primitives live under packages/core/src/adapter/.

Before editing, state:

  • which public framework call, hook, callback, or wrapper is intercepted
  • which model, tool, handoff, child-agent, and failure events are observable there
  • when sessions and nodes are written, including what the caller observes if recording fails
  • which replay overrides can be applied at a real framework boundary
  • which streaming, tool, approval, resume, stateful, or dynamic cases remain unsupported

Preserve the framework's ordinary behavior, configured hooks and state, public entrypoint, and native result type. Reject unsupported replay configurations before model or tool execution. Treat passthrough tools as real side effects, not as a reversible transaction. If the framework has no public per-run model replacement point, do not emulate one by mutating shared agent state or reading private fields; stop and report that replay boundary.

Package and documentation work

Python feature PRs follow the version and dependency ownership rules in plugins/AGENTS.md. Leave existing package versions unchanged. Use the exact development dependency from plugins/DEVELOPMENT.md only when the adapter needs unreleased core; release prep selects the published compatibility floor.

For a new Python adapter, complete the new-distribution integration review in the kitaru-dev skill before the PR; it covers worker installation and release wiring beyond the adapter package itself. Inspect the current package inventory and update only the required integration points:

  • plugins/packages/<slug>/pyproject.toml, README, changelog, source package, public exports, and focused tests
  • tool.kitaru.artifact.import-module for standalone artifact-smoke coverage
  • plugins/pyproject.toml only when the adapter must be a workspace development dependency or source
  • release/release-units.toml for an independently released distribution

Python adapters are installed directly by agent projects. Keep default-catalog = false in release/release-units.toml and do not add them to DEFAULT_PLUGIN_DEFINITIONS.

For a new TypeScript adapter, add a separate package instead of framework-specific code in packages/core/. Inspect the root workspace scripts, lockstep version rules, packaging smoke, and .github/workflows/release-typescript.yml; do not assume a newly added package is automatically built or published.

Document shipped adapters under docs/book/adapters/, update docs/book/adapters/README.md and docs/book/toc.md, and add a runnable example only when it exercises a supported path.

Show full SKILL.md (385 more words)Show less

Core boundary

An adapter request does not authorize a new core abstraction, server resource, or replay protocol. Stop and surface the missing extension point before changing any of these areas merely to finish the adapter:

  • openapi/
  • src/kitaru/api_models/
  • src/kitaru/client/
  • src/kitaru/server/
  • src/kitaru/worker/
  • CLI or MCP code
  • packages/core/src/adapter/ when the proposed primitive is useful only to one framework package

Explain what the adapter cannot observe or override, why the current public boundary is insufficient, and the smallest separate core decision that would unblock it. Continue only after a maintainer approves that bounded core change; a request to change core "if needed" is not approval to broaden the adapter patch opportunistically.

Validation

Test the public wrapper, captured node semantics, native result preservation, supported replay, unsupported replay preflight, concurrency, and recording-finalization failures as applicable.

For Python adapters, run the focused adapter tests, then the plugin workspace format, lint, typecheck, and test commands from plugins/AGENTS.md. Run just plugin-artifact-smoke after package metadata or artifact-loading changes.

For TypeScript adapters, run the affected package's test, typecheck, lint, and build scripts. Run the root pnpm test, pnpm typecheck, pnpm lint, and pnpm pack:check when shared primitives, workspace metadata, or packaging changes.

The Mastra adapter is tested against every Mastra release set the memory replay factory accepts. MEMORY_REPLAY_TESTED_VERSIONS in packages/mastra/src/memory-replay-versions.ts lists those sets (@mastra/core, the @mastra/memory release built against it, and the @mastra/pg release the PostgreSQL tests use), and assertMemoryReplayVersions accepts exactly its core and memory pairs. packages/mastra/ installs the oldest set. Each private packages/mastra-compat/<major.minor>/ package installs one other set and runs every packages/mastra test against it through packages/mastra-compat/shared/; the 1.71 package also holds the Mastra compatibility suite. To add a Mastra release, check which memory and pg releases were built against it (their published devDependencies), copy a compat package with those pins, run its suite including PostgreSQL, then add the table row and the adapter's @mastra/memory peer version. packages/mastra/test/tested-versions.test.ts fails when the table, the test packages, the installed versions and the peer range disagree, and the packed-tarball smoke reads the table from the built adapter. Dependabot ignores these pins; see .github/dependabot.yml. When you raise the supported @mastra/core ceiling for the rest of the adapter, move the compatibility suite to the newest compat package in the same change.

Use live provider or framework tests only when their credentials and external side effects are explicitly in scope.

© zenml-io, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/kitaru-adapter-development of zenml-io/kitaru.

Open the folder on GitHubat commit e7e55f7

Compare with similar skills

Kitaru Adapter Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Kitaru Adapter Development compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kitaru Adapter Development this skillzenml-io/kitaru302—~1.7kAutomated safety check: PassApache-2.0
AWS Cdk Developmentsickn33/agentic-awesome-skills47k1 repos~2.5kAutomated safety check: PassMIT
AWS Cdk Developmentzxkane/aws-skills3672 repos~2.5kAutomated safety check: PassMIT
Liveblog Devliveblog/liveblog119—~1.9kAutomated safety check: PassAGPL-3.0
Logfire Instrumentationbasicmachines-co/basic-memory4.1k—~2.3kAutomated safety check: PassAGPL-3.0
Zizkadb ReleaseZIZKA-AI-SL/ZizkaDB125—~399Automated safety check: PassCustom licence

Similar skills

  • AWS Cdk Development

    sickn33/agentic-awesome-skills

    AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    DevOps & CloudAuto-check passed
  • AWS Cdk Development

    zxkane/aws-skills

    AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.

    367 GitHub starsUsed in 2 repos~2.5k tokens
    DevOps & CloudAuto-check passed
  • Liveblog Dev

    liveblog/liveblog

    Run a local Liveblog development environment. An agent skill from liveblog/liveblog.

    119 GitHub stars~1.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Logfire Instrumentation

    basicmachines-co/basic-memory

    Adds Pydantic Logfire tracing, logging and metrics to Python, JavaScript or TypeScript and Rust projects, with the correct setup order and library extras.

    4.1k GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Zizkadb Release

    ZIZKA-AI-SL/ZizkaDB

    Bumps versions, runs pre-push verification, and publishes ZizkaDB SDK and MCP packages.

    125 GitHub stars~399 tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Project Maturity

    KonghaYao/peri

    对任意项目进行全面的成熟度评估扫描。当用户说"检查项目成熟度"、"项目评估"、 "maturity assessment"、"代码质量扫描"、"项目健康度"、"项目体检"、 "scan project maturity"、"项目有多成熟"时触发。适用场景:接手新项目前的摸底、 发布前的质量审查、技术尽调、团队内部代码健康度盘点。

    224 GitHub stars~1.8k tokensUpdated today
    DevOps & CloudAuto-check: notes

More from zenml-io/kitaru

  • Kitaru Docs

    zenml-io/kitaru

    Kitaru documentation surfaces, link rules, and accuracy rules.

    302 GitHub stars~936 tokensUpdated today
    Auto-check passed
  • Kitaru Release

    zenml-io/kitaru

    Discover dependencies and prepare or execute Kitaru core and plugin releases, including version proposals, Kitaru UI selection, release PRs, ordered tag commands, artifact verification, and recovery.

    302 GitHub stars~7k tokensUpdated today
    Auto-check passed
  • Add, reuse, or change a frontend-specific Kitaru REST response under /api/v1/ui and its OpenAPI contract in zenml-frontend-monorepo.

    302 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Kitaru Dev

    zenml-io/kitaru

    Kitaru just recipes, CLI structure and structured-output contract, analytics events, and PR-description conventions.

    302 GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Add or change a separately packaged Kitaru trace importer that normalizes provider exports into imported sessions.

    302 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Kitaru Tests Release

    zenml-io/kitaru

    Kitaru test layout, CI workflows, and release-workflow behavior.

    302 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Questions about Kitaru Adapter Development

What does Kitaru Adapter Development do?

Add or change a Kitaru framework adapter that records native agent runs or supports bounded replay. Kitaru Adapter Development is an agent skill from zenml-io/kitaru. Add or change a Kitaru framework adapter that records native agent runs or supports bounded replay.

When should I use Kitaru Adapter Development?

Kitaru Adapter Development fits situations like: Python adapter distributions under plugins/packages; typeScript adapter packages under packages; not trace importers.

How do I install Kitaru Adapter Development in Claude Code?

Run `npx skills add zenml-io/kitaru --skill kitaru-adapter-development -a claude-code`. Or copy the skill folder (.agents/skills/kitaru-adapter-development in zenml-io/kitaru) into .claude/skills/kitaru-adapter-development in your project. Claude Code loads it when a task matches its description.

How do I install Kitaru Adapter Development in Codex?

Run `npx skills add zenml-io/kitaru --skill kitaru-adapter-development -a codex`. Or copy the skill folder (.agents/skills/kitaru-adapter-development in zenml-io/kitaru) into .agents/skills/kitaru-adapter-development in your project. Codex loads it when a task matches its description.

Can I use Kitaru Adapter Development in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zenml-io/kitaru --skill kitaru-adapter-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kitaru-adapter-development, .gemini/skills/kitaru-adapter-development, .github/skills/kitaru-adapter-development and .opencode/skills/kitaru-adapter-development in your project.

What does Kitaru Adapter Development need to run?

Going by SKILL.md and its folder, Kitaru Adapter Development needs the command-line tools its instructions call (pnpm and just). Our summary lists: Python 3.

Does Kitaru Adapter Development access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Kitaru Adapter Development safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Kitaru Adapter Development use?

Kitaru Adapter Development is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Kitaru Adapter Development use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Kitaru Adapter Development?

Skills that share tags, products or a category with Kitaru Adapter Development: AWS Cdk Development (sickn33/agentic-awesome-skills, 47k stars), AWS Cdk Development (zxkane/aws-skills, 367 stars), Liveblog Dev (liveblog/liveblog, 119 stars) and Logfire Instrumentation (basicmachines-co/basic-memory, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kitaru Adapter Development?

zenml-io (a GitHub organization) maintains it in zenml-io/kitaru, which has 302 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.

Source: zenml-io/kitaru on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.