Results for “explain”

Create, update, refactor, explain, or review Semantic Kernel solutions using shared guidance plus language-specific references for .NET and Python.

Explains MariaDB's REPLACE statement: its delete-then-insert behavior, when it triggers, data-loss risks, and the upsert alternative. Use when writing or reviewing REPLACE statements.

Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.

Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.

Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.

Create, update, refactor, explain, or review Microsoft Agent Framework solutions using shared guidance plus language-specific references for .NET and Python.

Explains MariaDB Connector/R2DBC specifics for writing reactive Java code: URL scheme, placeholder binding, lazy execution, consume-once results, transactions, pooling, and error handling.

Explains Next.js App Router architecture with file-based routing, layouts, loading and error states, dynamic routes, and route handlers.

Explains how to define and use tools with the Claude API, including tool schemas, tool choice, and server-side tools for code execution and web search.

Use this skill to explain to customers/sales prospects why FMCSA CSA scores are not available in real-time. Covers the SAFER refresh cycle and what 'real-time' actually means for CSA data.

Explains foundational concepts of context engineering: what context is, attention mechanics, the U-shaped attention curve, and why context quality matters more than quantity.

Explains MariaDB's three CREATE FUNCTION forms — stored functions, stored aggregate functions, and loadable UDFs — covering syntax, privileges, and behavior differences for writing or reviewing MariaDB SQL.

Explains MariaDB-specific SET TRANSACTION behavior, including scope rules, isolation levels, and innodb_snapshot_isolation conflict detection, to help write correct transaction statements and retry logic.

Produces a maintainer-grade review of a pull request or large contribution, explaining the change tutorial-style and delivering a polished HTML or Markdown report with a concrete merge recommendation.

Explains MariaDB Connector/C's `mysql_`-prefixed API, connection setup, result handling, prepared statements, and transaction behavior for writing or reviewing C code that talks to MariaDB.

Comprehensive Stata reference for writing correct .do files. Covers syntax, options, gotchas, and idiomatic patterns. Use this skill whenever the user asks you to write, debug, or explain Stata code. Generates ready-to-run .do files for the user to execute manually.

Explains MariaDB explicit table locking (LOCK TABLES/UNLOCK TABLES) and named user-level locks (GET_LOCK family), covering alias traps, implicit commits, and multi-lock semantics for writing or reviewing locking code.

Explains MariaDB Connector/Node.js specifics: Promise vs Callback API, placeholders, BigInt handling, batch inserts, query streams, pooling, transactions, and prepared statements, for writing or reviewing Node.js code that uses the `mariadb` package.

Explains MariaDB Connector/J JDBC driver behavior: auto-registration, URL schemes, prepared statement handling, batch inserts, transactions, fetch sizes, pooling, and failover. Use when writing or reviewing Java code that talks to MariaDB with the mariadb-java-client driver.

Explains MariaDB-specific CREATE INDEX and DROP INDEX syntax, including mapping to ALTER TABLE, prefix lengths for TEXT/BLOB, lack of expression indexes, real descending indexes, IGNORED indexes, and index kinds. Use when writing or reviewing index statements for MariaDB.

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: create a tour, onboarding tour, architecture tour, PR review tour, explain how X works, vibe check, RCA tour, contributor guide, or any structured code walkthrough request.

Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and stops as a concrete outcome the reader could observe rather than as a mechanism. Use when a skill is about to ask a person a question, stop for an input, or explain a technical consequence to someone who will not open the code. Governs what a run says to a person in a turn, where readability-guidance governs the shape of a written deliverable. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Carries guidance only and adds no self-check step.

Write the context brief a first-time tester gets before testing an app, tool, codebase, or product — it explains WHAT the thing is and why it exists, while deliberately withholding HOW anything works. The companion to the fresh-eyes skill; the brief it produces is the "starting information" handed to a fresh-eyes tester. Use this whenever the user is preparing a fresh-eyes or first-time-user test and needs the setup material, or says things like "describe my app without giving anything away", "write the context card for the tester", "explain what it is but not how to use it", "set up the newcomer test", "what would the tester be told going in?", or wants a spoiler-free description of their product. Also use it when someone asks for the briefing/intro that a new tester, new hire, or evaluator should receive before first contact with the thing being tested.

Teleological physiology analysis framework for understanding biological systems through multi-constraint optimization. Use when analyzing physiological mechanisms, explaining apparent biological "inefficiencies", preparing for medical examinations (CICM/ANZCA Primary), understanding why biological systems are designed the way they are, or when seeking deeper mechanistic understanding beyond descriptive knowledge. Triggers on questions like "why is X designed this way", "what purpose does Y serve", "how is Z optimized", analysis of physiological trade-offs, or exploration of evolutionary/design constraints.

The living embodiment of WinDAGs V3 — the AI orchestration platform where agents accumulate genuine expertise. Knows the full constitution, convention process, tradition positions, behavioral contracts, and derivative documents. Advises on architecture with ADR provenance, explains decisions with tradition attribution, grows source material as we build. Activate on "windags", "WinDAGs", "constitution", "convention", "why did we decide", "what does WinDAGs say", "how should we build", "architecture decision", "tradition", "behavioral contract". NOT for building specific DAGs (use windags-architect), creating individual skills (use skill-architect), or managing skill libraries (use windags-librarian).

Give a decisive, project-grounded point of view in the subject's own shape: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a user-supplied approach set. Use for a solo POV, a mid-session second opinion, a named-peer cross-check, any request to consult other models or reconcile their opinions, an `oracle` panel, or a correction-cost-gated proactive cross-check offer. Not for findings review (use ce-doc-review), neutral explainers, or generating options (use ce-ideate or ce-brainstorm).

Walks a person through code changes one step at a time in conversation, starting at the entry point and following the flow that changes, showing a small chunk per step and explaining it in plain language. Defaults to the current branch's changes, and walks the code from the perspective of any context provided instead — a file, directory, symbol, pull request, plan, or ticket. Use when someone wants to be walked through, taught, paced through, or shown around code or a branch step by step, or to learn how a change works before reviewing or extending it. Stops after every step and waits, so the learner sets the pace. Paces through code that already exists and builds nothing — to build new work while being paced through it, use pairing. Does not produce a written overview to read alone — use code-overview. Does not review code quality — use code-review. Does not diagnose bugs — use investigate.