Turtle
38c7a9fbf4
* feat(release): publish package source, declaration maps, and documentation Every release member publishes its TypeScript source and the declaration maps that resolve into it, and @deepseek-ai/dsh publishes the repository Markdown documentation staged from docs/ at prepack time. The ./src/* export most members already declared now resolves for an installed consumer, and a consumer editor follows a declaration to the implementation. Bundled JavaScript maps stay unpublished; the vendored family and the Desktop runtime file policy are unchanged. Rationale: .agents/notes/implemented/process/2026-10-08-published-source-and-docs.md * feat(release): publish JavaScript maps and compress bundles Every emitted JavaScript map ships beside the bundle it describes, and the workspace build and the client preset compress bundles without mangling identifiers. The documentation payload now mirrors the website publication manifest and is removed again by `postpack`; Desktop and the Python executable exclude the published source, documentation, and maps; `clean` removes a staged copy. Typert's publication contract gains the Remote declaration map. * fix(release): keep node bundles readable for the worker image The browser worker image lowers `yield*` only as a whole statement and rewrites `for await` loops by their source layout, so compressed node-side entries either fail that lowering or lower to unparseable code. Only the browser bundles keep compression, which removes about a third of their text. The bundle-purity assertion now matches the module-loader call regardless of the quote style compression picks, and the release-pack fixture exercises the installed package's new documentation requirement. * feat(release): publish the whole documentation tree `@deepseek-ai/dsh` copies `docs/` in full instead of the website's page set: the maintainer documents, the generated migration records, the translation guidelines, and the `*.i18n.yaml` consistency records ship with the installed package, so the documentation's own links resolve without a checkout. * feat(release): publish the upgrade guides with the documentation The staged documentation keeps the website's page set and adds every `docs/upgrade-guide/` document, which is what an installed reader consults when a released change breaks something. The rest of the maintainer tree stays out. * test(release): expect source and maps in master's new payload cases * feat(release): keep installed docs and source readable in Desktop Desktop keeps the published src/ and docs/ trees inside app.asar, and every model shell call receives DSH_INSTALL_DIR and DSH_NODE_EXECUTABLE so an agent can read them through Electron's Node mode. Staging also generates docs/upgrade-guide/README.md, an index of the upgrade guides grouped by the release they upgrade from. Minified client bundles print string literals with backticks: the worker image packer now recognizes those chunk requests, client license banners are prepended after minification so their text survives, and the affected artifact tests accept either quote. * test(desktop): read archived docs through the Windows PowerShell form Regenerate the config catalog for the shifted shell-env source line. * test(desktop): wait for the GUI-subsystem Electron process from PowerShell * build(release): publish source and maps from the message-quotes package * build(release): publish source and maps from packages new on master * build(release): publish source and maps from the tool-office package
description, kind
| description | kind |
|---|---|
| The skill group map: reusable agent instructions discovered from providers and loaded through the session catalog and skill tool, for users and maintainers navigating the group. | package-group |
skill/ — skill capability family
English | 中文
Summary
The skill family lets agents and users discover and load reusable task instructions only when needed. Use skill/ to combine catalogs and expose one instruction set per name; choose skill-filesystem for project, custom, or user-directory discovery, skill-office for Word, PowerPoint, and Excel workflows. Add tool-skill when models should receive a sorted, durable session catalog, load full instructions through the skill tool, or accept direct /name invocation. Different sources produce the same model-visible format, and model access requires at least one source.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
skill/ |
Registry that merges skill catalogs from any provider and resolves the winning skill for a name | ctx.skills |
skill-filesystem/ |
Discovers skills from project, custom, and user directories and watches them for changes | registers on ctx.skills |
skill-office/ |
Bundles Word, PowerPoint, and Excel workflows with structural file checks | registers on ctx.skills |
tool-skill/ |
Publishes the session skill catalog and the model-facing skill loader tool |
registers on ctx.tools |
tool-workspace-dependencies/ |
Reports bundled Office interpreter paths and versions for Desktop and SDK carriers | registers on ctx.tools |
Related documentation
Start with the subsystem reference for the shared vocabulary, then read the Agent Notes for the design rationale.
- Skill subsystem reference — the registry, provider contract, local discovery priority, and the catalog and tool.
- Skill invocation policy reference — the model and user invocation controls.
See skill-badge for the experimental optional capability.
Dev Note
Working context for maintainers — click to expand
None.