Skills.
Give your AI a better way to work.
A skill is a set of written instructions that teaches an AI how to do one job the way it should be done: review a pull request, plan a migration, write the release notes.
Install one here and it travels with your account into Claude, Claude Code, Cursor and every other client you sign in with.
Category: Dev tools
16,976 results · page 496 of 566
- View details
m06-error-handlingSkillDev tools
CRITICAL: Use for error handling. Triggers: Result, Option, Error, ?, unwrap, expect, panic, anyhow, thiserror, when to panic vs return Result, custom error, error propagation, 错误处理, Result 用法, 什么时候用 panic
Ready to connect
- View details
m07-concurrencySkillDev tools
CRITICAL: Use for concurrency/async. Triggers: E0277 Send Sync, cannot be sent between threads, thread, spawn, channel, mpsc, Mutex, RwLock, Atomic, async, await, Future, tokio, deadlock, race condition, 并发, 线程, 异步, 死锁
Ready to connect
- View details
m10-performanceSkillDev tools
CRITICAL: Use for performance optimization. Triggers: performance, optimization, benchmark, profiling, flamegraph, criterion, slow, fast, allocation, cache, SIMD, make it faster, 性能优化, 基准测试
Ready to connect
- View details
m11-ecosystemSkillDev tools
Use when integrating crates or ecosystem questions. Keywords: E0425, E0433, E0603, crate, cargo, dependency, feature flag, workspace, which crate to use, using external C libraries, creating Python extensions, PyO3, wasm, WebAssembly, bindgen, cbindgen, napi-rs, cannot find, private, crate recommend
Ready to connect
- View details
m15-anti-patternSkillDev tools
Use when reviewing code for anti-patterns. Keywords: anti-pattern, common mistake, pitfall, code smell, bad practice, code review, is this an anti-pattern, better way to do this, common mistake to avoid, why is this bad, idiomatic way, beginner mistake, fighting borrow checker, clone everywhere, unw
Ready to connect
- View details
Maple CSS EngineSkillDev tools
A variable-first, stack-agnostic runtime CSS engine for building responsive interfaces.
Ready to connect
- View details
menu-debugSkillDev tools
This skill should be used when the user asks about "Menu宽度为0", "Menu宽度问题", "Menu显示异常", "Menu子窗口问题", "Menu layout异常", "recreate subwindow", "快速打开Menu问题", "Menu闪退", "Menu位置错误", "子窗口recreate", "Menu崩溃", "Menu打印recreate", "点击无响应", "点击菜单关闭", "菜单位置左上角", "菜单方向不对", "菜单避让坑", "宽度高度为0", or mentions any Menu co
Ready to connect
- View details
modern-breakerSkillDev tools
Competitive strategy analysis for Magic: The Gathering's Modern format. Used for Modern meta queries, deck mechanics analysis, matchup advantages/disadvantages and sideboard advice, format breakthrough analysis, and deck selection recommendations. Triggered when the user explicitly asks about Modern
Ready to connect
- View details
mtg-judge-zhSkillDev tools
Magic: The Gathering Chinese rules judge. Answers questions on rules interpretation, card interactions, format legality, and tournament policy (MTR/IPG). Trigger when the user asks anything involving the Magic: The Gathering Comprehensive Rules (CR), Magic Tournament Rules (MTR), or Infraction Proce
Ready to connect
- View details
oh-arkruntime-thread-safety-auditSkillDev tools
Use this skill when auditing, reviewing, or fixing thread-safety issues in ArkCompiler Runtime Core, especially ArkTS-Sta ETS stdlib and plugin code under static_core/plugins/ets. It covers static mutable state, singleton initialization, shared maps/caches/counters/timers, taskpool/EAWorker concurre
Ready to connect
- View details
oh-graphic-gitcode-pr-creatorSkillDev tools
Automate Gitcode Pull Request creation workflow for OpenHarmony graphic subsystem including code commit, issue creation, and PR submission with proper template formatting. Use when user needs to create a PR for the Gitcode platform, especially for OpenHarmony graphic projects that require specific P
Ready to connect
- View details
oh-interfaces-ipc-to-serviceSkillDev tools
Adds a passthrough channel to the graphic_2d repository of the OpenHarmony project. Invoked when the user wants to add an RSInterface interface to the graphic_2d repository and specifies that the interface is ToSerivce.
Ready to connect
- View details
oh-precommit-codecheckSkillDev tools
Run local code quality checks covering a subset of OpenHarmony gate CI (copyright, CodeArts C/C++) plus additional local checks (pylint/flake8, shellcheck/bashate, gn format). Use before committing to reduce gate failures. Triggers on: /oh-precommit-codecheck, "门禁检查", "门禁预检", "检查代码", "run codecheck"
Ready to connect
- View details
ohos-dev-arkruntime-interop-developmentSkillDev tools
Expert assistant for ArkTS-JS interoperability in ArkCompiler (ArkTS runtime). Trigger scenarios: modifying/debugging ArkCompiler interop layer code (static_core/plugins/ets/runtime/interop_js/), implementing cross-language calls between ArkTS and JS, handling value conversion between ETS and JS (js
Ready to connect
- View details
ohos-dev-distributed-cpp-callgraph-analysisSkillDev tools
Use when an OpenHarmony C++ change must be checked for call-chain completeness, especially for data propagation, IPC/proxy/stub paths, virtual overrides, callbacks, or dlopen/dlsym boundaries. Produces evidence tables and modification coverage matrices; the helper script only discovers candidate edg
Ready to connect
- View details
ohos-dev-distributed-mmi-uinput-virtual-deviceSkillDev tools
Use when testing OpenHarmony input subsystem features (mouse/keyboard/touchpad event flow, device binding, display group isolation) on a real device without physical peripherals. Covers /dev/uinput device creation, event injection, InputManager device discovery, and hot-plug simulation.
Ready to connect
- View details
ohos-dev-distributed-mmi-wms-dms-simulationSkillDev tools
Use when testing OpenHarmony input features that depend on window/display state without running real WMS/DMS. Builds requested simulation scenarios from display groups, users, main/extended/mirror displays, per-display focus windows, z-order window stacks, hot areas, dynamic focus switching, pointer
Ready to connect
- View details
ohos-dev-graphics-stability-code-reviewSkillDev tools
C/C++ stability code review framework covering 5 stability categories (exception handling, concurrency stability, resource management, boundary conditions, graphics stability) with 34 rules in total. Trigger scenarios: stability-focused full-repo scans, local pre-commit code inspection, stability au
Ready to connect
- View details
ohos-dev-graphics3d-combined-postprocessSkillDev tools
Implement Combined post-processing effects (tone mapping, color grading, vignette) in Graphics3D. MUST use when: (1) Adding effect to Combined post-process, (2) User mentions 'Combined post-process' or 'post-processing'. DOES NOT apply to multi-pass effects (bloom, depth-of-field).
Ready to connect
- View details
ohos-req-arch-decisionSkillDev tools
Use when selecting an OHOS solution direction in Phase 0.3, especially for 03-arch-decision-record.md, candidate options comparison, or when the main session needs structured ADR output with user-provided decision. Do NOT use for feasibility analysis (ohos-req-feasibility-analysis), feature baseline
Ready to connect
- View details
ohos-req-feature-baselineSkillDev tools
Use when preparing an OHOS Feature for Phase 0.4 review, especially for 04-feature.md, SIG review readiness, proposal splitting, feature scope, acceptance criteria, or delivery impact. Do NOT use for requirement intake (ohos-req-requirement-intake), feasibility analysis (ohos-req-feasibility-analysi
Ready to connect
- View details
ohos-req-feature-to-irSkillDev tools
Use when an OHOS Feature has completed the Phase 0 Review Ready Gate and an Initial Requirement baseline is needed before proposal creation or cross-repository requirement splitting. Activation keywords: "IR.md baseline", "AC reference inheritance", "rr_id", "extension dimension confirmation". Do NO
Ready to connect
- View details
ohos-req-requirement-intakeSkillDev tools
Use when importing an OHOS requirement into Phase 0.1, especially for 01-requirement.md, requirement intake, background, user value, scenarios, scope, FR/NFR, affected modules, or priority. Triggers: 需求导入, 01-requirement, 需求基线, RR单号. Do NOT use for feasibility analysis (ohos-req-feasibility-analysis
Ready to connect
- View details
ohos-req-review-gateSkillDev tools
Use when performing the Phase 0 Step 0.5 Review Ready Gate on a 04-feature.md, especially when the user says "evaluate gate", "review readiness", "feature ready?", "should we generate IR", or when the ohos-req-intake-orchestration main session needs a structured Ready / Conditional Ready / Not Ready
Ready to connect
- View details
ohos-test-arkruntime-interop-testingSkillDev tools
Guide for adding and maintaining ArkTS <-> JS/TS interoperability tests in ArkCompiler. 触发场景：在 plugins/ets/tests/interop_js/tests/ 目录下创建新的 ArkTS 与 JS/TS 互操作（Interop）测试用例、调试/维护已有 Interop 测试、编写 C++ 运行器（GTest runner）或声明文件（.d.ets）时。
Ready to connect
- View details
ohos-test-graphics3d-static-api-unit-testSkillDev tools
Use when generating unit tests for ETS/ArkTS static API classes in OpenHarmony graphic_3d module, when adding new test cases for MaterialETS, CameraETS, SceneETS or similar wrapper classes, or when setting up test environment for GTest-based ETS unit tests
Ready to connect
- View details
ohos-ut-test-coverage-report-generationSkillDev tools
Provides UT-based code coverage report generation for OpenHarmony C/C++, supporting full and incremental coverage analysis; requires a test device connected via hdc. Use when: (1) the user requests full code coverage for a subsystem/component/module/test suite/test case; if a report path is provided
Ready to connect
- View details
omcustom-feedbackSkillDev tools
Submit feedback about oh-my-customcode (supports anonymous submission)
Ready to connect
- View details
omcustom-improve-reportSkillDev tools
Read-only report of improvement suggestions from eval-core analysis engine
Ready to connect
- View details
omcustom:auto-improveSkillDev tools
Apply verified improvement suggestions from eval-core analysis to omcustom configuration
Ready to connect
What is a skill?
A skill is plain text, usually a SKILL.md file and the scripts it refers to, written for an AI rather than for a person. It carries the steps, the house rules and the examples a good answer needs, so you stop pasting the same briefing into every new chat.
54,082 of the 54,514 skills listed here can be served through ahel today, and they come from public repositories. Each one has its own page with the instructions themselves on it, so you can read what a skill will tell your AI to do before you install it.
Install one and every AI you use gets it
Installing a skill adds it to your gateway and turns it on in the same step. Claude Code surfaces it as a slash command; any client can read the full instructions with the skill_read tool.
Nothing is copied into a project folder. The instructions are served from your account, so the same skill is there in every AI you connect, and turning it off removes it from all of them at once.