agent-skill-deploy

Deploy agent skill collections to GitHub, Claude Code, VS Code, and Copilot CLI marketplaces.

1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/webmaxru/ai-native-dev --skill agent-skill-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-skill-deploy
Source: https://github.com/webmaxru/ai-native-dev/tree/main/.github/skills/agent-skill-deploy
Command: npx skills add https://github.com/webmaxru/ai-native-dev --skill agent-skill-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Deploys agent skill collections from any GitHub repository with a /skills folder to distribution surfaces: GitHub releases, Claude Code marketplace, VS Code plugin marketplace, and Copilot CLI plugin marketplace. Handles pre-flight validation, conventional commit analysis, version bumping across surface configs, and surface-specific publishing with dry-run support. Use when releasing, publishing, or deploying a skills collection to any supported marketplace or creating a GitHub release for a skills repository. Don't use for deploying non-skill packages, npm modules, Docker images, or Azure resources.

Core Features & Use Cases

  • Pre-flight validation of git state, skills inventory, and surface readiness
  • Conventional commit analysis with version bump recommendations
  • Version bumping across all detected surface configuration files
  • Surface-specific deployment with dry-run capability
  • User approval gates before irreversible operations

Quick Start

Use the three bundled scripts from the skill directory to orchestrate a dry-run deployment across all supported surfaces.

Frequently Asked Questions about agent-skill-deploy

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

FAQPage Schema
How do I deploy agent skills to multiple marketplaces like VS Code and Claude Code?

Deploying agent skills to VS Code and Claude Code marketplaces requires inventorying skills, validating git state, bumping versions across surface configs, and publishing to each marketplace through an automated deployment workflow.

What is conventional commit analysis for version bumping in skill collections?

Conventional commit analysis for version bumping evaluates commit history since the last release to recommend semantic version increments across surface configuration files before publishing skill collections.

Do I need git and node installed to publish skill collections to distribution surfaces?

Yes, you need git and node installed to publish skill collections, as the deployment workflow uses bundled scripts to validate git state and execute surface-specific publishing across marketplaces.

Can I test a dry-run deployment before publishing skills to GitHub releases and marketplaces?

Yes, you can test a dry-run deployment before publishing skills, allowing you to validate pre-flight checks, analyze changes, and review version bumps without executing irreversible operations.

When should I not use an automated skill deployment workflow for my repository?

You should not use an automated skill deployment workflow for deploying non-skill packages, npm modules, Docker images, or Azure resources, as the process is specifically designed for skill collections in GitHub repositories.