add-vendor

Add a new Type 2 vendor to the marketplace.

Arguments: $ARGUMENTS (format: <vendor-name> <github-repo-url>)

Example: /add-vendor mastra https://github.com/mastra-ai/skills

---

Step 1 — Parse & Validate Input

Parse $ARGUMENTS to extract:

• VENDOR_NAME: first token (e.g. oxc)
• REPO_URL: second token (e.g. https://github.com/nicolo-ribaudo/oxc)

Validate:

• Both tokens are present. If not, stop and show: Usage: /add-vendor <name> <github-repo-url>
• REPO_URL matches pattern https://github.com/<owner>/<repo> (or [email protected]:<owner>/<repo>). Normalize to HTTPS form.
• VENDOR_NAME contains only alphanumeric characters, hyphens, and underscores.

Check scripts/meta.ts — read the file and verify VENDOR_NAME is NOT already a key in the vendors object. If it already exists, stop and report: Vendor '<name>' already exists in scripts/meta.ts.

Step 2 — Explore Vendor Repository

Use the GitHub MCP tool or gh CLI to browse the vendor repository and find its skills/ directory:

gh api repos/<owner>/<repo>/contents/skills

• If the API returns a 404 or the directory doesn't exist, stop and report:

  No skills/ directory found in <REPO_URL>.
  This repository is not a Type 2 vendor (it doesn't self-host skills).
  Consider using /generate-skill for Type 1 skill generation from docs.
  

• If the directory exists, list all subdirectory names under skills/ — these are the available source skills.

Display the found skills to the user:

Found skills in <REPO_URL>/skills/:
  - <skill-1>
  - <skill-2>
  ...

Step 3 — Determine Skill → Plugin Mappings

For each skill found, determine:

1. Output skill name — usually the same as the source skill name (identity mapping). Ask the user if they want to rename any skill.
2. Target plugin — which plugins/<plugin>/ directory the skill should go into.

Read scripts/cli.ts to see existing SKILL_TO_PLUGIN entries and existing plugins in plugins/.