Skills
98,067 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Conduct compensation benchmarking analysis to position salaries against market data. Use this skill when the user needs to assess pay competitiveness, build salary bands, or analyze pay equity — even if they say 'are we paying market rate', 'salary benchmarking', or 'compensation analysis'.
Calculate Cpk process capability index to assess whether a process meets specification requirements. Use this skill when the user needs to evaluate process capability, compare processes, or determine if quality targets are achievable — even if they say 'can our process meet spec', 'process capability', or 'Cpk calculation'.
ALGOPACK access, free and paid API keys, subscription, API key authorization, entitlement, and troubleshooting guidance for DataShop setup, bearer tokens, moexalgo .env session.TOKEN setup, direct REST headers, free or delayed access, 401, 403, 429, rate limits, and product boundaries.
Direct ALGOPACK and MOEX ISS market-data workflows for browser URLs, curl, JSON, CSV, simple HTML output, quotes, candles, trades, order books, securities metadata, EQ/FO/FX endpoint selection, iss.only filters, ISS columns/data normalization, start pagination, and no-library access.
Perform SysOM performance profiling on ACK cluster Pods to identify root causes of Pod-level performance issues (CPU throttling, OOM, memory distribution, network jitter, IO latency, etc.). Use when users report ACK Pod performance problems or need kernel-level container profiling.
Proactively use AgentLoop Recall to retrieve prior Alibaba Cloud AgentLoop experience through the bundled SearchContext CLI whenever the user asks or implies that prior work may help. Trigger for requests to check, search, recall, retrieve, look up, review, consult, reference, or compare prior experience, historical troubleshooting cases, past fixes, comparable incidents, lessons learned, old runbooks, previous remediations, or successful workflows before or during work. Also trigger for Chinese requests such as 先查历史经验、回忆类似案例、召回过往排障记录、看看之前有没有处理过类似问题、参考以前怎么处理、找找之前的踩坑记录、翻一下历史排障、有没有类似经验、先看看过去的案例.
Business Analyst Skill. Triggered when users ask about business analysis, industry research, competitive analysis, product analysis, business model analysis, business opportunity discovery, market entry strategy, investment decisions, strategic planning, due diligence, and other strategic topics. Delivers in-depth, decision-grade HTML research reports through a seven-stage workflow (Briefing → Framing → Planning → Research → Insights → Report → Iteration).
Search and retrieve research papers from AlphaXiv. Use when asked to search papers by title or topic, get paper details/metadata/metrics, retrieve AI overviews or summaries, find trending or top AI papers, get similar papers, browse implementations, look up SOTA benchmarks, or ask questions about a specific paper.
This skill should be used when the user asks about "documentary", "documentary research", "interview questions", "documentary treatment", "archival research", "documentary ethics", "act as a documentary researcher", "documentary mode", "non-fiction film", "documentary proposal", "documentary subject research", "oral history", "verite", "observational documentary", or needs expertise in documentary research methodology, interview preparation, treatment writing, and ethical frameworks for non-fiction filmmaking. Part of the AlterLab FC Skills collection (Cinema & Digital Media department).
This skill should be used when the user asks about "camera moves", "AI camera presets", "dolly", "crane shot", "orbit shot", "crash zoom", "bullet time", "360 orbit", "FPV arc", "pan", "tilt", "dutch angle", "tracking shot", "Higgsfield camera", "Cinema Studio", "camera direction", "cinematic grammar", "Sora 2 Presets", "Higgsfield Assist", "Soul Cast", "content scoring", "act as a camera director", "camera director mode", "camera language", "lens selection", "focal length", "21:9 cinematic", "camera motion storytelling", "Turbo model", "camera presets catalog", "combining camera moves", "camera style matching", or needs expertise in AI camera direction on Higgsfield, camera preset selection, cinematic grammar, motion sequencing, and matching camera language to narrative intent. Part of the AlterLab FC Skills collection (GenAI pack).
This skill should be used when the user asks about "AI talking head", "UGC builder", "Higgsfield Speak 2.0", "lipsync video", "Lipsync Studio", "selfie to video", "Kling Lipsync", "Kling Speak", "Sync.so", "Higgsfield Assist", "Soul Cast", "content scoring", "digital presenter", "AI spokesperson", "synthetic presenter", "talking avatar", "lip sync", "AI testimonial video", "act as a talking head creator", "talking head mode", "Veo 3 UGC", "photo to talking video", "AI voiceover video", "expression control video", "multilingual video presenter", "AI ad presenter", or needs expertise in creating realistic AI talking-head videos using Higgsfield. Part of the AlterLab FC Skills collection (GenAI pack).
This skill should be used when the user asks about "media theory", "critical theory", "academic writing", "Foucault", "Habermas", "McLuhan", "Baudrillard", "Stuart Hall", "act as a media theory companion", "media theory mode", "theoretical framework", "literature review", "discourse analysis", "semiotics", "cultural studies", "political economy", or needs expertise in applying media and communication theory to academic writing and critical analysis. Part of the AlterLab FC Skills collection (New Media & Communication department).
This skill should be used when the user asks about "UI design", "user interface design", "wireframing", "wireframe", "design system", "component library", "app design", "web interface design", "mobile UI", "atomic design", "8pt grid", "Material Design", "Human Interface Guidelines", "HIG", "design tokens", "responsive design", "act as a UI designer", "UI designer mode", "interface patterns", "UI kit", "navigation design", "form design", "dashboard layout", "button styles", "input fields", "card components", "modal design", "design handoff", or needs expertise in app and web interface design, wireframing, design systems, and component libraries. Part of the AlterLab FC Skills collection (VCD department).
Create custom directives in Angular v20+ for DOM manipulation and behavior extension. Use for attribute directives that modify element behavior/appearance, structural directives for portals/overlays, and host directives for composition. Triggers on creating reusable DOM behaviors, extending element functionality, or composing behaviors across components. Note - use native @if/@for/@switch for control flow, not custom structural directives.
Add CSS animations to HTML elements, React/JSX components, or WordPress PHP templates using Animate.css (v4.1.1). Use this skill whenever the user wants to animate UI elements, add entrance/exit effects, attention-seeker animations, or any CSS-based motion to their markup. Trigger on phrases like "add animation", "animate this", "make it bounce/fade/slide/zoom", "add transitions", "CSS animations", or any request to bring elements to life visually. Works with raw HTML snippets, full HTML files, React JSX, and WordPress PHP templates. Claude picks the most contextually appropriate animation — no guesswork needed from the user.
Evaluates anonymization as a retention alternative under GDPR Recital 26, applying the WP29 Opinion 05/2014 techniques including randomization and generalization. Validates anonymization effectiveness using k-anonymity, l-diversity, and t-closeness metrics. Activate for anonymization, de-identification, k-anonymity, retention alternative queries.
Reference guide for connecting popular APIs to Home Assistant via Node-RED, YAML, or custom integrations. Covers authentication, endpoints, and complete working examples for: energy APIs (Tibber, Nordpool), weather (SMHI, OpenWeatherMap, yr.no), transport (SL, Trafikverket, Resrobot), smart home clouds (Shelly, Tuya, Philips Hue, IKEA), and global APIs (OpenAI, Spotify, Google Calendar, Telegram, GitHub). Use this skill whenever the user mentions a specific external service, API, or data source they want to connect to Home Assistant - even if they don't say "API".
Guide a developer through setting up a Meta API integration from scratch — discovers the right APIs, fetches setup guides, authentication requirements, permissions, and code examples. Use when the user wants to build with a specific Meta product (WhatsApp, Instagram, Messenger, Pages, Ads, etc.).
Build a local-business lead list without scraping Google Maps. Routes "find dentists / plumbers / salons / restaurants in <city> with emails", "business email finder for <category> in <city>", "web-design prospects with no website or a weak one", "enrich my list of business websites with verified emails", "leads within 5 km of an address" and "alert me when new businesses appear" to an OpenStreetMap-based Actor that crawls each business's own website and returns one 73-column row per business with an MX-verified email, phone, social profiles, website platform and a 0-100 lead score. No Google Maps, no API key, no proxy, no login; every filter runs before billing. Use when the user wants local B2B leads for cold email or calls, a Google Maps alternative that avoids Google's terms, a bring-your-own-website-list enrichment pass, or a scheduled new-business watch for one category and city.
Design and audit permission request UX, consent moments, privacy rationale, denial recovery, settings paths, OS prompts, notification opt-ins, location/camera/microphone/photo/contact access, tracking prompts, and trust copy for mobile, desktop, web, and games. Use when products need sensitive access without hurting conversion, review approval, accessibility, or user trust.
Interactively guides the documentation of arc42 Section 7 (Deployment View). Asks about infrastructure, environments, and software-to-hardware mapping before generating C4 PlantUML deployment diagrams and environment comparison tables. Iterates until the user is satisfied.
Interactively guides the documentation of arc42 Section 10 (Quality Requirements). Elaborates quality goals from Section 1.2 into concrete, measurable scenarios grounded in Q42 quality criteria (quality.arc42.org). Coaches against vague metrics and checks coverage against architectural decisions. Iterates until the user is satisfied.
Interactively guides the documentation of arc42 Section 11 (Risks and Technical Debt). Pre-populates candidates from Sections 9 and 10, works through risk categories systematically, and generates a prioritized risk register and debt backlog with mitigation strategies. Iterates until the user is satisfied.
Interactively guides the documentation of arc42 Section 12 (Glossary). Scans other sections for undefined terms, asks about domain vocabulary and ambiguous terminology, and generates a structured glossary with consistent preferred terms. Iterates until the user is satisfied.
Use when recording an architectural decision so future maintainers know why—phrases like "ADR", "architecture decision record", "why did we pick X", "lightweight architecture documentation", "decision log", "should this be an ADR", "tribal knowledge", "we chose this two years ago and now nobody remembers why". Defines an ADR as a short, structured document capturing what was decided, why, alternatives considered, and consequences—written at the time of the decision and kept in the repo
Use when protecting a service from a degraded or failing dependency—phrases like "circuit breaker", "bulkhead", "retry policy", "exponential backoff", "fail fast", "fallback", "cascade failure", "open/closed/half-open state", "resilience4j", "Polly", "Hystrix". Defines the circuit breaker pattern and related failure-isolation tools (bulkhead, retry-with-backoff, timeout, fallback)
Use when separating read and write models — phrases like "CQRS", "Command Query Responsibility Segregation", "read model vs write model", "denormalized read side", "materialized view", "different scaling for reads and writes", "command bus", "query bus", "should we use CQRS here". Defines CQRS as keeping reads and writes on separate models, with picking criteria that resist over-application.
Use when designing a system around asynchronous events—phrases like "event-driven architecture", "EDA", "event broker", "Kafka", "publish-subscribe at scale", "event-first design", "choreography vs orchestration", "event broker vs message queue", "broker topology vs mediator topology". Defines event-driven as a macro architectural style where components emit and react to events, not direct calls
Use when persisting state as a sequence of events—phrases like "event sourcing", "event store", "append-only log of facts", "replay events to rebuild state", "audit log as source of truth", "temporal queries", "snapshot", "should we event-source this aggregate". Defines event sourcing as storing the history of what happened as the canonical state, with current state derived by replay
Use when enforcing architectural characteristics through automation — phrases like "architecture fitness function", "evolutionary architecture", "architecture tests", "ArchUnit", "dependency rules in CI", "automated architecture checks", "guardrails", "drift detection". Defines fitness functions as automated checks that verify architectural characteristics on every change, catching drift before it accumulates.
Use when picking a software architecture style or pattern for a system — phrases like "what architecture should we use", "monolith vs microservices", "should we go event-driven", "is this a CQRS situation", "do we need a saga here", "should we use hexagonal architecture", "what's the right architectural style for this problem". Diagnostic mode that routes a stated problem to the relevant architecture skill or rules patterns out.
Use when discussing layered architecture (n-tier) — phrases like "layered architecture", "n-tier", "presentation / business / persistence layers", "should we go layered", "leaky layer", "sinkhole anti-pattern", "open vs closed layers". Defines the layered style with its strict top-down dependency rule, the open/closed layer concept, and the most common failure modes.
Use when designing or reviewing a microservices architecture — phrases like "microservices", "should we split this service", "service boundaries", "bounded context per service", "API gateway", "backend for frontend", "BFF", "service mesh", "microservices vs monolith", "database per service", "data ownership". Defines microservices as independently deployable services aligned with business capabilities — and the discipline of resisting the style until the monolith proves inadequate.
Use when migrating a legacy system incrementally — phrases like "strangler fig", "strangler pattern", "incremental migration", "monolith to microservices", "rewrite without big bang", "replace legacy in place", "facade in front of the legacy system", "anticorruption layer". Defines Fowler's Strangler Fig as the migration discipline of gradually replacing legacy functionality behind a stable facade, never doing a big-bang rewrite.
Analyze totalitarianism, the banality of evil, political judgment, and the public sphere from Hannah Arendt's perspective, safeguarding humanity's capacity to act and think. Use when the user explicitly asks for this figure's perspective, mentions “arendt-perspective”, or wants to apply her core method to analyze a problem; do not trigger automatically for general questions.
ArkTS static language specification reference for OpenHarmony. Use this skill when reading or writing ArkTS (.ets), explaining ArkTS type-system and static-semantics rules, validating code against the ArkTS spec, investigating ArkTS compile-time behavior, or comparing ArkTS with TypeScript migration guidance.
Use when building App Store screenshot pages, generating exportable marketing screenshots for iOS apps or iPad apps, or creating programmatic screenshot generators with Next.js. Triggers on app store, screenshots, marketing assets, html-to-image, device mockup, frameme, asc-client, asc-screenshots.
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.