菜单
Set up and diagnose Pkl CLI, language-server, editor, formatter, renderer, documentation, code-generation, and build tooling. Use when installing Pkl, configuring an LSP or editor, choosing JSON/YAML output, or checking local readiness.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | pkl-tooling-setup |
| description | Set up and diagnose Pkl CLI, language-server, editor, formatter, renderer, documentation, code-generation, and build tooling. Use when installing Pkl, configuring an LSP or editor, choosing JSON/YAML output, or checking local readiness. |
Establish a version-aware Pkl toolchain before changing configuration. Prefer official editor integrations over hand-built LSP clients and keep installation writes explicit.
Resolve this skill directory, then inspect the workspace:
<skill-dir>/scripts/pkl_tooling --workspace <repo>
<skill-dir>/scripts/pkl_tooling --workspace <repo> capabilities
The doctor reports the resolved Pkl and Java versions, LSP jar status, detected editors, project and lock presence, and module/test counts. A missing Pkl CLI is a blocking setup failure; a missing standalone LSP is not a failure when an official editor plugin manages it.
pkl --version.pkl-lsp only for a custom editor client.PklProject after dependency changes..pkl file, checking diagnostics/completion, and
running the repository's real format, evaluation, and test loop.Generate a non-mutating plan before installing:
<skill-dir>/scripts/pkl_tooling install-plan cli [--manager homebrew|mise|winget|download]
<skill-dir>/scripts/pkl_tooling install-plan lsp --editor vscode|intellij|neovim|custom
Read installation-and-lsp.md when
installing the CLI, choosing an editor integration, configuring standalone
pkl-lsp, or enabling repository hooks.
Read tooling-capabilities.md when choosing renderers, transformations, docs generation, Gradle/Bazel integration, bindings, or language code generation.
Design OpenAPI component schemas with discriminated variants, constrained primitives, subtype/composition choices, nullability, examples, and invalid-state prevention.
Set up a repository for marketplace-driven AI tooling. Use when onboarding a new repo, refreshing a checked-in marketplace reference, installing core marketplace plugins, or documenting which configured marketplaces should be available by default.
Use when validation, authorization, normalization, or state checks produce facts later code must retain. Replace primitive contracts, flags, sentinel states, string protocols, and call-order conventions with proof-carrying values in any language.
Use when Kotlin work needs type-driven modeling, parse-dont-validate boundaries, semantic package layout, explicit failures, API review, or package cohesion checks.
Pkl engineering for typed configuration contracts, expressions, amendments, evaluation, formatting, tests, projects, dependencies, rendering, and packages. Use when a repository contains `.pkl` modules or `PklProject`, or when configuration behavior should be modeled and enforced with Apple Pkl.
Use when creating or validating referential plugin manifests, marketplace entries, primitive references, or payload-to-reference plugin conversions.