52 skills · sorted by relevance
Check a gbrain installation after a restart or when services seem broken. It tests key components, repairs some local problems, checks OpenClaw when installed, and records results, with support for custom test scripts.
Create a Mastra project at a specified version and check its Studio in Chrome. Test page loading, agent chat, tool execution, and workflows, then report passed and failed checks, encountered errors, and screenshots.
Create a dedicated test project linked to the current worktree and check Agent Builder through APIs and browser interactions. It covers agent and skill management, permissions, defaults, and related features, with selectable test sections.
Check opencode commands, HTTP server behavior, lifecycle events, and terminal startup with purpose-built scripts. Find stored sessions by ID, title, or scoped message searches, and export conversations as JSON for further inspection.
Prepare the local environment for the Maestro smoke-test suite — verify tooling, select a device, collect the APK if needed, validate the .env file by variable name only, then hand the user the exact lab-store CLI command to run or run it on request.
The English summary is being prepared. Showing the original description.
Check the full connection between a local agent API and a remote sandbox through a temporary tunnel. Run a task that needs no connected tools, verify its response, and restore the web app’s original API connection.
Test community plugin imports in OpenDesign from folders, zip archives, GitHub subpaths, or marketplace entries. Produce a compact receipt showing the plugin name, source type, detected files, and user notes for inspection.
Check a DeerFlow installation from code updates through deployment and basic service checks. Supports local and Docker setups, verifies frontend pages and API health, and produces a report with results and troubleshooting recommendations.
Test the Senpi adapter and task engine against the real senpi binary in an isolated environment. Check task and team behavior, record evidence in a consistent location, and verify that the existing agent directory remains untouched.
Test omo Codex Light edition in an isolated environment using real Codex and a local mock model. Verify installation, plugin hooks, and terminal startup, with captured evidence and no calls to a real model API.
Run diffusers generation pipelines from a terminal and save their outputs. Inspect accepted inputs without downloading model weights, apply LoRA adapters during generation, run remotely through HF Jobs, and inspect software and GPU environment details.
Run smoke tests, or basic operational checks, for Mastra projects locally or in staging and production. Verify Studio screens, agents, tools, workflows, traces, and memory, then report results, blockers, and skipped checks.
Run OpenShell’s Release Canary checks to verify that published development packages and Helm charts install and support basic sandbox operations. Use workflow logs and local Kubernetes reproduction steps to investigate failures before a public release.
Run MNN checks and regression tests on a host computer or Android device, with stage summaries and failure logs. A separate workflow benchmarks LLM prompt processing and token generation on real iPhones and iPads, including branch comparisons.
Evaluate a driving agent on CARLA Leaderboard routes after checking the required setup. Select routes and repetitions, save driving scores and infractions, record runs, and resume interrupted evaluations from a saved checkpoint.
Test Omnigent’s native Antigravity integration with a live local server and the real agy CLI. Verify messages traveling between the web interface and terminal, mirrored replies, permission requests, interruption, session resumption, and process cleanup.
Test Omnigent’s native Pi integration using the real terminal interface and a local server. Verify messages sent through the web or API, recorded replies, interruption, session resumption, authentication, and model settings to investigate integration problems.
Test Omnigent’s Cursor SDK integration against a live local server. Build test agents, run real conversations, and check authentication, model selection, and tool connections while investigating empty responses or bridge processes left after shutdown.
Test Omnigent’s GitHub Copilot SDK integration on a live local server. Build test agents, run real conversations, and inspect authentication, model selection, tool connections, policy enforcement, and leftover processes to investigate integration failures.
Test Omnigent’s Antigravity SDK integration against a live local server. Build test agents and run real conversations to check Gemini authentication, model selection, tool connections, and failures across the full execution path.
Configure how Dynamo routes requests to workers, then check model discovery and a chat response. Supports local and Kubernetes setups, including routing based on cached model data, with clear commands, results, and limitations.
Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after BB feature changes or when asked to verify or smoke-test BB. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected recipes and platform prerequisites.
The English summary is being prepared. Showing the original description.
Start or patch Dynamo router modes and run router endpoint smoke checks. Use for round-robin, KV-aware, least-loaded, or device-aware routing setup; use recipe-runner for recipe deployment and troubleshoot for failure diagnosis.
The English summary is being prepared. Showing the original description.
Use this skill when the user wants to invoke the read-only doca_caps CLI to ask what DOCA sees on this host — listing DOCA devices and PCIe addresses, listing representor devices, asking which DOCA libraries are available on the current OS, checking per-device per-library capabilities, scoping output to a specific PCIe address, or capturing a side-effect-free capability snapshot for debug or install smoke-test. Trigger even when the user does not explicitly mention "doca_caps" or "capabilities print tool" — typical implicit phrasings include "what does DOCA actually see on this box", "is my BlueField PF visible to DOCA", "is Flow available on my RHEL host", "enumerate VF representors for pf0", "doca_caps: command not found", or "empty output for RDMA, is the tool broken". Refuse and route elsewhere for DOCA installation (doca-setup owns it; never walk the steps), library-internal capability matrices (Flow pipe creation, RDMA verbs features), streaming telemetry / DTS, or modifying the shipped binary.
The English summary is being prepared. Showing the original description.