runkids/skillshare-hub

skillshare-hub

A curated catalog of skillshare skills — and a reference for building your own. Search, discover, and install AI CLI skills. Fork this repo to create your organization’s internal hub.

What is this?

A curated index of skillshare skills that serves two purposes:

1. Ready-to-use catalog — Pre-configured as the default hub in skillshare. Run skillshare search --hub or open Skills > Hubs in the Web UI.
2. Reference for your own hub — Fork this repo, replace the skills with your organization’s catalog, and customize the CI pipeline. Same schema, same tooling.

Usage

Search via CLI

skillshare search --hub https://raw.githubusercontent.com/runkids/skillshare-hub/main/skillshare-hub.json 

Search via Web UI (built-in)

1. Open the Hubs page. Run skillshare ui, open Skills in the sidebar, then click Hubs.

2. Pick Skillshare Hub. It is built in, so it is always in the Hubs list. Click it to load the whole catalog.

3. Narrow the list. Choose a Tag (for example testing) and type a word into Filter.

4. Install. Click Install on a row. The Install skills dialog opens with the source filled in: click Find skills, keep the skill checked, then click Install 1 skill. Every skill is audited before it is installed, and the row then shows Installed.

5. Preview before installing (optional). On the Skills page, click Install, open the Search tab, set In to Skillshare Hub, and click a result. Preview shows the skill’s content, license and tags without installing anything.

To use another hub, click Add or create a Hub on the Hubs page, paste the URL of its skillshare-hub.json under Add an existing Hub, and click Add.

Install a skill you found

skillshare install 

Skills Catalog

232 skills across 11 categories — browse via skillshare search --hub or the Web UI

Frontend (11)

Marketing (23)

Workflow (108)

Agent (41)

Design (10)

Docs (10)

Testing (7)

Backend (1)

DevOps (21)

Share Your Skill

Built a useful skill? Share it with the community! Adding your skill to this hub makes it discoverable by all skillshare users — via CLI, Web UI, or direct install.

How to Submit

1. Fork this repo
2. Add your skill entry to the appropriate skills/*.json category file:

   {
     "name": "my-skill",
     "description": "One-line description of what the skill does",
     "source": "your-username/your-repo",
     "tags": ["relevant", "tags"]
   }
   

3. Open a Pull Request

CI will automatically:

• Validate JSON format, required fields, and naming conventions
• Clone your skill repo and run skillshare audit (security scan)
• Post audit results as a PR comment

See CONTRIBUTING.md for full guidelines.

Schema

{
  "schemaVersion": 1,
  "skills": [
    {
      "name": "ascii-box-check",
      "description": "Verify and fix ASCII box-drawing diagram alignment in markdown files",
      "source": "runkids/my-skills",
      "skill": "ascii-box-check",
      "tags": ["docs", "workflow"],
      "riskScore": 8,
      "riskLabel": "clean",
      "auditedAt": "2026-02-22T04:00:00Z"
    }
  ]
}

CI Automation

This hub runs three automated workflows:

Build Your Organization’s Hub

Fork this repo to create an internal hub for your team or company. What you get out of the box:

• CI validation — JSON format checks and skillshare audit security scans on every PR
• Audit scores — Weekly security scans with risk scores written to the hub JSON
• Contribution workflow — Fork → add entry → PR, with automated gates

The key advantage: source fields can point to private repos (GitHub Enterprise, internal GitLab, Gitea, etc.) that public tools like GitHub Search can never reach.

The typical company setup keeps both the skills and the hub in internal Git repos that everyone already reaches over SSH. No public raw URL and no tokens are needed. The steps below walk through that setup. For HTTP hosting, file shares and the full reference, see the Hub Index guide and the hub command.

1. Set up the repos

This guide uses two repos on a fictional git.company.com:

One repo can hold both. Everyone who uses the hub needs read access to both repos, and SSH must already work:

ssh -T [email protected]

2. Write the index

Give each skill an SSH source. The // separates the repo from the skill’s folder inside it:

{
  "schemaVersion": 1,
  "skills": [
    {
      "name": "reviewer",
      "description": "Company code review checklist",
      "source": "[email protected]:platform/ai-skills.git//skills/reviewer",
      "tags": ["review"]
    }
  ]
}

The scheme form works too, and it is the one to use when the server listens on another port: ssh://[email protected]:2222/platform/ai-skills.git//skills/reviewer.

[!TIP] On GitHub Enterprise, a short entry like github.company.com/platform/ai-skills/skills/reviewer also installs over SSH, as long as the hub itself was added over SSH from the same host. This only applies to hosts whose name contains github or ends in .ghe.com. Anywhere else (GitLab, Gitea, or GHE on a host like git.company.com) the short form means HTTPS, so write the full SSH URL.

3. Build the index and push it

Build skillshare-hub.json with the CLI or the dashboard.

CLI. Install the skills once over SSH, then generate the index from them. Each entry keeps the SSH source it was installed from:

skillshare install [email protected]:platform/ai-skills.git//skills/reviewer
skillshare hub index -o ./skillshare-hub.json    # add --audit for risk scores

The generated file lists every skill you have installed and records your local sourcePath. Review it and remove what you don’t want to publish.

Dashboard. Run skillshare ui, open Skills > Hubs, click Add or create a Hub, and choose Create a new Hub. Click Add skill, choose Can’t find it? Enter the source yourself, enter a name and the SSH source, then click Save.

Click Share, then Download skillshare-hub.json. Paste the hub repo’s SSH URL into the second step to get the command for your team. Its --label is the Hub’s name.

Either way, commit the file to the hub repo and push over SSH:

git add skillshare-hub.json
git commit -m "feat: add reviewer skill"
git push

4. Teammates subscribe once

skillshare hub add [email protected]:platform/skills-hub.git --label company
skillshare hub default company     # only if you saved other hubs before; the first hub you add becomes the default

skillshare search --hub            # browse the default hub
skillshare search review --hub company
skillshare install [email protected]:platform/ai-skills.git//skills/reviewer

If the index is not at the repo root, add its path after //:

skillshare hub add [email protected]:platform/skills-hub.git//hubs/team.json --label team

skillshare search without --hub searches public GitHub, not your hub.

In the dashboard, open Skills > Hubs, click Add or create a Hub, paste the SSH URL under Add an existing Hub, and click Add. The dashboard runs git on the machine where skillshare ui runs, so that machine needs the SSH key.

5. Keep it up to date

Contributors change skillshare-hub.json through pull requests or merge requests to the hub repo. There is no cache to refresh: every search clones the hub repo again, so teammates see a merged change on their next search.

This repo’s automation runs on GitHub Actions (.github/workflows/). On another CI system you need to port it yourself. The workflows call the scripts/*.sh files, which need bash, jq and the skillshare CLI. The audit scripts (scripts/audit.sh, scripts/audit-all.sh) only turn GitHub and HTTPS sources into clone URLs, so extend their parse_source() for SSH sources and give the CI runner read access to the skill repos.

6. Troubleshooting

Documentation

• skillshare documentation — full CLI reference and guides
• Hub Index guide — create and manage hub indexes
• CONTRIBUTING.md — how to submit a skill

License

MIT