@vibe-agent-toolkit/vat-development-agents 0.1.20 → 0.1.21-rc.2

package/dist/.claude/plugins/marketplaces/vat-skills/plugins/vat-development-agents/skills/vibe-agent-toolkit__skills-distribution/SKILL.md

@@ -1,228 +0,0 @@
----
-name: vibe-agent-toolkit:skills-distribution
-description: Use when setting up vat build, configuring plugin distribution for the Claude ecosystem (marketplace, plugins, managed settings), npm publishing with postinstall hooks, or vat verify orchestration. Covers the full pipeline from skill source to installed plugin.
----
-
-# VAT Distribution: Build, Publish & Install
-
-## Overview
-
-VAT distributes skills as **Claude plugins** via npm packages. The pipeline:
-
-1. `vat build` compiles SKILL.md sources into plugin artifacts
-2. `npm publish` pushes the package to a registry
-3. `npm install` triggers a postinstall hook that registers the plugin in Claude's plugin system
-
-Skills installed this way appear in Claude Code as `/plugin-name:skill-name`.
-
-## Project Structure
-
-```
-my-project/
-├── package.json                    ← vat.skills + postinstall hook + publishConfig
-├── vibe-agent-toolkit.config.yaml  ← skills: + claude: config
-├── resources/
-│   └── skills/
-│       └── SKILL.md
-└── dist/                           ← generated by vat build
-    ├── skills/my-skill/            ← packaged skill
-    └── .claude/plugins/marketplaces/
-        └── my-marketplace/plugins/my-plugin/
-            ├── .claude-plugin/plugin.json
-            └── skills/my-skill/SKILL.md
-```
-
-## Step 1: package.json Configuration
-
-```json
-{
-  "name": "@myorg/my-skills",
-  "version": "1.0.0",
-  "vat": {
-    "version": "1.0",
-    "skills": ["my-skill"]
-  },
-  "scripts": {
-    "build:vat": "vat build",
-    "postinstall": "vat skills install --npm-postinstall || exit 0"
-  },
-  "files": ["dist", "README.md"],
-  "publishConfig": {
-    "registry": "https://registry.npmjs.org"
-  }
-}
-```
-
-The `vat.skills` array contains skill name strings for npm discoverability. Skill source paths and packaging config live in `vibe-agent-toolkit.config.yaml` (see Step 2).
-
-For private GitHub Packages registry:
-```json
-"publishConfig": {
-  "registry": "https://npm.pkg.github.com",
-  "access": "restricted"
-}
-```
-
-Users installing from GitHub Packages need `.npmrc` with the scope registry and auth token:
-```
-@myorg:registry=https://npm.pkg.github.com
-//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}
-```
-
-## Step 2: vibe-agent-toolkit.config.yaml
-
-```yaml
-version: 1
-
-skills:
-  include:
-    - "resources/skills/**/SKILL.md"
-
-claude:
-  marketplaces:
-    my-marketplace:                   # org/publisher identity
-      owner:
-        name: My Organization
-      plugins:
-        - name: my-plugin             # installable unit
-          description: My plugin description
-          skills: "*"                  # all discovered skills
-```
-
-The `skills:` section discovers SKILL.md files via include/exclude globs. The `claude:` section defines how skills are packaged into plugins. Each marketplace has `owner` and `plugins` fields (strict schema — no extra fields).
-
-**Naming convention:** marketplace = org identity (e.g. `acme`), plugin = this package
-(e.g. `acme-tools`). Registers as `my-plugin@my-marketplace` in Claude's plugin registry.
-
-### Multiple skills in one package
-
-List all skills in `vat.skills` for npm discoverability:
-
-```json
-"vat": {
-  "version": "1.0",
-  "skills": ["my-linting", "my-testing"]
-}
-```
-
-Use a selector in the plugin config to include matching skills:
-
-```yaml
-plugins:
-  - name: my-plugin
-    description: Linting and testing skills
-    skills:
-      - "my-linting"
-      - "my-testing"
-```
-
-Or use `"*"` to include all discovered skills in the plugin.
-
-## Step 3: Build
-
-```bash
-vat build        # skills phase then claude phase
-vat verify       # validates resources + skills + claude artifacts
-```
-
-### What vat build does
-
-Two phases, run in dependency order:
-
-1. **`vat skills build`** — reads `vibe-agent-toolkit.config.yaml skills:` section, discovers SKILL.md files via include/exclude globs, compiles each into `dist/skills/<name>/`
-2. **`vat claude build`** — reads `vibe-agent-toolkit.config.yaml claude:` section, wraps built skills into `dist/.claude/plugins/marketplaces/<mp>/plugins/<plugin>/` structure with `.claude-plugin/plugin.json`
-
-Individual commands still work:
-```bash
-vat skills build       # skills phase only
-vat claude build       # claude plugin phase only (requires skills already built)
-vat claude verify      # validate plugin artifacts only
-```
-
-## Step 4: Publish
-
-```bash
-npm publish --tag next    # RC/pre-release
-npm publish               # stable release
-```
-
-## Step 5: User Install
-
-```bash
-vat skills install npm:@myorg/my-skills
-```
-
-Or via standard npm install (postinstall hook triggers automatically):
-```bash
-npm install -g @myorg/my-skills
-```
-
-### How plugin installation works
-
-When `npm install` runs the postinstall hook (`vat skills install --npm-postinstall`):
-
-- VAT detects `dist/.claude/plugins/marketplaces/` directory in the installed package
-- Copies the plugin tree to Claude's plugin directory (dumb recursive copy)
-- Writes to these locations:
-  1. `~/.claude/plugins/marketplaces/<marketplace>/plugins/<plugin>/` — plugin files
-  2. `~/.claude/plugins/known_marketplaces.json` — marketplace registry
-  3. `~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/` — version cache
-  4. `~/.claude/plugins/installed_plugins.json` — installation record
-  5. `~/.claude/settings.json` `enabledPlugins` — activates the plugin
-
-If no `dist/.claude/plugins/marketplaces/` directory exists (package wasn't built before publish): a guidance message is emitted and the hook exits 0. The publisher must run `vat build` and re-publish.
-
-Skills are then available in Claude Code as `/plugin-name:skill-name`.
-
-## managed-settings.json Validation (Enterprise)
-
-```yaml
-claude:
-  managedSettings: managed-settings.json
-```
-
-`vat verify` validates this file against the ManagedSettings schema. Catches typos and schema errors before deployment. Does NOT deploy the file — deployment is a separate concern.
-
-## --target claude-web (ZIP Upload)
-
-For uploading skills directly to `claude.ai/settings/capabilities`:
-
-```bash
-vat skills package ./SKILL.md -o ./dist/ --target claude-web
-```
-
-Produces a ZIP:
-```
-my-skill.zip
-└── my-skill/
-    ├── SKILL.md             # skill definition (required)
-    ├── scripts/             # executable code (.mjs, .py, .sh) — optional
-    ├── references/          # markdown reference material — optional
-    └── assets/              # static data, templates, config — optional
-```
-
-Configure source path mappings in `vibe-agent-toolkit.config.yaml`:
-```yaml
-skills:
-  include:
-    - "skills/**/SKILL.md"
-  config:
-    my-skill:
-      claudeWebTarget:
-        scripts: ["./src/helpers/**/*.ts"]
-        assets: ["./assets/**"]
-```
-
-TypeScript files in `scripts` are tree-shaken and compiled to standalone `.mjs`.
-
-## Quick Reference
-
-| Task | Command |
-|---|---|
-| Build everything | `vat build` |
-| Verify everything | `vat verify` |
-| Build skills only | `vat skills build` |
-| Build claude artifacts only | `vat claude build` |
-| Verify claude artifacts only | `vat claude verify` |
-| Install from npm | `vat skills install npm:@org/pkg` |
-| Package for claude.ai upload | `vat skills package ./SKILL.md -o ./dist/ --target claude-web` |

package/dist/skills/vibe-agent-toolkit__skills-distribution/SKILL.md

@@ -1,228 +0,0 @@
----
-name: vibe-agent-toolkit:skills-distribution
-description: Use when setting up vat build, configuring plugin distribution for the Claude ecosystem (marketplace, plugins, managed settings), npm publishing with postinstall hooks, or vat verify orchestration. Covers the full pipeline from skill source to installed plugin.
----
-
-# VAT Distribution: Build, Publish & Install
-
-## Overview
-
-VAT distributes skills as **Claude plugins** via npm packages. The pipeline:
-
-1. `vat build` compiles SKILL.md sources into plugin artifacts
-2. `npm publish` pushes the package to a registry
-3. `npm install` triggers a postinstall hook that registers the plugin in Claude's plugin system
-
-Skills installed this way appear in Claude Code as `/plugin-name:skill-name`.
-
-## Project Structure
-
-```
-my-project/
-├── package.json                    ← vat.skills + postinstall hook + publishConfig
-├── vibe-agent-toolkit.config.yaml  ← skills: + claude: config
-├── resources/
-│   └── skills/
-│       └── SKILL.md
-└── dist/                           ← generated by vat build
-    ├── skills/my-skill/            ← packaged skill
-    └── .claude/plugins/marketplaces/
-        └── my-marketplace/plugins/my-plugin/
-            ├── .claude-plugin/plugin.json
-            └── skills/my-skill/SKILL.md
-```
-
-## Step 1: package.json Configuration
-
-```json
-{
-  "name": "@myorg/my-skills",
-  "version": "1.0.0",
-  "vat": {
-    "version": "1.0",
-    "skills": ["my-skill"]
-  },
-  "scripts": {
-    "build:vat": "vat build",
-    "postinstall": "vat skills install --npm-postinstall || exit 0"
-  },
-  "files": ["dist", "README.md"],
-  "publishConfig": {
-    "registry": "https://registry.npmjs.org"
-  }
-}
-```
-
-The `vat.skills` array contains skill name strings for npm discoverability. Skill source paths and packaging config live in `vibe-agent-toolkit.config.yaml` (see Step 2).
-
-For private GitHub Packages registry:
-```json
-"publishConfig": {
-  "registry": "https://npm.pkg.github.com",
-  "access": "restricted"
-}
-```
-
-Users installing from GitHub Packages need `.npmrc` with the scope registry and auth token:
-```
-@myorg:registry=https://npm.pkg.github.com
-//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}
-```
-
-## Step 2: vibe-agent-toolkit.config.yaml
-
-```yaml
-version: 1
-
-skills:
-  include:
-    - "resources/skills/**/SKILL.md"
-
-claude:
-  marketplaces:
-    my-marketplace:                   # org/publisher identity
-      owner:
-        name: My Organization
-      plugins:
-        - name: my-plugin             # installable unit
-          description: My plugin description
-          skills: "*"                  # all discovered skills
-```
-
-The `skills:` section discovers SKILL.md files via include/exclude globs. The `claude:` section defines how skills are packaged into plugins. Each marketplace has `owner` and `plugins` fields (strict schema — no extra fields).
-
-**Naming convention:** marketplace = org identity (e.g. `acme`), plugin = this package
-(e.g. `acme-tools`). Registers as `my-plugin@my-marketplace` in Claude's plugin registry.
-
-### Multiple skills in one package
-
-List all skills in `vat.skills` for npm discoverability:
-
-```json
-"vat": {
-  "version": "1.0",
-  "skills": ["my-linting", "my-testing"]
-}
-```
-
-Use a selector in the plugin config to include matching skills:
-
-```yaml
-plugins:
-  - name: my-plugin
-    description: Linting and testing skills
-    skills:
-      - "my-linting"
-      - "my-testing"
-```
-
-Or use `"*"` to include all discovered skills in the plugin.
-
-## Step 3: Build
-
-```bash
-vat build        # skills phase then claude phase
-vat verify       # validates resources + skills + claude artifacts
-```
-
-### What vat build does
-
-Two phases, run in dependency order:
-
-1. **`vat skills build`** — reads `vibe-agent-toolkit.config.yaml skills:` section, discovers SKILL.md files via include/exclude globs, compiles each into `dist/skills/<name>/`
-2. **`vat claude build`** — reads `vibe-agent-toolkit.config.yaml claude:` section, wraps built skills into `dist/.claude/plugins/marketplaces/<mp>/plugins/<plugin>/` structure with `.claude-plugin/plugin.json`
-
-Individual commands still work:
-```bash
-vat skills build       # skills phase only
-vat claude build       # claude plugin phase only (requires skills already built)
-vat claude verify      # validate plugin artifacts only
-```
-
-## Step 4: Publish
-
-```bash
-npm publish --tag next    # RC/pre-release
-npm publish               # stable release
-```
-
-## Step 5: User Install
-
-```bash
-vat skills install npm:@myorg/my-skills
-```
-
-Or via standard npm install (postinstall hook triggers automatically):
-```bash
-npm install -g @myorg/my-skills
-```
-
-### How plugin installation works
-
-When `npm install` runs the postinstall hook (`vat skills install --npm-postinstall`):
-
-- VAT detects `dist/.claude/plugins/marketplaces/` directory in the installed package
-- Copies the plugin tree to Claude's plugin directory (dumb recursive copy)
-- Writes to these locations:
-  1. `~/.claude/plugins/marketplaces/<marketplace>/plugins/<plugin>/` — plugin files
-  2. `~/.claude/plugins/known_marketplaces.json` — marketplace registry
-  3. `~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/` — version cache
-  4. `~/.claude/plugins/installed_plugins.json` — installation record
-  5. `~/.claude/settings.json` `enabledPlugins` — activates the plugin
-
-If no `dist/.claude/plugins/marketplaces/` directory exists (package wasn't built before publish): a guidance message is emitted and the hook exits 0. The publisher must run `vat build` and re-publish.
-
-Skills are then available in Claude Code as `/plugin-name:skill-name`.
-
-## managed-settings.json Validation (Enterprise)
-
-```yaml
-claude:
-  managedSettings: managed-settings.json
-```
-
-`vat verify` validates this file against the ManagedSettings schema. Catches typos and schema errors before deployment. Does NOT deploy the file — deployment is a separate concern.
-
-## --target claude-web (ZIP Upload)
-
-For uploading skills directly to `claude.ai/settings/capabilities`:
-
-```bash
-vat skills package ./SKILL.md -o ./dist/ --target claude-web
-```
-
-Produces a ZIP:
-```
-my-skill.zip
-└── my-skill/
-    ├── SKILL.md             # skill definition (required)
-    ├── scripts/             # executable code (.mjs, .py, .sh) — optional
-    ├── references/          # markdown reference material — optional
-    └── assets/              # static data, templates, config — optional
-```
-
-Configure source path mappings in `vibe-agent-toolkit.config.yaml`:
-```yaml
-skills:
-  include:
-    - "skills/**/SKILL.md"
-  config:
-    my-skill:
-      claudeWebTarget:
-        scripts: ["./src/helpers/**/*.ts"]
-        assets: ["./assets/**"]
-```
-
-TypeScript files in `scripts` are tree-shaken and compiled to standalone `.mjs`.
-
-## Quick Reference
-
-| Task | Command |
-|---|---|
-| Build everything | `vat build` |
-| Verify everything | `vat verify` |
-| Build skills only | `vat skills build` |
-| Build claude artifacts only | `vat claude build` |
-| Verify claude artifacts only | `vat claude verify` |
-| Install from npm | `vat skills install npm:@org/pkg` |
-| Package for claude.ai upload | `vat skills package ./SKILL.md -o ./dist/ --target claude-web` |