deploy

Dispatch deploy requests to a repository-owned .agents/scripts/deploy.sh script.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/graysurf/agent-runtime-kit --skill deploy-graysurf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/graysurf/agent-runtime-kit/tree/main/tests/golden/claude/plugins/meta/skills/deploy/expected
Command: npx skills add https://github.com/graysurf/agent-runtime-kit --skill deploy-graysurf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the initiation of repository-local deployments by delegating to a project-owned deploy script.

Core Features & Use Cases

  • Dispatches deployment commands to a repository-owned deploy script to ensure project-local consistency.
  • Validates the script exists and is executable before invocation, preventing silent failures.
  • Returns the script's stdout, stderr, exit code, and deployment evidence to aid auditing and rollback.

Quick Start

Invoke the deploy skill to trigger the repository's .agents/scripts/deploy.sh from the project root with your deployment arguments.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I automate deployment using a repository-local script?▼

To automate deployment, you can dispatch deploy requests to a project-owned script located at .agents/scripts/deploy.sh. This ensures project-local consistency by executing the script directly from your repository root with your specified deployment arguments.

What happens if my deployment script is not executable?▼

If the deployment script is not executable, the dispatch process validates its existence and executability before invocation to prevent silent failures. You must ensure the .agents/scripts/deploy.sh file has executable permissions before deployment.

Can I pass custom arguments to the deploy script for different targets?▼

Yes, you can pass custom arguments to the deploy script for different deployment targets. The dispatch process invokes the repository-owned .agents/scripts/deploy.sh from the project root, forwarding your deployment arguments directly to the script.

How do I get deployment evidence and logs after running a deploy script?▼

After running the deploy script, the system returns the script's stdout, stderr, exit code, and deployment evidence. This output aids in auditing the deployment process and facilitating rollback if necessary.

Does this deployment automation work across multiple local repositories?▼

Yes, this deployment automation works across local repositories where a .agents/scripts/deploy.sh file exists and is executable. It applies the dispatch mechanism consistently across different repository environments.