Veloxdb Scalable Performance
veloxbase/veloxdb
Guides scalability and performance work for VeloxDB's Tauri + Rust PostgreSQL backend and React + TanStack frontend.
A skill your agent uses when adding, updating, documenting, or validating an 8StarLabs UI component in this repository.
Install 8sl Component Ship
$ npx skills add 8starlabs/ui --skill 8sl-component-ship -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install 8starlabs/ui 8sl-component-ship --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/8starlabs/ui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/8sl-component-ship .claude/skills/8sl-component-ship && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "8sl-component-ship" agent skill from https://github.com/8starlabs/ui/tree/main/skills/8sl-component-ship into .claude/skills/8sl-component-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "8sl-component-ship", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/8starlabs/ui/tree/main/skills/8sl-component-shipType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add 8starlabs/ui --skill 8sl-component-ship -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install 8starlabs/ui 8sl-component-ship --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/8starlabs/ui.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/8sl-component-ship .agents/skills/8sl-component-ship && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "8sl-component-ship" agent skill from https://github.com/8starlabs/ui/tree/main/skills/8sl-component-ship into .agents/skills/8sl-component-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "8sl-component-ship", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add 8starlabs/ui --skill 8sl-component-ship -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install 8starlabs/ui 8sl-component-ship --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/8starlabs/ui.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/8sl-component-ship .cursor/skills/8sl-component-ship && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "8sl-component-ship" agent skill from https://github.com/8starlabs/ui/tree/main/skills/8sl-component-ship into .cursor/skills/8sl-component-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "8sl-component-ship", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/8starlabs/ui.git --path skills/8sl-component-ship--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add 8starlabs/ui --skill 8sl-component-ship -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install 8starlabs/ui 8sl-component-ship --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/8starlabs/ui.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/8sl-component-ship .gemini/skills/8sl-component-ship && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "8sl-component-ship" agent skill from https://github.com/8starlabs/ui/tree/main/skills/8sl-component-ship into .gemini/skills/8sl-component-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "8sl-component-ship", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install 8starlabs/ui 8sl-component-shipInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add 8starlabs/ui --skill 8sl-component-ship -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/8starlabs/ui.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/8sl-component-ship .github/skills/8sl-component-ship && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "8sl-component-ship" agent skill from https://github.com/8starlabs/ui/tree/main/skills/8sl-component-ship into .github/skills/8sl-component-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "8sl-component-ship", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add 8starlabs/ui --skill 8sl-component-ship -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install 8starlabs/ui 8sl-component-ship --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/8starlabs/ui.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/8sl-component-ship .opencode/skills/8sl-component-ship && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "8sl-component-ship" agent skill from https://github.com/8starlabs/ui/tree/main/skills/8sl-component-ship into .opencode/skills/8sl-component-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "8sl-component-ship", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
8sl-component-ship- GitHub stars
- 140
- Token cost
- ~824 tokens
- SKILL.md length
- 395 words
- Files
- 3 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when adding, updating, documenting, or validating an 8StarLabs UI component in this repository.
- Works in 4 steps: Treat component shipping as one workflow. → Follow existing component patterns… → Keep changes minimal and coherent. → …
- Validating an 8StarLabs UI component in this repository
- SKILL.md covers Apply this skill when, Repo map, Core rules and Workflow, plus 3 more sections
- Calls pnpm
What it does
8sl Component Ship is an agent skill from 8starlabs/ui. Use when adding, updating, documenting, or validating an 8StarLabs UI component in this repository. Covers the full maintainer workflow across blocks, examples, docs, registry metadata, generated index files, and validation commands.
Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `evals/evals.json` and `references/shipping-checklist.md`).
It sits in Development. It works with shadcn/ui and pnpm. The repository describes itself as: 8StarLabs UI is a component library designed for developers who want niche, high-utility UI elements that you won’t find in standard libraries. The licence is MIT.
When your agent uses it
- Validating an 8StarLabs UI component in this repository
Example prompts
- “/8sl-component-ship”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Treat component shipping as one workflow.
- Follow existing component patterns before inventing new structure.
- Keep changes minimal and coherent.
- Prefer explicit validation.
What it can do on your machine
Read from SKILL.md and the folder at commit 9633e2f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
8sl Component Ship loads about 824 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 395 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from 8starlabs/ui at commit 9633e2f, republished under its MIT licence (© 8starlabs). 395 words, ~824 tokens.
Download SKILL.mdSave it as
.claude/skills/8sl-component-ship/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- 8sl-component-ship
- description
- Use when adding, updating, documenting, or validating an 8StarLabs UI component in this repository. Covers the full maintainer workflow across blocks, examples, docs, registry metadata, generated index files, and validation commands.
8StarLabs Component Ship
Maintainer skill for work inside this repository. Use it when the task is to ship or update a component end-to-end, not when the task is only to consume an already-published registry item in another app.
Apply this skill when
- adding a new component to the registry
- updating an existing block, demo, or docs page
- fixing registry metadata, generated index output, or install targets
- validating that a component change is shippable
Repo map
- Component source:
registry/8starlabs-ui/blocks - Examples and demos:
registry/8starlabs-ui/examples - Docs content:
lib/docs/components - Registry manifest:
registry.json - Generated index:
registry/__index__.tsx - Generation script:
scripts/generate-index.mts
Core rules
- Treat component shipping as one workflow. A real change usually touches source, at least one demo, docs, and registry output expectations together.
- Follow existing component patterns before inventing new structure. Inspect similar blocks and docs pages first.
- Keep changes minimal and coherent. Do not refactor unrelated registry or docs infrastructure unless the current task truly requires it.
- Prefer explicit validation. When registry-facing files change, run the generation/build commands instead of assuming metadata still lines up.
Workflow
- Inspect the current component and the nearest comparable component in the same repo.
- Decide the shipping surface: block only, or block + demo + docs + registry metadata.
- Update the component source in
registry/8starlabs-ui/blocks. - Update or add example files in
registry/8starlabs-ui/exampleswhen the user-facing API or behavior changes. - Update docs in
lib/docs/componentsso installation, usage, and API remain accurate. - Check whether
registry.jsonmust be updated or regenerated expectations changed. - Run the registry sync commands when applicable:
pnpm registry:generate-indexpnpm registry:build - Run additional validation that fits the change, such as
pnpm lintorpnpm tscheck, when the edited files could break site or type behavior. - Review generated diffs before finishing. Make sure output matches source intent and no unrelated artifacts slipped in.
Show full SKILL.md (92 more words)Show less
Heuristics
- New block: add source, at least one example, docs page content, and registry entry.
- API change: update demos and docs in the same pass.
- Docs-only change: keep code untouched unless docs prove current implementation wrong.
- Registry/index mismatch: trust generated output after verifying source inputs, not hand-edited drift.
Avoid
- editing only the block when the public API changed
- leaving docs or demos stale after changing props or behavior
- hand-waving registry sync without running the repo commands
- treating consumer-app integration advice as maintainer workflow
References
- Read
references/shipping-checklist.mdfor repo-specific authoring and validation details.
© 8starlabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/8sl-component-ship of 8starlabs/ui.
- SKILL.md
- evals/evals.json
- references/shipping-checklist.md
Open the folder on GitHubat commit 9633e2f
Compare with similar skills
8sl Component Ship next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| 8sl Component Ship this skill8starlabs/ui | 140 | — | ~824 | Automated safety check: Pass | MIT | |
| Veloxdb Scalable Performanceveloxbase/veloxdb | 646 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Weft FrontendWeaveMindAI/weft | 2k | — | ~8k | Automated safety check: Notes | Custom licence | |
| @pierre/diffs Code Renderingpierrecomputer/pierre | 6.3k | 2 repos | ~803 | Automated safety check: Pass | Apache-2.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Link Workspace Packagesnomcopter/react-mosaic | 4.8k | 6 repos | ~760 | Automated safety check: Pass | Custom licence |
Similar skills
Weft Frontend
WeaveMindAI/weft
Read when the user wants a page, app or site for the program, and before dispatching the frontend-builder: the verified scaffold commands, the default stack (pnpm, SvelteKit, PostgreSQL, BetterAuth…
@pierre/diffs Code Rendering
pierrecomputer/pierre
Guides an agent through using @pierre/diffs to render syntax-highlighted files and diffs, and to build editing and review surfaces in React or plain JavaScript.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Link Workspace Packages
nomcopter/react-mosaic
Link workspace packages in monorepos (npm, yarn, pnpm, bun).
Pull Requests
pnpm/pnpm
Take a change through a pull request in the pnpm repository — opening it, then staying with it after every push until CI is green and the review round is quiet.
More from 8starlabs/ui
8sl Consume Registry
8starlabs/ui
A skill your agent uses when users want to install, integrate, or adapt 8StarLabs UI components in a Next.js plus shadcn project.
PR Comment
8starlabs/ui
A skill your agent uses when the user asks to write, draft, summarize, or compose a pull request description or change summary.
8sl Pattern Review
8starlabs/ui
A skill your agent uses when reviewing, debugging, or cleaning up existing 8StarLabs UI usage.
Related
Categories
Questions about 8sl Component Ship
What does 8sl Component Ship do?
A skill your agent uses when adding, updating, documenting, or validating an 8StarLabs UI component in this repository. 8sl Component Ship is an agent skill from 8starlabs/ui. Use when adding, updating, documenting, or validating an 8StarLabs UI component in this repository.
When should I use 8sl Component Ship?
8sl Component Ship fits situations like: validating an 8StarLabs UI component in this repository.
How do I install 8sl Component Ship in Claude Code?
Run `npx skills add 8starlabs/ui --skill 8sl-component-ship -a claude-code`. Or copy the skill folder (skills/8sl-component-ship in 8starlabs/ui) into .claude/skills/8sl-component-ship in your project. Claude Code loads it when a task matches its description.
How do I install 8sl Component Ship in Codex?
Run `npx skills add 8starlabs/ui --skill 8sl-component-ship -a codex`. Or copy the skill folder (skills/8sl-component-ship in 8starlabs/ui) into .agents/skills/8sl-component-ship in your project. Codex loads it when a task matches its description.
Can I use 8sl Component Ship in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 8starlabs/ui --skill 8sl-component-ship -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/8sl-component-ship, .gemini/skills/8sl-component-ship, .github/skills/8sl-component-ship and .opencode/skills/8sl-component-ship in your project.
What does 8sl Component Ship need to run?
Going by SKILL.md and its folder, 8sl Component Ship needs the command-line tools its instructions call (pnpm).
Does 8sl Component Ship access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is 8sl Component Ship safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does 8sl Component Ship use?
8sl Component Ship is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does 8sl Component Ship use?
About 824 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 551 tokens, read only when the agent opens those files.
What are the alternatives to 8sl Component Ship?
Skills that share tags, products or a category with 8sl Component Ship: Veloxdb Scalable Performance (veloxbase/veloxdb, 646 stars), Weft Frontend (WeaveMindAI/weft, 2k stars), @pierre/diffs Code Rendering (pierrecomputer/pierre, 6.3k stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 8sl Component Ship?
8starlabs (a GitHub organization) maintains it in 8starlabs/ui, which has 140 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 5, 2026.
Source: 8starlabs/ui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.