Bklit UI is an open-source collection of customizable interface components and charts for building React applications with shadcn. Developers use it to add data visualizations such as funnels, gauges, maps, financial charts, and other interactive displays. The catalogue add-ons provide workflows for using its components and chart registry.
Borrowing it
Nothing to install: this file belongs to bklit/bklit-ui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bklit/bklit-ui/main/.agents/skills/bklit-ship/SKILL.mdgit clone --depth 1 https://github.com/bklit/bklit-uiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/bklit/bklit-ui/bklit-ship)<a href="https://agentmods.dev/skills/bklit/bklit-ui/bklit-ship"><img src="https://agentmods.dev/badge/skills/bklit/bklit-ui/bklit-ship/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bklit/bklit-ui/bklit-ship"><img src="https://agentmods.dev/badge/skills/bklit/bklit-ui/bklit-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.01522 |
| Opus 5 | $0.00017 | $0.00761 |
| Sonnet 5 | $0.00007 | $0.00304 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade A, and why
bklit-ship scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bklit Ship Skill
This skill is for bklit-ui monorepo contributors taking a chart or component validated in Studio into production: published in the UI package, documented, and ready for users.
When to use this skill
- You cloned
bklit/bklit-uiand have a working prototype validated in Studio (/studio) and want to ship it. - You are ready to move from "scaffolding" to "permanent": the API and key props/variants are decided from the prototyping phase.
Plan: Prototype → Production
Follow these steps in order. Treat this as a checklist; each step has concrete locations in the repo.
1. Move into the UI package and export
- Move or finalize chart/component source in
packages/ui/(e.g.packages/ui/src/charts/for charts). Prototypes should already live here if you followed bklit-studio; remove any leftover copies underapps/web/components/playground/if present. - Export the new chart/component from the package’s public API:
- For charts: add exports in
packages/ui/src/charts/index.ts. - If the package uses
exportsinpackage.jsonfor specific entry points, add or update the relevant entry so the new component is importable as@bklitui/ui/charts(or the appropriate path).
- For charts: add exports in
- Do not add app-only chart copies under
apps/web/components/playground/(deprecated). Studio previews belong inpackages/studio.
2. Documentation and examples (apps/web)
Documentation lives under apps/web/. Do all of the following.
- Update existing component docs when shipping extends an existing chart (new props, subcomponents, or behavior):
- Add new props to the relevant tables in the parent doc (e.g.
line-chart.mdxforGrid highlightRowValues,ChartTooltip indicatorColor). - Update related utility docs if needed (e.g.
content/docs/utility/grid.mdx,tooltip.mdx). - Keep the primary docs preview unchanged — do not swap the standard preview on an existing page for the new variant.
- Add a short section linking to a dedicated doc page when the feature warrants one (e.g. Profit/Loss →
profit-loss-line.mdx).
- Add new props to the relevant tables in the parent doc (e.g.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 116 lines · 34 tokens per session scan A 56e496263733
bklit-ship is a skill published in the GitHub repository bklit/bklit-ui (1,619 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,522 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
commit
Create git commits in the Unovis repo that pass its commitlint rules. Unovis uses a CUSTOM commit format (Type | Scope | Subscope: Sentence-case subject), NOT Conventional Commits, so feat:/fix: will be rejected by the commit-msg hook. Use this whenever staging and committing changes, writing or rewriting a commit…
open-pr
Open a pull request for the Unovis repo with the project's conventions — correct branch off main, the standard commit grouping, and the checklist-style PR body used by the maintainers. Use when asked to open/create/submit a pull request, prepare a branch for review, or write a PR description in this repository.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.