Skills
97,905 packaged capabilities and playbooks for agents. Install any of them with one command.
All
TypeScript coding conventions for writing, reviewing, and refactoring typed code. Use when working on `.ts`, `.tsx`, or files that embed TypeScript such as Vue, Astro, or Svelte components. Also use for TypeScript snippets, typed refactors, and review comments about code organization or function structure.
Use whenever a running TYPO3 instance is wanted, started or reached: ddev commands, backend URLs, DDEV setup, multi-version testing — and when DDEV cannot run, so the instance must be provisioned directly. Triggers on: I need an instance, install TYPO3 locally, ddev URLs, docker environment, CI or container without DDEV.
Codex UI anti-slop workflow for frontend design and implementation. Use automatically when Codex builds, reviews, fixes, styles, redesigns, or improves user interfaces: landing pages, dashboards, app UI, admin panels, editors, checkout and pricing flows, docs, mobile UI, visual QA, screenshots, DESIGN.md design systems, or when the user says ai-slop, anti-slop, visual contract, make it look better, less generic, or invokes $ui-anti-slop-codex / ui-anti-slop-codex.
Design and refine coherent, content-led UI within an authorized prototype or implementation scope. Use as a supporting skill when creating a screen, choosing hierarchy or visual direction, or correcting generic AI-generated UI; skip routine UI changes already determined by established components.
Plans and generates UIGraph artifacts, syncs them to the local viewer, UIGraph Cloud, or a self-hosted gateway, starts, opens, stops, kills, restarts, or checks the local UIGraph viewer, and launches Lens reviews. Use for any request about UIGraph, including `.uigraph.yaml` and `.uigraph/` artifacts, the local viewer, `uigraph` or `npx uigraph` commands, syncing, and Lens.
UiPath Integration Service connector authoring (REST+JSON) on disk via `uip is connectors builder`. Triggers on `element.json`, `element-metadata.json`, `standard-resources/*.json`, a `periodic-uipath-*`/`periodic-design-*` connector repo, or any request to build/edit an IS connector: init the connector shell, configure auth (19 types via `auth set`, incl. jwtOauth claims, FPS, none), add activities with fields/params/methods/hooks, wire polling/webhook triggers, add auth-system resources, inspect, validate, and surgically read/write files via state. Import + publish live on the parent `uip is connectors` (need `uip login`). NOT for operating a published connector — connections, ping, run an activity→uipath-platform; NOT for `.flow` connector nodes→uipath-maestro-flow.
Uniwind — Tailwind CSS v4 styling for React Native. Use when adding, building, or debugging components in a React Native project that uses Uniwind classNames. Covers setup, Metro config, global.css, theming, className props, accent-* color props, platform/data/state/responsive variants, CSS variables, custom utilities, withUniwind for third-party components, cn/tailwind-merge, tailwind-variants, safe area utilities, gradients, fonts, React Navigation, UI kits, diagnostics, troubleshooting, and Uniwind Pro features. Does not cover NativeWind migration.
Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".
Builds a client × services cross-sell map for a B2B service company: which active client uses which services, where the gaps are, and which gaps are realistic expansion opportunities — with a prioritized action list. Use when the user says: "карта апсейлів", "upsell map", "cross-sell map", "кому що допродати", "де ростити акаунти", "expansion opportunities", or pastes a client list + service list and asks where the growth is. NOT for account health scoring (use client-health-check) and NOT for new-business offers (use offer tools).
Evaluate UI designs and implementations against established UX principles. Use this skill when the user wants a UX heuristic evaluation, usability review, UX critique, or analysis of a design against best practices. Triggers include: 'evaluate the UX', 'heuristic evaluation', 'UX review', 'usability critique', 'does this follow UX best practices', 'what UX issues do you see', 'critique this design', 'review this flow', or when the user provides a screenshot or HTML file and asks for UX feedback. Also trigger when users reference specific heuristics like 'visibility of system status', 'Fitts's Law', 'Hick's Law', 'cognitive load', or any of Nielsen's heuristics or Laws of UX by name.
Use the Valyu CLI when the user needs a knowledge-work answer grounded in real sources: private equity / M&A due diligence, financial analysis, SEC filings, healthcare and life sciences research, clinical trials, patent landscapes, academic literature, and GTM / ICP account research. The `valyu` command wraps search, AI answers, URL content extraction, and async deep research with deliverables (CSV / XLSX / PPTX / DOCX / PDF). Prefer this over generic web search for anything that needs citations, structured output, or deliverables. Always load this skill before running `valyu` commands.
Covers integrating Vercel Blob object storage (@vercel/blob) into Next.js and other Vercel apps: server-side uploads with put, client-side uploads via presigned client upload tokens, listing, downloading and deleting blobs, streaming and multipart uploads for large files, public versus private access, content-type and caching settings, and automatic CDN delivery. Use when adding file, image, PDF or video uploads to a Next.js app, handling user-generated content such as avatars and attachments, building file management features, migrating from Cloudflare R2 to Vercel Blob, or hitting errors like BLOB_READ_WRITE_TOKEN is not defined, file size limit exceeded, client upload token failures, filename collisions, upload timeouts, or blobs that fail to delete.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Use before declaring a task complete, after code/content/config changes, or when the user asks to verify, QA, smoke test, validate, or inspect whether something really works. Inspect the changed scope, run the right checks, verify runtime behavior when needed, and report evidence without inventing results.
Use when someone wants to design their own Video.js player skin: a custom look, layout, or set of controls for a Video.js 10 video or audio player, including one that replicates another player's look, such as YouTube's or Netflix's, built and previewed in a standalone workbench and published to share. Sets up the project with `npx @videojs/cli skin create`, then guides the design, motion, and accessibility work on the skin source. Also use in any project with a `skin.json` from `videojs skin create`.
Use when working with Vunor, the Vue 3 + UnoCSS design system and component library. Covers presetVunor, vunorShortcuts/defineShortcuts/mergeVunorShortcuts, VunorVueResolver, Nuxt module, Vu-prefixed components, semantic UnoCSS classes (scope-*, layer-*, surface-*, current-*, c8-*, i8-*, card, fingertip, spacing, typography), public composition primitives (btn, menu-item, popup-card, i8-bare, disabled-soft), palette/theme tuning, and shortcut override patterns. Imports: vunor, vunor/theme, vunor/utils, vunor/vite, vunor/nuxt.
Walrus publisher and aggregator REST API for storing and reading blobs over HTTP. Use when the user needs to store or read Walrus blobs using HTTP PUT/GET requests, integrate Walrus from any programming language, configure storage options (epochs, deletable, permanent, send_object_to), or parse store/read API responses. Also use when troubleshooting HTTP API errors or CDN caching issues after upload. For quilt HTTP endpoints, see the `walrus-quilts` skill. For CLI usage, see `walrus-cli`.
High-level overview of Walrus: what it is, how it works, and which tool to use. Use when the user is new to Walrus, asks "what is Walrus", "how does Walrus work", "what is a blob", or needs to choose between CLI, HTTP API, TypeScript SDK, and Move integration. Also use when explaining Walrus architecture, comparing Walrus to AWS S3 or IPFS, explaining the publisher/aggregator/upload relay distinction, or clarifying blob ID vs Sui object ID. This is the entry-point skill for Walrus newcomers.
Walrus TypeScript SDK (@mysten/walrus) for storing and reading blobs programmatically. Use when writing TypeScript/JavaScript code that interacts with Walrus for blob storage, reading, or lifecycle management: the WalrusFile API (getFiles, writeFiles), the raw readBlob/writeBlob API, the writeFilesFlow/writeBlobFlow step-by-step flows for browser wallets and crash-recoverable uploads, upload relays and tips, WASM loading in Vite or Next.js, and verifying a blob before depending on it. For CLI usage, see the `walrus-cli` skill. For HTTP API, see the `walrus-http-api` skill.
A Vue SFC best-practices guide for mini-program projects using weapp-vite, covering script setup, template-only SFCs, JSON macros, `definePageMeta`/layout, `defineModel`, `usingComponents`, built-in i18n Behavior, JSX/TSX script blocks, template directive compatibility, multi-platform SFCs, `.weapp-vite` type support files, and the managed `prepare` workflow.
Web front-end reverse engineering skill: for reversing web front-end JS/WASM logic, deobfuscation/unpacking, bundle analysis (Webpack/Vite/Rollup), JS-VM/custom VM bytecode recovery, WebCrypto/custom encryption and API signing algorithm reproduction, source map rebuilding, browser anti-debugging bypass, protocol/request replay, and CTF Web challenges. Always trigger when the user mentions "reverse a website / reproduce signing or encryption parameters / recover JS logic / packet capture replay / VM / WASM / obfuscator / JSFuck / eval-pack". This skill is not for front-end development, performance optimization, general encryption teaching, penetration scanning, or Android reverse engineering.
Web2 recon pipeline — subdomain enumeration (subfinder, Chaos API, assetfinder), live host discovery (dnsx, httpx), URL crawling (katana, waybackurls, gau), directory fuzzing (ffuf), JS analysis (LinkFinder, SecretFinder), continuous monitoring (new subdomain alerts, JS change detection, GitHub commit watch). Use when starting recon on any web2 target or when asked about asset discovery, subdomain enum, or attack surface mapping.
Test local web applications using Playwright with Python. Verify frontend functionality, debug UI behavior, capture screenshots, and view browser console logs. Supports static HTML files, dynamic webapps with running servers, and automated test generation.
Use when the complete Spring Boot 3 request path is reactive: WebFlux controllers, Reactor pipelines, R2DBC persistence, streaming, backpressure, or cancellation. For defining and registering declarative outbound API interfaces, use http-interface-clients
Generate structured Markdown documents and local image assets directly from WeChat official account article links. Suited to scenarios that need one-click fetching, conversion, image downloading and Markdown cleanup; can be moved to other projects independently.
Best practices for designing UI widgets in xmcp. Use when creating interactive widgets for GPT Apps or MCP Apps, choosing between React components and template literals, designing widget layouts, handling state and data fetching, or troubleshooting widget rendering issues.
Respond to questions through Wittgenstein's philosophy of language, logical analysis and wisdom of silence. Use when the user explicitly asks for this figure's perspective, mentions "wittgenstein-perspective", or wants to apply his core methods to analyze a problem; do not trigger automatically for general questions.
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.