Rename marketplace to webhook-skills, narrow per-skill sources, add bundle entry (#62)

* Switch marketplace to per-skill subdir sources, rename to `webhook-skills`

Two metadata-only changes to .claude-plugin/marketplace.json:

1. Marketplace `name`: `hookdeck-webhook-skills` → `webhook-skills`.
   The skills cover 33 third-party providers (Stripe, Shopify, GitHub,
   etc.) plus Hookdeck's own infrastructure. Hookdeck branding in the
   install command surface (`@hookdeck-webhook-skills`) implies a
   Hookdeck-specific catalog, which isn't what this is. Users now
   install via `<skill>@webhook-skills`.

2. Plugin `source`: `"./"` → `"./skills/<name>"` for all 37 entries,
   and `skills: ["./skills/<name>"]` → `skills: ["./"]` to reflect that
   the plugin root IS the skill folder.

   Before: installing one skill copied the entire repo (37 SKILL.mds,
   examples/, results/, scripts/, etc.) into
   ~/.claude/plugins/cache/. With 37 plugins installable, that meant
   up to 37 full repo copies on disk.

   After: each install pulls only `skills/<provider>-webhooks/`.

   Doc reference: https://code.claude.com/docs/en/plugin-marketplaces.md
   `Relative path | string (e.g. "./my-plugin") | Local directory
   within the marketplace repo. Must start with ./. Resolved relative
   to the marketplace root, not the .claude-plugin/ directory`

Cross-skill references audit: every provider SKILL.md recommends
installing `webhook-handler-patterns` alongside, but every reference
uses absolute https://github.com/hookdeck/webhook-skills/... URLs, not
relative file paths. The same is true in reverse from
webhook-handler-patterns/SKILL.md. No file-path coupling between
skills; the per-subdir migration does not break any cross-reference.

No SKILL.md content changed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Add `webhook-skills` bundle plugin entry

Adds a 38th plugin entry to .claude-plugin/marketplace.json that
bundles all 37 skill folders as a single plugin named `webhook-skills`.
The bundle entry uses `source: "./"` + `skills: [./skills/<each>, ...]`
because it deliberately exposes all 37 skills from the repo root —
unlike the 37 granular entries which each narrow to a single
subdirectory.

Why a bundle entry: Anthropic's plugin directory submission form is
per-plugin. Submitting 37 separate entries to the directory would be
onerous and would dilute the catalog. One bundle plugin lets a single
directory submission cover the whole repo. The 37 granular entries
stay so users adding the marketplace directly can still install
per-provider via `<provider>-webhooks@webhook-skills`.

After this change there are two install paths:
- Granular: /plugin install stripe-webhooks@webhook-skills
- Bundle:   /plugin install webhook-skills@webhook-skills

Bundle name `webhook-skills` matches the marketplace name. That makes
the install command read as `webhook-skills@webhook-skills`, which is
intentional — it mirrors the anthropics/skills `claude-api@claude-api`
pattern where a "default" plugin shares its marketplace's name.

No SKILL.md content changed; no granular entry changed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* README: document `/plugin` install path for Claude Code

Adds a new "Install with `/plugin` (Claude Code)" subsection alongside
the existing `npx skills add` instructions. Documents both install
paths now available via the marketplace.json:

- Granular: `/plugin install <provider>-webhooks@webhook-skills`
- Bundle:   `/plugin install webhook-skills@webhook-skills`

Also clarifies the skill namespacing users will see in each case.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: leggetter