@dsh-cc/skill-loader 0.5.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.i18n.yaml

@@ -0,0 +1,6 @@
+# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
+# side as of the last confirmed-consistent state. Both languages carry equal authority;
+# after editing either side, bring the other along and re-record with:
+#   pnpm run verify-translation-pairing --write packages/skill/skill-claude-code/README.md
+README.md: b923e9dbaea04f31c9a3343cb60fa72873ea3aba
+README.zh.md: 407d463dab330c7732dcc2d0960ace5a5f93ada0

package/README.md

@@ -0,0 +1,75 @@
+# @dsh-cc/skill-loader
+
+English | [中文](README.zh.md)
+
+Claude Code skill-format compatible provider for the `ctx.skills` registry.
+
+This package discovers `SKILL.md` skills in Claude Code's directory layout (managed, project, user, and additional roots), parses the full Claude Code frontmatter spec, and serves them through `@deepseek-ai/dsh-skill`. It is a compatibility provider: the harness can consume skills written for Claude Code without copying the runtime that executes them. The registry remains in `@deepseek-ai/dsh-skill`; the session catalogs and loader remain in `@deepseek-ai/dsh-tool-skill`.
+
+## Plugin
+
+Requires `ctx.skills` (`inject: ['skills']`).
+
+### Config
+
+| Field | Default | Meaning |
+|---|---|---|
+| `providerName` | `claude-code` | Unique name used to register this provider on `ctx.skills`. |
+| `dshHome` | `$DSH_HOME` or `~/.dsh` | Harness home resolved by [`@deepseek-ai/dsh-home-paths`](../../util/home-paths/README.md); scans `skills` under this directory as the user root. |
+| `managedDir` | — | Optional managed policy root scanned before all defaults. |
+| `additionalDirs` | `[]` | Additional skill roots appended after project and user roots. |
+
+## Discovery
+
+Roots are discovered in this precedence order (lower rank wins name conflicts):
+
+| Rank | Source | Path |
+|---|---|---|
+| 100 | managed | `config.managedDir` |
+| 200 | project | `<projectRoot>/.claude/skills` |
+| 300 | user | `<dshHome>/skills` |
+| 400 | additional | each `config.additionalDirs` |
+
+The project root is the nearest ancestor containing `.git`; without one, the current cwd is used. Skills are directory bundles `<name>/SKILL.md`; legacy `.claude/commands/*.md` files are also loaded and marked `deprecated` in their metadata. Discovery deduplicates by the real path, so a symlinked or overlapping file is served once.
+
+## Skill Format
+
+`SKILL.md` is parsed as a YAML frontmatter document split from a Markdown body. The provider reads every known Claude Code field and tolerates unknown fields; a known field with an invalid value fails loudly at load rather than silently mis-activating.
+
+Supported fields: `description`, `name`, `allowed-tools`, `argument-hint`, `arguments`, `when_to_use`, `version`, `model` (including `inherit`), `user-invocable`, `disable-model-invocation`, `context` (including `fork`), `agent`, `effort`, `shell`, `hooks`, and `paths`. Names must be kebab-case to register on the registry.
+
+## Semantic translation
+
+The provider parses and serves Claude Code fields unchanged; for most fields applying them to harness seams is the consumer's job at activation time (`paths` is the exception — see [Conditional activation](#conditional-activation), which the provider wires itself). The package exports the translators:
+
+- `ccRestriction(allowedTools)` — turns `allowed-tools` into an allow-only `tools.restrict()` filter (a `*` or empty list yields `undefined`, so the skill inherits the caller's surface).
+- `ccPathMatcher(patterns)` / `registerPathActivator(ctx, ...)` — the low-level primitives behind conditional activation (see below).
+- `ccInvocation(parsed)` — resolves `disable-model-invocation` and `user-invocable` into the registry's invocation policy.
+- `context: fork` — surfaced as `metadata.executionContext`; consumers route the skill to `ctx.subagents.start()` with its rendered body.
+
+## Conditional activation
+
+A skill whose frontmatter declares `paths` is a *conditional* skill matching Claude Code's semantics: it is not served until a Read/Write/Edit tool touches a file that matches one of its gitignore-style project-relative `paths`. The provider wires this itself at `apply()`:
+
+1. `list()` parses every candidate; a `paths`-gated skill is **excluded from the catalog** until activated.
+2. On `fs/observed`, a `read`/`write`/`edit` actor touching a matching path inside the project activates that skill (once — repeat touches are idempotent), then calls the provider control's `invalidate()`. Consumers refetch the catalog via `skills/change` and the skill now appears.
+3. `get()` serves the activated skill normally.
+
+This is `registerPathActivator` wired onto the provider's live per-project conditional catalog (the helper's static `projects` shape cannot model per-skill dynamic patterns, so the provider owns the listener while reusing `ccPathMatcher`). Skills already in the catalog never re-notify.
+
+## Bundled skills
+
+The provider ships a portable subset of Claude Code's own bundled skills as in-package `SKILL.md` documents, served directly (no disk extraction). Current subset: `debug`, `simplify`, `batch`. They are provided with `source: 'bundled'`, `rank = BUNDLED_SKILL_RANK` (600), and bodies available via `get()`. Because 600 is the highest rank in this package's range, any managed (100), project (200), user (300), or additional (400) skill of the same name wins the name conflict — matching Claude Code's precedence where local skills override built-ins.
+
+CC's `verify` and `stuck` bundled skills are **not** ported: both are `USER_TYPE === 'ant'`-only, and `verify`'s companion body/examples are absent from the Claude Code build surface, so they cannot be reproduced faithfully.
+
+## Rendering
+
+`renderSkillBody` substitutes `$ARGUMENTS`, `$ARGUMENTS[n]`, `$n`, named `$name` placeholders, and `${CLAUDE_SKILL_DIR}` / `${CLAUDE_SESSION_ID}`, and segments inline-shell `` !`...` `` commands for the caller to execute (guarded by `allowInlineShell`, which MCP-sourced skills must force off). `estimateFrontmatterTokens` counts only name, description, and `when_to_use` — the body is never counted during discovery.
+
+## Known Limitations and Deferred Work
+
+- **Most semantic translation is consumer-side** — `allowed-tools`, `context: fork`, and `argument-hint` are surfaced as metadata and helpers and applied by the consumer, because a provider has no agent reference at load time. `paths` conditional activation is the exception and is applied by this provider.
+- **Inline shell is not executed by this package** — commands are extracted and returned; execution is the caller's responsibility.
+- **One-level discovery** — only `<root>/<name>/SKILL.md` and legacy top-level `.claude/commands/*.md` are recognized.
+- **Bundled subset is partial** — `verify` and `stuck` are omitted (ant-only / missing content); `batch`'s and `debug`'s runtime-injected values (tool names, log paths) are kept as authored literal placeholders rather than resolved at invocation.

package/README.zh.md

@@ -0,0 +1,75 @@
+# @dsh-cc/skill-loader
+
+[English](README.md) | 中文
+
+面向 Claude Code skill 格式兼容的 `ctx.skills` 注册表 Provider。
+
+本包在 Claude Code 的目录布局（managed、project、user 与附加目录）中发现 `SKILL.md` skill，解析完整的 Claude Code frontmatter 规范，并通过 `@deepseek-ai/dsh-skill` 提供给 harness。它是一个兼容性 Provider：harness 可以消费为 Claude Code 编写的 skill，而无需复制执行它们的运行时。注册表仍位于 `@deepseek-ai/dsh-skill`；会话目录与加载器仍位于 `@deepseek-ai/dsh-tool-skill`。
+
+## 插件
+
+需要 `ctx.skills`（`inject: ['skills']`）。
+
+### 配置
+
+| 字段 | 默认值 | 含义 |
+|---|---|---|
+| `providerName` | `claude-code` | 用于在 `ctx.skills` 上注册此 Provider 的唯一名称。 |
+| `dshHome` | `$DSH_HOME` 或 `~/.dsh` | 由 [`@deepseek-ai/dsh-home-paths`](../../util/home-paths/README.md) 解析的 harness 主目录；将其下的 `skills` 作为 user 根扫描。 |
+| `managedDir` | — | 可选的托管策略根，在所有默认根之前扫描。 |
+| `additionalDirs` | `[]` | 在 project 与 user 根之后追加的附加 skill 根。 |
+
+## 发现
+
+按以下优先级顺序发现根（rank 越小越优先处理同名冲突）：
+
+| Rank | 来源 | 路径 |
+|---|---|---|
+| 100 | managed | `config.managedDir` |
+| 200 | project | `<projectRoot>/.claude/skills` |
+| 300 | user | `<dshHome>/skills` |
+| 400 | additional | 每个 `config.additionalDirs` |
+
+project 根是最近包含 `.git` 的祖先；若无则使用当前 cwd。skill 是目录包 `<name>/SKILL.md`；旧的 `.claude/commands/*.md` 文件也会被加载，并在元数据中标记为 `deprecated`。发现按真实路径去重，因此通过符号链接或重叠路径指向的同一文件只会被提供一次。
+
+## Skill 格式
+
+`SKILL.md` 被解析为与 Markdown 正文分离的 YAML frontmatter 文档。Provider 读取每个已知的 Claude Code 字段并容忍未知字段；已知字段的值无效时会在加载期响亮失败，而不是静默地错误激活。
+
+支持的字段：`description`、`name`、`allowed-tools`、`argument-hint`、`arguments`、`when_to_use`、`version`、`model`（含 `inherit`）、`user-invocable`、`disable-model-invocation`、`context`（含 `fork`）、`agent`、`effort`、`shell`、`hooks` 与 `paths`。名称必须是 kebab-case 才能注册到注册表中。
+
+## 语义翻译
+
+Provider 原样解析并提供 Claude Code 字段；对大多数字段，在激活时将它们应用到 harness 接缝是消费方的职责（`paths` 是例外 —— 见[条件激活](#条件激活)，由本 Provider 自行接线）。本包导出的翻译器：
+
+- `ccRestriction(allowedTools)` — 将 `allowed-tools` 转成仅允许（allow-only）的 `tools.restrict()` 过滤器（`*` 或空列表给出 `undefined`，因此该 skill 继承调用方的表面）。
+- `ccPathMatcher(patterns)` / `registerPathActivator(ctx, ...)` — 条件激活背后的低层原语（见下文）。
+- `ccInvocation(parsed)` — 将 `disable-model-invocation` 与 `user-invocable` 解析为注册表的调用策略。
+- `context: fork` — 以 `metadata.executionContext` 形式呈现；消费方将该 skill 与其渲染后的正文一起路由到 `ctx.subagents.start()`。
+
+## 条件激活
+
+frontmatter 声明了 `paths` 的 skill 是*条件* skill，与 Claude Code 语义一致：直到 Read/Write/Edit 工具触碰了匹配其 gitignore 风格、项目相对 `paths` 之一时，它才会被提供。Provider 在 `apply()` 时自行接线：
+
+1. `list()` 解析每个候选；带 `paths` 门控的 skill 在激活前**从目录中排除**。
+2. 在 `fs/observed` 上，`read`/`write`/`edit` actor 触碰项目内匹配路径时将激活该 skill（仅一次 —— 重复触碰是幂等的），随后调用 provider 控制的 `invalidate()`。消费方通过 `skills/change` 重新拉取目录，该 skill 随即出现。
+3. `get()` 正常提供已激活的 skill。
+
+这是 `registerPathActivator` 接在 provider 的按项目实时条件目录上（该辅助函数的静态 `projects` 形态无法表达按 skill 的动态模式，因此 Provider 自行持有监听器，同时复用 `ccPathMatcher`）。已在目录中的 skill 绝不重复通知。
+
+## Bundled skill
+
+Provider 随包提供一个 Claude Code 自带 bundled skills 的可移植子集，作为包内 `SKILL.md` 文档，直接提供（无需落盘）。当前子集：`debug`、`simplify`、`batch`。它们以 `source: 'bundled'`、`rank = BUNDLED_SKILL_RANK`（600）提供，正文可通过 `get()` 获取。由于 600 是本包范围内最大的 rank，任何同名 managed（100）、project（200）、user（300）或 additional（400）skill 都会在同名冲突中胜出 —— 与 Claude Code 本地 skill 覆盖内置内容的优先级一致。
+
+CC 的 `verify` 与 `stuck` bundled skill **未移植**：两者都仅限 `USER_TYPE === 'ant'`，且 `verify` 的伴随正文/示例在 Claude Code 构建面中缺失，无法忠实复现。
+
+## 渲染
+
+`renderSkillBody` 替换 `$ARGUMENTS`、`$ARGUMENTS[n]`、`$n`、命名 `$name` 占位符以及 `${CLAUDE_SKILL_DIR}` / `${CLAUDE_SESSION_ID}`，并将内联 shell `` !`...` `` 命令分段供调用方执行（由 `allowInlineShell` 门控，MCP 来源的 skill 必须强制关闭）。`estimateFrontmatterTokens` 只统计 name、description 与 `when_to_use` —— 发现期间从不统计正文。
+
+## 已知限制与待办
+
+- **多数语义翻译在消费方完成** —— `allowed-tools`、`context: fork` 与 `argument-hint` 以元数据和辅助函数形式呈现，由消费方应用，因为 Provider 在加载时没有 agent 引用。`paths` 条件激活是例外，由本 Provider 应用。
+- **本包不执行内联 shell** —— 命令被提取并返回，执行是调用方的职责。
+- **单层发现** —— 仅识别 `<root>/<name>/SKILL.md` 与旧的顶层 `.claude/commands/*.md`。
+- **Bundled 子集不完整** —— 省略 `verify` 与 `stuck`（ant-only / 内容缺失）；`batch` 与 `debug` 的运行时注入值（工具名、日志路径）保留为其原文的占位符，而非在调用时解析。

package/lib/bundled/batch.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Ported Claude Code bundled `batch` skill.
+ *
+ * Source: `~/workspace/github.com/claude-code/skills/bundled/batch.ts`. The
+ * original `buildPrompt(instruction)` injects the user's argument at invocation;
+ * this port keeps the authored instruction body verbatim, leaving the runtime
+ * tool-name and argument placeholders (\${SKILL_TOOL_NAME}, \${ENTER_PLAN_MODE_TOOL_NAME},
+ * \${EXIT_PLAN_MODE_TOOL_NAME}, \${ASK_USER_QUESTION_TOOL_NAME}, \${AGENT_TOOL_NAME},
+ * \${instruction}) literal.
+ *
+ * @module
+ */
+export declare const name = "batch";
+export declare const SKILL_MD = "---\nname: batch\ndescription: Research and plan a large-scale change, then execute it in parallel across 5\u201330 isolated worktree agents that each open a PR.\nwhen_to_use: Use when the user wants to make a sweeping, mechanical change across many files (migrations, refactors, bulk renames) that can be decomposed into independent parallel units.\nargument-hint: '<instruction>'\ndisable-model-invocation: true\nuser-invocable: true\n---\n\n# Batch: Parallel Work Orchestration\n\nYou are orchestrating a large, parallelizable change across this codebase.\n\n## User Instruction\n\n${instruction}\n\n## Phase 1: Research and Plan (Plan Mode)\n\nCall the ${ENTER_PLAN_MODE_TOOL_NAME} tool now to enter plan mode, then:\n\n1. **Understand the scope.** Launch one or more subagents (in the foreground \u2014 you need their results) to deeply research what this instruction touches. Find all the files, patterns, and call sites that need to change. Understand the existing conventions so the migration is consistent.\n\n2. **Decompose into independent units.** Break the work into 5\u201330 self-contained units. Each unit must:\n   - Be independently implementable in an isolated git worktree (no shared state with sibling units)\n   - Be mergeable on its own without depending on another unit's PR landing first\n   - Be roughly uniform in size (split large units, merge trivial ones)\n\n   Scale the count to the actual work: few files \u2192 closer to 5; hundreds of files \u2192 closer to 30. Prefer per-directory or per-module slicing over arbitrary file lists.\n\n3. **Determine the e2e test recipe.** Figure out how a worker can verify its change actually works end-to-end \u2014 not just that unit tests pass. Look for:\n   - A browser-automation tool (for UI changes: click through the affected flow, screenshot the result)\n   - A tmux or CLI-verifier skill (for CLI changes: launch the app interactively, exercise the changed behavior)\n   - A dev-server + curl pattern (for API changes: start the server, hit the affected endpoints)\n   - An existing e2e/integration test suite the worker can run\n\n   If you cannot find a concrete e2e path, use the ${ASK_USER_QUESTION_TOOL_NAME} tool to ask the user how to verify this change end-to-end. Offer 2\u20133 specific options based on what you found. Do not skip this \u2014 the workers cannot ask the user themselves.\n\n   Write the recipe as a short, concrete set of steps that a worker can execute autonomously. Include any setup (start a dev server, build first) and the exact command/interaction to verify.\n\n4. **Write the plan.** In your plan file, include:\n   - A summary of what you found during research\n   - A numbered list of work units \u2014 for each: a short title, the list of files/directories it covers, and a one-line description of the change\n   - The e2e test recipe (or \"skip e2e because \u2026\" if the user chose that)\n   - The exact worker instructions you will give each agent (the shared template)\n\n5. Call ${EXIT_PLAN_MODE_TOOL_NAME} to present the plan for approval.\n\n## Phase 2: Spawn Workers (After Plan Approval)\n\nOnce the plan is approved, spawn one background agent per work unit using the ${AGENT_TOOL_NAME} tool. **All agents must use `isolation: \"worktree\"` and `run_in_background: true`.** Launch them all in a single message block so they run in parallel.\n\nFor each agent, the prompt must be fully self-contained. Include:\n- The overall goal (the user's instruction)\n- This unit's specific task (title, file list, change description \u2014 copied verbatim from your plan)\n- Any codebase conventions you discovered that the worker needs to follow\n- The e2e test recipe from your plan (or \"skip e2e because \u2026\")\n- The worker instructions below, copied verbatim:\n\n```\nAfter you finish implementing the change:\n1. **Simplify** \u2014 Invoke the ${SKILL_TOOL_NAME} tool with `skill: \"simplify\"` to review and clean up your changes.\n2. **Run unit tests** \u2014 Run the project's test suite (check for package.json scripts, Makefile targets, or common commands like `npm test`, `bun test`, `pytest`, `go test`). If tests fail, fix them.\n3. **Test end-to-end** \u2014 Follow the e2e test recipe from the coordinator's prompt (below). If the recipe says to skip e2e for this unit, skip it.\n4. **Commit and push** \u2014 Commit all changes with a clear message, push the branch, and create a PR with `gh pr create`. Use a descriptive title. If `gh` is not available or the push fails, note it in your final message.\n5. **Report** \u2014 End with a single line: `PR: <url>` so the coordinator can track it. If no PR was created, end with `PR: none \u2014 <reason>`.\n```\n\nUse `subagent_type: \"general-purpose\"` unless a more specific agent type fits.\n\n## Phase 3: Track Progress\n\nAfter launching all workers, render an initial status table:\n\n| # | Unit | Status | PR |\n|---|------|--------|----|\n| 1 | <title> | running | \u2014 |\n| 2 | <title> | running | \u2014 |\n\nAs background-agent completion notifications arrive, parse the `PR: <url>` line from each agent's result and re-render the table with updated status (`done` / `failed`) and PR links. Keep a brief failure note for any agent that did not produce a PR.\n\nWhen all agents have reported, render the final table and a one-line summary (e.g., \"22/24 units landed as PRs\").\n";
+//# sourceMappingURL=batch.d.ts.map

package/lib/bundled/batch.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"batch.d.ts","sourceRoot":"","sources":["../../src/bundled/batch.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,eAAO,MAAM,IAAI,UAAU,CAAA;AAE3B,eAAO,MAAM,QAAQ,uwKAkFpB,CAAA"}

package/lib/bundled/batch.js

@@ -0,0 +1,97 @@
+/**
+ * Ported Claude Code bundled `batch` skill.
+ *
+ * Source: `~/workspace/github.com/claude-code/skills/bundled/batch.ts`. The
+ * original `buildPrompt(instruction)` injects the user's argument at invocation;
+ * this port keeps the authored instruction body verbatim, leaving the runtime
+ * tool-name and argument placeholders (\${SKILL_TOOL_NAME}, \${ENTER_PLAN_MODE_TOOL_NAME},
+ * \${EXIT_PLAN_MODE_TOOL_NAME}, \${ASK_USER_QUESTION_TOOL_NAME}, \${AGENT_TOOL_NAME},
+ * \${instruction}) literal.
+ *
+ * @module
+ */
+export const name = 'batch';
+export const SKILL_MD = `---
+name: batch
+description: Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
+when_to_use: Use when the user wants to make a sweeping, mechanical change across many files (migrations, refactors, bulk renames) that can be decomposed into independent parallel units.
+argument-hint: '<instruction>'
+disable-model-invocation: true
+user-invocable: true
+---
+
+# Batch: Parallel Work Orchestration
+
+You are orchestrating a large, parallelizable change across this codebase.
+
+## User Instruction
+
+\${instruction}
+
+## Phase 1: Research and Plan (Plan Mode)
+
+Call the \${ENTER_PLAN_MODE_TOOL_NAME} tool now to enter plan mode, then:
+
+1. **Understand the scope.** Launch one or more subagents (in the foreground — you need their results) to deeply research what this instruction touches. Find all the files, patterns, and call sites that need to change. Understand the existing conventions so the migration is consistent.
+
+2. **Decompose into independent units.** Break the work into 5–30 self-contained units. Each unit must:
+   - Be independently implementable in an isolated git worktree (no shared state with sibling units)
+   - Be mergeable on its own without depending on another unit's PR landing first
+   - Be roughly uniform in size (split large units, merge trivial ones)
+
+   Scale the count to the actual work: few files → closer to 5; hundreds of files → closer to 30. Prefer per-directory or per-module slicing over arbitrary file lists.
+
+3. **Determine the e2e test recipe.** Figure out how a worker can verify its change actually works end-to-end — not just that unit tests pass. Look for:
+   - A browser-automation tool (for UI changes: click through the affected flow, screenshot the result)
+   - A tmux or CLI-verifier skill (for CLI changes: launch the app interactively, exercise the changed behavior)
+   - A dev-server + curl pattern (for API changes: start the server, hit the affected endpoints)
+   - An existing e2e/integration test suite the worker can run
+
+   If you cannot find a concrete e2e path, use the \${ASK_USER_QUESTION_TOOL_NAME} tool to ask the user how to verify this change end-to-end. Offer 2–3 specific options based on what you found. Do not skip this — the workers cannot ask the user themselves.
+
+   Write the recipe as a short, concrete set of steps that a worker can execute autonomously. Include any setup (start a dev server, build first) and the exact command/interaction to verify.
+
+4. **Write the plan.** In your plan file, include:
+   - A summary of what you found during research
+   - A numbered list of work units — for each: a short title, the list of files/directories it covers, and a one-line description of the change
+   - The e2e test recipe (or "skip e2e because …" if the user chose that)
+   - The exact worker instructions you will give each agent (the shared template)
+
+5. Call \${EXIT_PLAN_MODE_TOOL_NAME} to present the plan for approval.
+
+## Phase 2: Spawn Workers (After Plan Approval)
+
+Once the plan is approved, spawn one background agent per work unit using the \${AGENT_TOOL_NAME} tool. **All agents must use \`isolation: "worktree"\` and \`run_in_background: true\`.** Launch them all in a single message block so they run in parallel.
+
+For each agent, the prompt must be fully self-contained. Include:
+- The overall goal (the user's instruction)
+- This unit's specific task (title, file list, change description — copied verbatim from your plan)
+- Any codebase conventions you discovered that the worker needs to follow
+- The e2e test recipe from your plan (or "skip e2e because …")
+- The worker instructions below, copied verbatim:
+
+\`\`\`
+After you finish implementing the change:
+1. **Simplify** — Invoke the \${SKILL_TOOL_NAME} tool with \`skill: "simplify"\` to review and clean up your changes.
+2. **Run unit tests** — Run the project's test suite (check for package.json scripts, Makefile targets, or common commands like \`npm test\`, \`bun test\`, \`pytest\`, \`go test\`). If tests fail, fix them.
+3. **Test end-to-end** — Follow the e2e test recipe from the coordinator's prompt (below). If the recipe says to skip e2e for this unit, skip it.
+4. **Commit and push** — Commit all changes with a clear message, push the branch, and create a PR with \`gh pr create\`. Use a descriptive title. If \`gh\` is not available or the push fails, note it in your final message.
+5. **Report** — End with a single line: \`PR: <url>\` so the coordinator can track it. If no PR was created, end with \`PR: none — <reason>\`.
+\`\`\`
+
+Use \`subagent_type: "general-purpose"\` unless a more specific agent type fits.
+
+## Phase 3: Track Progress
+
+After launching all workers, render an initial status table:
+
+| # | Unit | Status | PR |
+|---|------|--------|----|
+| 1 | <title> | running | — |
+| 2 | <title> | running | — |
+
+As background-agent completion notifications arrive, parse the \`PR: <url>\` line from each agent's result and re-render the table with updated status (\`done\` / \`failed\`) and PR links. Keep a brief failure note for any agent that did not produce a PR.
+
+When all agents have reported, render the final table and a one-line summary (e.g., "22/24 units landed as PRs").
+`;
+//# sourceMappingURL=batch.js.map

package/lib/bundled/batch.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"batch.js","sourceRoot":"","sources":["../../src/bundled/batch.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,MAAM,CAAC,MAAM,IAAI,GAAG,OAAO,CAAA;AAE3B,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkFvB,CAAA"}

package/lib/bundled/debug.d.ts

@@ -0,0 +1,14 @@
+/**
+ * Ported Claude Code bundled `debug` skill.
+ *
+ * Source: `~/workspace/github.com/claude-code/skills/bundled/debug.ts`. The
+ * original resolves runtime values (the session debug-log path and its tail) at
+ * invocation; this port keeps the authored instruction body verbatim, leaving
+ * those runtime-injected fragments as literal placeholders for whichever
+ * consumer runs the skill.
+ *
+ * @module
+ */
+export declare const name = "debug";
+export declare const SKILL_MD = "---\nname: debug\ndescription: Enable debug logging for this session and help diagnose issues\nallowed-tools: Read, Grep, Glob\nargument-hint: '[issue description]'\ndisable-model-invocation: true\nuser-invocable: true\n---\n\n# Debug Skill\n\nHelp the user debug an issue they're encountering in this current Claude Code session.\n\n## Session Debug Log\n\nThe debug log for the current session is at: `${debugLogPath}`.\n\nFor additional context, grep for [ERROR] and [WARN] lines across the full file.\n\n## Issue Description\n\n${issueDescription}\n\n## Settings\n\nRemember that settings are in:\n* user - ${userSettingsPath}\n* project - ${projectSettingsPath}\n* local - ${localSettingsPath}\n\n## Instructions\n\n1. Review the user's issue description\n2. Look for [ERROR] and [WARN] entries, stack traces, and failure patterns across the file\n3. Consider launching the `claude-code-guide` subagent to understand the relevant Claude Code features\n4. Explain what you found in plain language\n5. Suggest concrete fixes or next steps\n";
+//# sourceMappingURL=debug.d.ts.map

package/lib/bundled/debug.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"debug.d.ts","sourceRoot":"","sources":["../../src/bundled/debug.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,eAAO,MAAM,IAAI,UAAU,CAAA;AAE3B,eAAO,MAAM,QAAQ,whCAqCpB,CAAA"}

package/lib/bundled/debug.js

@@ -0,0 +1,51 @@
+/**
+ * Ported Claude Code bundled `debug` skill.
+ *
+ * Source: `~/workspace/github.com/claude-code/skills/bundled/debug.ts`. The
+ * original resolves runtime values (the session debug-log path and its tail) at
+ * invocation; this port keeps the authored instruction body verbatim, leaving
+ * those runtime-injected fragments as literal placeholders for whichever
+ * consumer runs the skill.
+ *
+ * @module
+ */
+export const name = 'debug';
+export const SKILL_MD = `---
+name: debug
+description: Enable debug logging for this session and help diagnose issues
+allowed-tools: Read, Grep, Glob
+argument-hint: '[issue description]'
+disable-model-invocation: true
+user-invocable: true
+---
+
+# Debug Skill
+
+Help the user debug an issue they're encountering in this current Claude Code session.
+
+## Session Debug Log
+
+The debug log for the current session is at: \`\${debugLogPath}\`.
+
+For additional context, grep for [ERROR] and [WARN] lines across the full file.
+
+## Issue Description
+
+\${issueDescription}
+
+## Settings
+
+Remember that settings are in:
+* user - \${userSettingsPath}
+* project - \${projectSettingsPath}
+* local - \${localSettingsPath}
+
+## Instructions
+
+1. Review the user's issue description
+2. Look for [ERROR] and [WARN] entries, stack traces, and failure patterns across the file
+3. Consider launching the \`claude-code-guide\` subagent to understand the relevant Claude Code features
+4. Explain what you found in plain language
+5. Suggest concrete fixes or next steps
+`;
+//# sourceMappingURL=debug.js.map

package/lib/bundled/debug.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"debug.js","sourceRoot":"","sources":["../../src/bundled/debug.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,MAAM,CAAC,MAAM,IAAI,GAAG,OAAO,CAAA;AAE3B,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqCvB,CAAA"}

package/lib/bundled/index.d.ts

@@ -0,0 +1,36 @@
+/**
+ * Bundled skills shipped with this compatible provider.
+ *
+ * A portable subset of Claude Code's own bundled skills (`~/workspace/github.com/claude-code/skills/bundled/`),
+ * authored as `SKILL.md` documents and served directly from this package — no
+ * disk extraction. They are provided with `source: 'bundled'` and the registry's
+ * `BUNDLED_SKILL_RANK`, so any project, user, managed, or additional skill of the
+ * same name wins the name conflict — matching Claude Code's precedence where
+ * local skills override built-ins.
+ *
+ * Only self-contained, harness-portable skills are included; ant-only skills
+ * (`verify`, `stuck`) and claude.ai/vendor-bound skills are excluded.
+ *
+ * @module
+ */
+import { type ParsedCcFrontmatter } from '../frontmatter.ts';
+/** One parsed bundled skill with a stable locator for the provider. */
+export interface BundledSkillFile {
+    /** Discriminator so the provider can tell bundled locators from `CcSkillFile`. */
+    readonly kind: 'bundled';
+    /** Kebab-case skill name, validated for the registry. */
+    readonly name: string;
+    /** Logical base directory string (in-package; not a real filesystem dir). */
+    readonly directory: string;
+    /** Human-readable source description for logs. */
+    readonly path: string;
+    /** Already-read Markdown body. */
+    readonly body: string;
+    /** Parsed frontmatter with a proven-valid registry name. */
+    readonly parsed: ParsedCcFrontmatter & {
+        name: string;
+    };
+}
+/** Parse the in-package bundled skill set once. Skills with missing or invalid names are skipped. */
+export declare function discoverBundledSkills(): readonly BundledSkillFile[];
+//# sourceMappingURL=index.d.ts.map

package/lib/bundled/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/bundled/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAGH,OAAO,EAGL,KAAK,mBAAmB,EACzB,MAAM,mBAAmB,CAAA;AAK1B,uEAAuE;AACvE,MAAM,WAAW,gBAAgB;IAC/B,kFAAkF;IAClF,QAAQ,CAAC,IAAI,EAAE,SAAS,CAAA;IACxB,yDAAyD;IACzD,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAA;IACrB,6EAA6E;IAC7E,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAA;IAC1B,kDAAkD;IAClD,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAA;IACrB,kCAAkC;IAClC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAA;IACrB,4DAA4D;IAC5D,QAAQ,CAAC,MAAM,EAAE,mBAAmB,GAAG;QAAE,IAAI,EAAE,MAAM,CAAA;KAAE,CAAA;CACxD;AAQD,qGAAqG;AACrG,wBAAgB,qBAAqB,IAAI,SAAS,gBAAgB,EAAE,CAiBnE"}