Feat: Re-publish skills vendored via `npx skills` (skills.sh) into a skillrig origin

[so0k]

Summary

There's no easy path to re-publish a skill that was vendored into a skillrig origin via npx skills add (the Vercel-owned skills.sh public registry). To get such a skill into our origin's catalog (skillrig index) and under skillrig verify, we currently have to hand-author all the x-skillrig.* metadata and manually wire the skill into the origin's configured skills_dir. A first-class skillrig command (e.g. skillrig adopt / skillrig import / skillrig publish) should bridge this.

Context

Origin repos commonly vendor skills two ways:

• skillrig add — writes the x-skillrig.* frontmatter metadata and places the skill under the origin's skills_dir.
• npx skills add <repo> --skill <name> — pulls from skills.sh, lands the skill in .agents/skills/<name>/, symlinks it into agent dirs, and tracks it in npx's own skills-lock.json.

When you pull a useful skill via npx skills and then want to re-publish it through your own org's skillrig origin, the two formats don't line up.

Repro

npx skills add skillrig/cli --skill agentic-go-cli-design

Gap 1 — no x-skillrig.* metadata

A skillrig-vendored skill carries the metadata index/search/verify rely on:

# skills/jira-cli/SKILL.md
metadata:
  x-skillrig.namespace: my-org-skills
  x-skillrig.version: "1.0.0"
  x-skillrig.convention-version: "1"
  x-skillrig.topics: [platform-team, jira, atlassian]
  x-skillrig.requires:
    - tool: jira
      version: ">=1.7.0"
      source: my-org/my-skills
      manager: mise

The npx skills-installed skill has none of it — just plain frontmatter:

# .agents/skills/agentic-go-cli-design/SKILL.md
---
name: agentic-go-cli-design
description: >-
  Design principles for Go CLIs (Cobra) ...
---

It is only tracked in npx's lockfile, which is not skillrig's scheme:

// skills-lock.json
"agentic-go-cli-design": {
  "source": "skillrig/cli",
  "sourceType": "github",
  "skillPath": ".agents/skills/agentic-go-cli-design/SKILL.md",
  "computedHash": "9fb2970b..."
}

Gap 2 — not placed in the origin's skills_dir

Our origin config points the index builder at skills/:

# .skillrig-origin.toml
skills_dir = "skills"

But npx skills installs only into .agents/skills/ and does not create a symlink into skills/:

skills/skill-creator -> ../.agents/skills/skill-creator   # has a symlink
skills/agentic-go-cli-design                               # MISSING - never created

Since skillrig index walks ${skills_dir}/*/SKILL.md, the npx-installed skill is invisible to it.

Request

A first-class command to "adopt"/re-publish an npx-vendored skill into the current skillrig origin, that:

1. Places (or symlinks) the skill into the origin's configured skills_dir.
2. Scaffolds the x-skillrig.* metadata - prompting for / defaulting namespace, version, topics, requires, and stamping convention-version from the origin.
3. Leaves the skill ready for skillrig index and skillrig verify.

Even a skillrig add --from-npx <name> flag or an --adopt mode would remove a fiddly, error-prone manual step and make the skills.sh registry a clean upstream source for org origins.

Environment

• skillrig origin convention_version: 1
• Installed via npx skills (skills.sh / Vercel registry), skill source skillrig/cli