Kartik-Doye/Ravengard-AI-Recruiter / .agents/skills/runway
runway
VerifiedDeploys 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.0 KB |
| references/platforms.md | markdown | 3.6 KB |
| references/release-protocol.md | markdown | 1.3 KB |
| references/research.md | markdown | 823 B |
references/release-protocol.md
View on GitHub# Release protocol: authorize, observe, recover
Use this reference for production, traffic changes, migrations, or a failed
release. Preview work uses the entrypoint unless it exposes material risk.
## Release record
Capture target, immutable artifact or commit, explicit authorization, method,
environment names, migration sequence, fingerprint, health and smoke checks,
observation boundary, rollback method, and owner. Rebuild record if target,
artifact, authorization, or migration state changes.
## Migration sequencing
Prefer compatible expand, deploy, backfill, contract sequencing when old and new
versions overlap. A destructive migration needs backup/restore or approved
forward-fix plan before release. Green build does not prove data compatibility.
## Evidence boundary
Record command or CI result, release identifier, public response fingerprint,
smoke outcomes, logs, cache or async completion signal, and observation end.
Dashboard green is deployment evidence, not product behavior evidence.
## Incident decision
Contain traffic expansion first. Roll back only when prior artifact and data
compatibility are known; otherwise propose forward fix, maintenance action, or
owner escalation. Preserve evidence, expose no secret values, and do not repeat
unchanged deployment attempts.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |