Individual skill
deploy-templates
Reusable deployment templates — one-click deploys, blueprints, and environment-as-code — vendor-neutral patterns.
skills/deploy-templates/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 56
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
## Overview
Deploy templates (one-click deploy buttons, blueprints, compose-style specs)
let anyone spin up a full stack — app + database + cache + config — from a
declarative definition. They're how open-source projects offer "deploy your
own instance" and how teams standardize environments. This skill covers
authoring templates that actually work for strangers.
## When to use
- Publishing a "Deploy" button for an open-source project
- Standardizing dev/staging/prod environments as code
- Defining multi-service stacks (app, DB, cache, worker) declaratively
- Templating config with per-deployment variables and secrets