agentsclimarketplace
Sign in

Publish to skills registry

Skill voodootikigod/publish-to-skills-registry/skills/publish-to-skills-registry

Publish a skill to the skills.sh registry by opening a GitHub indexing request in vercel-labs/skills. Use when you want to list a skill on skills.sh so others can discover and install it via `npx skills add`. Triggers on "publish skill", "register skill", "list on skills.sh", "submit to skills registry", "index my skill".From its SKILL.md

Install
npx -y skills add voodootikigod/publish-to-skills-registry --skill publish-to-skills-registry

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.5 KB, 816 tokens by cl100k_base, as published. Nobody here has run it

Publish to Skills Registry

Register a skill on skills.sh by filing an indexing request in the vercel-labs/skills GitHub repository. Once indexed, anyone can install the skill with npx skills add <owner>/<repo>.

Prerequisites

  • The skill must be in a public GitHub repository.
  • The repo must contain at least one SKILL.md with valid name and description frontmatter, discoverable under skills/<name>/SKILL.md (or the repo root).
  • The gh CLI must be authenticated (gh auth status).

Steps

  1. Identify the skill to publish. If the user didn't specify, check the current repo:

    gh repo view --json nameWithOwner,description,repositoryTopics
gh repo view --json licenseInfo --jq '.licenseInfo.spdxId // "unknown"'

    Find all skill names:

    find . -name "SKILL.md" | head -20

  2. Gather the required fields:

    • owner/repo — GitHub repo identifier (e.g. voodootikigod/adversarial-review)
    • skill-name — the name field from the skill's frontmatter
    • description — a one-paragraph plain-text description of what the skill does and why it's useful
    • license — the repo's SPDX license identifier (e.g. MIT, Apache-2.0)
    • topics — 3–6 relevant tags including agent-skills and any supported agents (e.g. claude-code, cursor, codex)

    If any field is missing or unclear, ask the user before opening the issue.

  3. Check for an existing indexing request to avoid duplicates:

    gh issue list -R vercel-labs/skills \
  --search "in:title \"Request to index skill: <owner>/<repo>\"" --limit 5

    If one exists and is open, report the URL and stop. If it's closed/resolved, proceed.

  4. Open the indexing request (write body to a temp file to avoid heredoc indentation issues):

    cat > /tmp/skill-issue-body.md <<'EOF'

Skill Information

  • Repository: https://github.com/<owner>/<repo>
  • Skill name: <skill-name>
  • Install: npx skills add <owner>/<repo> -g -y
  • License: <license>
  • Topics: <comma-separated topics>

Description

<description>

Why index this?

<one sentence on the gap this fills on skills.sh> EOF

gh issue create -R vercel-labs/skills
--title "Request to index skill: <owner>/<repo>"
--body-file /tmp/skill-issue-body.md


5. **Report the issue URL** to the user and confirm that once processed, the skill will be
discoverable at `https://skills.sh/<owner>/<repo>` and installable via:
```bash
npx skills add <owner>/<repo>

Notes

  • If the repo has multiple skills, open one issue per skill with the skill name in the title (e.g. Request to index skill: owner/repo (skill-name)).
  • The vercel-labs/skills maintainers review and index requests manually — turnaround is typically within a few days.
  • To verify the skill is discoverable before filing the issue: 
    npx skills add <owner>/<repo> --list

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,149. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.