jonslimak

Omgskills — Development skill for Claude Code

Development community

Search for Claude & Codex skills from your macOS menu-bar.

How to install Omgskills

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jonslimak/omgskills and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Omgskills does

Search for Claude & Codex skills from your macOS menu-bar.

Alternatives in Development

  • Cc Bar — Native macOS menu bar app: track quota, usage and cost for Codex (multi-account) and Claude Code, from your me 119 ★
  • CoderBar — Native macOS agent control for Codex and Claude — monitor, approve, ask, and jump back from the menu bar 100 ★
  • Claude Status — macOS Menu Bar + Desktop Widget for Claude Code Session Monitoring 59 ★

README

omgskills

omgskills

A macOS menubar app for browsing and installing Claude, Codex, and agent skills from GitHub. Two independent parts: a Node.js scraper that builds the public skill library, and a Swift menubar app that reads bundled or remotely refreshed library data.


MCP server

Agents can search the omgskills library through the published read-only MCP server:

npm install -g omgskills-mcp

Add it to your MCP client:

{
  "mcpServers": {
    "omgskills": {
      "command": "omgskills-mcp"
    }
  }
}

The npm package uses hosted library data by default from:

https://omgskills.com/data/manifest.json

No local repo checkout is required for MCP users. Full tool docs live in [mcp/README.md](mcp/README.md).


Trust and safety

This repo is public so people can inspect how omgskills works before running it. It is source-available, not open source. You may read and audit the code, but you may not copy, redistribute, or repackage it without permission.

The app:

  • reads public skill-library data bundled with the app or served from omgskills.com
  • scans local Claude, Codex, and agent skill folders to show installed skills
  • installs skills from public GitHub repositories only when you choose to install them
  • uses Developer ID signing and Apple notarization for public macOS releases

Local crawl logs, browser traces, `.env` files, signing certificates, API tokens, and release credentials are intentionally not part of the public repo.

Security reports should follow [SECURITY.md](SECURITY.md).


Release first

For any public macOS download, use:

./scripts/release-mac.sh

Do not use `menubar/build.sh` for public distribution. It is dev-only and uses ad-hoc signing, which will trigger Gatekeeper warnings.

Required env vars:

  • DEVELOPER_ID_APPLICATION
  • ASC_PRIVATE_KEY_PATH
  • ASC_KEY_ID
  • ASC_ISSUER_ID

Tem