Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Build web3 applications, scripts, CLIs, bots, mobile apps, and desktop apps that need blockchain data via the Blockscout PRO API — a single HTTP API spanning 100+ EVM chains. Invoke this skill whenever the user wants to read blockchain data over HTTP (transactions, blocks, addresses, tokens, NFTs, logs, contract context, internal txs, account abstraction, etc.) and is building software that calls an API directly. Trigger on direct mentions of `Blockscout PRO API`, `pro-api`, `proapi_`, `Blockscout API`, `block explorer API`, `api.blockscout.com`, or on broader phrasing like "build a web3 app", "index/query on-chain data", "wallet history", "NFT inventory", "transaction logs across chains", "how much does the Blockscout API cost", "chain IDs supported by Blockscout". Use this skill for direct HTTP integrations; the sibling `blockscout-analysis` skill covers the Blockscout MCP Server.
Automatically collect trending AI content, write official account articles, generate accompanying images, and publish them to the WeChat Official Account draft folder. Trigger when the user says “发布AI热点,” “写公众号文章,” “采集AI内容,” or “publish AI news.”
WeWrite self-learning module: learn writing preferences from the user's manual edits (the playbook flywheel), import sample articles to build a style library, and learn layout themes from WeChat Official Account articles. Trigger keywords: 学习我的修改, 我改了学习一下, 导入范文, 学习这篇文章, 查看范文库, 学习排版, 学排版. Should not be triggered by generic "learn" or "summarize this article" — WeChat Official Account/WeWrite context is required.
Use when the user asks to audit what's wrong with a project, "make it right", "看看项目出了什么问题", "为什么用户的需求还没上线", "为什么没提交App Store", "为什么没新build", or wants a holistic state-of-the-project check covering unmerged branches, stalled PRs, failed GitHub Actions, stale builds, plan drift (TODOS.md / ROADMAP), unreleased commits, and log errors. Runs read-only investigation, presents a grouped checklist, fixes only after explicit user confirmation. Aware of the Cathier iOS app workflow (Xcode + fastlane + auto-merge @claude PRs from in-app feedback).
Use when the user wants to set up automated daily promotion / marketing for their Claude Code skills — researching how top skills are promoted on marketplaces (ClawHub / openclaw / SkillsMP / agentskills.io), generating a per-skill marketing plan, auto-posting to X (Twitter) via xurl, and drafting community discussion posts (Reddit / HN / Discord). Triggers — "推广 skills", "营销 skills", "自动发推广", "每天自动推广", "skill marketing", "promote my skills", "/wjs-promoting-skills".
Provides battle-tested patterns, best practices, and code examples for building Phaser 3 games. Use when writing game code, implementing game mechanics, setting up scenes, handling physics, animations, input, or any Phaser-related development. Covers architecture, performance, algorithms, and common pitfalls.
Prepare, review, and package Y Combinator application answers and founder-video notes using the live form and verified founder facts. Use for a YC application, requested interview practice, or reapplication; not general fundraising or unrelated decks.
Help with abapGit workflows including repository setup, cloning, serialization, branching strategies, transport-vs-git workflows, CI/CD integration, and .abapgit.xml configuration. Use when users ask about abapGit, git for ABAP, ABAP version control, abapGit clone, abapGit pull, abapGit push, branching strategy for ABAP, abapGit configuration, serialization, deserialization, transport vs git, gCTS, abapGit CI/CD, or managing ABAP code in git repositories. Triggers include "set up abapGit", "clone a repo", "push ABAP to git", "abapGit branching", "abapGit configuration", ".abapgit.xml", "transport vs git", or "CI/CD for ABAP".
Implement QRSPI-planned OpenSpec changes with intelligent parallelization. Use when the user wants to apply a QRSPI change, implement tasks with parallelization, or says "apply this QRSPI change", "implement with parallelization", "run the parallel slices". This skill is specifically designed for changes created via accelint-qrspi that include "Parallelization Strategy" sections in tasks.md. It orchestrates parallel sub-agent execution for independent task slices using OpenSpec CLI workflows. Make sure to use this skill when the user mentions applying QRSPI changes, running parallel implementation, or working on changes with vertical slices.
Alibaba Cloud PDS (intelligent cloud drive/network drive) file operation skill. Supports file search, upload, download, rename, move, copy, folder creation, tags/notes, share links, document/audio-video analysis, batch download, image editing, reverse image search, and installation and mounting of the PDS mount app (mountapp, which mounts the cloud drive as a local disk). Use this skill when users want to operate on files or spaces in their PDS, network drive, or cloud drive (including only describing safe ways to handle operations such as renaming, moving, or copying, without actually performing them), or want to mount the cloud drive locally to access it like local files. Trigger even for simple requests such as “help me download from PDS,” “upload to the network drive,” “rename report.pdf,” “what files are in PDS,” “batch-download the files,” “analyze this document,” “mount the cloud drive locally,” or “install the mount app.” Triggers: “PDS,” “network drive,” “cloud drive,” “personal space,” “enterprise space,” “team space,” “drive_id,” “domain_id,” “upload file to PDS,” “download from PDS,” “PDS rename,” “PDS move file,” “PDS copy file,” “PDS create folder,” “PDS document analysis,” “PDS video analysis,” “PDS image editing,” “PDS file search,” “PDS reverse image search,” “PDS batch download,” “bulk download,” “aliyun pds,” “PDS Drive,” “mount app,” “PDS mount app,” “enterprise cloud drive mount app,” “mountapp,” “mount cloud drive,” “mount the cloud drive locally,” “PDSDrive.” Do not trigger merely because PDS is mentioned in informational content: general product concepts, product comparisons, pricing, deployment methods, or documentation questions are outside this skill; neither are local file system operations or operations on other cloud drives. Use this skill for operations on the user's PDS files or spaces, and for installing/mounting the PDS mount app (mountapp) to access the cloud drive as a local disk. Do not trigger for generic PDS product concepts, comparisons, pricing, deployment, or documentation questions.
Use when data needs statistical analysis. Runs reproducible Python/R code for Table 1, diagnostic accuracy, agreement, regression, survival, propensity score, survey-weighted and repeated-measures models, with publication tables. Sample size is /calc-sample-size; pooling studies is /meta-analysis.
Use when the user asks to “create a Next.js route,” “add a page,” “set up layouts,” “implement loading states,” “add error boundaries,” “organize routes,” or “create dynamic routes,” or needs guidance on Next.js App Router file conventions and routing patterns.
Analyze Huawei Ascend NPU profiling data to discover hidden performance anomalies and produce a detailed model architecture report reverse-engineered from profiling. Trigger on Ascend profiling traces, NPU bottlenecks, device idle gaps, host-device issues, kernel_details.csv / trace_view.json / op_summary / communication.json. Also trigger on "profiling", "step time", "device bubble", "underfeed", "host bound", "device bound", "AICPU", "wait anchor", "kernel gap", "Ascend performance", "model architecture", "layer structure", "forward pass", "model structure". Runs anomaly discovery (bubble detection, wait-anchor, AICPU exposure) alongside model architecture analysis (layer classification, per-layer sub-structure, communication pipeline). Outputs a separate Markdown architecture report alongside anomaly analysis.
Use this skill when an agent needs to complete Bilibili login, account verification, or video upload via the installed `sau` CLI. Prefer `sau bilibili ...`; the program automatically prepares `biliup` and does not require the user to install it manually.
Read-only public market data for Bithumb: prices, ticker, order book, candles (minute/day/week/month), recent trades, market list, virtual asset warnings, notices, and fees. No API credentials required. Do NOT use for wallet/blockchain status or deposit-withdrawal availability — use bithumb-account. 빗썸 시세·호가·캔들·체결 내역·마켓 목록·유의 종목·경보제·공지사항·수수료 등 공개 시장 데이터를 조회합니다. 인증 불필요. 빗썸 시세·차트·호가·체결 내역·유의 종목·경보제 관련 요청에 사용하세요. 입출금 현황·블록 갱신시각·블록 동기화·입출금 가능 여부는 bithumb-account를 사용하세요.
Applies structured divergent-convergent thinking to generate many creative options, organize them into meaningful clusters, then systematically evaluate and narrow to the strongest choices. Balances creative exploration with disciplined decision-making. Use when exploring product ideas, solving open-ended problems, generating strategic alternatives, developing research questions, designing experiments, or when user mentions brainstorming, ideation, divergent thinking, generating options, or evaluating alternatives.
Bulletproof React architecture patterns for scalable, maintainable applications. Covers feature-based project structure, component patterns, state management boundaries, API layer design, error handling, security, and testing strategies. Use when structuring a React project, designing application architecture, organizing features, or when the user asks about React project structure or scalable patterns.
Use when the user wants to turn text content into a set of polished, shareable visual CARD IMAGES or narrated card VIDEOS — knowledge cards, quote cards, 小红书图文, carousel cards, poster cards — rendered as HTML/CSS and exported via Playwright at ratios like 1:1 / 3:4 / 9:16; optionally produces a narrated MP4 video from those cards via `voxflow card render` (per-card TTS + FFmpeg static-image clips with optional subtitle bar / intro+outro cards / BGM mix). Triggers: card / 卡片 / 知识卡 / 文字卡片 / 金句卡 / 图文卡片 / 卡片生成 / make cards / card video / 卡片视频. For article → Slice-themed card VIDEO use voxflow:slice; for short videos / AI clips use voxflow:video; for podcasts use voxflow:podcast.
Generate, refine, and validate Character Card V3 cards and lorebooks. Use when creating new characters from a concept, converting or upgrading existing cards to CCv3, improving weak character behavior consistency, or building lorebook entries that steer scenario outcomes while staying token-efficient.
Makes narrated cinematic films entirely from code, on any subject. One continuous camera glides over one designed world of photos, documents, cards, maps with routes and big numbers, with every stamp, highlight and number landing on the narrator's word, then sound effects, an optional score and burned-in captions. For documentaries and history, product launches, brand and founder stories, science and tech explainers, biographies and true crime. Covers the script, voiceover from any TTS split into timed lines, images (archives with their licences, your own photos, AI stills), a beat table, the scene, self-review stills and a memory-safe parallel render. Use for "make a cinematic video about", "documentary about", "explainer video", "launch film", "Vox-style video", "evidence board animation", or turning a story into a video for X, YouTube or TikTok.
Install, set up, configure, or troubleshoot CKEditor 5 — the rich text editor / WYSIWYG editor — in any JavaScript project, vanilla or with a framework (React, Vue, Angular, Next.js, …). Covers install method (npm, CDN, ZIP), wiring the editor component, editor type, configuring plugins / toolbar / menu bar, loading editor CSS, license keys, free and premium features, starting a free trial, and setup errors. NOT for authoring custom plugins, upgrading versions, or CKEditor 4.
Generate and optimize CLAUDE.md files for Claude Code projects. Capabilities: initialize project instructions, analyze codebase context, optimize existing CLAUDE.md, apply Anthropic best practices, reduce token usage, and improve effectiveness. Actions: initialize, create, optimize, and enhance CLAUDE.md files. Keywords: CLAUDE.md, project instructions, Claude Code setup, project context, codebase analysis, Anthropic best practices, token optimization, project configuration, AI instructions, coding guidelines, project rules, workspace setup. Use when initializing CLAUDE.md for new projects, optimizing existing project instructions, setting up Claude Code for a codebase, or improving AI coding guidelines.
Optimize a complete candidate context package by deduplicating, filtering, ordering, and allocating its token budget. Use when retrieved or assembled material is noisy or exceeds the useful context budget; use context-ranking for scoring chunks and context-compression for shrinking selected content.
Resolve which slide, page, and (optionally) selected element the user is currently viewing in the open-slide dev server. Consult this whenever the user references "this page", "this slide", "this element", "the slide I'm on", "the current page", or any deictic reference to slide content without naming it. Re-read `node_modules/.open-slide/current.json` at the start of every such turn — the user navigates between turns, so a value you read earlier in the conversation is almost certainly stale.
Extracts key specifications from component datasheet PDFs for maker projects. Use when user shares a datasheet PDF URL, asks about component specs, needs pin assignments, I2C addresses, timing requirements, or register maps. Downloads and parses PDF to extract essentials. Complements datasheet-parser for quick lookups.
Domain-driven design complete workflow — event-storming-driven 6-step domain modeling process, aggregate design 5-principles + 6-rules, bounded context identification, entity/value object design patterns, domain event catalog, and code mapping. Use when user asks about domain modeling, 领域建模, aggregate design, 聚合设计, bounded context, 限界上下文, or needs to design DDD domain model.
Systematic evidence-based debugging using runtime logs. Generates hypotheses, instruments code with NDJSON logs, guides reproduction, analyzes log evidence, and iterates until root cause is proven with cited log lines. Use when the user reports a bug, unexpected behavior, or asks to debug an issue.
Svelte 5 adapter for the json-render devtools inspector. Use whenever the user wants to add, configure, or troubleshoot @json-render/devtools-svelte in a Svelte json-render app, including spec inspection, state editing, action and stream timelines, catalog browsing, or DOM picking.
Diagnoses bias, anomalies, and strange results on a PostHog experiment. Covers 0-exposure experiments, sample ratio mismatch, identity fragmentation, multi-variant exposure, uneven-split exclusion bias, significance traps (peeking, A/A, Bayesian vs Frequentist), PostHog-vs-SQL discrepancies, surprises after mid-run edits, and qualitative follow-up via a variant-split survey. TRIGGER when: user asks 'is my experiment biased?' or 'why 0 exposures?', references the bias banner, says a variant looks strange / wrong / off, sees significance flipping or A/A significance, finds PostHog numbers disagreeing with their SQL, reports surprises after mid-run edits, or wants qualitative feedback or a survey for an experiment. DO NOT TRIGGER when: creating an experiment (use creating-experiments), only configuring rollout (use configuring-experiment-rollout) or metrics (use configuring-experiment-analytics), or only asking lifecycle questions (use managing-experiment-lifecycle).
For Codex, Claude Code, WorkBuddy and other Agent Skills clients, turn a one-line idea, story outline, novel, copy, script, storyboard or existing material into understandable, connectable, publishable AI short dramas and AI short films. Suitable for landscape or portrait content on Douyin, Hongguo Short Drama, WeChat Channels, Kuaishou, Bilibili, YouTube and more; supports live action, standalone short films, anthology series, serial dramas, pets, anthropomorphic fantasy, animation/anime-style dramas, UGC and branded storylines. Used for story diagnosis, screenwriting, storyboarding, character/recurring prop consistency, model routing for Wan 3, Seedance 2.5/2.0/Fast, MiniMax H3 and others, 15–30 second long takes, native dialogue, reference audio, dubbing, paid budgets, continuity editing, physical quality checks and cold-audience acceptance, especially to avoid fragmented hard-cutting, random jump cuts, static talking-head dialogue, identity/costume/prop drift, text distortion, wrong motion direction, clipping, flat observational shots, lip-sync/voice mismatch, music restarts and incomprehensible plots.
Use when the current working directory is inside a DWE project — a Docker-based developer environment manager. Detect one by walking up from cwd to a directory containing `workspace.yml`; that directory is the project root. A populated project also has a `workspace/` subdirectory (services, pipelines), but its absence does not disqualify it (e.g. a freshly-initialized project). Applies anywhere beneath the root, including service folders like `workspace/services/<name>/` and their source subtrees. The skill is both a navigator — which `dwe` commands to use for inspection vs mutation, and how to look up everything else via the built-in `dwe docs` subsystem — and an authoring guide for extending a project (scaffolding from git repos, adding services and tools, authoring commands and daemons, wiring render packs and vars, customizing deploy/lifecycle pipelines, integration tests). Activates on the word "dwe", on editing any file under `workspace/`, or when working inside a service directory.
Analyzes moral dimensions and value conflicts through ethical frameworks using deontology, consequentialism, virtue ethics, and applied ethics methodologies. Provides insights on moral obligations, rights, justice, and ethical decision-making. Use when: Ethical dilemmas, policy decisions, technology ethics, professional conduct issues. Evaluates: Moral principles, stakeholder interests, consequences, rights, justice, virtues.
A step-by-step problem-solving loop (classify the ask, define done, gather evidence, decide, act surgically, verify by observation, report outcome-first). Use when the user says "/fable-method", "use the fable method", or "approach this like Fable", or proactively when starting any multi-step task that no task-specific skill covers. Subcommands - plan (stop after the plan), audit (grade finished work against the loop), report (rewrite an answer outcome-first).
Execute any of 240+ specialized prompt patterns natively across Extraction, Summarization, Analysis, Creation, Improvement, Security, Rating. Common: extract_wisdom, create_threat_model, analyze_claims, improve_writing, review_code, mermaid, youtube_summary. CLI used only for YouTube transcript (-y) and URL fallback (-u). Two workflows: ExecutePattern, UpdatePatterns. USE WHEN fabric, fabric pattern, run fabric, update patterns, threat model, analyze claims, improve writing, review code, mermaid, STRIDE, sigma rules. NOT FOR multi-agent investigation (Research) or content-adaptive extraction (ExtractWisdom).
A terminology layer for the web and mobile H5: turns imprecise interface descriptions into a precise request that can be sent directly to an Agent, and identifies the term the user described but could not name. Applies to every turn of the conversation, at any stage: whenever the user casually describes the appearance, interaction, state, motion, feel, or a problem with a web page or H5 ("changes color on hover", "clicking does nothing", "the black bar at the bottom covers the button", "the page still scrolls under the popup", "the keyboard covers the input", "truncate the long content", "looks a bit tacky", "too cramped", "when there’s no data", "the page jumps down after the image loads", "looks wrong when opened in WeChat", "this H5 looks strange on desktop"), use this Skill: complete the requested task as usual, then naturally mention the relevant term in the progress update or result, give a plain-language explanation, and note its most common pitfall. Includes 142 local terminology entries across five volumes (web · h5 · motion · mp · base), covering layout, interaction, state, components, forms, motion, visual feel, accessibility, performance, container platforms, mini programs, and frontend fundamentals. No network dependency. Use `scripts/term.mjs find` to search by the user's exact words—the search key is how users describe the issue, not what it is called, because not knowing the name is the problem to solve. Three strict rules: every term given must be tied to specific words in the user's current turn; if you cannot point to them, leave it out rather than forcing it. H5 pitfalls come in pairs: terms paired in the `pairs` entries must be mentioned together (sticky-to-bottom ↔ safe area, overlay ↔ scroll lock, input ↔ keyboard lift, image ↔ aspect-ratio placeholder); mentioning only one leaves a trap. Always deliver the task result before adding terminology, with at most 1–3 terms; do not teach when the user's wording is already precise. Also use for the reverse case, when the user does not understand something an Agent or colleague said ("they said to use optimistic updates and error rollback", "they said there’s a CLS issue here"): choose the concept most relevant to the next decision, explain what it means in this task and one boundary it is easy to confuse. Optionally produce `.finesse/lexicon.md`, a terminology alignment sheet for the project to prevent the same component from having three different names in requirements, code, and communication. Supports action commands (say · name · explain · check · align · list). Triggers: "say it more professionally", "how do I phrase this accurately", "turn this into a request I can send to an Agent", "what is this called", "the professional term", "terminology", "I don't understand what they mean", "H5", "mobile", "on a phone", "responsive", "safe area", "sticky-to-bottom", "popup", "skeleton screen", "empty state", "accessibility", "terminology alignment", "/term".
Create distinctive, production-grade frontend interfaces with high design quality. Use when building or refining web components, pages, or apps (HTML/CSS/JS/React) with bold aesthetics, purposeful layouts, motion, and accessibility. Avoid generic AI-looking output.
Implements the fixes a PR review asked for — maps each thread to the code it touches, edits that code, and drafts a reply per thread for approval before anything is posted. Starts from feedback that is already understood; producing the read-only digest is `pr-comments`.
A guide to good Chinese writing: improve Chinese writing and revise existing articles. Based on the writing insights of Paul Graham, Yu Guangzhong, and Wang Dingjun. Use when the user says “polish,” “rewrite,” or “make the text flow better”; asks to “improve the writing,” “write it better,” or produce “high-quality Chinese”; provides an article for editing or polishing; or needs high-quality Chinese content. For technical documents (README, API documentation, CLI instructions), use conservative mode (see mode three below) to avoid changing structured lists and terminology sequences. Triggers: /good-writing, /润稿, good writing, 润稿, 改写, rewrite, 文笔, 让文字更顺, 技术文件润饰, conservative mode
Safe workflow for reading, mapping, and writing Google Sheets without shifting columns or overwriting the wrong ranges. Use when the user wants to read, update, or append spreadsheet data, fix sheet structure, or sync data into Google Sheets.
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.