HivePaaS
An open-source, self-hosted PaaS on Docker Swarm. Deploy apps, databases and functions from one VPS to a whole cluster, with SSL, backups and autoscaling built in.
A local-first dashboard to discover, organize, and favourite the agent skills scattered across your machine — global, project, and repository sources, unified.
Developer toolsTypeScript · CSSGitHub @klubinskakOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Skilldex is a local-first desktop dashboard for developers to discover, organize, and favourite their agent skills across global, project, and repo sources
Taken from the repository README
Loading the full README.
Read the full README ↗Skilldex is a local-first desktop app for managing your agent skills. If you
use AI coding agents, your skills pile up fast — scattered across your home
directory, installed plugins, and individual project repos, each with its own
SKILL.md. It gets hard to remember what you have, where it lives, or whether a
skill is even turned on. Skilldex scans all of those locations, pulls every
skill into one searchable dashboard, and lets you browse, favourite, toggle, and
install skills without hunting through folders.
Everything runs on your machine. Skilldex reads your local skill directories directly and never sends your data anywhere — the renderer has no filesystem access and talks to disk only through a locked-down Electron bridge.
~/.claude/skills)SKILL.md and directory are
laid out correctly for you.SKILL.md and scripts flags known attack patterns (piping
remote content into a shell, credential/.env exfiltration, obfuscated
payloads, prompt-injection phrasing) and shows a red / amber / green trust
badge with the exact risky line. It runs on your installed skills and again
before you install one from a repo — a risky install asks for a deliberate
confirmation. GitHub stars sit beside the badge as a separate reputation
signal, never mixed into the safety verdict.SkillWorkspace module behind the preload seam that discovers skill
directories, dedups across roots, parses manifests, and isolates per-source
errorsSkilldex isn't notarized by Apple yet, so on first launch macOS shows "Apple could not verify 'Skilldex' is free of malware..." and refuses to open it. This is expected for an unnotarized open-source app — it's a one-time approval, not a sign anything is wrong. Choose Done (not Move to Trash), then approve it once:
skilldex.dmg and drag Skilldex into Applications.Skilldex opens normally from then on.
Prefer the terminal? Clear the download quarantine flag once instead:
xattr -dr com.apple.quarantine /Applications/Skilldex.app
On macOS 13+ (Ventura/Sonoma/Sequoia) the older right-click → Open shortcut no longer bypasses this — approval must go through Privacy & Security as above.
Code is organized by feature, not by generic presentation folders:
src/
app/ # composition only
features/
dashboard/ # dashboard state and orchestration
skills/ # catalog model, skill list, favourites, detail
navigation/ # workspace navigation
settings/ # source configuration
ui/ # shared shadcn/ui primitives only
lib/ # shared helpers
Each feature owns its model, state, and UI. The app module only composes features. On the Electron main side, the SkillWorkspace module (electron/main/workspace/) exposes a small interface — get config, get snapshot, configure sources, and skill-change intents — while directory walking, manifest parsing, dedup, and settings persistence stay hidden behind that seam. The renderer reaches it only through the context-isolated window.skilldex preload bridge.
npm install
npm run dev
npm run build
npm run lint
npm run package
New capabilities go behind the SkillWorkspace seam rather than into the renderer. Callers request a normalized workspace snapshot and send skill-change intents; directory walking, manifest parsing, Git inspection, dedup, and settings persistence all stay inside the module. Skill scaffolding, enable/disable, and Git provenance (upstream host deep-links from .git/config) already live there.
Contributions are welcome! See CONTRIBUTING.md for how to set up your environment, the conventions the codebase follows, and how to get a change merged. Skilldex is MIT-licensed.