Use when addressing PR review threads on a GitHub PR — replying to review comments, resolving threads after fixes, looping through reviewer feedback, applying or counter-proposing suggestion blocks, sweeping outdated threads, checking PR mergeability, or discovering which PRs are open on a repository. Applies when the `spn` CLI is on PATH (`command -v spn`). Prefer spn over hand-rolled `gh api graphql` for review-thread work.

Draft user-facing Minutes release notes for a version from the commit range, recent GitHub releases, and the repository release checks. Use when the user asks to write, generate, prepare, revise, or review release notes or a changelog for a Minutes version.

Trace CrewAI crews and flows with Maple: OpenInference CrewAI instrumentor plus the model-SDK instrumentor, GenAI dual-write, one Maple Agent Session per conversation with transcript, model and tool calls, tokens, failed tools and one lane per agent. Triggers on 'trace my crewai agent', 'add Maple to crewai', 'agent sessions for crewai', 'OpenTelemetry for crewai'.

Trace Claude Agent SDK agents (TypeScript and Python) and Claude Code CLI sessions with Maple: configure Claude Code's built-in OpenTelemetry so each conversation becomes one Maple Agent Session with prompts, model calls, tool calls and tokens. Triggers on 'trace my claude agent sdk agent', 'add Maple to claude agent sdk', 'agent sessions for claude code', 'OpenTelemetry for claude agent sdk', 'send my claude code sessions to Maple'.

Enzyme kinetics — Michaelis-Menten Km, Vmax, kcat (turnover), and kcat/Km (catalytic efficiency / specificity constant) from substrate-velocity data, plus inhibition-mechanism analysis (competitive / uncompetitive / non-competitive, Ki). Fits the MM equation by nonlinear regression (and reports Lineweaver-Burk for reference). Use when you have substrate concentrations and initial reaction velocities and need kinetic parameters or to classify an inhibitor. NOT for BRENDA database lookups of published constants (use the BRENDA tools).

Dereplicate a putative natural product and assign its chemical taxonomy. Use to answer "is [compound] a known natural product", "what microbe/organism produces [compound]", "what chemical class is [compound]", "dereplicate this metabolite (by formula/exact mass/InChIKey/SMILES)", or "classify this molecule into ChemOnt". Searches NPAtlas for known microbial natural products (producing organism + literature reference), assigns the ChemOnt kingdom→superclass→class→subclass hierarchy via ClassyFire, resolves systematic IUPAC names to structure via OPSIN, and cross-references identity in PubChem. NOT for general drug/compound identity or ADMET (use tooluniverse-chemical-compound-retrieval / tooluniverse-small-molecule-discovery) and NOT for metabolomics pathway/enrichment analysis (use tooluniverse-metabolomics skills).

Use when authoring the **non-layout** parts of the MPS editor aspect — what happens when the user types, presses a key, triggers completion, pastes, or invokes a context action. Covers action maps (`CellActionMapDeclaration`), cell keymaps (`CellKeyMapDeclaration`), transformation menus (`TransformationMenu_Default` / `_Named` / `_Contribution`), substitute menus (`SubstituteMenu_Default` / `SubstituteMenu` / contributions), side transforms (LEFT/RIGHT), legacy cell menus, paste wrappers and copy-paste handlers (in the actions language), completion styling, reference presentation, two-step deletion, and the editor selection API. Trigger terms: `actionMap`, `keyMap`, `delete_action_id`, `transformationMenu`, `substituteMenu`, `Ctrl+Space`, `Ctrl+Alt+B`, side transform, paste wrapper, completion styling, `PasteWrappers`, `CopyPasteHandlers`. For the **layout** side (cells, layouts, style sheets) use `mps-aspect-editor` instead.

Select the best MetaTrader 5 trading robots (Expert Advisors) that have not been backtested yet, by running the MT5 Strategy Tester from the command line through a 3-round pipeline. Use when the user wants to batch-test MT5 bots/EAs, screen robots across all symbols, optimize EA parameters, or move candidate bots to finalists based on profit, drawdown, positive months/years and equity-curve criteria. Runs terminal64.exe headless; Windows + MetaTrader 5 required at run time.

Use this skill when the user asks for online music reference metadata, artist, album/release, release-group, or recording lookups, Wikipedia summaries, MusicBrainz identifiers, release dates, labels, source URLs, or external music metadata after Plex is insufficient or when the question is not about local availability. This skill uses Wikipedia and MusicBrainz public read-only APIs through bundled scripts. Do not use this skill to claim that music exists in Plex, fetch lyrics, stream or download music, submit MusicBrainz data, or edit metadata.

Trigger whenever the user wants to do anything with a real email account: check inbox, read messages, reply, forward, compose, send, search, archive, delete. Typical phrasing: "check my inbox", "what did X send me", "查下我邮箱". **Do not use for**: instant messaging / IM / WeChat / Slack, translating text that merely contains the word "email", or offline parsing of `.eml` files (→ just use Read).

Triggers when the user asks about settings, preferences, API keys, model switching, theme / language / shortcuts / proxy / backup, or related failures (key invalid, model not found) within the OpenLoaf desktop product — where to configure and how to configure them. **Not for**: code configuration files inside a project such as tsconfig / .env (→ use Read/Edit directly), general programming questions (→ answer directly), or system-level OS settings.

Builds a Claude Code statusline from scratch or extends an existing one. A statusline is a live status bar that runs a shell script after every Claude response and displays data — security scans, git status, API quotas, build state — directly in the session. Use this skill when the user says "create a statusline", "make a statusline for X", "add X to my statusline", "show Y in the status bar", "build a statusline plugin", or "I want live data in my Claude session". Trigger even if the user just describes wanting live feedback during a Claude session without naming "statusline" explicitly. The skill drives from idea to a working, installed, tested statusline without requiring the user to direct every step.

Test-driven development workflow using red-green-refactor cycles with integration tests at service boundaries and property-based testing. Use when the user explicitly requests TDD, test-first development, write tests first, unit tests, red-green-refactor, or property-based testing approaches.

Use when designing new screens, redesigning existing UI, creating visual concepts, or improving interfaces in Nicolify. Executes a 7-phase creative Design Thinking workflow: defines user personas, frames problems, audits existing components (Shadcn UI + Tailwind CSS v4 + FSD architecture), researches SaaS UI patterns, proposes multiple distinct layout paradigms with ASCII wireframes and HTML mockups, iterates through dialogue, and delivers a complete UI-SPEC.md with component trees, data flow, responsive behavior, and interaction patterns — all following Nicolify's design tokens and codebase conventions. Triggers: 'diseña', 'rediseña', 'nueva pantalla', 'concepto visual', 'propuesta de diseño', 'UX', 'layout', 'prototipo', 'mejora la interfaz', 'wireframe', 'mockup', 'esquema de color', 'componentes de pantalla'.

Live verification of frontend changes in dev-app.nicolify.com using Chrome DevTools MCP from WSL2. Use when: verifying a frontend bug fix, reproducing a user-reported UI bug step-by-step, checking real-time SSE/polling behavior, validating card/form interactions, inspecting DOM or console or network live, or any task where 'me lo muestres en el navegador' would be cheaper than guessing. Triggers: 'verifica en el navegador', 'prueba con chrome-devtools', 'reproduce el bug en vivo', 'abrí el navegador', 'chrome-devtools-mcp', 'live test', 'verify UI fix'.

Select electronic components and build a procurement-ready BOM with real LCSC/JLC supplier evidence (stock, price, datasheet). Use after the PRD stage and before PCB design. Provides parts_search.py (jlcsearch API) and bom_validate.py (schema gate).

Parametric CAD modeling with build123d (Python) - enclosures, mechanical parts, assemblies. Builds a scene from cad/parts/*.py, exports STEP/GLB, renders PNG views for visual self-review, and prepares STL/3MF for printing. Use after PCB release (or directly for non-PCB products).

Delegate a hard decision or conundrum to the Kyotee harness engine — a cross-vendor Council that debates to consensus, a Two-Brain divergent/ convergent debate, or a forced tool-checking solo run. Use when a decision is high-stakes, genuinely contested, or benefits from multiple model perspectives, and you want a synthesised answer (with dissent noted) back in this session. Requires a running kyotee engine (see setup).

Turn one finding from a conformance sweep into a small pull request that brings the code back in line with the team standard it cites. Use as the action for a `tessl:finding.created` trigger on the conformance-sweep loop.

Carry a factory pull request through review by resolving review comments and failed checks on its existing branch, until it is ready for a person to merge or needs one to decide. Use as the action for review, review-comment, `@factory` conversation and failed-check triggers on `factory/` branches.