add-external-skill

Add or update external skills in a marketplace catalog and regenerate the README listing.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/filippolmt/skills --skill add-external-skill-filippolmt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-external-skill
Source: https://github.com/filippolmt/skills/tree/main/.claude/skills/add-external-skill
Command: npx skills add https://github.com/filippolmt/skills --skill add-external-skill-filippolmt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a skill marketplace's marketplace.json and README catalog synchronized with upstream external skill repositories is manual, error-prone work: refs drift, SHAs go stale, new upstream skills get missed, and removed ones linger. This Skill automates adding and updating git-subdir entries so the catalog always matches upstream reality. ## Core Features & Use Cases - Add mode: Discovers skill folders in a GitHub repo via the GitHub API, pins a tag or branch ref with its resolved SHA, and appends correctly formatted entries to marketplace.json. - Update mode: Reconciles existing entries against upstream — adding new skills, confirming removals, bumping SHAs, and refreshing descriptions. - README regeneration: Runs scripts/gen-readme.js to project the catalog from marketplace.json, then validates with claude plugin validate. - Use Case: You want to vendor a skill from owner/repo into your marketplace. Run the skill with the repo path and it discovers the skills, picks a Renovate-compatible ref, writes the entries, and regenerates the README in one pass. ## Quick Start Ask the assistant to add the skill from a specific GitHub owner and repository into this marketplace and regenerate the README catalog.

Frequently Asked Questions about add-external-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add an external skill to a Claude Code marketplace?

Run the skill with the owner and repo, optionally a path and name. It discovers SKILL.md folders via the GitHub API, pins a tag or branch ref with its SHA, appends entries to marketplace.json, and regenerates the README catalog.

How do I update vendored skills to their latest upstream versions?

Use update mode, optionally scoped to one repo. It reconciles entries against upstream: new folders get entries, removed ones are confirmed then deleted, and surviving entries are bumped to the SHA their ref now resolves to.

Should I pin a skill to a tag or a branch?

Pin to a semver tag when the repo publishes them, since tag and SHA bump together under Renovate. Use a branch pin (main or master) only when the repo publishes no usable tags; other ref shapes are never updated by Renovate.

Why is my marketplace entry never updated by Renovate?

Renovate only matches refs shaped as a semver tag (optionally prefixed) or literally main or master. A ref like a bare SHA or release-2026 matches neither customManager, so that entry is silently never bumped.

Can I add a whole plugin instead of individual skills?

Yes. When the path points at a plugin root containing .claude-plugin/plugin.json with bundled artifacts, the skill creates one whole-plugin entry, taking the name from plugin.json and listing its agents and skills in the description.