Skills
99,064 packaged capabilities and playbooks for agents. Install any of them with one command.
All
AI-agent commit protocol that establishes a Shadscan baseline and reruns the audit immediately before every agent-created commit without installing dependencies or configuring Git. Use when an agent is asked to commit work in a React shadcn project, prevent UI regressions during an agent task, or run Shadscan before commits.
Prepare a feature branch for a pull request: verify scope, sync when needed, test, review, push and open or update the PR. This skill MUST be used when the user requests this branch-to-PR workflow or explicitly invokes ship-it (開 PR、準備 PR、整理分支交付). It SHOULD be used when the user asks to prepare a completed feature for review. It MUST NOT be triggered solely by a push, merge, release, deployment request or a general readiness question.
Transform learning content (like YouTube transcripts, articles, tutorials) into actionable implementation plans using the Ship-Learn-Next framework. Use when user wants to turn advice, lessons, or educational content into concrete action steps, reps, or a learning quest.
Use when an app developer needs to bill a Shoplazza merchant for app usage through the CLI — one-time application charges, recurring (subscription) charges, metered usage charges, and app-charge transaction records. Triggers include 应用收费 / 订阅费 / 一次性收费 / 用量费 / 计费 / app billing / recurring / one-time / usage charge. NOT buyer order payments or refunds (那是 shoplazza-orders 的 transactions / +refund).
Shared foundation for the shoplazza CLI: installing the CLI (安装 CLI / command not found), authentication (auth login — account-level and store-level; 登录 / 授权), auth status/scopes/logout, store switching (auth store use; 切换店铺 / 换店), multi-store profiles (add/list/use/rename/remove/info), the three access tiers (+shortcut / spec leaf / api rest), the output envelope ({ok,data} / .data), --dry-run / --jq / --fields / --format, schema introspection, api rest fallback, update notice, the safety protocol, and how to trust a filtered list read (pagination / has_more / cursor, silently-dropped filters, the exact-match precision ladder). Read this FIRST on first use of the shoplazza CLI, when the CLI is missing, when logging in / authorizing / switching store or profile, on permission errors, when a search or filter looks like it returned too much, and before using any domain skill.
Use when the user wants to manage customers (buyers) on a shoplazza store through the CLI — create a customer profile, find a customer by email or phone, get customer details or the total customer count, update names / tags / email or SMS marketing subscription, or manage a customer's shipping addresses including the default checkout address. Triggers include 客户 / 买家 / 顾客 / 客户资料 / 新建客户 / 按邮箱查客户 / 按手机号查客户 / 给客户打标签 / 退订营销 / 收货地址 / 默认地址 / customer profile / new customer / find customer by email or phone / customer count / tag a customer / unsubscribe marketing / shipping address / default address. Finding the customer RECORD by email (按邮箱找客户资料) belongs HERE (customers +search); that customer's ORDER HISTORY (该客户下过的订单 / orders placed by this email) belongs to shoplazza-orders.
Use when the user wants to manage a shoplazza store's orders through the CLI — searching / counting / viewing orders (查订单 / 找订单 / 订单列表 / 订单详情 / 新订单 / order search), shipping and fulfillment (发货 / 标记发货 / 物流 / 运单号 / 改运单号 / ship an order / update tracking), refunding a buyer (退款 / 给顾客退钱 / 退钱给买家 / refund an order — buyer refunds live HERE, not in discounts and not in billing), cancelling / creating / updating / marking orders paid (取消订单 / 代客下单 / 标记支付), an order's payment transactions (订单支付流水 / 支付交易记录 / buyer payment transactions — app-charge transactions → shoplazza-billing), fraud risk records (欺诈 / 风控 / 高风险订单 / order risk), after-sales records (售后 / post-sales), shipping zones and rates (运费区域 / 邮费 / 运费方案 / shipping zones — real-time rate carriers → shoplazza-shop carrier-services), and tracking-carrier lookup (快递承运商 / 运单号识别承运商). A customer's orders by email (按邮箱查某客户的订单) are searched HERE; the customer record itself → shoplazza-customers. NOT product stock / 库存 / 补货 (→ shoplazza-products).
Use when an app developer needs to manage webhook subscriptions on a Shoplazza store through the CLI — subscribe to store events (order created, product updated, …) so the platform pushes notifications to an app's endpoint, and list / get / update / delete / count those subscriptions. Triggers include webhook / 事件订阅 / 事件回调 / 事件通知 / 推送通知 / 回调地址 / subscribe to an event / event notification. NOT the events themselves in shoplazza-orders / shoplazza-products — this domain owns the SUBSCRIPTION.
An industrial-scale scriptwriting super-system for hit short dramas on Douyin/Hongguo v4.9.1. A pure script engine (public, general-purpose edition for all genres; no production handoff). Core features: dynamically mounted matrix on demand (8 interaction modes, mounting only core files to prevent Context overload); emotional contract unit-chain round-trip method; full map of 40 genre tracks (12 male-oriented/14 female-oriented/14 neutral); six archetypal hook library (including irreversible deprivation of the core trump card) plus five cliffhanger formulas; rotation matrix for nine A~I reversal techniques plus layered hot/cold ledger; three length tiers (standard: 90~120 seconds/480~850 main-text characters; long: flexible 150~195 seconds/820~1400 characters; manhua drama: 60~90 seconds/330~620 characters); four-beat pacing chart for 15-second episode shifts (hook and establish stakes -> direct confrontation -> reveal and reverse -> aftermath hook); three visual anchors for strong imagery (insert a strong visual △ every 2~4 sentences; E24 blocks dry-talk gaps/E26 blocks ineffective micro-actions); rules for plain language delivered directly in the same beat and fast/slow pacing (state evidence and conclusion together/translate setting terms into plain language in the same sentence; E25 blocks cryptic jargon); three-layer, similarity-not-imitation adaptation method (strip surface and banned terms -> extract dramatic formula -> reskin across dimensions); duration conversion anchors (write at target 4.5 characters/s and validate at 4.5 characters/s minimum to prevent inflated runtime claims); production-side check of <=95 characters per 15-second window; soft constraint of <=40 characters per action paragraph; golden dialogue/action ratio of 25%~70%; first three episode beat cards; four paywall variants; cross-episode continuity ledger; web-fiction adaptation pipeline; character bible; dramatic craft layer; controlled monologue and narration rules; expression phrase format (visual word | tone word); review and repair issue cards; protective counterexample set; 11 compliance red lines under NRTA Order No. 16; tiered script machine checks (E1~E26) plus full-series ledger checks (S1~S8). Triggers: writing short dramas or outlines, project proposals, fixing pacing, episode breakdowns, long-form episodes, script doctoring, polishing, inner monologue, narration, voiceover, ultra-fast short dramas, compliance review, or consecutive writing.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. Don't use for running skills themselves, generating prose/blog content, or scaffolding unrelated Python projects — this is only for authoring and evaluating skill-packaged capabilities.
Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns, file paths, content patterns), enforcement levels (block, suggest, warn), hook mechanisms (UserPromptSubmit, PreToolUse), session tracking, and the 500-line rule.
Use when the user explicitly asks to build, extend, validate, repair, rebuild, or merge an LLM-optimized knowledge wiki from markdown notes, documentation, source code, or mixed folders. Default output is a single stable sibling `<source>.wiki/` with full history in a private git repo under `.llmwiki/git/`; `--layout-mode in-place` transforms the source folder itself, and `--layout-mode hosted --target <path>` honours a user-provided `.llmwiki.layout.yaml` contract. SKILL.md is the entry point; detailed operation instructions are loaded on demand from `guide/` per the routing procedure below.
Audit the skill inventory for quality, coverage, and staleness. Detect overlapping, incomplete, or outdated skills and produce a health report. Activate when: skill audit, stocktake, skill inventory, check skills, which skills exist, audit skills, skill quality, skill coverage.
BDD-style behavior specification engine for the skill system. Use when: (1) defining a new skill's behavior before implementation, (2) validating a spec against the schema, (3) generating a behavior contract (Mermaid DAG) from a spec, (4) running structural acceptance tests against a built skill. Workflow: Spec → Test → Develop → Contract.
Comprehensive toolkit for managing large Claude Code skill collections including bulk downloading from GitHub, organizing into categories, detecting and removing duplicates, consolidating skills, and maintaining clean skill repositories with 100+ skills.
Use when the user wants to build, migrate, or troubleshoot a Smart X routine -- TOTVS's metadata-driven UI framework that generates modern PO-UI screens from a data dictionary Object/Model/Interface/Launcher chain. Covers the model.tlpp/interface.tlpp/launcher artifacts, ADVPL function integration via pageActions/tableActions/onChange, converting a legacy MVC browse to Smart X, and common troubleshooting. Also triggers on Portuguese phrasing like "tela Smart X", "gerar tela por metadados", "migrar MVC para Smart X", "criar Modelo e Interface Smart X", "launcher Smart X", or names like FINA050SM/MATA110SX.
Smoke test identification, authoring, and CI integration for HTTP APIs — using Hurl or curl only. TRIGGER when: smoke test, smoke testing, critical path test, CI gate, gate before full suite, write smoke tests, add smoke test, smoke test template, which tests are smoke tests, hurl, .hurl file, curl smoke test. DO NOT USE when: user needs full testing strategy or philosophy — use `testing` instead.
Interview the user in ten questions or fewer and produce a social-context.md file that captures who they are, who they are talking to, what they post about, and what they refuse to post. Covers LinkedIn, X (Twitter), Instagram, Threads, TikTok, and YouTube — the interview decides which of those platforms actually matter. Use when the user says "set up my social context", "onboard me", "set up my socials", or "create my social profile". Every other skill in this collection reads social-context.md for brand voice and setup, so this is the skill to run first. Re-running it updates the existing file section by section and never overwrites the user's manual edits without asking.
Multi-slide carousel design for Instagram, LinkedIn, and Twitter/X with layout rules and hooks. Covers slide structure, text hierarchy, swipe psychology, and platform-specific specs. Use for: carousel posts, Instagram carousels, LinkedIn carousels, slide posts, educational content. Triggers: carousel, instagram carousel, linkedin carousel, slide post, carousel design, swipe post, multi-image post, carousel template, educational carousel, carousel content, instagram slides, linkedin slides
Use for social science academic paper drafting, outlining, diagnosis, review, and revision. Trigger for topic diagnosis, research question refinement, literature review planning, CNKI/Google Scholar literature search-to-Zotero workflows, structured paper reading notes, theoretical framework design, research design critique, draft review, section or paragraph revision, citation and evidence risk checking, causal-claim checking, and pre-submission review. Do not use for purely creative writing or non-academic editing.
Write professional software requirements documents (SRS, PRD, BRD, FRD, User Stories, Use Cases). Use when a user asks to write requirements, create an SRS or PRD, turn a feature description into user stories, generate acceptance criteria, review an existing requirements document, or convert an informal idea into structured requirements. Also trigger when the user mentions "acceptance criteria", "functional requirements", "non-functional requirements", or "requirements traceability matrix".
Hardhat 3 development workflow for Solidity smart contracts. Use when building, testing, or deploying with Hardhat 3.x (hardhat, ignition, EDR). Covers ESM-first project setup, defineConfig, Solidity-native tests, TypeScript tests, multichain support, Hardhat Ignition deployment, and hook-based plugin system. Triggers on tasks involving hardhat init, hardhat build, hardhat test, hardhat ignition, or Hardhat-based Solidity development.
Generate custom sound effects using each::sense AI. Create realistic and stylized audio for any scenario including impacts, ambiences, foley, UI sounds, nature, mechanical effects, and transitions. Powered by stable-audio-2-5 for precise audio generation. Use for: video production, game development, podcasts, apps, UI/UX, presentations, film. Triggers: sound effect, sfx, audio effect, foley, generate sound, ambient sound, ui sound, impact sound, whoosh, explosion, nature sound, notification sound, create audio
Create 2.35:1 header image covers for WeChat official accounts, generated with Codex's built-in image_gen, following the "lightweight AI product infographic" visual system (white/light lavender background, ink-black large headings, tech purple and lime green accents, rounded cards, linear icons). Includes a built-in share safe-zone check — when a WeChat official account cover is shared to Moments, only the central 1:1 square is kept, and this Skill ensures the title is not cropped. Triggered when the user says "make a WeChat official account cover", "make a header image", "article lead image", "2.35:1 cover", "WeChat official account cover image", or "make a few cover versions".
Statistical Process Control (SPC) — select the correct control chart, interpret out-of-control signals using Western Electric rules, calculate and interpret Cp, Cpk, Pp, Ppk. Use when setting up SPC for a new characteristic, interpreting control chart signals, responding to special cause variation, or auditing SPC implementation. Covers AIAG SPC 2nd edition and IATF 16949 §8.3.3.
Generate a structured sprint brief from sprint data and goals. Use when asked to write a sprint brief, create a sprint summary, document sprint goals and scope, or produce a team-facing sprint overview. Produces a scannable brief with sprint goal, rationale, grouped work, critical path, risks, and definition of done.
Structure and facilitate sprint planning sessions. Use when asked to plan a sprint, organise backlog items, assign story points, create sprint goals, or prepare sprint planning agendas. Produces a sprint goal, velocity-calibrated backlog, capacity plan, risk flags, and a structured sprint planning meeting agenda.
Explains, optimises, writes, and documents SQL queries. Use when asked to explain a SQL query, optimise slow SQL, translate SQL to plain English for non-technical stakeholders, write a query from a natural language description, or produce query documentation. Produces plain-English explanations, annotated optimised queries, or a data dictionary covering output shape, assumptions, and known limitations. Works across PostgreSQL, MySQL, BigQuery, Snowflake, and standard SQL.
ACTIVATE when developing long-term strategy, setting OKRs, creating vision statements, building SWOT analyses, designing strategic frameworks, defining company direction, planning multi-year initiatives, or aligning organizational strategy with business goals. Executive must think through market positioning, competitive advantage, and measurable strategic objectives.
Production logging patterns for observability and incident debugging. Structured JSON logging, correlation IDs, context propagation, log levels, and performance. Use when implementing logging, adding observability, or debugging production systems. Triggers on logging setup, logger configuration, observability, distributed tracing, or incident response workflows.
Contributing to the Twenty codebase itself (twentyhq/twenty server internals), not for building apps on top of Twenty. Create validation logic and migration action builders for syncable entities in Twenty. Use when implementing business rule validation, uniqueness checks, foreign key validation, or building workspace migration actions for syncable entities. Validators never throw and never mutate.
Complete guide to implementing the Syncfusion DatePicker component in ASP.NET Core applications with Tag Helpers, custom date formats, range validation, events, globalization, and styling for building professional date input forms.
Complete guide to implementing the Syncfusion MultiSelect component in ASP.NET Core applications with tag helpers, data binding, filtering, templates, checkboxes, and accessibility for building advanced dropdown selection forms.
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.