Individual skill
runway
Deploys software through the target platform's real release model, sequencing configuration, secrets, data, and code safely, then verifying the immutable release and public behavior. Use when the user asks to deploy, release, publish, roll back, or prove a version is live.
skills/runway/SKILL.md
Source commit cfa78f744564cec2c5aaf0cbacbada58d79b9e59
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 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)
- 12
- Repository last updated
- Nov 2, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-coding Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- code-review Repository topic
- coding-agents Repository topic
- debugging Repository topic
- developer-productivity Repository topic
- developer-tools Repository topic
- llm Repository topic
- engineering Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 11,027 bytesSKILL.mdcore · 11,027 bytesreferences/platforms.mddoc · 4,052 bytesreferences/release-protocol.mddoc · 2,276 bytesreferences/research.mddoc · 3,545 bytesscripts/check-receipt.pyruns · 3,279 bytes
Read excerpt
# runway: deploy down the runway, verify on the ground
A deploy command can succeed while live behavior remains unverified. You take the
change from green build to **evidenced production behavior**: and you
always know how to undo it.
## Prerequisites
Candidate-bound readiness evidence (a `cleared` verdict when available), a
successful applicable build locally or in the trusted pipeline, and access to
the target platform (CLI authed or CI wired).
Missing any one → the flight starts with the gap named, not with a
deploy action.
