AWS Cdk Development
sickn33/agentic-awesome-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Add or change a Kitaru framework adapter that records native agent runs or supports bounded replay.
$ npx skills add zenml-io/kitaru --skill kitaru-adapter-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zenml-io/kitaru kitaru-adapter-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "kitaru-adapter-development" agent skill from https://github.com/zenml-io/kitaru/tree/develop/.agents/skills/kitaru-adapter-development into .claude/skills/kitaru-adapter-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kitaru-adapter-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zenml-io/kitaru/tree/develop/.agents/skills/kitaru-adapter-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zenml-io/kitaru --skill kitaru-adapter-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zenml-io/kitaru kitaru-adapter-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zenml-io/kitaru.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/kitaru-adapter-development .agents/skills/kitaru-adapter-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "kitaru-adapter-development" agent skill from https://github.com/zenml-io/kitaru/tree/develop/.agents/skills/kitaru-adapter-development into .agents/skills/kitaru-adapter-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kitaru-adapter-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zenml-io/kitaru --skill kitaru-adapter-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zenml-io/kitaru kitaru-adapter-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zenml-io/kitaru.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/kitaru-adapter-development .cursor/skills/kitaru-adapter-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "kitaru-adapter-development" agent skill from https://github.com/zenml-io/kitaru/tree/develop/.agents/skills/kitaru-adapter-development into .cursor/skills/kitaru-adapter-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kitaru-adapter-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zenml-io/kitaru.git --path .agents/skills/kitaru-adapter-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zenml-io/kitaru --skill kitaru-adapter-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zenml-io/kitaru kitaru-adapter-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zenml-io/kitaru.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/kitaru-adapter-development .gemini/skills/kitaru-adapter-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "kitaru-adapter-development" agent skill from https://github.com/zenml-io/kitaru/tree/develop/.agents/skills/kitaru-adapter-development into .gemini/skills/kitaru-adapter-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kitaru-adapter-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zenml-io/kitaru kitaru-adapter-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zenml-io/kitaru --skill kitaru-adapter-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zenml-io/kitaru.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/kitaru-adapter-development .github/skills/kitaru-adapter-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "kitaru-adapter-development" agent skill from https://github.com/zenml-io/kitaru/tree/develop/.agents/skills/kitaru-adapter-development into .github/skills/kitaru-adapter-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kitaru-adapter-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zenml-io/kitaru --skill kitaru-adapter-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zenml-io/kitaru kitaru-adapter-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zenml-io/kitaru.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/kitaru-adapter-development .opencode/skills/kitaru-adapter-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "kitaru-adapter-development" agent skill from https://github.com/zenml-io/kitaru/tree/develop/.agents/skills/kitaru-adapter-development into .opencode/skills/kitaru-adapter-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kitaru-adapter-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
kitaru-adapter-developmentAdd 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. 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.
Read from SKILL.md and the folder at commit e7e55f7. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
pnpmjustFrom the folder's file list and the shell code blocks in SKILL.md.
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.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from zenml-io/kitaru at commit e7e55f7, republished under its Apache-2.0 licence (© zenml-io). 848 words, ~1,746 tokens.
.claude/skills/kitaru-adapter-development/SKILL.md (or your agent's skills folder).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.
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:
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.
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 teststool.kitaru.artifact.import-module for standalone artifact-smoke coverageplugins/pyproject.toml only when the adapter must be a workspace development dependency or sourcerelease/release-units.toml for an independently released distributionPython 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.
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/packages/core/src/adapter/ when the proposed primitive is useful only to one framework packageExplain 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.
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
Just SKILL.md in .agents/skills/kitaru-adapter-development of zenml-io/kitaru.
Open the folder on GitHubat commit e7e55f7
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Kitaru Adapter Development this skillzenml-io/kitaru | 302 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| AWS Cdk Developmentsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Liveblog Devliveblog/liveblog | 119 | — | ~1.9k | Automated safety check: Pass | AGPL-3.0 | |
| Logfire Instrumentationbasicmachines-co/basic-memory | 4.1k | — | ~2.3k | Automated safety check: Pass | AGPL-3.0 | |
| Zizkadb ReleaseZIZKA-AI-SL/ZizkaDB | 125 | — | ~399 | Automated safety check: Pass | Custom licence |
sickn33/agentic-awesome-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
liveblog/liveblog
Run a local Liveblog development environment. An agent skill from liveblog/liveblog.
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.
ZIZKA-AI-SL/ZizkaDB
Bumps versions, runs pre-push verification, and publishes ZizkaDB SDK and MCP packages.
KonghaYao/peri
对任意项目进行全面的成熟度评估扫描。当用户说"检查项目成熟度"、"项目评估"、 "maturity assessment"、"代码质量扫描"、"项目健康度"、"项目体检"、 "scan project maturity"、"项目有多成熟"时触发。适用场景:接手新项目前的摸底、 发布前的质量审查、技术尽调、团队内部代码健康度盘点。
zenml-io/kitaru
Kitaru documentation surfaces, link rules, and accuracy rules.
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.
zenml-io/kitaru
Add, reuse, or change a frontend-specific Kitaru REST response under /api/v1/ui and its OpenAPI contract in zenml-frontend-monorepo.
zenml-io/kitaru
Kitaru just recipes, CLI structure and structured-output contract, analytics events, and PR-description conventions.
zenml-io/kitaru
Add or change a separately packaged Kitaru trace importer that normalizes provider exports into imported sessions.
zenml-io/kitaru
Kitaru test layout, CI workflows, and release-workflow behavior.
Works with
Categories
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.
Kitaru Adapter Development fits situations like: Python adapter distributions under plugins/packages; typeScript adapter packages under packages; not trace importers.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.