README.md 5.4 KB
description: "The bundled 'powered by dsh' badge skill for users and maintainers enabling, using, or debugging the optional badge provider."
kind: "package-reference"
@deepseek-ai/dsh-skill-badge
English | 中文
Summary
Agents can load the official "powered by dsh" badge skill from this bundled provider and follow its instructions for adding attribution badges to documents, PRs, and other content produced with DeepSeek Harness. The provider has no configuration, and the shipped CLI composition includes the plugin disabled, so deployments enable it explicitly. The skill ships both Markdown snippets and a packaged PNG for systems that cannot reliably import remote images.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
Enable the plugin to make the dsh-badge skill available in the session skill catalog; the model can then load it like any other skill and follow its instructions for adding a "powered by dsh" badge.
When to choose it
Choose this provider when content produced with DeepSeek Harness should carry official attribution badges, and the deployment wants the badge skill available to agents without storing it in a local skill directory. Skip it when the badge is irrelevant to the deployment — the plugin is disabled by default and adds nothing until enabled.
Enable the plugin
The plugin has no configuration. Add its composition row to a composition; the shipped CLI composition carries the row as disabled: true, so enable it explicitly there.
- name: '@deepseek-ai/dsh-skill-badge'
After enabling, dsh-badge appears in the available skills of the session catalog. The skill covers remote Markdown badges (Shields.io-based) and a packaged PNG badge asset for targets that cannot fetch remote images reliably.
What the badge skill provides
- Markdown snippets. Instructions for embedding the official badge markup in documents, PRs, and merge requests.
- Packaged PNG asset. A
dsh-badge.pngresource (726×120 source, rendered at 121×20) that works where remote images cannot be imported.
Observable success and failures
Enabling the plugin makes dsh-badge appear in the catalog and loadable by name; disabling or omitting the row keeps it out of every catalog. Because the provider is immutable, discovery always succeeds with exactly one skill and never reports partial results.
Understand the implementation
Implementation internals — click to expand
This section explains how the bundled provider is wired; the observable behavior is fully covered in [Use this package](#use-this-package). ### Design concept The provider is an immutable, synchronously registered skill source: it registers one fixed candidate at the bundled skill rank (600) under the provider name `dsh-badge`, exposes its packaged `assets/` directory as the skill's directory resource base, and reads the skill body from the packaged `assets/dsh-badge.md` file on every load. ### Source map | File | Role | |---|---| | [`src/index.ts`](src/index.ts) | Plugin entry and the immutable provider: one candidate, resource base, body load | | — | No runtime invariant companion is published; the package owns one immutable provider registration, while the skill registry owns registration uniqueness and lifecycle checks. | | [`assets/`](assets/) | Packaged skill body (`dsh-badge.md`) and PNG asset (`dsh-badge.png`) |Further Exploration
Read these pages when the package-level contract is not enough. They move from the registry this provider registers on to how the skill reaches the model.
- Skill subsystem reference — the registry and provider contract this provider implements.
- skill package — the registry the provider registers on, and the shared rendering of loaded skills.
- tool-skill package — how the badge skill reaches the session catalog and the model.
Model Experience
Indirectly, through dsh-tool-skill, which renders the provider's catalog entry and the selected skill body to the model.
KV Cache effect
Disabled by default, the plugin changes no request. When enabled, its catalog entry and any loaded body change the provider KV prefix at their insertion points.
Known Limitations and Deferred Work
These limits define what the bundled provider does not do. They are current package constraints, not a task backlog.
- One fixed skill, no runtime customization — the provider contributes exactly the
dsh-badgeskill; deployments that need another badge variant author their own skill instead. - Remote Markdown relies on Shields.io — the remote badge markup embeds a Shields.io image; use the packaged PNG when the target cannot fetch remote images reliably.