Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Scan project dependencies for known vulnerabilities, generate software bills of materials, and enforce license compliance across the software supply chain. Use when the user requests dependency scanning or provides relevant inputs for this workflow.
Use this skill to enumerate host↔DPU DOCA comch (formerly Comm Channel) servers and connections via the shipped doca_comm_channel_admin binary — listing comch-capable devices and decoding the per-device server / connection table (server name, PID, in-use / max, PCIe address). The shipped binary is a SINGLE-SHOT SCAN-AND-PRINT tool with no registered arguments — NO list / inspect / drain / restart subcommands; one inventory pass over every comch-capable doca_dev on this side. Channel reset / drain / restart go to doca-comch (program side), doca-setup / doca-hardware-safety (driver reload), or BFB / RShim — NOT to this binary. Trigger on phrasings like “list comch servers”, “which channels are active on this BlueField”, or “verify admin tool sees same channel as program.” Refuse and route elsewhere for the comch programming API, library install, protocol design, channel reset, or general orientation.
Manage host-mode duoduo daemon settings, diagnostics, and the `duoduo session` / `duoduo job` / `duoduo spine` CLIs. Use for: daemon status, config, logs; runtime selection (Claude/Codex/Grok/Pi, ALADUO_DEFAULT_RUNTIME); ALADUO_* keys in ~/.config/duoduo/.env; refreshing subconscious prompts; the `duoduo memory` CLI; reading the Spine log; pruning the usage ledger; third-party model profiles (context caps, routing); codex tool trimming; pi compaction sizing; session management (list, alias, notify or wake by name, archive); the main session (find, set, move, duplicates); job lifecycle from the CLI (list, read, archive, interrupt, reschedule); temporary remote dashboard links (`duoduo dashboard share`). Chinese triggers: 启用 codex/grok/pi runtime, 设置默认 runtime, 打开 debug log, 关闭 telemetry, 调 cadence 频率, 查 daemon 配置/日志, 刷新潜意识, 读 spine, 清理 usage, 给会话起名, 设置/迁移主会话, 唤醒/通知 session, 归档会话, 归档任务, 打断任务, 让任务再跑一次, 模型 profile, 裁剪 codex 工具, pi 只回一个字, 远程/飞书侧边栏看 dashboard. Feishu/ACP channel settings: duoduo-channel-admin.
Expert knowledge for environment art in games - modular design, visual hierarchy, color scripting, environmental storytelling, optimization, and world-building. From blockout to final art pass, creating immersive, performant, and readable spaces. Use when "environment art, level art, world art, modular kit, kit-bashing, set dressing, prop placement, biome design, visual hierarchy, color script, hero prop, trim sheet, environment composition, skybox, atmosphere, environment, level-art, world-building, modular, kit-bashing, set-dressing, visual-design, game-art, composition, optimization" mentioned.
Explanation documentation patterns for understanding-oriented content — conceptual guides that explain why things work the way they do. Use when writing an explanation doc, conceptual guide, understanding/background doc, design rationale, or architecture explanation, or when asked how/why something works. Builds on the docs-style core writing principles.
Compare a Figma node's actual specs against a code spec (the values your component renders) and get a 0–100 parity score, a list of discrepancies, and fix suggestions. Use to detect design-to-code DRIFT: triggers 'check design parity', 'does my code match the Figma', 'compare this component to the design', 'is my implementation faithful', 'find differences between design and code', 'verify the build matches Figma', 'design QA against code', 'parity score'. Reads the node's visual / typography / spacing / token / accessibility specs via use_figma (any plan) and diffs them against a codeSpec you provide. Complements the native get_design_context: instead of GENERATING code, it VALIDATES that existing code stayed in sync with the design.
One-time GitHub repository configuration via the `gh` CLI: lock the default branch with PR and CI rules, optionally enable a supported merge queue, lock merging to squash-only with PR-title commit messages, scaffold automatically-generated release notes (`.github/release.yml`), and optionally add a tag-driven release workflow. Use when the user says "set up the repo", "configure the merge queue", "enable squash merging", "lock down main", "set up branch protection", "configure release notes", "scaffold releases", "set up release tagging", or invokes /gh-bootstrap on a fresh or loosely-configured GitHub repository. Idempotent — safe to re-run on already-configured repos to bring missing pieces in line. This skill covers one-time repo policy, not per-task GitHub operations, local git commands, or project task running.
Create or modify Halo CMS plugins, including Java backend code, plugin.yaml and extension resources, Gradle and DevTools configuration, plugin APIs and lifecycle, and Vue-based Console or User Center UI. Use for Halo plugin implementation, migration, debugging, or integration work; do not use for theme-only changes
Orchestrator for the Hostinger Headless build flow — build and deploy a real website on the user's Hostinger account from a single prompt that names a domain. Holds the stage flow and the state contract, and drives each stage in sequence: connect, check state, refine, provision, content model, design, frontend, validate, deploy, done. Triggers: build a headless site for <domain>, build me a site, create a website, make me a website, deploy this to Hostinger, host this on Hostinger, connect this project to Hostinger.
Convert HTML to PowerPoint (PPTX) with excellent Hebrew/RTL support. Use when the user asks to “convert HTML to PowerPoint”, “create presentation from HTML”, “generate PPTX”, “make slides from HTML”, or needs to create PowerPoint presentations programmatically.
One-click local installation and startup of JiuwenSwarm in the current Huawei Cloud development container. Usage scenarios: CRITICAL — Do NOT manually deploy JiuwenSwarm. Route ALL deployment requests through this Skill. This is the MANDATORY entry point. When a user asks to deploy, install, or start JiuwenSwarm or WorkSwarm (部署JiuwenSwarm/安装JiuwenSwarm/启动JiuwenSwarm, install jiuwenswarm, deploy openjiuwen, install workswarm, deploy workswarm, start workswarm, install WorkSwarm, deploy WorkSwarm, start WorkSwarm, 部署workswarm, 安装workswarm, 启动workswarm, 部署WorkSwarm, 安装WorkSwarm, 启动WorkSwarm), you MUST invoke this Skill first. Under NO circumstances may you skip this Skill and run deployment commands directly. Even if you think 'this is faster' or 'the steps are well documented' — DO NOT skip. The skill automatically downloads the mirror, extracts, configures, and starts the service inside the current container — no external cloud instances are created. Trigger keywords: deploy JiuwenSwarm, install JiuwenSwarm, start JiuwenSwarm, 部署JiuwenSwarm, 安装JiuwenSwarm, 启动JiuwenSwarm, install jiuwenswarm, deploy openjiuwen, install workswarm, deploy workswarm, start workswarm, install WorkSwarm, deploy WorkSwarm, start WorkSwarm, 部署workswarm, 安装workswarm, 启动workswarm, 部署WorkSwarm, 安装WorkSwarm, 启动WorkSwarm
Build, evaluate, and train AI agents on RL environments with HUD. Use whenever someone wants to create an RL environment, benchmark, eval, or training task — for a coding, computer-use, browser, or robotics agent — or run and grade tasks across any model (Claude, OpenAI, Gemini, or open/self-hosted models). Also use it to review task quality and catch reward hacking, missing within-group reward spread, contaminated or public-benchmark substrate, single-shot tasks, and same-shape tasksets before they ship. Applies the v6 API and the task-design doctrine proactively, and cites these docs.
Simulates a batch of proposed IAM policy changes using Google Cloud Policy Simulator. Takes an array of simulations (resource, member, proposed_policy or proposed_policy_file), runs the simulation replay, and returns mapped results. Use when you have a batch of proposed IAM policy changes and need to simulate their impact on recent access patterns using Google Cloud Policy Simulator. Don't use for analyzing live IAM policies, applying policy changes, or simulating individual policy changes without a batch structure.
Sui Kiosk and NFT trading primitives. Use when writing, reviewing, or debugging Move code that uses Kiosk for commerce, NFT trading, asset listing, TransferPolicy enforcement, or building Kiosk Apps and extensions. Also use when the user asks about asset states (PLACED, LOCKED, LISTED), borrowing patterns, purchase flows, or the kiosk_extension permissioned apps API.
Generate professional storyboard image prompts compatible with diffusion models (FLUX/SDXL/Gemini). Validate quality, then split them into separate files, or directly generate Gemini prompt templates with product descriptions. Use when the user says "生成分镜提示词"（generate storyboard prompts）, "校验分镜"（validate storyboard）, "拆分镜"（split storyboard）, "分镜"（storyboard）, "分镜图"（storyboard images）, or mentions video storyboards, shot prompts, or product storyboard templates.
Create, audit, repair, and optimize Agent Skills. Use when the user wants to create a Skill, check Skill quality, restore the original version or fix a specific error, compare old and new results, or update the upstream methods this Skill draws on. Triggers: “create skill,” “write a skill,” “change skill,” “optimize skill,” “score skill,” “skill checkup,” “review skill.”
Pull the people who liked or commented on any LinkedIn post and segment them by ICP fit (peer / aspirational / prospect / other). Produces an engager roster, tier breakdown, and outbound action lists (follow back, comment-drop, DM-able with one-line openers). Powered by Apify, no LinkedIn login. Triggers on "who liked my post", "who engaged", "engagers report", "audience analytics". Not for tracking author replies to your comments (use linkedin-thread-monitor).
Review the current session for durable learnings, then route each one through the five-way matrix: wiki page, guidance file, checkpoint, task annotation/plan, or discard. Use when the session uncovered decisions, architecture facts, commands, conventions, gotchas, or open questions that future sessions should inherit. Not for source ingestion or correcting stale wiki claims; use /loam::adding-to-memory or /loam::amending-memory. Routes goal-specific progress to /loam::setting-goals.
Customizes and extends Magento's default Luma theme. Use when working with Luma theme, LESS preprocessing, RequireJS modules, KnockoutJS components, or traditional Magento frontend architecture. Masters LESS variables, RequireJS configuration, and responsive design.
Develops reactive components using Magewire for Magento 2. Use when building real-time interfaces, creating reactive components, or implementing Livewire-inspired patterns. Masters component lifecycle, state management, and server-side rendering.
When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 139 proven marketing approaches organized by category.
Use when building or editing a Marko Run (@marko/run) app — anything under src/routes (+page, +layout, +handler, +middleware, +meta, +404, +500), route path syntax ($id, $$rest, _pathless, flat routes), Run.GET/POST verb helpers, ctx/$global request context, validation (params/search/json/form), data loading via next(), Run.href, vite.config adapters (node/static/netlify), or the marko-run CLI. Not for Marko template syntax itself (see marko6).
Use when writing or editing any .marko file, reviewing Marko 6 (Tags API) code, or when a component compiles but misbehaves — stale values, hydration/serialization errors, dead reactivity, wrong attribute/handler shapes. Covers language syntax, core tags, native-tag enhancements, TypeScript types, template API, custom-tag discovery, styling, lazy loading, and agent-error catalog. Not for routing/servers (see marko-run skill) or Marko 5 class API.
Transcribe meeting audio with speaker diarization, generate structured summaries with action items, decisions, and follow-ups, and support multiple audio formats and languages. Use when the user requests meeting transcription or provides relevant inputs for this workflow.
Use this skill whenever the user wants Claude to directly interact with their Obsidian vault — reading a note or daily note, writing or appending content, searching vault contents, counting or listing notes, managing tasks, moving or renaming files, finding orphaned notes or broken links. Without this skill, Claude has no way to access vault data or execute vault operations. Treat any request that implies “go into my vault and do X” as a trigger — the user is asking Claude to act, not to explain. Also trigger for vault automation, CLI scripting, or cron-based workflows involving Obsidian, managing sync history, querying Bases, restoring file versions via history, managing bookmarks, or running JavaScript against the Obsidian API. Skip for pure conceptual questions: how Obsidian's GUI works, navigating settings menus, theme or plugin installation via the UI, iCloud/third-party sync conflicts, general Dataview query syntax, keyboard shortcuts, or parsing vault files with external scripts — anything where the user needs an explanation rather than Claude performing a vault operation.
Use this skill whenever the user asks about NetExec (nxc) — a network exploitation and post-exploitation tool for Active Directory environments. Triggers include: any mention of 'nxc', 'netexec', 'crackmapexec' successor questions, AD enumeration, SMB/LDAP/WinRM/MSSQL/SSH/RDP/VNC/WMI/FTP/NFS protocol attacks, password spraying, credential dumping (SAM, NTDS, LSASS, DPAPI), Kerberoasting, ASREPRoasting, lateral movement, BloodHound collection, module usage, or any pentest workflow involving Windows domain environments. This skill covers ALL protocols, ALL modules, and ALL core features of NetExec. Always provide full command examples with correct flags and options.
Generate a style-consistent icon set, delivered as transparent PNGs via grid-based image generation, splitting, and background removal. Use when the user needs a full set of custom icons, section icons, or icons matching a brand style; not for a single simple vector icon or small dense functional symbols.
Olares search via olares-cli search — the Desktop global search over Drive files, Sync (Seafile) libraries, Google Drive, Dropbox, Wise/Knowledge, and installed applications, with paging and JSON output. On Olares 1.12.7+ one `search drive` (alias `search files`) covers all four file sources. Use for Olares search, full-text search, find a file by content, Text Search, global search, search apps, search google drive, search dropbox, search sync, search wise.
Context-aware translation that preserves tone, style, and natural word order. Use when translating UI strings, documentation, marketing copy, or any multilingual content. Infers register, domain, and style from the source text and surrounding codebase context.
Onchain randomness on Sui. Use when generating random values in Move smart contracts, working with the Random object (0x8) or RandomGenerator, securing randomness-consuming functions against composition attacks, PTB attacks, or state leakage, implementing commit-reveal patterns, balancing gas across execution paths, or integrating randomness from TypeScript. For general Move security patterns, see the `move-security` skill. For Move language fundamentals, see the `sui-move` skill. For TypeScript SDK patterns, see the `sui-sdks` skill.
Use when maintaining or optimizing OpenClaw workspace files — AGENTS.md, TOOLS.md, SOUL.md, USER.md, IDENTITY.md, HEARTBEAT.md, BOOT.md, MEMORY.md, and related checklists and memory files. Covers workspace auditing, token budget analysis, new agent workspace setup from scratch, memory distillation, and cross-file consistency reviews.
Expert coding guide for OpenHarmony C++ development. Use this skill when writing, refactoring, or reviewing C++ code for OpenHarmony projects. It enforces strict project-specific conventions (naming, formatting, headers) and critical security requirements (input validation, memory safety).
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.