Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Codify reusable pygame patterns for entities, projectiles, movement, and sprite handling. Use when implementing pygame entities or systems that need frame-independent physics, collision detection, or sprite management. References verified patterns from project implementation.
Look up the public API of a Python package against the *installed version* and cache what's worth keeping. Four shapes by question type: (0) cache hit under `scratch/api/<lib>/<version>/`; (1) `inspect.signature` + `pydoc.render_doc` for a symbol; (2) `dir` / `pkgutil.iter_modules` for a module surface; (3) WebSearch + WebFetch of versioned docs for narrative ("how", "which", "what does X return when Y?"). Never write a symbol from training-data memory — recognition is not a lookup. TRIGGER — any of: - About to name a symbol (function / class / method / arg) in code. - User asks "what's the signature of X?", "what's in module Y?", "how do I call X?", "which of A/B should I use?". - User asks "what does X return when <condition>?" (Shape 3 — see decision table). - Another workflow skill (`build-ml-pipeline`, `evaluate-ml-pipeline`, `iterate-from-skore`, `smoke-test-ml-pipeline`) says "consult the API skill". - About to reach for a library's "obvious" pattern from memory. SKIP when: the signature is obvious from a call site you just read in this turn; the work is filesystem / shell only (no Python symbols); a `scratch/api/<lib>/<version>/<topic>.md` cache file already answers the question (still a Shape 0 consultation — you just don't fetch). HOW TO USE: resolve the package version first via a scratch file (`scratch/<ts>_version_<pkg>.py` with `import <pkg>; print(<pkg>.__version__)` — run with `pixi run python scratch/<ts>_version_<pkg>.py`). Then list `scratch/api/<lib>/<version>/`. Then pick the shape from the "What kind of question?" table. Narrative findings get cached back. **All Python execution goes through `scratch/<ts>_*.py` files — inline `python -c` is forbidden regardless of length.** Stack-specific orientation lives in `references/stack_orientation.md` — load on demand.
Generate comic- or anime-style images with Tongyi Qianwen · Wanxiang (wan2.6-t2i). Use this skill for requests related to comic-style image generation, such as “generate a comic,” “draw a comic with Wanxiang,” “generate a comic-style image,” or “draw a 2D character with Qianwen.”
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization.
Analyze development sessions, capture learnings, and improve Claude Code instructions. Use when the user wants to reflect on a session, improve CLAUDE.md, extract learnings, or optimize AI-human collaboration. Supports two modes: quick (default) focuses on CLAUDE.md improvements, deep mode performs comprehensive session analysis with learning capture.
End-to-end release cutting for a GitHub repo: decide the next semantic version from the Conventional Commits since the last tag, draft proper release notes (GitHub auto-generated via `.github/release.yml`, or hand-curated grouped by change type with highlights and upgrade notes for breaking changes), create and push an annotated tag, publish the GitHub release, and optionally update `CHANGELOG.md`. Use when the user says "cut a release", "tag a release", "publish a release", "ship vX.Y.Z", "bump the version", "what version should this be", "write the release notes", "draft the changelog", or invokes /release. Distinct from /gh-bootstrap (which scaffolds the `.github/release.yml` + release workflow plumbing once): this skill runs the actual release ceremony — version decision, notes, tag, publish. Run after the work is merged to the default branch.
Configure .gitattributes, .editorconfig, .gitignore, and Git LFS filters for a repository: normalize line endings, mark generated, vendored, and documentation paths for GitHub linguist, set per-language editor defaults, and merge .gitignore content from GitHub templates. Use when the user says "add .gitattributes", "fix line endings", "CRLF", "linguist", "mark generated files", "set up .editorconfig", "gitignore template", "git lfs", or invokes /repo-attributes. Do NOT use for prek or pre-commit hook configuration — use /prek. GitHub custom properties (organization-level metadata) are out of scope; this skill only touches per-repository attribute, editor, and ignore files. Community health files (README, LICENSE, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY) belong to /oss-hygiene, not this skill.
Resolve an in-progress git conflict without a silent drop. Use when the worktree is mid-merge, mid-rebase, mid-cherry-pick or mid-stash-pop: `CONFLICT (content)`, `<<<<<<<` markers, `Unmerged paths`, or `fix conflicts and then commit the result`.
Deprecated and migrated to https://github.com/simonwong/writing-skills. Rewrites English content in Simplified Chinese. Use for rewriting English articles, documents, and blogs in Chinese. Uses the deverbalization technique: understand the original meaning, then express it naturally in Chinese rather than translating word for word. Preserves Markdown formatting and AI proper nouns.
Build and operate production-safe Runway API video generation, video editing, and character-performance workflows with native Runway models, explicit paid-call approval, duplicate-create protection, asynchronous task handling, secure media transfer, and evidence-aware governance.
Audits any SDK documentation site and produces a fully scored, downloadable HTML report. Use this skill whenever a user provides a documentation URL and asks to audit, review, analyse, score, or check the quality of SDK docs. Also trigger for phrases like "audit the SDK docs at X", "check if the docs at X are complete", "review this SDK documentation", "how good are these docs", "run an SDK audit on X", or any time a user pastes a URL alongside words like audit, review, crawl, check, analyse, quality, completeness, or gaps. ALWAYS use this skill — do not attempt the audit without following this structured crawl → analyse → cross-reference → report workflow.
Generate luxury and premium aesthetic video prompts for Seedance 2.0 on Higgsfield. Use for luxury brand content, premium product showcases, high-end lifestyle, minimalist aesthetic, elegant brand videos, or any content requiring sophisticated visual treatment. Triggers on luxury, premium, high-end, elegant, minimalist, sophisticated, exclusive, refined, designer, couture, bespoke.
The all-in-one ship pipeline — commit uncommitted work, run the change-gated lint preflight, author the dated changelog entry, compose a Conventional Commits PR title, push, open or update a PR, move linked Linear issues to In Review, then chain into `triage-pr` (Step 11) to drive the PR to merge-ready. Incomplete until triage-pr reaches a terminal outcome (its Step 13 report, its human envelope, or a documented stop), or `--skip-triage` / `triage: false` was used with a stated reason. Use when asked to ship, send it, finish a branch, open or update a PR, or wrap up and push. Thin orchestrator over `commit`, `preflight`, `changelog`, `linear-sync`, `pr`, and `triage-pr`; owns branch guard, release-type decision, PR title, push, and PR. Serves monorepos and single-package repos alike.
Co-write a top-down design spec for software projects. Shape vague ideas into clear specs by working layer-by-layer — vision, scope, building blocks, then detail. Use when user wants to design a system, plan a project, write a design spec, or needs to see the big picture before diving into details. Use before /grill-design to prevent losing focus on large projects.
A high-performance analysis engine for Excel datasets of ten thousand rows or more. It provides openpyxl read_only streaming reads (iter_rows supports over 100,000 rows), Parquet conversion for speed, memory optimization, chunked processing, and large-file write mode. **Proactively use this skill in any of the following cases**: ① the row count ≥ 10k (triggered by the row-count assessment step of sn-da-excel-workflow); ② the user uses trigger words: 大文件 / 大数据量 / 性能优化 / 内存不足 / OOM / 百万行 / 十万行 / 流式读取 / Parquet / 分块处理 / large file / big data / streaming read / chunked processing; ③ using pd.read_excel() directly causes a timeout or memory overflow; ④ the user explicitly requests high-performance processing of a large-scale dataset. Not for: routine Excel analysis of fewer than 10k rows (just use sn-da-excel-workflow).
Provides comprehensive guidance for Spring Boot development, including project creation, auto-configuration, dependency injection, web development, data access, security, testing, and deployment. Use when the user asks about Spring Boot, needs to create Spring Boot applications, configure Spring Boot, or implement Spring Boot features.
Execute read-only T-SQL queries against Fabric Data Warehouse, Lakehouse SQL Endpoints, and Mirrored Databases via the MCP `fabric-sqlendpoint-execute_query` tool. Default skill for any lakehouse data query (row counts, SELECT, filtering, aggregation) unless the user explicitly requests PySpark or Spark DataFrames. Use when the user wants to: (1) query warehouse/lakehouse data, (2) count rows or explore lakehouse tables, (3) discover schemas/columns, (4) generate T-SQL scripts, (5) monitor SQL performance, (6) export results to CSV/JSON. For a Fabric notebook cell (%%sql or other notebook magics), use `spark-authoring-cli`, not this skill. Triggers: "warehouse", "SQL query", "T-SQL", "query warehouse", "show warehouse tables", "show lakehouse tables", "query lakehouse", "lakehouse table", "how many rows", "count rows", "SQL endpoint", "describe warehouse schema", "generate T-SQL script", "warehouse performance", "export SQL data", "connect to warehouse", "lakehouse data", "explore lakehouse".
A guide for building applications with the SUZURI REST API. Use when developing apps that create, search, or display merchandise with the SUZURI API, or services that integrate with SUZURI. When topics about SUZURI-related application development come up, such as "SUZURIのAPIで", "SUZURIで商品を", "SUZURIと連携", "スズリAPI", or "suzuri.jpのAPI", refer to this skill.
Use when the user says "brief this task", "scope this properly", "what do you need from me", "improve my prompt", "help me get better output", "turn this into a reusable prompt", "a prompt I can hand to a colleague", or hands over a SUBSTANTIAL task — multi-step, multi-document, or a deliverable someone else will read — as a thin one-line request. Compile a task brief BEFORE starting substantial work — pin down the goal with checkable "done when" tests, context, constraints (standing rules included automatically), and tooling — confirm with the user, then execute against it. Reusable-prompt mode saves the brief as a structured prompt for recurring work instead of running it. Asks at most 2-3 clarifying questions, only where the answer would change the output; otherwise states assumptions in the brief and proceeds. Not for quick one-step asks — answer those directly.
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
Drive a change through a red-green-refactor loop - failing test first, minimal code to pass, then clean up. Use when implementing a feature or fixing a bug where correctness matters and a test can pin the behavior. Says "TDD", "test first", "red green refactor", "write the test first".
Plan and execute technical product launches for developer tools, APIs, and technical products. Use this skill when technical PMMs need to "plan a launch", "create a launch strategy", "coordinate a product release", or "prepare for GA/beta launch".
Audit crawlability, indexability, HTTPS and redirects, Core Web Vitals, mobile parity, metadata, canonicals, structured data, and internal architecture using Semrush Site Audit data, separating confirmed defects from analyst judgment. Use when the user asks for a technical SEO audit or a site health check, why pages are not indexed, or why a site is losing search visibility for technical reasons.
Answer questions using the Tenzir documentation. Use whenever the user asks about TQL syntax, pipeline operators, functions, data parsing or transformation, normalization, OCSF mapping, enrichment, lookup tables, contexts, packages, nodes, platform setup, deployment, configuration, integrations with tools like Splunk, Kafka, S3, Elasticsearch, or any other Tenzir feature. Also use when the user asks how to collect, route, filter, aggregate, or export security data with Tenzir, or needs help writing or debugging TQL pipelines, even if they don't mention 'Tenzir' explicitly but are clearly working in a Tenzir context.
Mendelian randomization (MR) causal inference — does an exposure, risk factor, or biomarker CAUSALLY affect a disease/outcome, using genetic variants as instrumental variables (IEU OpenGWAS / EpiGraphDB MR-EvE). Use this whenever the user asks if X causes Y, whether an observational association is actually causal or just correlation, if a biomarker/trait is a causal risk factor, wants to triangulate epidemiology against genetic evidence, or mentions Mendelian randomization, instrumental-variable analysis, two-sample MR, or genetic causal evidence — even if they never say "MR" (e.g. "is LDL cholesterol actually causal for heart disease?", "does BMI cause type 2 diabetes or just correlate?", "is CRP a causal driver of stroke?"). Covers trait-label resolution, MR effect direction/magnitude, instrument quality (MOE score), method agreement (IVW vs MR-Egger vs weighted median), bidirectional MR for reverse causation, and distinguishing causation from genetic correlation. Not for plain GWAS association lookups (use the GWAS skills) or fitting your own instruments from raw summary statistics.
World-class trading psychology: emotional control, cognitive biases, discipline, and journaling. The mental game separates consistent winners from everyone else. Use when “trading psychology,” “emotional trading,” “discipline,” “tilt,” “revenge trading,” “FOMO,” “fear,” “trade journal,” “mental game,” or “mindset” is mentioned.
Write correct Sarvam translation code (sarvam-translate:v1, mayura:v1) — mode/script/numeral options and silent parameter failures. Use this skill when building translation or localization features in Python or JS/TS. For live translate/localize in chat via MCP, use sarvam-mcp instead.
Use when the user needs a business-trip itinerary built, updated, shared, or exported — create, update, sanitize, route, and export structured business-trip itineraries from booking confirmations, emails, tickets, PDFs, screenshots, calendar invites, or notes. Covers day-by-day itinerary generation, privacy-safe sharing, route links, and Markdown/PDF/DOCX/Google Doc/ICS exports.
Advanced Twitter search and social media data analysis. Fetches tweets by keywords using Twitter API, processes up to 1000 results, and generates professional data analysis reports with insights and actionable recommendations. Use when the user requests Twitter/X social media search, social media trend analysis, tweet data mining, social listening, influencer identification, topic sentiment analysis from tweets, or any task involving gathering and analyzing Twitter data for insights.
Core UI patterns for components and app screens: tokens, visual hierarchy, interactive states, forms, navigation, feedback states, accessibility, and responsive rules. Use when the user asks to "design a UI", "build a component", "create an interface", "style a form", "make it look good", "improve the design", "add hover states", "make it accessible", or any general UI work. This is the base the other UI skills build on; prefer landing-page-design for full marketing pages, hero-section for only the above-the-fold block, card-design for cards, dashboard-design for data-dense admin views, mobile-ui-design for touch-first screens, dark-mode for theming, and email-design for HTML email.
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.
