What you can do with Skillbox
Skillbox stores versioned skill files for AI agents, with a single owner controlling what each client can read or change. Use it if you need a maintained library shared through permissioned connections. Our sandbox installed and built the project, but its test command failed, and a separate deployment attempt never reached a working application. Skip it if you need a proven, ready-to-pull service before you can commit operating time.
A skill is a set of instructions and supporting files an agent loads for a task. The current README describes an editor, immutable revisions, conflict detection, restore and profiles with separate grants. Its MCP server, using the protocol AI assistants use to call outside tools, exposes search and file access. You can keep one client read-only while allowing another to propose changes for owner review. That is a concrete reason to run a library service instead of copying folders between computers.
The operating boundary matters just as much as the editor. The README calls this a single-owner, self-hosted application. Client connections and permissions do not turn it into a public service with separate customer accounts. A hosted roadmap is future work. You own the PostgreSQL database, the instance configuration and the credentials used by integrations.
What people use Skillbox for
The contributor behind issue #4 reports testing an OpenRouter patch with a real key, including the settings interface, and getting it working end to end. That is the clearest attributed integration use case in the research, with an important limit:
- The issue #4 contributor ran the OpenRouter provider patch, reported successful operation with smaller candidate sets, and reported intermittent
max_tokens_exceededor HTTP 520 failures with larger ones. The captured issue remained open and offered a patch rather than documenting an accepted release.
That report helps you choose the next evaluation task: try the actual library you intend to rank, rather than assume a successful request proves the provider handles every catalog. It also explains why the current README's batching description matters. That description is upstream documentation, while the contributor's earlier experiment is a report about a particular patch. They answer different questions.
What happened when we ran it
Our November 13 deployment attempt used commit dfc974f36fcb and the project's Docker Compose configuration, with every port bound to localhost; it failed after 161 seconds while pulling skillbox:local. Compose tried to pull the application image, then returned pull access denied for skillbox, repository does not exist or may require 'docker login'. That stopped the attempt before a skill-library task could begin. The teardown completed successfully.
The November 18 sandbox run at dfc974f got further through the source checks: our install succeeded in 10 seconds and build succeeded in 7 seconds. Tests exited 1 after 3 seconds. The log counted 46 passes and two failures across 48 tests in 13 files, but named both failing cases only (unnamed).
| Check | Recorded result | What you can conclude |
|---|---|---|
| November 13 Compose deployment | Failed after 161 seconds, pull access denied for skillbox:local | This attempt did not reach a working service |
| November 13 cleanup | Teardown ok | Cleanup completed |
| November 18 install | Succeeded in 10 seconds | Dependency installation completed in this sandbox |
| November 18 dependencies | 332 recorded, 234 MB on disk | This is the measured installed footprint |
| November 18 build | Succeeded in 7 seconds | The recorded build step completed |
| November 18 tests | Failed, exit 1 after 3 seconds; 46 pass, 2 fail | This checkout did not have a passing test command |
Bun's own summary reports 370 expectation calls and 631.00 milliseconds for its test execution. The outer test step lasted 3 seconds. Those are different scopes, so neither should replace the other. The two unnamed failures prevent a useful diagnosis from this tail: it identifies the outcome, not which behavior failed or why.
The sandbox configuration recorded three CPUs, 8 GB RAM and image label lab-node:22. The label alone does not identify the runtime version actually used. The checkout had 107 files, about 13,706 source lines and a 1 MB footprint, plus a Dockerfile, Compose file and tests directory; the scan found no CI workflow files.
Where people get stuck: source-built hosting and file fidelity
The author of issue #3 requests an official container image, explaining that self-hosting required a source build and Kubernetes users needed a private-registry push. The captured report quotes the docs' instruction to build from source until an image is published and checked. It remained an open request. A publish script and a plausible image name are separate from an anonymously downloadable artifact, as our failed pull illustrates.
| Report | Where it hurts | Available response and status in the captured issue |
|---|---|---|
| Issue #3 | Operators expecting a public image | Build from source; official image requested |
| Issue #5 | Importing a shared GitHub link | Local-directory importer described; URL import requested |
| Issue #7 | Repeated Windows package materialization | Check the existing revision after rename failure; proposed, issue open |
| Issue #8 | Invalid UTF-8 read through a text path | Reject malformed text while preserving binary reads; requested, issue open |
The author of issue #7 reports an EPERM rename failure when materializing the same package again on Windows. The proposed response checks whether the target revision already exists, rather than treating every failed rename as a cache collision. The captured report contains no completed fix. If Windows clients are central to your workflow, repeated downloads are a more useful acceptance task than a single successful fetch.
The author of issue #8 reports replacement of malformed UTF-8 bytes during text-only MCP reads. The requested behavior is a clear unsupported-content error for invalid text, with original bytes preserved for binary or resource reads. This is a file-fidelity concern: a returned string can differ from the stored bytes without looking like an obvious transport failure.
GitHub imports and OpenRouter are now documented
The current README documents public GitHub URL imports and OpenRouter recommendations, so the older requests cannot safely describe today's feature list. In issue #5, the contributor described a local-only importer. The current import instructions instead describe an owner preview, a pinned commit and an explicit publish action, with revision conflicts blocking stale overwrites.
That does not make every repository importable. The documented importer accepts public repositories, excludes private repositories, redirects, symlinks, submodules and Git LFS, and treats secret detection as a heuristic. You get a specific source-import workflow, not permission to assume arbitrary packages are safe. Existing IDs require an explicit overwrite choice and publication of a new revision.
The same dating problem affects OpenRouter. Issue #4 asked for it as a third provider, but the current README lists it beside TypeSafe AI and Vercel AI Gateway. It documents the decisions endpoint, batching and normalized cost reporting. An open request is evidence of what a contributor encountered, not proof that subsequent documentation still lacks the feature.
Recommendations send task text to your chosen provider
Jev recommendations send task text and authorized skill descriptions to the configured provider, according to the README. You supply the provider account and key. Saving the key does not purchase credit or confirm provider access, and the project documents search fallback when model recommendations fail. Decide whether those descriptions can leave your instance before enabling the option.
The issue #4 contributor identified a dedicated OpenRouter decisions endpoint, rather than the chat-completions endpoint. The report describes successful smaller requests and intermittent larger-request failures. The current README says OpenRouter now processes the catalog in bounded batches and returns search fallback for the whole request if a batch fails, rather than a partial model ranking.
For your application, the distinction between model ranking and search fallback should remain visible. The README calls relevance an uncalibrated rubric score, not a probability. A skill appearing near the top is therefore a recommendation to inspect, rather than a confidence guarantee that its instructions are appropriate or safe to execute.
Security depends on grants and the code your agent chooses to run
Skillbox says it never executes uploaded skill code, while its clients can download and apply those files. The current README documents revocable client keys, scoped grants and hash-checked downloads. It also says revoking a key cannot retract files already downloaded. Keep the owner credential out of client configurations and use a separate key for each connection you may need to revoke.
The researchers behind issue #11 describe possible manipulation of Jev judgments by untrusted context. They explicitly say their notice does not imply this repository is exploitable in its current configuration. Their recommendation is to add independent validation before consequential actions. Calling that notice a confirmed Skillbox exploit would go beyond their report.
Credential recovery deserves attention before an upgrade. The README says integration keys are encrypted using key material derived from the owner token, and changing that token makes existing integration credentials unreadable. Follow the documented rotation process, and protect database backups alongside the token. Content export and credential recovery are different jobs.
Skillbox vs Skills, OpenSkills and similarly named services
Skills and OpenSkills document command-line skill installation, while Skillbox documents a shared service with profiles and revisions. Start with your distribution problem: do you need local files for a coding agent, or a server deciding which client may access which revision?
| Candidate or search | What it refers to | Useful decision |
|---|---|---|
| kitze/skillbox | Self-hosted versioned library with client grants | Consider for centrally managed access |
| vercel-labs/skills | CLI for the open agent skills ecosystem | Consider for installing skills into projects or agents |
| numman-ali/openskills | Skills loader and installer for coding agents | Consider for a file-based local workflow |
| skillboxes, skillbox tickets, skillbox events | SkillBox's Indian live-event service | These searches do not compare AI library software |
| skillbox vs skillfactory, geekbrains vs skillbox | Education-oriented searches | This repository review supplies no course recommendation |
The SkillBox events site describes booking live events. Queries such as skillbox india, skillbox mumbai, skillbox delhi, skillbox bangalore, skillbox seedhe maut and skillbox promo code concern a different decision from running kitze/skillbox. A ticket refund complaint should not become a reliability finding about this code.
The same caution applies to developer marketing. The X search includes posts promoting skillbox.so, including cross-agent syncing claims. Those posts do not identify a relationship to kitze/skillbox. The meddwl/skillbox README describes computational-chemistry tutorials, another separate project. A matching name is insufficient evidence for transferring features or complaints.
Questions people ask
Skillbox here means kitze/skillbox, a self-hosted AI skills library; the similarly named Indian site sells event tickets.
Does a search for Skillbox refer to kitze/skillbox, Indian event tickets, or an education platform?
It can refer to different entities: the events site offers bookings, while kitze/skillbox describes an AI skills library. Keep the repository owner in your search. Terms such as skillbox vs skillfactory and geekbrains vs skillbox do not turn this software review into a comparison of education providers.
Can I import a skill directly from a GitHub URL?
Yes, the current README documents public GitHub URL preview and import. The older issue #5 requested that feature. Private repositories and the listed unsupported Git features remain outside that documented path.
Is an official container image available for self-hosting?
Use the source-build route unless you have a published artifact you can actually pull. In issue #3, a contributor requests an official public image; our attempt failed pulling skillbox:local. That failure does not say every documented source deployment fails.
Can Skillbox use an OpenRouter key for Jev recommendations?
Yes, the current README lists OpenRouter in Settings. The contributor's earlier patch report used the dedicated decisions endpoint and found larger requests could fail. Use the selected version's provider configuration rather than a generic chat endpoint.
How large a skill library can the proposed OpenRouter integration evaluate?
The contributor reported smaller requests working and larger ones intermittently failing; that patch report is no capacity promise. The current README describes bounded batches and whole-request fallback. Catalog eligibility and successful model evaluation are separate outcomes.
Does the Jev security notice demonstrate that Skillbox is exploitable?
No. The researchers explicitly exclude that conclusion in their notice about potential decision hijacking. Their notice describes a potential decision-hijacking risk and recommends independent safeguards before consequential decisions, rather than documenting a successful exploit of this installation.
What we have not tested yet
Our measurements establish source-step outcomes and one failed deployment attempt, not a working library under daily use. We have not tested today's GitHub importer, current OpenRouter batching, credential rotation, backup restoration, Windows repeatability or binary-file fidelity. The unnamed test failures need full logs before anyone can connect them to a reported issue. Neither a capacity benchmark nor a security audit was performed.
The video records contained no usable YouTube transcripts, and the Bilibili result list did not establish a demonstrated kitze/skillbox workflow. The Reddit discussions concerned tickets or education, so they supply no repository adoption evidence. GitHub's last push was November 13, 2026, but sampled issue reports and that date do not measure production adoption or support responsiveness. A useful next evaluation is to start the documented source-built service, import a small library, connect one scoped client and restore its backup before granting it access to private instructions.


