194 skills · sorted by relevance
Guides development of iii functions, event triggers, and workers, the processes that execute functions. Helps choose result-returning calls, one-way calls, or queued work, inspect live registrations, and connect existing HTTP services.
Build charts with TradingView's lightweight-charts, including candlesticks, lines, live updates, scales, and annotations. Guidance checks installed types and v5 APIs to support chart integration, framework lifecycle handling, and troubleshooting of common data and display issues.
Turn OpenClaw conversations, actions, and tool history into structured long-term memory. Agents can retrieve past facts, decisions, and summaries when needed, helping them continue work across sessions and recover context after it is shortened.
Create animated GIFs for Slack messages and custom emoji from a description. Combine motion such as bouncing, spinning, and shaking, then check dimensions and file size and adjust frames or colors to fit the intended use.
Build the user interface for a holaOS app whose data resources are already connected through the SDK. Choose a feed, table, kanban board, form, or calendar layout using shared components and workspace styling.
Build holaOS apps for connecting external services or managing work through a dashboard. The skill uses shared SDK building blocks for stored records, actions, and synchronization, with the dashboard and agent tools working on the same data.
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.
Builds and updates OpenClaw interfaces using shared styling rules, existing components, and semantic tokens—named values for visual roles. Helps keep themes, controls, and interaction states consistent while preserving application behavior unless changes are requested.
Generates cryptographic test vectors, inputs with expected outcomes, by deliberately changing implementation code and finding changes existing tests miss. Verifies new vectors across independent implementations and compares detection rates before and after adding them.
Investigate TOCTOU flaws: race conditions where a checked property changes before an action uses it. The skill covers filesystem, kernel, web, and container testing, helping identify vulnerable sequences, reproduce timing issues, and document observed impact.
Guides security testing of Android and iOS apps through file inspection and observation while the app runs. Covers network traffic, stored secrets, external app interfaces, authentication, and backend APIs, with tool examples and a testing checklist.
Build OpenBot administration and settings screens with shared layout components. Provides consistent page widths, row structures, control sizes, and dialog layouts, including patterns for switches, editable summaries, and read-only values.
Assess enterprise sign-in environments that use Okta, from identifying tenants to reviewing authentication factors and connected applications. The skill provides security testing workflows, configuration checks, and guidance on validating findings within an authorized assessment.
Investigate subdomain takeover risks caused by DNS records pointing to abandoned services. The skill covers discovery, provider error checks, resource claimability, and evidence collection, then examines potential effects on login flows, shared cookies, and trusted content.
Review multi-factor authentication flows for skipped checks, reused one-time codes, weak backup paths, and verification races. It focuses on proving access to protected resources rather than relying on interface behavior or response codes alone.
Assess account takeover risks across password resets, email changes, JWT tokens, SSO, and recovery flows. The skill connects individual weaknesses into testable scenarios and requires proof that an attacker session can gain access to a separate test account.
Examine password reset and account recovery flows for account disclosure, exposed or reusable reset tokens, and missing request limits. Compare responses and verify token behavior to document specific authentication weaknesses.
Compare project options by valuing costs and benefits over time. Report net present value, the value remaining after discounted costs, separately for society and the sponsor, alongside funding needs and tests of how assumptions affect results.
Build React interfaces with coss components using documented imports, properties, and composition patterns. It helps select components, implement forms and overlays, preserve accessibility, and address migration mistakes when moving from shadcn/Radix to coss/Base UI.
Find reusable interface examples built with coss UI components. Match forms, dialogs, calendars, and other interface needs to indexed patterns, retrieve their source code through JSON links, and adapt the code for your project.
Convert Python browser-use scripts into TypeScript workflows using Stagehand v3 on Browserbase. Separate predictable steps from actions that need AI, and provide runnable project setup plus a migration summary identifying features that require human review.
Raw verbs inside DOCA Core (doca-verbs): direct control of QP, CQ, PD, SRQ and address-handle objects through doca_verbs_context, doca_verbs_qp_create / doca_verbs_qp_modify and doca_verbs_cq_create, porting libibverbs code into DOCA Core, or a QP attribute, opcode or WR flag the doca-rdma task API does not expose. Trigger on "raw QP attribute the task API does not expose", "porting libibverbs code", "IO_FAILED on WR submit", "QP state transition rejected", or "attach a congestion-control group", even without naming doca-verbs. Its first job is to route MOST users back up to doca-rdma, doca-eth or doca-rmax. Covers CC-group and Ethernet SQ/RQ primitives, capability queries via doca_verbs_query_device, and DOCA_ERROR_* from doca_verbs_* calls. Refuse and route elsewhere for ordinary doca-rdma / doca-eth / doca-rmax workloads, DOCA install, Core internals, and general libibverbs theory.
The English summary is being prepared. Showing the original description.
Use this skill whenever the user is doing hands-on DOCA programming on a BlueField DPU or ConnectX NIC and needs the foundation primitives every per-library context rests on — walking the doca_ctx lifecycle, discovering doca_dev / doca_devinfo and gating on doca_*_cap_* before trusting a feature, wiring doca_mmap / doca_buf_inventory / doca_buf for zero-copy I/O across libraries, driving doca_pe for completions, or DOCA Log's two-tier (--sdk-log-level vs app-side) model. Trigger even when the user does not say "DOCA Common" — typical implicit phrasings include "my tasks submit but nothing completes", "DOCA_ERROR_BAD_STATE from doca_ctx_start", "--sdk-log-level does nothing for my DOCA_LOG_DBG lines", "share a buf between doca_dma and doca_rdma", or "crashes far from the offending line". Refuse and route elsewhere for per-library questions in isolation (load doca-flow / doca-rdma / doca-eth alongside), installing DOCA (doca-setup), or doc lookup (doca-public-knowledge-map).
The English summary is being prepared. Showing the original description.
Use this skill when the user is doing hands-on DOCA Device Emulation on a BlueField DPU — exposing a custom emulated PCIe device the host sees as a real peripheral while DPU-side code runs the backend, picking the sub-library (PCI Generic, virtio-net, virtio-fs), wiring the per-sub-library Core context plus doorbell / DMA primitives, querying `doca_devemu_*_cap_*`, or debugging DOCA_ERROR_* from a `doca_devemu_*` call. Trigger even when the user does not say "devemu" — typical implicit phrasings include "expose a custom PCIe device from BlueField to the host", "host should see a virtio NIC backed by my DPU code", "lspci does not show my emulated device", "device enumerated but no driver binds", "DPU sees nothing when host kicks the queue", or "virtio feature negotiation failed at bind". Refuse and route elsewhere for the packaged DOCA SNAP / Virtio-net Services, host-side virtio kernel drivers, backend body design, or standard BlueField NIC behavior — those belong to other skills.
The English summary is being prepared. Showing the original description.