Menü
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
npx skills add https://github.com/zenml-io/kitaru --skill kitaru-docsDer Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.
Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.
SKILL.md wird angezeigt
Full reference for Kitaru v2 development commands, tests, docs generation, packaging, Docker builds, and CI workflows. Use when a task needs commands beyond just check, just fix, or just test.
Prepare or execute Kitaru core and plugin releases, including Kitaru UI publication in the frontend monorepo, version and changelog updates, frontend declarations, default plugin pins, validation, release tags, artifact verification, and recovery. Use when a user asks to prepare, cut, publish, verify, or recover a Kitaru, Kitaru UI, or Kitaru plugin release.
Use for Kitaru tests, CI, releases.
Basierend auf der SOC-Berufsklassifikation
| name | kitaru-docs |
| description | Use for Kitaru docs. |
Use this when editing or reviewing Kitaru documentation, examples, generated reference docs, docs redirects, or docs CI behavior.
Kitaru docs live on three surfaces:
docs/book/, published to docs.zenml.io/kitaru through GitBook Git Sync. Navigation is docs/book/toc.md, configuration is docs/book/.gitbook.yaml, and authoring conventions live in docs/book/AGENTS.md.docs/, with output under docs/content/docs/reference/python/ served from sdkdocs.kitaru.ai. The v2 Python generator is currently absent, so reference generation and deployment are blocked. CLI reference publishing is deferred.kitaru.ai/docs/* redirects are handled by docs/worker/redirect.mjs and wrangler.redirect.toml.Do not add hand-written pages to docs/content/docs/. The public changelog is owned by the changelog repository at docs.zenml.io/changelog. This repository may generate a gitignored docs/content/docs/changelog.mdx for local reference builds, but agents should not hand-edit or commit it.
The public marketing/runtime site lives in zenml-io-v2. If a task involves Astro pages, public site assets, marketing Cloudflare deployment, or runtime website APIs, switch to that repository instead of adding the code here.
docs/book/, link to sibling pages with relative .md paths.https://sdkdocs.kitaru.ai.https://docs.zenml.io/... URLs.https://assets.kitaru.ai/docs/diagrams/<slug>.png.KITARU_* variables as the public configuration surface.src/kitaru/cli/app.py and are available offline through kitaru schema.src/kitaru/api_models/ are the API contract authorities.src/kitaru/mcp/registry.py and tests/mcp/snapshots/metrics.json. Run just mcp-schema-check; do not copy tool counts into prose.kitaru init, kitaru stack, kitaru model, kitaru executions, kitaru.llm(), or kitaru.create_stack() unless they are reintroduced in v2 source and tests.--machine, --non-interactive, and --no-browser contracts..mdx page needs title and description frontmatter.Do not run or advertise just generate-docs as healthy until scripts/generate_sdk_docs.py is restored for the v2 public SDK and the docs workflow passes.
Example READMEs are user-facing. They should teach new users what Kitaru does and walk them through the specific example.
Do not add maintainer-oriented sections such as "Testing", CI-only credential setup, or notes about stubbed or mocked runs. If a section would not help a first-time user understand Kitaru, it belongs in tests, contributor docs, or PR descriptions instead.