Skills
99,448 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Receive and verify Notion webhooks. Use when setting up Notion webhook handlers, debugging Notion signature verification, completing the verification_token handshake, or handling workspace events like page.content_updated, page.properties_updated, comment.created, or data_source.schema_updated.
Use for OpenHarmony build execution and diagnosis, including 编译OpenHarmony/完整代码/测试/SDK/host/最小模拟器/全量模拟器/部件独立编译/测试列表, plus full product builds, targeted component/test builds, fast rebuilds, hb independent builds, and build.log failure analysis.
OpenTelemetry in Python — SDK setup, declarative config, zero-code instrumentation (opentelemetry-instrument, opentelemetry-distro), contrib auto-instrumentation, manual API, performance tuning, breaking changes. Use when configuring or troubleshooting OpenTelemetry in a Python service. Triggers on "setup otel in python", "python telemetry", "python tracing", "opentelemetry-instrument", "opentelemetry-distro", "TracerProvider python", "MeterProvider python", "FastAPI/Flask/Django otel", "python logging bridge".
DOM-free multiline text measurement and layout using @chenglou/pretext. Use when the user needs text height calculation, virtualized list row sizing, canvas/SVG text rendering, rich-text inline flow, or any scenario involving text layout without DOM reflow.
Двусторонняя сверка кода и графа — уборочный такт: всюду ли код соответствует графу, а граф — коду; конец каждой сущностной задачи. Триггеры: reconcile, «сверь код с графом», «приведи граф в порядок», «протки свою область», «отдай долги графа», does the graph match the code, tidy the graph. Также: задача, записанная крией; феномен-ярлык состояния; комментарий-портянка, пересказывающая граф. Distinct from weaving (ремонт графа изнутри), integrity (claim-аудит), reality-audit (поведенческие заявки). Композирует entry, writing, weaving. Нужны тулы iskron_*.
Provider-independent production workflow for assembling generated or sourced media into React/Remotion videos. Use when an agent must plan, build, render, review, variant-render, or hand off Remotion compositions with media custody, captions, audio, animation, accessibility, provenance, QA, and delivery requirements.
Validates locally (`robomotion validate`) then executes a Robomotion flow on a robot (`robomotion run <flow-dir>`), tailing the agent-mode JSONL session log to drive a validate → run → observe → fix loop with bounded retries. Use when the user says "run the flow", "start on robot X", "trigger this on the robot", "test on a robot", or "deploy and run".
Initialize Spec-Driven Development context in any project. Detects stack, conventions, and bootstraps the active persistence backend. Trigger: When user wants to initialize SDD in a project, or says "sdd init", "iniciar sdd", "openspec init".
Finds Robomotion packages, nodes, and templates via the `robomotion` CLI, which is backed by Bleve full-text search with fuzzy matching and semantic expansion. Use when the user asks to find a package, explore templates, discover what nodes exist for a task, or check exact property names before writing a flow.
Read-only cross-artifact consistency check across spec.md, plan.md, and tasks.md, ideally by an agent that did not write them. Detects coverage gaps, conflicts, FRAMEWORK.md violations, and plan claims about the code that do not hold, before implementation begins
RUNTIME skill — use when implementing the runtime side of Stigg — gating feature access (`hasAccess`, `getMeteredEntitlement`, `getBooleanEntitlement`, `getEntitlement`), reporting usage (`reportEvent` for raw events vs `reportUsage` for calculated measurements), promotional entitlements, and configuring local caching / fallback so checks stay reliable when Stigg is unreachable. Triggers include "gate this feature with Stigg", "check entitlement", "is the customer allowed to", "hasAccess", "feature flag with Stigg", "report usage to Stigg", "report a usage event", "increment usage", "events.report vs usage.report", "Stigg fallback strategy", "Stigg cache", "Stigg sidecar", "Stigg goes down", "Stigg offline", "stale entitlements", "promotional entitlement", "grant a one-off entitlement". Skip for catalog modeling (stigg-pricing-modeling), subscription lifecycle (stigg-subscriptions), or generic feature flags with no Stigg integration (e.g., LaunchDarkly).
TanStack Query v5 performance optimization for data fetching, caching, mutations, and query patterns. This skill should be used when using useQuery, useMutation, queryClient, prefetch patterns, or TanStack Query caching. This skill does NOT cover generating query hooks from OpenAPI (use orval skill) or mocking API responses in tests (use test-msw skill).
Technical blog post writing with structure, code examples, and developer audience conventions. Covers post types, code formatting, explanation depth, and developer-specific engagement patterns. Use for: engineering blogs, dev tutorials, technical writing, developer content, documentation posts. Triggers: technical blog, dev blog, engineering blog, technical writing, developer tutorial, tech post, code tutorial, programming blog, developer content, technical article, engineering post, coding tutorial, technical content
Generate authored procedural trees, grass, ivy, flowers, and vegetation in Three.js or raw WebGPU. Use for surface-following vines, painted ivy paths, stylized or GPU grass, GPU-culled virtual flower fields, trunks, recursive branches, roots, canopies, leaf cards, species presets, deterministic growth, distance-tiered plant geometry, and rooted blade, stem, or petiole-hinge wind.
Build production analytic and bounded water in Three.js. Use for luminescent shallow-water rivers with coupled flow, bioluminescent excitation, advected foam and RGB caustics, photoreal shallow water with gravity-capillary FFT waves, dispersive caustics and diffraction glare, shared multi-wave displacement and normals, bounded RGBA heightfield pool simulation, local drops, object-driven ripples, differential-area caustics, ray-traced pool/water/sphere volume optics, derivative-filtered normal bands, analytic sky reflection, side-aware Fresnel, heuristic screen refraction, Beer-Lambert absorption, and crest foam.
Build apps with the TomTom Maps SDK for JavaScript (@tomtom-org/maps-sdk). Use when working with TomTomMap setup (including the map attribution — its TomTom and OpenStreetMap logos, which the license keeps on screen, their corner and padding, and the soft backdrop behind them with attribution.backdrop — and adding your own credits with attribution.credits, transformRequest to hold or rewrite map requests, the MapLibre web worker it registers for Vite builds, registerMapLibreWorker, and a map that stays blank under webpack, Next.js with Turbopack, or a re-bundling CDN because the worker doesn't load), MapLibre integration (map.mapLibreMap, and when to prefer SDK features over raw MapLibre), custom layers drawing a three.js or raw WebGL scene in metres around a place, aligned with the map through localFrameMatrix, placed under the 3D buildings and kept through style switches with map.addCustomLayer and the lowest3D anchor, and their objects made clickable and hoverable with a hitTest, instancing many moving objects (the three-buffer ring for ANGLE on Direct3D 11), BaseMapModule (showing or hiding layer groups such as 3D buildings and road shields, and road markings such as arrows and exit numbers, and its own 3D buildings hovered, clicked and coloured by id with buildings3D.hover, buildings3D.click and setBuildingColors, and buildings highlighted by place with getBuildingIdAt) and its settings as data with baseMapKnobCatalogue, setting, reading and resetting any module knob by id with setKnob, setKnobs, getKnob and resetKnob (StylingFoundationsModule and MapEffects too) and when to use them rather than applyConfig and updateConfig and checking a value with validateKnobValue, TerrainModule (hillshade and its look, 3D terrain elevation and exaggeration, every setting as data with terrainKnobCatalogue), and viewport utilities; geopolitical views of disputed territories and borders (the global `geopoliticalView`, `geopoliticalViews`, setGeopoliticalView, and which views each API serves with servesGeopoliticalView and GeopoliticalViewAPI); map styles, standard style IDs (standardStyleIDs, streetLight, streetDark, streetLightDriving, streetDarkDriving, monoLight, monoDark, streetSatellite), setStyle and StyleChangeHandler, style switcher; semantic map styling with StylingFoundationsModule (label/icon/road size knobs, the typeface of every map label from the style's serif and italic faces or your own font files with labels.customTypeface, globe projection and sky, the light on 3D buildings and reading it with getMapLight, rounded building corners, the stylingFoundationsKnobCatalogue, raw style-layer edits through layers.query and LayerSelection (exact layer ids, paint and layout derived from the style's or a knob's value, addFilterClause to narrow a layer's filter), while the POI, traffic and hillshade looks sit on POIsModule, the traffic modules and TerrainModule; map presets with applyMapPreset and mapPresetCatalogue; reading any style colour by its map-wide id with getStyleColor and styleColorKnobIds; theming the map from a website's colours, a CSS stylesheet, an image, a palette description or an artist's style with the map-theme plugin's deriveMapColors, mapColorsLightDark, deriveMapColorsFromCss and deriveMapColorsFromImage, and the accent colour routes, geometries and places follow — colors.accent, map.mapColors), recolouring the base map with setMapColors, switching it between day and night looks, and exporting the result with exportStyle, and the map-effects plugin (bloom and its bloom.only colour scope, glare that makes lights cast streaks like street lamps through a lens with glare.only, tint, grade, vignette, fog and the colour of its air with fog.color, depth of field, capture, your own GLSL passes with addPass, their vec3 and vec4 uniforms, textures and mipmapped, and your own 2D canvas layers between the overlays with addLayer and removeLayer, for paper, film grain or a watermark); flying a camera along a route with the flyover plugin (RouteFlyover, aim ahead, junction framing, terrain clearance, where the followed position sits on screen with anchorForPitch, the marker that follows the route with setMarker, flying it once to the destination with loop: false and onArrive, and seeking it by time or distance); editing a route by dragging with the route-dragging plugin (RouteDragging, an editable route whose stops move by their pins and gain new ones pulled off the route line, re-planned live while you drag every planIntervalMS with the answers in order, and handed to your own state with showOnMap: false, onWaypointsChange and onRoutes); 3D landmarks and buildings with the landmarks-3d plugin (Landmarks3D models of recognizable buildings, its KTX2 transcoder and transcoderPath, in their own textured colours with the texture knob, and Buildings3D, the base map's buildings in 3D with windows, lit windows at night, reflective glass, a sun and shadows, road names or POIs hidden behind them, their walls, roofs and the landmarks coloured from palettes of your own colours, picked or blended, each a shade of its own with variation, and single buildings and landmarks hovered, clicked and coloured by id with buildings.events, landmarks.events, setBuildingColors and setLandmarkColors, and their knob catalogues read from landmarks-3d/knobs without loading three.js); textures on the map's water, land cover and roads with the Landmarks 3D plugin's GLSurfaces (gl-surfaces, waves that mirror the sky, tree crowns, 3D trees, grass, field parcels, dunes, glaciers, scrub, mud flats, shingle, rock, paving, built-up ground and asphalt, all following 3D terrain, coloured for a season with surfaceSeasons, the light and wind they follow, sharing the map's light and the buildings' shadows with Buildings3D, every look as data with glSurfacesKnobCatalogue); user interaction events (click, hover, contextmenu, recently-hovered, dragging a feature with dragstart, drag and dragend, such as a waypoint, a place pin or a route line to pull a new stop onto, the pointer leaving a feature with no leave event, clicks and hovers on the rest of the map with BaseMapModule, changing their timings with updateEventsConfig), selecting and highlighting features yourself and reading which are selected with setEventState, clearEventStates and getEventStates on every data-owned module and module lifecycle events, and saving and replaying a module's display configuration as JSON (the *SerializableConfig types); search, geocoding, reverse geocoding (ReverseGeocodingResponse, which has no properties where nothing matches), autocomplete, search-box suggestions of places, brands and categories with getSearchSuggestions(), discovering places with discoverPlaces() (categories in words with filters.poiCategoryQuery, or resolved first with resolvePOICategories) and place details with getPlaceDetails(), area outlines with geometryData (PlaceGeometryProps), places and POIs (PlacesModule and its markerType, color, label and icon.opacity, where its pins and connections sit in the layer stack with PlacesBeforeLayerConfig, every places setting as data with placesKnobCatalogue, POIsModule and poisKnobCatalogue, hiding single POIs by id with filters.ids, custom icons and pins per POI category on the map's own POIs and on shown places with categoryIcons), clustering them with the pin-clustered marker type, drawing their entry points, which results PlacesModule.show() takes and what it adds to them (preparePlacesForDisplay), and a popup or result card on a clicked place, fuzzy search (FuzzyLevel), geometry and along-route search, all through discoverPlaces (route, maxDetourTimeSeconds, sortBy, each result's detourTimeInSeconds and detourDistanceInMeters), search filters and cursor pagination, geographic bias with geoBias, and EV charging stations (charging stations, charging points and connectors on search results); routing and calculateRoute (RoutingModule), a departure or arrival time with when (departAt, arriveBy), at a local wall-clock time with localDateTime, the route's color, widthPreset, widthFactor, opacity, waypoints.sizePreset and waypoints.sizeFactor, waypoint pins per role (start, stop, finish), stop numbering in numbers or letters, waypoint labels and hover growth, waypoint icons of your own or a POI category pin per stop, waypoints versus places (who draws a route's stops), every routing setting as data with routingKnobCatalogue, route alternatives and what sets each apart (the distinct sections no other route drives, getDistinctSections, DistinctSectionProps, DistinctSectionsOptions, and the roads each takes by road number, getImportantRoads, ImportantRoad, ImportantRoadsOptions, and the ferries, tolls and traffic on them or what an alternative adds and avoids against another route, getSectionsWithin, SectionsWithin, SectionsWithinOfType, SectionsWithinOptions, getSectionOverlap, RouteSpan, and why the live route avoids the usual one's jams and closures, compareRoutes, RouteComparison, CompareRoutesOptions), the route summary bubbles (what they say, the time against the selected route, which routes carry one and where they sit, their colour, typeface and zooms), which vehicle and truck parameters routing accepts, turn-by-turn guidance instructions and the lanes to take at each (getInstructionLanes), route sections including toll and charged roads (the default ones as defaultSectionTypes, to add to), the curves and curvy stretches of a route with their turn radius, heading change and severity, for keeping clear of winding roads (motion sickness) or seeking them (motorbiking), with getCurveSections, getCurvyStretchSections and isHairpin (hairpinCount), the tight ones drawn with a kerb (sections.curve.kerb), their thresholds set with calculateRoute's curveDetection or tried again on routes already calculated with withCurveSections, ringing a leg or any section from your UI with setSectionFocus, speed limits and the tunnel and closed-to-vehicles signs, border crossings between country sections, and reachable ranges (isochrones) with ReachableRangesModule, its bands coloured from the map's accent and land or your own palette, faded band by band with fill.outermostOpacityFactor, every setting as data with reachableRangesKnobCatalogue; GeometriesModule (color, your own fill colours with fill.palette, cycled or ramped with fill.paletteMode, dashed or dotted borders with line.pattern, fill.style, label, lineLabel, every setting as data with geometriesKnobCatalogue); traffic flow and incidents faded with opacityFactor, incidents in a bbox or a polygon and their icons (isIconsVisible), planned incidents (timeValidity) and the highlight of a focused or hovered incident (IncidentHighlightConfig), the other incidents dimmed while one is focused (highlight.unfocusedOpacityFactor) and its lines faded with line.opacity (IncidentLineConfig), and area analytics, and their settings as data with trafficAreaAnalyticsKnobCatalogue and the other traffic knob catalogues; custom GeoJSON layers and bring-your-own-data (CustomGeoJSONModule, BYOD, its settings as data with customGeoJSONKnobCatalogue, and colouring areas by the median or mean of your points per hexagon, square or district with aggregateIntoCells); and the agent-toolkit plugin for conversational map agents (createMapAgent, LLM tools, custom tools with locatePlace and getViewportBias, the user's location precision with createGetCurrentLocationTool, the opt-in executeMaplibreCode tool with createExecuteMaplibreCodeTool, the generated-code sandbox and the page CSP it needs with getCodeExecutionMode and allowMainThreadFallback, Vercel AI SDK). Also covers core Place/Route types and importing GeoJSON types such as Position from geojson (@types/geojson under pnpm), service config and a per-call retry, cancelling in-flight service calls with an AbortSignal and keeping only the latest one with createLatestRequest (search-as-you-type, refetch on map move, stale responses, race conditions, debounced input, and showing each answer of requests that start faster than they answer with supersede: 'on-answer') and the SDKError/SDKServiceError/SDKAbortError classes, their SDKErrorCode codes and the ServiceName in error.service (a 401 rejected key versus a 403 key not allowed an API or domain, and the Private Preview access such as Calculate Reachable Range or the 3D Landmarks tiles that a key lacks, read from apiErrorCode and privatePreviewAccess on services and the map alike), map failures (TomTomMapError, addErrorHandler, WebGL unsupported or context lost, rejected API key, a refused style or tile, Landmarks 3D tile errors), ViewportPlaces onError, and utilities such as bboxFromGeoJSON, bboxFromCoordsArray, isBBoxWithArea, getPosition, formatDistance, and formatDuration. Before integrating any SDK feature in Public Preview or Private Preview, plugins included (every plugin below 1.0.0 is in Public Preview, or in Private Preview where its doc says so), it shows the developer a preview notice and asks them to confirm. At the start of SDK work, it offers the developer the tomtom-maps-sdk-js-feedback skill, which reports what the SDK got wrong to TomTom with the developer's consent.
Provides comprehensive uni-app-x component and API integration guidance. Use when the user needs official uni-app-x components or APIs, wants per-component or per-API examples, or needs cross-platform compatibility details for uni-app-x.
Helps engineering managers work effectively with Software Architects, Staff Engineers, and Principal Engineers — covers the EM's side of the relationship (responsiveness, proactive consultation, giving credit), how to advocate for architect time, pre-consultation preparation, and the two architecture team models (Centralized vs. Decentralized). Use when the user says "architect," "staff engineer," "principal engineer," "technical design review," "working with senior technical people," "getting architecture help," or "how do I get more architect time." Do NOT use for managing staff/principal engineers who report directly to you (use `managing-high-performers` or `delegation`).
Expert skill for understanding, using, and modifying the xanoscript_docs documentation system in the xano-developer-mcp project. Use this skill whenever working with XanoScript documentation files (.md files in src/xanoscript_docs/), modifying the xanoscript_docs MCP tool, adding new documentation topics, editing existing docs, updating the topic registry in xanoscript.ts, or changing how documentation is served. Also use when someone asks about the xano-developer-mcp project architecture, the MCP server setup, or how the documentation delivery system works. Trigger on any mention of xanoscript_docs, XanoScript documentation, Xano MCP tools, or documentation authoring for this project.
Map player input (keyboard, mouse, touch, gamepad) to game logic with the @pmndrs/viverse action/binding system. Use when building movement controls, input handling, or custom state/event actions for a Three.js game, or when controls must change across game modes (menu, play, pause, cutscene) — e.g. pointer-lock controls wrongly stay live during a menu and a button click locks the pointer.
Use when the user asks about Volcano Ark model information documentation or model selection, or requests model upgrades/migration, or model inventory/replacement risk analysis for code projects. For actual deployment, Endpoint management, account resources, usage, billing, authentication, or real calls, use it only to route to the corresponding arkcli skill.
Star the ax repo, file an issue / bug report, or fork-and-open-a-PR against github.com/Necmttn/ax on the user's behalf, by shelling out to the `gh` CLI. Triggers when the user says "star ax", "star the repo", "I want to support ax", "report this as an ax bug", "file an ax issue", "open an issue on ax", "this looks like an ax bug", "I want to contribute to ax", "fix this in ax", "open a PR against ax", or after an unhandled ax error when the user wants to report it. Acts only on an explicit user request - proactive star prompting is handled deterministically by the CLI (`ax star`), not this skill. Confirms before any account-mutating action (never stars without an explicit yes); falls back to a plain GitHub URL when `gh` is missing or unauthenticated. Do NOT auto-trigger on unrelated GitHub work or other repos.
Production-grade Bootstrap 5.3 patterns for building modern, responsive web UIs in HTML and ASP.NET Core Razor Pages/Views. Use when creating or styling web pages, layouts, navigation, forms, cards, modals, tables, or any UI component with Bootstrap 5. Covers the grid system, responsive breakpoints, utility classes, color modes (dark/light), accessibility, and integration with ASP.NET Core tag helpers and Razor syntax. Trigger on any task involving Bootstrap CSS classes, responsive HTML layouts, Razor Page UI design, or front-end styling for .NET web applications.
Use this skill when an LLM should act inside a business process — choosing tools or next steps, calling systems, handing off to people — with guardrails, human review, or an audit trail, even if Camunda isn't mentioned, and before hand-coding an agent loop. Models Camunda 8 AI Agent sub-processes: tools as BPMN tasks, fromAi() parameters, prompts, and limits. Also covers v1/v2 element-template selection and upgrading v1 elements to v2.
This skill should be used when the user asks to "triage coderabbit", "check coderabbit comments", "analyze coderabbit review", "fetch coderabbit findings", "coderabbit PR", "review coderabbit suggestions", "run coderabbit review", "coderabbit review", "review with coderabbit", or mentions analyzing CodeRabbit PR comments or running CodeRabbit CLI review locally.
Verify and classify Comet GitHub issues against the current repository contracts, source, Runtime, tests, and install behavior. Use when the user asks whether an issue is real, reproducible, a duplicate, already implemented, a configuration problem, or suitable for follow-up.
Review Comet community PRs read-only and evidence-first, including the latest diff, linked issues, review thread status, mergeability, and CI. Use when the user asks to review a PR, judge whether comments are still valid, or prepare concise merge-blocking comments.
Parallel C++ Core Guidelines code review using multiple specialized sub-agents. Use when reviewing C++ code, modules, or files against C++ Core Guidelines to identify violations. Each sub-agent reviews against a specific guideline section (Functions, Classes, Resource Management, etc.) and outputs findings to separate markdown files in the review/ directory, followed by a consolidated summary.
Use for any change to a GTK 4/libadwaita app, new or existing, whether or not the request mentions GTK. Trigger on the repo rather than the wording — if Cargo.toml depends on gtk4/libadwaita, or sources import gi/Gtk (Python) or use Gtk (Vala), this applies to every change to that app, including requests phrased purely as symptoms ("reordering doesn't work", "pressing enter should continue the list", "the window opens too small"). Covers app boilerplate and new features; behaviour bugs in drag-and-drop, context menus, keyboard and text editing, focus, selection, and window sizing; threading, signals, and lifecycle; gtk-rs calls that fail to compile; GSettings, resources, packaging, and tests. Delegates widget choice, layout, and HIG to designing-gnome-ui.
When the user wants to create technical content for developers including blog posts, tutorials, and documentation. Trigger phrases include "write a blog post," "technical article," "developer content," "tutorial," "devrel content," "dev blog," "technical writing," or "content for developers."
Guide for using direnv - a shell extension for loading directory-specific environment variables. Use when setting up project environments, creating .envrc files, configuring per-project environment variables, integrating with Python/Node/Ruby/Go layouts, working with Nix flakes, or troubleshooting environment loading issues on macOS and Linux.
Two related workflows for a locally-cloned codebase, in one skill. Documentation mode produces a single, comprehensive, verifiable architecture document primarily by reading files on disk (local-first) — use it whenever the user wants to understand, map, document, research, or onboard onto a codebase ("research this repo", "write up the architecture", "do an architecture deep dive", "document how this codebase works", "map the system design", "create an onboarding doc"). Modernization mode generates a phased plan to modernize, migrate, upgrade, or rewrite a legacy system ("modernize this", "plan the migration", "how would we rewrite this", "how do we get off this legacy stack"); if no architecture document exists yet it first runs Documentation mode, then continues straight through to the plan. It assumes the legacy stack may be dead, runs a time-boxed feasibility spike, and picks the highest achievable rung on a safety ladder instead of demanding a fully-green legacy CI gate up front.
Hunt for real bugs in the vigiles CLI/codebase with a parallel expert fan-out, then FIX them directly — source-trace each defect to file:line, add a regression test, commit per theme. Use when asked to dogfood vigiles, find/fix bugs across the CLI the source-traced way, or fan out agents to audit the tool on itself.
Find, classify, triage, re-implement and verify a source site's dynamic surface (APIs, search, forms, modals, media, tags, client-rendered and sheet-backed content) during a migration to a platform. Migration-bound — invoked by prepare-migration, replica, migrate and rollout, or standalone on an already-migrated site; never for redesign-only work.
Pattern for wrapping third-party SDK clients (Stripe, Resend, AWS, etc.) with Effect. Use when creating Effect services that wrap external libraries with Promise-based APIs. Provides type-safe error handling, automatic tracing, and clean dependency injection via the "use" pattern.
Use when drafting, rewriting, classifying, or improving code review comments as a reviewer. TRIGGER on rough review notes, requests to make comments clearer or kinder, severity labels, "how should I phrase this review comment?", "write review comments", author pushback, or turning findings into PR comments. If role is unclear, ask reviewer or author. DO NOT TRIGGER for full code review, PR descriptions, or author responses unless wording is requested.
Build, configure, flash, test, debug, and recover firmware for ESP32-family boards, including ESP-Mosaico kit bring-up, ESP-IDF C/C++, Arduino/PlatformIO, MicroPython, CircuitPython, ESPHome, Zephyr, Rust, and NuttX. Use when identifying an ESP32 board, choosing a framework, wiring GPIO or peripheral buses, integrating sensors or actuators, diagnosing serial/boot/power/network failures, planning OTA and production security, or automating hardware tests and fault injection. Do not use as a substitute for the exact board schematic, SoC datasheet, or attached component datasheet.
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.