Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use when investigating the current state of a Datex Studio codebase with read-only inspection — answers questions about existing components, flow code, type definitions, datasource shapes, and configuration without modifying anything. Carries Datex Studio- specific patterns: extract flow code from `nodes[0].stepConfig.executeCodeConfig.code` (not from the JSON surface), delegate OData schema queries to `schema-explorer`, fetch enum values from `*-customType` configs on the branch via `dxs source explore`, return in `Answer / Sources / Caveats` format. Triggers: "research the codebase", "investigate how X works", "find where Y is defined", "answer questions about current code state". Consumed by impact-analysis, requirements-gathering, report-creator, and any skill needing grounded read-only inspection.
Apply standardized formats for internal business communications. Use for status reports, company newsletters, FAQs, and leadership updates. Use proactively when consistency in corporate communication is required. Examples: - user: "Write a 3P update for the week" -> use Progress/Plans/Problems template - user: "Draft a company-wide announcement" -> use newsletter format - user: "Create an FAQ for the new project" -> use internal FAQ guidelines
Compare a site against its own baseline, against a staging deployment, against up to four competitors, or against the pages that already answer a query (content gap). Produces score, category, finding and structure deltas from persisted audit runs. Read-only. Use when the user asks what changed after a deploy, whether staging is worse than production, how they stack up against competitors, or what rivals cover that they do not.
Use when scaffolding a new Datex Studio component from a documented skeleton — maps a requested type to folder, suffix, configurationTypeId, minimal-valid skeleton, and matching creator skill. Owns scaffold-routing so creator skills stay focused on authoring their own type. After creating the minimal-valid skeleton on the branch via dxs, hands off to the matching creator (action-creator, function-creator, grid-creator, hub-creator, form-creator, editor-creator, embed-creator, selector-creator, storage-creator, type-definition-creator, backend-test-creator, datasource-creator) for body authoring. Triggers: "scaffold a new component", "create a new grid/hub/form/editor/embed/selector/storage/interface/enum/backendTest/action/function/datasource", "starter <type> file", "new <type> from scratch".
Use when auditing a Datex Studio component file before merge — final gate after authoring or modifying any component (action, function, grid, hub, form, editor, selector, storage, customType, backendTest, datasource). Generic dispatcher: reads the component file, picks the matching creator skill's rule set by file suffix, and runs the audit per those rules. Output is a structured punch-list (Blockers / Warnings / Nits). Triggers: "audit a component", "check it before merge", "final gate after authoring or modifying". For grid-specific gotchas (envelope shape, text-display coercion) use grid-validator instead.
Use this skill to run a scored 53-point conversion audit covering customer focus, narrative, copy, design, calls to action, and proof. Trigger it when a landing, sales, product, or ad destination page needs diagnosis, pre-launch review, or prioritized conversion fixes.
Use when creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Triggers include requests for generative art, algorithmic art, flow fields, particle systems, or any art created through code. Always create original algorithmic art — never copy existing artists' work to avoid copyright violations.
Apply 25 professional mental models to solve complex problems. Use when: (1) facing multi-faceted challenges that require diverse perspectives, (2) stuck in single-minded approaches, (3) need innovative solutions, (4) making major decisions with multiple stakeholders, (5) understanding complex human behavior, or (6) seeking to break cognitive biases and adopt alternative viewpoints.
Datex Studio platform conventions for component file authoring: file format invariants (configurationTypeId table, file locations and suffixes, TS-expression encoding rule for declarative string slots, the `return;` outparam pitfall), naming conventions (per-component-type suffix indicators, tailored_/custom_ provenance prefixes, sentence-case display-text rule, user-facing `title` vs `referenceName` distinction), and defaults (package=Utilities, accessModifier=public, descriptions ≤100 chars and mandatory), plus the universal cross-cutting component checklist that validators and creators link. Not invoked directly — other skills link into the files below. Install this alongside any Datex Studio component-creator skill (action-creator, function-creator, grid-creator, hub-creator, form-creator, editor-creator, selector-creator, storage-creator, type-definition-creator, datasource-creator, backend-test-creator, tailoring-overlay) so cross-skill references resolve.
Datex Studio platform runtime semantics: platform-injected globals (`$flow`, `$datasources`, `$db`, `$shell`, `$frontendFlows`, `$operations`, `$apis`, `$flows`, `$types`, `$utils`, `$services.jobs`, `$editor`, `$datasource`), the three-tier execution model (functions / actions / UI components) and the caller→callee allow/deny matrix per tier, the generic CRUD action set in the Utilities package, and the `controlConfig.type` values used on field controls (codeBox, textBox, numberBox, dateBox, checkBox, selectBox, button, label, text, image, draw, progressBar, matrix) with sibling-config-block rules. Not invoked directly — other skills link into the files below. Install this alongside any Datex Studio component-creator skill (action-creator, function-creator, grid-creator, hub-creator, form-creator, editor-creator, selector-creator, storage-creator, db-query, tailoring-overlay) so cross-skill references resolve.
Diagnose Fireworks training and deployment issues, including stuck or failed jobs, error messages, poor quality, checkpoint and resume problems, LoRA adapter load mismatches, and deployments that are ready but not serving. Use for systematic read-only triage before retrying. Use configure for a new or approved retry run; use research when the starting method, data, or cookbook example is unclear.
Design, build, audit, redesign, study, and polish distinctive, production-grade web interfaces without generic AI aesthetics. Use for landing pages, websites, product UI, dashboards, portfolios, frontend components, HTML/CSS/JS, React, Next.js, Vue, Svelte, design-system work, visual redesigns, UI critiques, accessibility reviews, responsive hardening, or requests to remove AI slop
Keeping a design system in an LLM's context: loading tokens compactly, persisting design decisions across sessions, handling multiple variants, and budgeting the context window. Use when generated UI drifts from the design system, or when setting up tokens and decisions so every session and agent uses the same ones.
Use when creating beautiful visual art in .png and .pdf documents using design philosophy. Triggers include requests to create posters, pieces of art, designs, or other static visual pieces. Always create original visual designs — never copy existing artists' work to avoid copyright violations.
When the user wants to understand, reduce, or recover from developer churn. Trigger phrases include "why developers leave," "churn rate," "win-back campaign," "at-risk users," "developer retention," "preventing churn," or "competitor switching."
Design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization. Trigger phrases: developer signup, dev registration, OAuth flow, API key onboarding, reduce signup friction, developer authentication, signup conversion, registration UX
Guide for implementing sortable and droppable components using dnd-kit library. Use this skill when building React applications that require drag-and-drop functionality with both container reordering (useSortable) and item dropping (useDroppable) capabilities, such as Kanban boards, file management systems, or playlist editors.
Collaboratively draft, revise, and reader-test substantial documentation such as proposals, RFCs, decision records, technical specifications, strategy documents, and cross-team plans. Use when the user needs help transferring context, shaping an argument, resolving gaps, iterating on an existing document, or validating whether a document works for readers. Use a more specialized document skill when the requested artifact is a product-doc suite, technical tutorial, or API reference.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Improve source-code understanding with useful comments, API docs, or focused docs without changing behavior. Use when the user asks to document code, add comments or docstrings, or run a documentation pass over code or a diff; not for explanation-only requests.
Help agents write correct, production-ready TypeScript using `@contentstack/delivery-sdk` for Contentstack entries, assets, references, filtering, sorting, pagination, locale, Live Preview, and Visual Builder support. Verify SDK behavior against the Delivery SDK Spec when method names, options, or chain order matter. Use when a user asks for Contentstack Delivery SDK code, query examples, helper functions, SDK setup, stack initialization, reference inclusion, filtering, sorting, pagination, typed entry fetching, asset fetching, Live Preview setup, Visual Builder support, SSR preview handling, or debugging SDK query chains.
Expert in optimizing the end-to-end developer journey. Specializes in Internal Developer Portals (IDP), DORA metrics, and on-call health. Use when improving developer experience, building internal platforms, measuring engineering productivity, or reducing developer friction.
CodeStable is an AI coding workflow for serious software engineering that keeps humans in the loop. Rather than centering on Agent orchestration, it organizes requirements, architecture, features, issues, and historical decisions to make development driven by Codex and Claude controllable, traceable, and continuously evolvable.
CodeStable is an AI coding workflow for serious software engineering that keeps humans in the loop. Rather than centering on Agent orchestration, it organizes requirements, architecture, features, issues, and historical decisions to make development driven by Codex and Claude controllable, traceable, and continuously evolvable.
CodeStable is an AI coding workflow for serious software engineering that keeps humans in the loop. Rather than centering on Agent orchestration, it organizes requirements, architecture, features, issues, and historical decisions to make development driven by Codex and Claude controllable, traceable, and continuously evolvable.
Use when authoring or modifying a Datex Studio editor (configurationTypeId=4, *-editor.json suffix) on a branch — single-entity view/edit screen with embedded single-result datasource, onInit/onDataLoaded lifecycle, view/edit mode toggle, and save-button gating via onFormValidateFlowConfig. Triggers: "create an editor", "build a detail screen for X entity", "view/edit a single record", "add a field to xxx_editor", "add save/cancel buttons", "$editor.entity is undefined in onInit", "save button never enables".
Add access-controlled, end-to-end encrypted key-value storage to a canister with the vetKeys EncryptedMaps library (ic-vetkeys for Rust and Motoko backends, @icp-sdk/vetkeys for the frontend). Values are encrypted client-side under vetKeys and shared between principals with per-user access rights (Read, ReadWrite, ReadWriteManage). Use when building a password manager, encrypted notes, a secure vault, or any app that stores and shares encrypted data on-chain. Start here for encrypted storage; escalate to the vetkeys skill only for BLS signatures, custom IBE, or timelock encryption.
Manage eSIM Access API operations including balance checks, package listing, order creation, eSIM status monitoring, top-ups, cancellations, profile management, webhooks, and refund/reissue workflows. Use when user mentions eSIM, ICCID, data plan, roaming, SIM card, mobile data package, travel connectivity, cellular data usage, or interacts with the eSIM Access API at api.esimaccess.com. Also trigger when user asks about balance, top-up, order status, QR code provisioning, or uploads a list of ICCIDs or order numbers.
Web toolkit powered by Exa, tuned for scientific and technical content. Use this skill when the user needs to search the web or fetch/extract URL content. Covers: web search (semantic lookups, research, current info — with optional research-paper category and academic domain filtering) and URL extraction (fetching pages, articles, academic PDFs in batch). Use this skill for web-related tasks when the user wants high-quality search or scholarly filtering via category=research paper. Triggers on requests to search, look up, fetch a page, or extract an article.
Export Figma variables to design token files in DTCG, CSS custom properties, Tailwind v4/v3, SCSS, TypeScript, JSON, Style Dictionary, or Tokens Studio. Use when the user wants to pull design tokens OUT of Figma into code — triggers: 'export tokens', 'export Figma variables', 'generate CSS variables from Figma', 'turn my Figma variables into a tokens.json / Tailwind config / SCSS', 'sync design tokens to code'. Works on ANY Figma plan (reads via the Plugin API, not the Enterprise-only Variables REST API). For the reverse direction (code → Figma) use import-tokens-figma.
Specialized agent for multi-repository analysis, searching remote codebases, retrieving official documentation, and finding implementation examples using GitHub CLI, Context7, and Web Search. Use proactively when unfamiliar libraries or frameworks are involved, working with external dependencies, or needing examples from open-source projects to understand best practices and real-world implementations.
FFmpeg CLI reference for video and audio processing, format conversion, filtering, and media automation. Use when converting video formats, resizing or cropping video, trimming by time, replacing or extracting audio, mixing audio tracks, overlaying text or images, burning subtitles, creating GIFs, generating thumbnails, building slideshows, changing playback speed, encoding with H264/H265/VP9, setting CRF/bitrate, using GPU acceleration, creating storyboards, or running ffprobe. Covers filter_complex, stream selectors, -map, -c copy, seeking, scale, pad, crop, concat, drawtext, zoompan, xfade. Do NOT use for image-only processing (use ImageMagick), live-streaming server setup (use OBS/nginx-rtmp), or NLE-style timeline editing (use a video editor).
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.