็จไบ็ป OpenClaw ๅฎ่ฃ ๅฏๅค็จ็ continuity ๆจกๆฟไธ็ปไธๅฎ่ฃ ๅ ฅๅฃ๏ผๆฏๆ workspace-onlyใcontinuity-only ๅ full continuity ไธๆก่ทฏ็บฟ๏ผๅฏ้ๅฏนๅน้ ๆบ็ ๆ ๅบ็จ runtime patch๏ผๅฎ็ฐๅๅฐๅไธๅฏน่ฏใๅๅฐ่ชๅจ็ปญๆฅใ้้ป continuity ๅๅค็ๅทฅไฝๆตใ
ๆๅคไธช Skill ็ปๅๆๅฅ่ฃ ๏ผๆฃๆฅ slugใไพ่ตใ่ตๆบๅๅฎไฝๅฒ็ชใ๏ผuse for skills, bundle, packaging workflows๏ผdo not use for ๆททๅ ฅ้ๅค่่ดฃ็ skill, ๅฟฝ็ฅไพ่ตๅฒ็ช.
Discover and inspect verifiers environments through the Prime ecosystem. Use when asked to find environments on the Hub, compare options, inspect metadata, check action status, pull local copies for inspection, or choose environment starting points before evaluation, training, or migration work.
Create or migrate verifiers environments for the Prime Lab ecosystem. Use when asked to build a new environment from scratch, port an eval or benchmark from papers or other libraries, start from an environment on the Hub, or convert existing tasks into a package that exposes load_environment and installs cleanly with prime env install.
Orchestrate E2E test triage and fix implementation: runs triage-ci then implement sequentially. Accepts test names, --agent, artifact path, or CI run reference. For individual phases, use /e2e:triage-ci, /e2e:debug, or /e2e:implement. Use when the user says "triage e2e", "fix e2e failures", or wants the full triage-to-fix pipeline.
Tool-calling pipeline with cost metering and approval workflows
Builds Docker images, starts local servers, and runs smoke tests for the AMD/ROCm development environment. Use when validating changes locally on AMD hardware, building AMD container images, or running AMD-specific smoke and explicit runtime checks.
Builds Docker images, starts local servers, and runs smoke tests for the CPU-only development environment. Use when validating changes locally on CPU, building CPU container images, or running CPU-specific smoke and E2E tests.
Research-to-implement pipeline chaining 5 MCP tools with graceful degradation
Use this skill to build, implement, and test Vizro dashboards (Phase 2). Activate when the user wants to create a working app, says "just build it", or has data ready for implementation. Requires spec files from the dashboard-design skill (Phase 1), or user confirmation to skip design.
Run Erigon CI checks locally and/or trigger them remotely on a branch via GitHub Actions workflow_dispatch. Use this when you need to verify a branch passes all CI before or after pushing โ especially for branches like bal-devnet-2 that don't auto-trigger on push/PR events.
Run Erigon Hive simulator tests locally or via GitHub Actions. Tests EL/CL protocol interoperability (engine API, RPC compat, EEST fixtures). Requires Docker and either `act` (for CI simulation) or direct hive invocation.
Deploy Bindu agents to various environments with safety checks and verification
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort.
modifying build configuration to enable/disable variants, switch compilers or flags, or otherwise prepare for a build
how to run make correctly to get a good build, and otherwise understand the build system
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Re-run failed CI jobs for a brave/brave-core PR. Detects failure stage and uses WIPE_WORKSPACE for build/infra failures. Triggers on: make ci green, retry ci, rerun ci, fix ci, re-run failed jobs, retrigger ci.
Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production". (gstack)
