Cloud, CI/CD, monitoring, and deployment (7.3K skills)
Post-deployment ownership transfer and registry PR for a warp route. Transfers ownership from the temporary deployer address to real owners, adds CoinGecko ID, commits, and opens a registry PR. Run after warp-deploy-init completes deployment.
The English summary is being prepared. Showing the original description.
Canonical legend for expanding a `less than KEY_PROTOCOL_VALUEgreater than ` placeholder into a shell substitution based on the key-context artifact's `source` field, plus the mandatory `pnpm --silent` rule that keeps the resolved key out of logs and the display-the-key-name-before-CONFIRM disclosure. Referenced by every warp deploy/update skill that passes a `--key.protocol` flag.
The English summary is being prepared. Showing the original description.
Create, check, and read on-chain Sealevel (SVM) Address Lookup Tables (ALTs) for a warp route. Use after deploying, extending, or upgrading an SVM warp route, when transfers fail with transaction-too-large errors, or when asked to inspect or verify a route's ALTs. Fee-enabled SVM transfers bundle 40+ accounts and require ALTs to fit under the 1232-byte tx limit.
The English summary is being prepared. Showing the original description.
Stop the background HTTP registry server started by /start-http-registry — TaskStop / KillShell by the recorded task ID, plus a /proc cmdline-scan fallback for minimal-tool sandboxes with no ps/lsof/pkill/fuser. Referenced by every warp deploy/update skill that starts the registry.
The English summary is being prepared. Showing the original description.
Find existing Docker image tags on GHCR for Hyperlane agent, monorepo, or node service images. Use when the user wants to find a recent image, look up an image for a branch or commit, or check what's currently deployed.
The English summary is being prepared. Showing the original description.
Read and query GCP logs for Hyperlane agents using gcloud CLI. Use when investigating relayer, validator, or scraper logs, debugging message processing, or analyzing operational issues. Provides efficient filtering and context management strategies.
The English summary is being prepared. Showing the original description.
The alphabetical-sort invariants the hyperlane-registry CI / CodeRabbit enforces on warp route YAML (deploy.yaml and config.yaml) — top-level chain entries sorted by chain name, and keys within each entry in strict alphabetical order — plus the canonical per-file key orderings and a verification pass. Referenced by any warp deploy/update skill that writes or edits a registry YAML file.
The English summary is being prepared. Showing the original description.
First step of deploying a new warp route (steps 1–9). Reads a Linear ticket to extract token details and chain configuration, looks up mailbox addresses from the local registry, generates the deploy.yaml, runs the deploy, and optionally runs a send test. Follow up with /warp-deploy-update-owners.
The English summary is being prepared. Showing the original description.
Maintain the durable, per-ticket run log that warp deploy/update skills append to at every milestone — a Linear-document-by-title primary with single-writer discipline and a local-file fallback, a machine-parseable per-chain row plus prose entry shape, and a surface-the-URL-as-proof hard gate. Referenced by any warp deploy/update skill that must leave a retrospective trail across worker restarts.
The English summary is being prepared. Showing the original description.
A skill that allows a user to validate that a warp route deployment will be in the expected state after applying some configuration
The English summary is being prepared. Showing the original description.
Create and read offchain-signed standing warp fee quotes on a deployed warp route, on both EVM and SVM chains. Use when asked to set, submit, update, or inspect standing (reusable, on-chain-expiring) offchain fee quotes for a warp route via the hyperlane warp quote command. One secp256k1 signer key works across EVM and SVM.
The English summary is being prepared. Showing the original description.
Preflight that resolves which private key(s) to use for the warp-deploy chain across every protocol in the route (EVM / Sealevel / Cosmos / Starknet / Tron). For each protocol the user supplies either a specific key spec (GCP secret name, env var, or keystore path) or a candidate list of GCP secret names for the agent to surface and the user to pick. The agent never enumerates GCP secrets on its own and never reads secret values without an explicit user-approved pick. Persists the resolution to `~/.hyperlane/key-contexts/ticket-id.yaml` for downstream warp-deploy skills to auto-load.
The English summary is being prepared. Showing the original description.
Add a new warp route to the Nexus UI whitelist. Checks out the nexus branch of hyperlane-warp-ui-template, adds the warp route ID to warpRouteWhitelist.ts, and opens a PR targeting the nexus branch.
The English summary is being prepared. Showing the original description.
Pre-flight gas and balance check before deploying a warp route. Reads a Linear ticket, checks deployer wallet native gas balances per chain (warn if less than $10), and checks collateral token balance (need ~$1 for testing).
The English summary is being prepared. Showing the original description.
Deploy and operate apps on Prisma Compute with the Prisma 8 CLI. Use whenever the user mentions Prisma Compute, deploying or hosting a Prisma app, `prisma deploy`, `prisma dev module.ts`, Prisma Composer apps (`module.ts`, `compute()`, the `composer` section of `prisma.config.ts`), preview stages, deploy on push (`prisma git connect`, `prisma/cloud-deploy-action`), `prisma service` logs, versions, rollback, or custom domains, `project env`, `PRISMA_SERVICE_TOKEN`, regions, 504s, sleeping instances, or `waitUntil`; also when a project still uses the removed `@prisma/cli app deploy`, `prisma.compute.ts`, `defineComputeConfig`, `compute:deploy`, or `build logs` surface.
The English summary is being prepared. Showing the original description.
Assess and improve cloud portability — identify lock-in, prioritize abstraction, and design migration paths. Use when asked "how locked in are we", "reduce vendor lock-in", or "plan a cloud migration".
The English summary is being prepared. Showing the original description.
Design service mesh observability — distributed tracing, service-level metrics, and dashboards. Use when asked to "add service mesh observability", "set up distributed tracing in the mesh", or "build service-level dashboards".
The English summary is being prepared. Showing the original description.
Survey existing cloud architecture for lock-in depth and portability gaps. Use when asked to "survey our cloud lock-in", "find portability gaps", or "how cloud-agnostic are we".
The English summary is being prepared. Showing the original description.
Survey corporate documents — articles, bylaws, cap table, board resolutions. Use when asked to "survey our corporate documents", "check cap table hygiene", or "what governance docs exist".
The English summary is being prepared. Showing the original description.
Infrastructure engineer — cloud services, IaC, networking, cost optimization. Use when asked to "provision infra", "write Terraform", "cut cloud costs", or "design the network".
The English summary is being prepared. Showing the original description.
Design and build networking infrastructure — VPCs, subnets, DNS, load balancers, firewall rules. Use when asked to "set up networking", "VPC design", "configure DNS", "load balancer setup", "network architecture", or "firewall rules".
The English summary is being prepared. Showing the original description.
Build zero-downtime database migrations — forward SQL, rollback SQL, deployment sequence. Use when asked to "write migration", "schema change", "add column", "rename table", "drop column", or "migrate safely".
The English summary is being prepared. Showing the original description.
Infrastructure reconnaissance — inventory all cloud resources, map connections, flag risks. Use when asked to "inventory our infra", "what infrastructure do we have", "map our cloud resources", "infra discovery", or "what's running in our cloud".
The English summary is being prepared. Showing the original description.
Diagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".
The English summary is being prepared. Showing the original description.