179 skills · sorted by relevance
Apply Carapace styling to existing OpenClaw interfaces through shared CSS, themes, and semantic tokens—named values for visual roles. Reuse existing components and check interaction states, accessibility, and browser screenshots for consistent presentation.
Guide changes to RDD reviewer integrations through a shared Go contract, a common set of processing rules. Define adapter boundaries, validate result handling, and check that runtime migrations preserve existing review outcomes.
Map wireless networks before a security assessment. Choose compatible adapters, configure packet capture, identify access points and clients, and record channels, encryption, and management frame protection across 2.4, 5, and 6 GHz bands.
Validate FASTQ sequencing files, run local quality checks, and interpret reports to decide whether trimming is needed. Optionally remove adapters or low-quality read ends while preserving original reads and their quality reports.
Review domain code for classes that hold data while business logic lives elsewhere. Using domain-driven design patterns, diagnose problems and refactor objects to keep business rules, state changes, and validation together, with before-and-after diffs.
Design a modular monolith, a single application with clear business boundaries. Plan module structure, external service integration, failure handling, and future separation, then produce an HTML architecture document with SVG diagrams.
Build and check monsters for Three.js and web action games using shared rules for joints, attachment points, collision shapes, and combat states. Separate visual animation from damage decisions, and provide reproducible checks for attacks and detail-level changes.
Develop, adapt, review, test, and troubleshoot Nexent external memory provider plugins, including plugin.yaml manifests, searchable and ingestible provider protocols, error mapping, network-isolated unit tests, deployment configuration, and Mem0-based examples. Use when adding a new external memory vendor, changing an existing memory plugin, validating partner adapters, or diagnosing plugin discovery, authentication, retrieval, ingestion, or CI failures.
The English summary is being prepared. Showing the original description.
Build, migrate, review, and maintain third-party NVIDIA NeMo Fabric adapters against the public adapter contract. Use when creating adapter or target descriptors, mapping AgentConfig into an agent harness or custom-agent runtime, implementing start/invoke/stop, declaring schemas and capabilities, packaging discovery metadata, or assessing adapter conformance. Do not use for consumer applications that only call the NVIDIA NeMo Fabric SDK.
The English summary is being prepared. Showing the original description.
[omh] Lost track of agent sessions and worktrees: normalize Codex, Claude Code, Hermes, OpenCode, Cursor, MCP host, worktree, and wrapper session metadata into one drift-aware inventory. Use when the user says: harness-session-inventory, harness session inventory, session inventory, session adapter, session adapters, harness sessions, mcp inventory, mcp config inventory.
The English summary is being prepared. Showing the original description.
Remove sequencing adapters from FASTQ files using Cutadapt and Trimmomatic. Supports single-end and paired-end reads, Illumina TruSeq, Nextera, and custom adapter sequences. Use when FastQC shows adapter contamination or before alignment of short reads.
The English summary is being prepared. Showing the original description.
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
The English summary is being prepared. Showing the original description.
Configures and runs agents with different adapters including Claude, OpenAI, CrewAI, Lyzr, and GitHub Models. Supports local execution, remote git repos, and one-shot prompts. Use when the user wants to run an agent, switch LLM providers, configure adapter settings, or launch agents from git repositories.
The English summary is being prepared. Showing the original description.
Route Alchemy work to viem, direct Data APIs, Wallet APIs v5, or Solana Web3.js without reviving the archived SDK. Use when designing shared clients and adapters. Trigger with "Alchemy SDK pattern", "replace alchemy-sdk", or "choose an Alchemy client".
The English summary is being prepared. Showing the original description.
Design a production Alchemy architecture with capability-specific adapters, explicit trust boundaries, partial-state semantics, and reversible operations. Use when reviewing or creating an Alchemy-backed system. Trigger with "Alchemy architecture", "design an Alchemy dApp backend", or "review Alchemy boundaries".
The English summary is being prepared. Showing the original description.
Create narrow, version-pinned Adobe SDK and REST adapters with typed contracts, redaction, bounded polling, and compatibility evidence. Use when writing or upgrading integration code. Trigger with "Adobe SDK patterns", "wrap Adobe API", or "review Adobe client".
The English summary is being prepared. Showing the original description.
Build deterministic CI gates for Adobe adapters without giving fork jobs credentials or spending against live creative/document APIs. Use when testing integration changes. Trigger with "test Adobe in CI", "Adobe contract tests", or "gate Adobe deploy".
The English summary is being prepared. Showing the original description.
Build a local synthetic rehearsal for customer-owned Abridge workflow adapters and failure states. Use when developing integration code without access to patient data or a documented public Abridge sandbox. Trigger with "create an Abridge dev loop".
The English summary is being prepared. Showing the original description.
Build a repeatable local loop for Adobe adapters using synthetic contracts before any remote Runtime or product call. Use when implementing or debugging locally. Trigger with "develop Adobe integration locally", "mock Adobe API", or "aio app dev".
The English summary is being prepared. Showing the original description.
Define a production Adobe architecture spanning identity, service adapters, async workers, asset custody, I/O Events, App Builder, evidence, and recovery. Use when the task requires adobe integration reference architecture. Trigger with "design Adobe architecture", "Adobe reference architecture", or "standardize Adobe services".
The English summary is being prepared. Showing the original description.
Work on Grida account and billing client adapters, credit display, Console handoffs and native execution receipts. Excludes financial policy and provider operations.
The English summary is being prepared. Showing the original description.
Work on Grida's Gateway product consumer, scoped native AI tokens, installed gg provider and Desktop integration. Use for product execution adapters, not standalone Gateway service implementation or billing policy.
The English summary is being prepared. Showing the original description.
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
The English summary is being prepared. Showing the original description.
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
The English summary is being prepared. Showing the original description.