1.3K skills · sorted by relevance
Inspect automatic retries for failed Codex and Claude Code turns in bb after provider overloads or subscription usage windows. Check pending retry times and recorded decisions, send a scheduled retry immediately, or cancel it.
Add GitHub Copilot CLI as an optional research provider in Claude Octopus workflows using an existing Copilot subscription. The skill covers authentication, model selection, and skipping Copilot when unavailable; each prompt consumes a premium request.
Diagnose Claude Octopus installation and runtime problems across 15 categories, including provider authentication, configuration, hooks, and scheduling. Get a readable or JSON report, investigate specific areas, and review proposed fixes before approving changes.
Guides typed data integration in NeMo Relay by choosing codecs, converters between application values and JSON. Helps preserve middleware edits and caller-visible responses while distinguishing application data conversion from provider-specific LLM request and response handling.
[omh] Model and provider configuration changes: diagnose role-slot model configuration, guide provider connection, and apply changes only after diff approval. Use when the user says: model-setup, hermes model setup, set up my models, set up my model, configure my models, configure model provider, connect my model provider, set up model role slots.
The English summary is being prepared. Showing the original description.
Migrate Terraform provider resources and data sources from Plugin SDKv2 to the Plugin Framework: muxing both plugins in one provider (terraform-plugin-mux, tf5to6server), per-resource migration workflow, SDKv2-to-Framework schema mapping (ForceNew, ValidateFunc, DiffSuppressFunc, Default, Timeouts, blocks), null-vs-zero-value behavioral traps, and state-compatibility verification. Use when converting or translating SDKv2 resources to the Framework, setting up a muxed provider server, deciding whether a resource should be migrated at all, or debugging plan diffs and state errors that appeared after a migration.
The English summary is being prepared. Showing the original description.
Terraform provider acceptance test patterns using terraform-plugin-testing with the Plugin Framework. Covers test structure, TestCase/TestStep fields, ConfigStateChecks with custom statecheck.StateCheck implementations, plan checks, CompareValue for cross-step assertions, config helpers, import testing with ImportStateKind, sweepers, and scenario patterns (basic, update, disappears, validation, regression), and ephemeral resource testing with the echoprovider package. Use when writing, reviewing, or debugging provider acceptance tests, including questions about statecheck, plancheck, TestCheckFunc, CheckDestroy, ExpectError, import state verification, ephemeral resources, or how to structure test files.
The English summary is being prepared. Showing the original description.
Implement Terraform provider ephemeral resources with the Plugin Framework: the Open/Renew/Close lifecycle, ephemeral schema design, registration via EphemeralResources, renewal for expiring credentials, and how ephemeral values flow into write-only attributes and provider configuration. Use when adding an ephemeral resource, exposing secrets/tokens/certificates that must never persist in state or plan, deciding between an ephemeral resource and a data source, or wiring short-lived credentials from one provider into another.
The English summary is being prepared. Showing the original description.
Fix Riverpod "Cannot use Ref or modify other providers inside life-cycles/selectors" crash in @riverpod provider bodies. Use when: (1) Crash during provider disposal with this exact error message, (2) Using keepAlive() with timer-based disposal, (3) Async callbacks (.then, .catchError) try to use ref.read() or ref.invalidateSelf(), (4) Error occurs after ref.onCancel/onResume/onDispose callbacks fire. Solution: wrap ref operations in try-catch or avoid using ref in async callbacks entirely.
The English summary is being prepared. Showing the original description.
Fix Flutter TabController crash when dynamically showing/hiding tabs. Use when: (1) TabController rebuild causes "SingleTickerProviderStateMixin but multiple tickers were created", (2) Tabs need to appear/disappear based on feature flags or async state, (3) TabController.length changes at runtime based on provider state. The fix is to use TickerProviderStateMixin instead of SingleTickerProviderStateMixin.
The English summary is being prepared. Showing the original description.
arkcli helper：为 Claude Code / Codex / OpenCode / OpenClaw / Hermes / ZCode 配置火山方舟 Plan 或 Platform Endpoint 的 model/provider，或给支持的 Agent（含 MCP-only Trae）配置 Harness 工具。真人 TTY 运行 `arkcli helper` 可选择模型和 Harness 能力；`helper mcp` 默认保持整组 Agent Plan MCP 行为，传 `--capability datapro|web-search|agent-memory` 只配单项，传 `--capability cua` 只给目标 Agent 安装云电脑 Skill；连 model/provider 一起配置用 `helper configure`，查状态用 `helper list`，移除用 `helper reset`。Agent Plan / Team 还支持专业数据集、豆包搜索、Agent 记忆、AI Native 应用开发底座、Agent 进化与 routing.v1 强制检索路由；上下文出现 ARKCLI ROUTING ENFORCEMENT / routing.v1，或用户要求在豆包搜索、DataPro、OpenViking、Supabase 之间强制分流时也使用本 Skill：调用这四类受管 Provider 前先提交 Route Plan，再调用唯一授权 Provider；原生 WebSearch/WebFetch/WebExtract 位于路由管理范围之外。Platform 只允许本人创建、Running、已验证为文本输出的 Endpoint，不配置 MCP、Supabase 或强制路由。豆包搜索配置成功后默认关闭目标客户端原生 WebSearch；传 `--keep-native-websearch` 可保留，并可用 `helper reset` 完整恢复 ArkCLI 配置。
The English summary is being prepared. Showing the original description.
Provider-neutral entry point for discovering, planning and synchronizing MCP configuration between user-selected providers and app classes. The user selects truth, targets and scope; no provider is an implicit hub.
The English summary is being prepared. Showing the original description.
依存パッケージ（Go modules / npm / Terraform provider / GitHub Actions / pre-commit 等）の アップグレードを、outdated 検出 → CHANGELOG・破壊的変更の確認 → 更新 → lint/test 検証 → コミットまで一連の手順で安全に適用する。「依存更新」「パッケージを上げて」「dependency update」 「go get -u」「npm update」「provider を上げる」等に言及されたときに使用する。
The English summary is being prepared. Showing the original description.
Brokered short-lived provider credentials client in matrx-frontend (`lib/api/broker/`). Use when browser code needs a provider realtime session, a direct provider call, an ephemeral token, or a provider API key in the browser or `NEXT_PUBLIC_*`. NOT for adding a new audience server-side (use aidream's token-broker).
The English summary is being prepared. Showing the original description.
Configure AIsa as a first-class model provider for OpenClaw, enabling production access to major Chinese AI models (Qwen, DeepSeek, Kimi K2.5, Doubao) through official partnerships with Alibaba Cloud, BytePlus, and Moonshot. Use this skill when the user wants to set up Chinese AI models, configure AIsa API access, compare pricing between AIsa and other providers (OpenRouter, Bailian), switch between Qwen/DeepSeek/Kimi models, or troubleshoot AIsa provider configuration in OpenClaw. Also use when the user mentions AISA_API_KEY, asks about Chinese LLM pricing, Kimi K2.5 setup, or needs help with Qwen Key Account setup.
The English summary is being prepared. Showing the original description.
Run and monitor OpenClaw release validation, including live provider checks and installation or update tests. Diagnose failing jobs, manage targeted retries, and summarize evidence for the release operator’s decision.
Create and update OpenClaw end-to-end tests in Docker, checking complete workflows. Use fake servers to verify requests and real providers to check service behavior, including image understanding and the final text users receive.
Guides implementation and maintenance of Claude applications using language-specific references and official SDKs, the libraries used to call the API. Covers tool integration, streaming responses, model migration, cost reviews, prompt audits, and evaluation workflows.
Add a new execution tool or provider to native Paperclip Runner. Define requirements, investigate its communication protocol, implement the integration, package it, and verify complete tasks in the intended environment, including cancellation, recovery, and cleanup.
Review a Homecore server operation plan before startup. Check authentication, restoration order, feature tests, speech provider configuration, and handling of pairing secrets. The skill reviews the plan without starting the server.
Browse and search OmniRoute's AI model catalog from the command line. Filter by provider or capability, check model aliases, validate compatible models before adding them, and maintain manually registered model details.
Review AI call logs by provider, model, time range, status, and cost. Aggregate token usage, export logs, configure budgets, and inspect response times and prompt cache statistics to understand usage and performance.
Check OmniRoute server health, component status, and live metrics from the command line. Filter alerts or watch a refreshing dashboard to see provider status and circuit breakers, which interrupt requests when failures occur.
Inspect OmniRoute connection restrictions, usage quotas, and retry delays from the command line. Reset stuck providers and adjust failure thresholds, cooldowns, and recovery timing to manage how connections respond to errors.