Showing 37561–37590 of 77104 skills
Upgrade a deployed Sealevel (SVM) warp-route token or IGP program to a newer contract version (e.g. to enable token/IGP fee support), driven by warp apply. Use when asked to upgrade, bump, or migrate an SVM warp/IGP program to a fee-enabled or newer version, or when a config diff reports a contractVersion mismatch on a Sealevel chain.
recoil-labs/recoil-link
Verify EVM warp route contract source code on block explorers (implementation, ProxyAdmin, TransparentUpgradeableProxy)
recoil-labs/recoil-link
Check token balances for each leg of a warp route. Shows collateral locked (for collateral/native legs) and total circulating supply (for synthetic legs). Use when you want to inspect the current state of a warp route's liquidity.
recoil-labs/recoil-link
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).
recoil-labs/recoil-link
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.
recoil-labs/recoil-link
Post-registry-merge steps for a new warp route deployment. Adds the warp route ID to warpIds.ts, updates .registryrc to latest registry commit, runs update-agent-config, then guides the user through warp monitor deployment and PR creation.
recoil-labs/recoil-link
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.
recoil-labs/recoil-link
Run the post-deploy send test that validates a freshly deployed or updated warp route end-to-end — real token transfers across the route's legs, delivery confirmation, and fee-accrual checks. Use when asked to send-test, round-trip, or validate transfers on a warp route. Defaults to a full collateral-mesh test for multi-collateral routes.
recoil-labs/recoil-link
Ownership-validation preflight for a warp route. For each chain in the route, determine the owner type (ICA / Safe / Squads / other multisig), confirm it exists on chain (or deploy if missing for ICAs), and reject EOAs. Run before /warp-deploy-init-route generates the deploy.yaml so the deployment never proceeds against an invalid owner set.
recoil-labs/recoil-link
Fork a warp route from the local HTTP registry for development and testing. Forks each chain with the right local node per protocol — anvil for EVM chains, surfpool (Solana mainnet fork) for Sealevel chains. Use when the goal is to simulate transactions on a set of local forks before submitting them on-chain.
recoil-labs/recoil-link
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.
recoil-labs/recoil-link
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.
recoil-labs/recoil-link
Simulate pending Sealevel (SVM) warp-route governance txs — signed directly or via a Squads multisig — by forking Solana mainnet locally with surfpool, replaying the exact transactions, then running warp check against the desired registry config. Use to verify that a not-yet-submitted SVM governance change produces the intended on-chain config before it is signed/executed.
recoil-labs/recoil-link
Generic update orchestrator for an already-deployed warp route. Reads a Linear ticket describing any combination of warp-fee changes / ISM changes / hook changes / owner-address changes / additional-collateral-chain additions, edits the registry deploy.yaml accordingly, builds a per-chain strategy file from the artifact-context owner classifications, runs `hyperlane warp apply`, fork-simulates the resulting receipts via `/warp-route-check`, and hands off to `/warp-update-propose` to land the proposals. Chain extension (adding a brand-new chain with new on-chain contracts) is a separate skill — see `/warp-update-extend`.
recoil-labs/recoil-link
Add a new chain to an existing warp route owned by a customer. Reads a Linear ticket, adds the new chain to the deploy.yaml, builds a customer-specific strategy file for existing chains, runs warp apply, and outputs transaction files for the customer to sign via their multisig.
recoil-labs/recoil-link
Orchestrator skill that takes a warp-apply receipts directory and proposes each batch to its corresponding multisig signer — Safe Transaction Service via `safes/propose-warp-batch.ts` for EVM batches (auto-detects governance context: AW / Foundation / Regular / etc. per filename), Squads via `squads/propose-warp-batch.ts` for SVM batches. Persists a per-ticket proposal summary at `~/.hyperlane/proposals/ticket-id.yaml` so the human can track signing progress in Heimdall or Squads.
recoil-labs/recoil-link
Foundation skill for warp-route updates. Reads the current on-chain config of a warp route via `hyperlane warp read`, enumerates every artifact (router, ProxyAdmin, ISM, hook, fee contracts) per chain, classifies each artifact's owner (auto-detects Safe / ICA / EOA; asks the user for everything else — Turnkey, Privy, MPC, custom multisig, timelock, etc.), and persists a per-artifact owner table that downstream update skills consume to know which signing path each batch needs. Read-only — no signing, no on-chain mutations.
recoil-labs/recoil-link
The post-change validation contract for warp routes — after any step that changes (or proposes) on-chain state, prove the route's config matches the target via hyperlane warp check. Run a live check when the change already executed (deployer-signed); run a fork-simulate-from-owner check via /warp-route-check when the change is pending multisig/file execution. Referenced by every deploy/update skill that mutates a route.
recoil-labs/recoil-link
生成中国中小学教案与配套材料。当用户要"备课""写教案""设计一节课""做课件大纲""出分层作业""写说课稿""评课"时使用。覆盖语文/数学/英语/科学等学科,小学到高中;先确认学段、教材版本与适用课程标准,再按学科核心素养、可观察任务和评价证据组织目标。
sanhuang520-ship-it/awesome-chinese-ai-tools
Cogni database architecture and operations. Use for PostgreSQL environment residency, database-per-node boundaries, secret custody versus data placement, shared/dedicated cells, noisy neighbors, role/pool budgets, DATABASE_URL or DOLTGRES_URL, migrations, backups, restore proof, database health, and database knowledge drift. The executable contract lives in the operator knowledge hub.
cogni-dao/cogni
DNS operations for Cogni multi-node infrastructure. Node app DNS is automatic (do NOT hand-set it); this skill covers DNS trust boundaries, one-time Cloudflare zone setup, the env apex record, removing a purged node's record, and protected-record safety. Use it whenever a test fleet, Akash workload, Cloudflare token, domain, zone, or node hostname is being created or changed.
cogni-dao/cogni
OAuth expert for Cogni nodes. Use for GitHub sign-in, linking a GitHub account, the operator identity broker, identity attestation, the consent screen, per-environment OAuth apps and callbacks, and redirect_uri, invalid_return_to or already_linked failures. For users.id, bindings, sessions and keys, use identity-expert. The design and known traps live in the operator knowledge hub.
cogni-dao/cogni
Validate a PR flighted to candidate-a with exact-SHA, behavior, authentication, UI/API and feature-specific Loki proof. Use for /validate-candidate, "prove this PR on candidate-a", or posting the PR validation scorecard. Fetch the authoritative hub contract first. Not for local tests or pre-flight CI.
cogni-dao/cogni
Graded health snapshot of every shared Cogni VM (production, preview, candidate-a) against the ONE reliability policy — GREEN/YELLOW/RED/UNKNOWN verdict, named memory consumers, next action. Use FIRST when asked "is prod healthy", "why is the fleet flapping", "is the VM overloaded / swapping / out of disk", "what is eating memory", "should we resize", or "did the fix work". Read-only; never SSH to answer these. The contract lives in the operator knowledge hub.
cogni-dao/cogni
Create or edit a GitHub issue with `gh` from the reviewed draft at `.github/drafts/issue-draft.md`. Use only when that draft exists and the user asks to publish, open, or file it — typically handed off from `github-issue-creator`. Assigns the issue to the user; never comments, closes, or reopens.
NagareNegishi/Job-Application-Tracker
Activate when the user types "/learn" or "/learn <topic>". This switches Claude Code into a teaching-first coding mode for unfamiliar technologies. Do NOT trigger on any other signal — only the explicit /learn command. Once activated, stay in this mode for the remainder of the conversation unless the user says "/learn off".
NagareNegishi/Job-Application-Tracker
On-demand OWASP Top 10:2025 security scanner. Scans a single file, captures cross-file connections for follow-up, and maintains a persistent findings record. Use when the user runs /owasp-scan with a file path, or asks to scan a file for security issues.
NagareNegishi/Job-Application-Tracker
Update the local OWASP cheat sheet cache. Use when the user explicitly runs /owasp-update to refresh cached OWASP Cheat Sheet Series content for the current project's language.
NagareNegishi/Job-Application-Tracker
Use this skill whenever the user wants a rough implementation plan — the "how", e.g. breaking a feature into build steps — from an existing product plan, or hands off from `plan-product`. Drafts a doc only; deep verification is the separate `plan-verify` skill.
NagareNegishi/Job-Application-Tracker
Use this skill whenever the user wants to turn a feature or project idea into a product plan — the "what and why" — before implementation planning, or hands loose talk over to formalize into requirements and goals. Drafts a doc only.
NagareNegishi/Job-Application-Tracker