deployment-scripts
Platform-specific deployment scripts and configurations. Use when deploying applications, configuring cloud platforms, validating deployment environments, setting up CI/CD pipelines, or when user mentions Vercel, Netlify, AWS, Docker, deployment config, build scripts, or environment validation.
What this skill does
# deployment-scripts This skill provides reusable deployment utilities, platform configurations, and automation scripts for deploying applications to various cloud platforms. ## Available Scripts ### Authentication & Validation - **scripts/check-auth.sh** - Verify authentication for deployment platforms (Vercel, Netlify, AWS, etc.) - **scripts/validate-env.sh** - Validate environment variables and secrets before deployment - **scripts/validate-build.sh** - Run pre-deployment build validation checks ### Deployment Helpers - **scripts/deploy-helper.sh** - Universal deployment wrapper with platform detection - **scripts/rollback-deployment.sh** - Rollback to previous deployment version - **scripts/health-check.sh** - Post-deployment health and smoke testing ### Platform-Specific - **scripts/vercel-deploy.sh** - Vercel deployment with environment handling - **scripts/netlify-deploy.sh** - Netlify deployment with configuration ## Available Templates ### Platform Configurations - **templates/vercel.json** - Vercel platform configuration template - **templates/netlify.toml** - Netlify platform configuration template - **templates/fly.toml** - Fly.io platform configuration template - **templates/render.yaml** - Render platform configuration template ### Docker Templates - **templates/Dockerfile.node** - Node.js optimized Dockerfile - **templates/Dockerfile.python** - Python optimized Dockerfile - **templates/.dockerignore** - Standard Docker ignore patterns ### CI/CD Templates - **templates/github-actions-deploy.yml** - GitHub Actions deployment workflow - **templates/gitlab-ci-deploy.yml** - GitLab CI deployment configuration - **templates/.env.example** - Environment variables template ## Available Examples - **examples/basic-deployment.md** - Simple deployment workflow - **examples/multi-environment.md** - Multi-environment deployment strategy - **examples/docker-deployment.md** - Containerized deployment patterns - **examples/cicd-integration.md** - CI/CD pipeline integration examples - **examples/troubleshooting.md** - Common deployment issues and solutions ## Usage Instructions ### 1. Validate Environment Before Deployment ```bash # Check authentication status for target platform bash scripts/check-auth.sh vercel # Validate all required environment variables bash scripts/validate-env.sh .env.production ``` ### 2. Use Platform Templates ```bash # Read template and customize for your project Read: templates/vercel.json # Modify configuration as needed Write: vercel.json ``` ### 3. Deploy with Helper Scripts ```bash # Deploy using platform-specific script bash scripts/vercel-deploy.sh production # Or use universal deployment helper bash scripts/deploy-helper.sh --platform vercel --env production ``` ### 4. Post-Deployment Validation ```bash # Run health checks after deployment bash scripts/health-check.sh https://your-app.vercel.app ``` ## Integration with Commands Commands should use these scripts via Bash tool: ```markdown # In a deployment command Bash: bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/deployment/skills/deployment-scripts/scripts/check-auth.sh vercel Bash: bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/deployment/skills/deployment-scripts/scripts/validate-env.sh .env.production Bash: bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/deployment/skills/deployment-scripts/scripts/vercel-deploy.sh production ``` ## Requirements - **Platform CLIs**: Install required CLI tools (vercel, netlify, aws, gcloud, etc.) - **Environment Files**: Maintain `.env.production`, `.env.staging` for each environment - **Git**: Scripts assume git repository for deployment tracking - **Permissions**: Ensure scripts are executable (`chmod +x scripts/*.sh`)
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.