Use before merging a branch or PR: review the diff for bugs that pass CI but break production, fix the obvious ones and ask about the rest. (gstack)
Use before merging a branch or PR: review the diff for bugs that pass CI but break production, fix the obvious ones and ask about the rest. (gstack)
Use before merging a branch or PR: review the diff for bugs that pass CI but break production, fix the obvious ones and ask about the rest. (gstack)
Use before merging a branch or PR: review the diff for bugs that pass CI but break production, fix the obvious ones and ask about the rest. (gstack)
Use before merging a branch or PR: review the diff for bugs that pass CI but break production, fix the obvious ones and ask about the rest. (gstack)
Working with the redis-docs MCP server (search / fetch / ask at redis.io/mcp) — how its index is shaped and how to read what it returns. Use when those tools are available and you are about to look something up in the Redis documentation, or when a result is confusing — fetch returned one short section instead of a page, several hits share one url, ids look like #sec:w1, metadata.version reads 1.0.0, a search came back empty, or ask was rate-limited or said the docs do not cover it. Also covers what redis.io does and does not index.
Writes, migrates, and fixes OpenAPI specs for Google Cloud API Gateway. Use when converting an OpenAPI 2.0 (Swagger) spec to OpenAPI 3.x, writing a new OpenAPI 3.x spec, or fixing a failed "gcloud api-gateway api-configs create", such as "extension is only supported in OpenAPI 2.x". Also use when quotas set with x-google-quota are never enforced, or when a backend receives path parameters as query parameters. Don't use for adding or debugging MCP tools (use api-gateway-mcp-server), backend lockdown or HTTP 429 tuning (use api-gateway-backend-security-and-rate-limiting), Cloud Endpoints, Apigee, or GKE Gateway API.
Rank open PRs for the automerge queue using eligibility tiers and AI judgment of meaningful fixes close to merge, including older PRs with screenshots and bounded requested changes. Exclude untrusted authors and apply the queue label only after human confirmation. Feeds om-auto-merge-buddy.
Rank open issues suitable for autofix and add the configured queue label only after human confirmation. Use for "triage issues for autofix", "mark issues cez-autofix", or "wybierz zgłoszenia do automatycznej naprawy". Proposes and labels; implementation belongs to om-auto-fix-issue.
Secures and rate limits backend services behind Google Cloud API Gateway across OpenAPI 2.0 and OpenAPI 3.0.x API configurations, including MCP-enabled gateways. Use when configuring API key or JWT authentication, locking down Cloud Run or Cloud Run functions backends with a gateway service account, reading authenticated claims from X-Apigateway-Api-Userinfo, setting per-project request quotas, or diagnosing HTTP 429 and HTTP 500 Service Control Quota errors. Do not use for Apigee, GKE Gateway API, Cloud Load Balancing custom domain setup, or LLM model routing.
Includes 13c Metabolic Flux, Alphagenome, Analytical Method Validation, Autoskill, Benchling Integration, Bgpt Paper Search, Biopython, Bioservices, Bulk Rnaseq, Cellprofiler, Cellxgene Census, Citation Management, Clinical Decision Support, Clinical Reports, Consciousness Council, Database Lookup, Deepspot M, Deeptools, Dhdna Profiler, Dnanexus Integration, Etetoolkit, Exa Search, Experimental Design, Exploratory Data Analysis, Folklore Variant Evidence, Generate Image, Genomic Coordinates, Genomic Intelligence, Get Available Resources, Ginkgo Cloud Lab, Glycoengineering, Hugging Science, Hypothesis Generation, Imaging Data Commons, Infographics, Iso Standards Readiness, Lab Hardware Cad, Labarchive Integration, Latchbio Integration, Latex Posters, Literature Review, Marine Carbonate Chemistry, Markdown Mermaid Writing, Market Research Reports, Markitdown, Matplotlib, Molecular Dynamics, Ncats Arax, Neuropixels Analysis, Nwb Conversion, Omero Integration, Ontology Term Resolution, Open Notebook, Opentrons Integration, Optimize For Gpu, Pacsomatic, Paper Lookup, Paperzilla, Parallel Web, Pathogen Variant Surveillance, Pathway Enrichment, Peer Review, Phylogenetics, Pkpd Modeling, Polars Bio, Pptx Posters, Primer Design, Protocolsio Integration, Pylabrobot, Pytorch Lightning, Qiime2 Amplicon, Relsa Severity Assessment, Research Grants, Research Lookup, Scholar Evaluation, Scientific Brainstorming, Scientific Critical Thinking, Scientific Schematics, Scientific Slides, Scientific Visualization, Scientific Writing, Scikit Bio, Scikit Learn, Scikit Survival, Scvi Tools, Stable Baselines3, Statistical Analysis, Statistical Power, Statsmodels, Timesfm Forecasting, Torch Geometric, Transformers, Treatment Plans, Umap Learn, Uncertainty And Units, Usfiscaldata, Venue Templates, Waypoint Bio, What If Oracle, Zarr Python
Configure singleton documents in a Sanity Studio using the document.singletons registry. Use when a developer wants a fixed-id document (settings, navigation, footer) edited in place, hidden from the default content list, with no "create new" or "duplicate" affordances — or when migrating a userland singleton implementation or a third-party singleton plugin (e.g. sanity-plugin-singleton-management) to the first-class API.
Provides guidance on the new System.Diagnostics.Process APIs introduced in .NET 11: Process.Run, Process.RunAndCaptureText, Process.StartAndForget, Process.ReadAllText/Bytes/Lines, KillOnParentExit, InheritedHandles, and StartDetached. USE FOR: starting, orchestrating, or capturing output from external processes in applications targeting net11.0 or later. DO NOT USE FOR: applications targeting .NET 10 or earlier, or basic pre-.NET 11 Process.Start usage without new APIs.
Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, OAuth server for MCP or third-party OAuth clients, passkeys, MFA, trusted domains, invalid domain, and @neon/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed Better Auth. A required plugin outside Managed support: self-managed Better Auth on a Neon Function or the existing app host. Also use for auth APIs in @neon/neon-js.
Includes Agent Email Inbox, Email Best Practices, React Email, Resend, Resend Cli
Add, configure, or review Ignite UI for Blazor Lite component support in Blazor applications. USE FOR: installing IgniteUI.Blazor.Lite or IgniteUI.Blazor.GridLite, registering AddIgniteUIBlazor() in Blazor Server, WASM, Hybrid, or split Blazor Web App projects, adding @using IgniteUI.Blazor.Controls, wiring the theme stylesheet, picking the right host page, locating the GridLite stylesheet path, explaining single-project vs split Server/Client Web App setup differences, and checking where an interactive render mode is needed for Ignite UI components to work. DO NOT USE FOR: general Blazor component authoring without Ignite UI, choosing app architecture or render mode from scratch (see create-blazor-project), JavaScript interop (see use-js-interop), authentication (see configure-auth), prerendering (see support-prerendering), or layout/component design questions that need no Ignite UI setup.
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a service, or names an API by domain.
Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.
Includes Mongodb Atlas Stream Processing, Mongodb Connection, Mongodb Mcp Setup, Mongodb Natural Language Querying, Mongodb Qe Size Estimation, Mongodb Query Optimizer, Mongodb Schema Design, Mongodb Search And Ai, Review Skill
Manages Google Analytics account and property settings, enables the Analytics Admin API via the Cloud CLI, lists accounts and properties, and manages data streams, custom dimensions, conversion events, and integrations. Use when you need to programmatically configure Google Analytics accounts, provision properties, manage data retention, configure Measurement Protocol secrets, or manage Firebase and Google Ads links.
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally sniff the source site for new endpoints). Confirms scope with the user, plans + executes the fix autonomously, scrubs PII, and opens a PR against mvanhorn/printing-press-library. Two user-in-loop checkpoints: scope after capture, PR draft before open. Trigger phrases: "amend the CLI", "submit a patch", "fix what I just dogfooded", "open a PR for this CLI", "patch this CLI", "add features to my CLI", "rename this command", "add these feeds to <cli>", "sniff for new APIs in <cli>", "amend with these ideas", "use printing-press-amend", "run printing-press-amend".
Order a private phone number in any country over the API, receive the SMS verification code, and hand the number back. Use when an agent has to pass a phone check during signup, login or account recovery, or needs a TOTP second factor computed locally.
Includes Extension To Functions Codebase, Firebase Ai Logic Basics, Firebase Analytics, Firebase App Hosting Basics, Firebase Auth Basics, Firebase Basics, Firebase Crashlytics, Firebase Firestore, Firebase Hosting Basics, Firebase Remote Config Basics, Firebase Security Rules Auditor, Firestore Rules Creation, Xcode Project Setup
Plug-in vision for text-only models. Hard rule: when a file path or URL with an image extension (.png, .jpg, .jpeg, .webp, .gif, .heic, .heif) appears anywhere in the conversation (typed by the user, injected as a `[Image: source: <path>]` line, or inside a tag) and you cannot see that image's content, run this skill on it before any other approach: no self-built OCR, no PIL, no tesseract. Also triggers on pasted-image placeholders such as `[Image #1]` and `[Unsupported Image]`. If you can actually see the image, do not use this skill. When unsure, run `modlens guard` before the first read of a session: a deny verdict means the active model has native vision and must read the image itself. Runs the modlens CLI to convert the image into structured JSON evidence: every word transcribed, layout regions, semantics, visual clues. Also use when the user asks how to install, configure, or switch modlens providers (Gemini API key, OpenAI-compatible endpoints, Claude API or Claude Code CLI).
Use this skill whenever the user wants to work with the Loops CLI from the terminal. This includes installing or updating the CLI, authenticating, storing and selecting API keys, validating credentials, and running commands for contacts, contact properties, lists, events, transactional email, campaigns, email messages, themes, components, and uploads. Trigger on phrases like "Loops CLI", "loops auth login", "loops campaigns create", "loops uploads create", "loops email-messages update", "loops themes list", "loops components get", "loops contacts create", "loops events send", "loops transactional send", "loops api-key", "loops agent-context", "brew install loops-so/tap/loops", or any time the user wants to use Loops from the shell instead of application code.
Use this skill whenever LMX is used, produced, reviewed, migrated, or modified. This includes composing campaigns, loops, lifecycle emails, or email-message bodies for the Loops editor or Content API. LMX (Loops Markup Language) is the format used for Loops email content. Trigger on phrases like "create a campaign", "generate an email", "write a welcome email", "draft a lifecycle email", "build an email template", "create an onboarding email", "copy this into LMX", "migrate this email", "convert this email to LMX", "design a new Loops email", "use imagegen for a Loops email", "use gpt-image for an LMX reference", "visual reference for a Loops email", "LMX", "Loops email", or any request to produce, copy, migrate, convert, review, or modify email body content intended for Loops. For net-new emails or major visual redesigns, follow this skill's Net-New Email Design Flow before generating or sourcing new visual assets. Source copy, existing HTML, MJML, Markdown, screenshots, and migration instructions do not bypass this skill's rules unless the user explicitly overrides a specific rule. Do not trigger for questions about the Loops HTTP API, SDK integration, or CLI unless email body content is also involved.
Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, transactional-email, content editing (campaigns, groups, audience segments, email messages, themes, and components), workflow graph/node mutation, and inbound Loops webhooks. Trigger on phrases like "Loops API", "Loops SDK", "create a campaign via API", "update email message LMX", "create a theme via API", "create a workflow via API", "add a workflow node", "Loops webhook", "send a Loops event from my app", "add a contact to Loops in a webhook", "send a transactional email from backend code", or any time the user wants to integrate Loops into their app, backend, webhook, or automation. Do not trigger for CLI or shell-only requests.
Use this skill when the user wants to review, audit, improve, or plan email sending best practices. This includes deliverability, inbox placement, sender reputation, consent, list hygiene, subject lines, preview text, preference centers, onboarding emails, lifecycle emails, product updates, or deciding between marketing and transactional email. It works for any email stack, but when Loops is involved, use Loops behavior and docs as the source of truth. Trigger on phrases like "email deliverability", "inbox placement", "sender reputation", "double opt-in", "unsubscribe", "subject line review", "preview text", "lifecycle emails", "onboarding emails", "product update email", "transactional vs marketing", or "email sending best practices". Do not prefer this skill for pure API implementation; use the Loops API skill for integration details.
Build feature work with high overbuilding risk. Use for new behavior, product slices, or integrations where repository reuse, strict scope, and an explicit stop condition matter.
Includes Hf Cli, Hf Cloud Aws Context Discovery, Hf Cloud Python Env Setup, Hf Cloud Sagemaker Deployment Planner, Hf Cloud Sagemaker Iam Preflight, Hf Cloud Serving Image Selection, Hf Mcp, Hf Mem, Huggingface Best, Huggingface Community Evals, Huggingface Datasets, Huggingface Gradio, Huggingface Llm Trainer, Huggingface Local Models, Huggingface Lora Space Builder, Huggingface Paper Publisher, Huggingface Papers, Huggingface Spaces, Huggingface Tool Builder, Huggingface Trackio, Huggingface Vision Trainer, Huggingface Zerogpu, Train Sentence Transformers, Transformers Js, Trl Training
Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.
Redis LangCache guidance for semantic caching of LLM responses on Redis Cloud — calling search/set via the SDK or REST API, tuning the similarity threshold, separating caches per task type, and filtering with custom attributes. Use when caching LLM completions or RAG answers to cut API cost and latency, building a cache-aside layer in front of OpenAI / Anthropic / etc., tuning hit rate vs precision, or splitting one app's LLM workloads into multiple LangCache caches.
Guide users through configuring key MongoDB MCP server options. Use this skill when a user has the MongoDB MCP server installed but hasn't configured the required environment variables, or when they ask about connecting to MongoDB/Atlas and don't have the credentials set up.
Includes Supabase, Supabase Postgres Best Practices
Working with the redis-docs MCP server (search / fetch / ask at redis.io/mcp) — how its index is shaped and how to read what it returns. Use when those tools are available and you are about to look something up in the Redis documentation, or when a result is confusing — fetch returned one short section instead of a page, several hits share one url, ids look like #sec:w1, metadata.version reads 1.0.0, a search came back empty, or ask was rate-limited or said the docs do not cover it. Also covers what redis.io does and does not index.
Writes, migrates, and fixes OpenAPI specs for Google Cloud API Gateway. Use when converting an OpenAPI 2.0 (Swagger) spec to OpenAPI 3.x, writing a new OpenAPI 3.x spec, or fixing a failed "gcloud api-gateway api-configs create", such as "extension is only supported in OpenAPI 2.x". Also use when quotas set with x-google-quota are never enforced, or when a backend receives path parameters as query parameters. Don't use for adding or debugging MCP tools (use api-gateway-mcp-server), backend lockdown or HTTP 429 tuning (use api-gateway-backend-security-and-rate-limiting), Cloud Endpoints, Apigee, or GKE Gateway API.
Rank open PRs for the automerge queue using eligibility tiers and AI judgment of meaningful fixes close to merge, including older PRs with screenshots and bounded requested changes. Exclude untrusted authors and apply the queue label only after human confirmation. Feeds om-auto-merge-buddy.
Rank open issues suitable for autofix and add the configured queue label only after human confirmation. Use for "triage issues for autofix", "mark issues cez-autofix", or "wybierz zgłoszenia do automatycznej naprawy". Proposes and labels; implementation belongs to om-auto-fix-issue.
Secures and rate limits backend services behind Google Cloud API Gateway across OpenAPI 2.0 and OpenAPI 3.0.x API configurations, including MCP-enabled gateways. Use when configuring API key or JWT authentication, locking down Cloud Run or Cloud Run functions backends with a gateway service account, reading authenticated claims from X-Apigateway-Api-Userinfo, setting per-project request quotas, or diagnosing HTTP 429 and HTTP 500 Service Control Quota errors. Do not use for Apigee, GKE Gateway API, Cloud Load Balancing custom domain setup, or LLM model routing.
Includes 13c Metabolic Flux, Alphagenome, Analytical Method Validation, Autoskill, Benchling Integration, Bgpt Paper Search, Biopython, Bioservices, Bulk Rnaseq, Cellprofiler, Cellxgene Census, Citation Management, Clinical Decision Support, Clinical Reports, Consciousness Council, Database Lookup, Deepspot M, Deeptools, Dhdna Profiler, Dnanexus Integration, Etetoolkit, Exa Search, Experimental Design, Exploratory Data Analysis, Folklore Variant Evidence, Generate Image, Genomic Coordinates, Genomic Intelligence, Get Available Resources, Ginkgo Cloud Lab, Glycoengineering, Hugging Science, Hypothesis Generation, Imaging Data Commons, Infographics, Iso Standards Readiness, Lab Hardware Cad, Labarchive Integration, Latchbio Integration, Latex Posters, Literature Review, Marine Carbonate Chemistry, Markdown Mermaid Writing, Market Research Reports, Markitdown, Matplotlib, Molecular Dynamics, Ncats Arax, Neuropixels Analysis, Nwb Conversion, Omero Integration, Ontology Term Resolution, Open Notebook, Opentrons Integration, Optimize For Gpu, Pacsomatic, Paper Lookup, Paperzilla, Parallel Web, Pathogen Variant Surveillance, Pathway Enrichment, Peer Review, Phylogenetics, Pkpd Modeling, Polars Bio, Pptx Posters, Primer Design, Protocolsio Integration, Pylabrobot, Pytorch Lightning, Qiime2 Amplicon, Relsa Severity Assessment, Research Grants, Research Lookup, Scholar Evaluation, Scientific Brainstorming, Scientific Critical Thinking, Scientific Schematics, Scientific Slides, Scientific Visualization, Scientific Writing, Scikit Bio, Scikit Learn, Scikit Survival, Scvi Tools, Stable Baselines3, Statistical Analysis, Statistical Power, Statsmodels, Timesfm Forecasting, Torch Geometric, Transformers, Treatment Plans, Umap Learn, Uncertainty And Units, Usfiscaldata, Venue Templates, Waypoint Bio, What If Oracle, Zarr Python
Configure singleton documents in a Sanity Studio using the document.singletons registry. Use when a developer wants a fixed-id document (settings, navigation, footer) edited in place, hidden from the default content list, with no "create new" or "duplicate" affordances — or when migrating a userland singleton implementation or a third-party singleton plugin (e.g. sanity-plugin-singleton-management) to the first-class API.
Provides guidance on the new System.Diagnostics.Process APIs introduced in .NET 11: Process.Run, Process.RunAndCaptureText, Process.StartAndForget, Process.ReadAllText/Bytes/Lines, KillOnParentExit, InheritedHandles, and StartDetached. USE FOR: starting, orchestrating, or capturing output from external processes in applications targeting net11.0 or later. DO NOT USE FOR: applications targeting .NET 10 or earlier, or basic pre-.NET 11 Process.Start usage without new APIs.
Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, OAuth server for MCP or third-party OAuth clients, passkeys, MFA, trusted domains, invalid domain, and @neon/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed Better Auth. A required plugin outside Managed support: self-managed Better Auth on a Neon Function or the existing app host. Also use for auth APIs in @neon/neon-js.
Includes Agent Email Inbox, Email Best Practices, React Email, Resend, Resend Cli
Add, configure, or review Ignite UI for Blazor Lite component support in Blazor applications. USE FOR: installing IgniteUI.Blazor.Lite or IgniteUI.Blazor.GridLite, registering AddIgniteUIBlazor() in Blazor Server, WASM, Hybrid, or split Blazor Web App projects, adding @using IgniteUI.Blazor.Controls, wiring the theme stylesheet, picking the right host page, locating the GridLite stylesheet path, explaining single-project vs split Server/Client Web App setup differences, and checking where an interactive render mode is needed for Ignite UI components to work. DO NOT USE FOR: general Blazor component authoring without Ignite UI, choosing app architecture or render mode from scratch (see create-blazor-project), JavaScript interop (see use-js-interop), authentication (see configure-auth), prerendering (see support-prerendering), or layout/component design questions that need no Ignite UI setup.
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a service, or names an API by domain.
Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.
Includes Mongodb Atlas Stream Processing, Mongodb Connection, Mongodb Mcp Setup, Mongodb Natural Language Querying, Mongodb Qe Size Estimation, Mongodb Query Optimizer, Mongodb Schema Design, Mongodb Search And Ai, Review Skill
Manages Google Analytics account and property settings, enables the Analytics Admin API via the Cloud CLI, lists accounts and properties, and manages data streams, custom dimensions, conversion events, and integrations. Use when you need to programmatically configure Google Analytics accounts, provision properties, manage data retention, configure Measurement Protocol secrets, or manage Firebase and Google Ads links.
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally sniff the source site for new endpoints). Confirms scope with the user, plans + executes the fix autonomously, scrubs PII, and opens a PR against mvanhorn/printing-press-library. Two user-in-loop checkpoints: scope after capture, PR draft before open. Trigger phrases: "amend the CLI", "submit a patch", "fix what I just dogfooded", "open a PR for this CLI", "patch this CLI", "add features to my CLI", "rename this command", "add these feeds to <cli>", "sniff for new APIs in <cli>", "amend with these ideas", "use printing-press-amend", "run printing-press-amend".
Order a private phone number in any country over the API, receive the SMS verification code, and hand the number back. Use when an agent has to pass a phone check during signup, login or account recovery, or needs a TOTP second factor computed locally.
Includes Extension To Functions Codebase, Firebase Ai Logic Basics, Firebase Analytics, Firebase App Hosting Basics, Firebase Auth Basics, Firebase Basics, Firebase Crashlytics, Firebase Firestore, Firebase Hosting Basics, Firebase Remote Config Basics, Firebase Security Rules Auditor, Firestore Rules Creation, Xcode Project Setup
Plug-in vision for text-only models. Hard rule: when a file path or URL with an image extension (.png, .jpg, .jpeg, .webp, .gif, .heic, .heif) appears anywhere in the conversation (typed by the user, injected as a `[Image: source: <path>]` line, or inside a tag) and you cannot see that image's content, run this skill on it before any other approach: no self-built OCR, no PIL, no tesseract. Also triggers on pasted-image placeholders such as `[Image #1]` and `[Unsupported Image]`. If you can actually see the image, do not use this skill. When unsure, run `modlens guard` before the first read of a session: a deny verdict means the active model has native vision and must read the image itself. Runs the modlens CLI to convert the image into structured JSON evidence: every word transcribed, layout regions, semantics, visual clues. Also use when the user asks how to install, configure, or switch modlens providers (Gemini API key, OpenAI-compatible endpoints, Claude API or Claude Code CLI).
Use this skill whenever the user wants to work with the Loops CLI from the terminal. This includes installing or updating the CLI, authenticating, storing and selecting API keys, validating credentials, and running commands for contacts, contact properties, lists, events, transactional email, campaigns, email messages, themes, components, and uploads. Trigger on phrases like "Loops CLI", "loops auth login", "loops campaigns create", "loops uploads create", "loops email-messages update", "loops themes list", "loops components get", "loops contacts create", "loops events send", "loops transactional send", "loops api-key", "loops agent-context", "brew install loops-so/tap/loops", or any time the user wants to use Loops from the shell instead of application code.
Use this skill whenever LMX is used, produced, reviewed, migrated, or modified. This includes composing campaigns, loops, lifecycle emails, or email-message bodies for the Loops editor or Content API. LMX (Loops Markup Language) is the format used for Loops email content. Trigger on phrases like "create a campaign", "generate an email", "write a welcome email", "draft a lifecycle email", "build an email template", "create an onboarding email", "copy this into LMX", "migrate this email", "convert this email to LMX", "design a new Loops email", "use imagegen for a Loops email", "use gpt-image for an LMX reference", "visual reference for a Loops email", "LMX", "Loops email", or any request to produce, copy, migrate, convert, review, or modify email body content intended for Loops. For net-new emails or major visual redesigns, follow this skill's Net-New Email Design Flow before generating or sourcing new visual assets. Source copy, existing HTML, MJML, Markdown, screenshots, and migration instructions do not bypass this skill's rules unless the user explicitly overrides a specific rule. Do not trigger for questions about the Loops HTTP API, SDK integration, or CLI unless email body content is also involved.
Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, transactional-email, content editing (campaigns, groups, audience segments, email messages, themes, and components), workflow graph/node mutation, and inbound Loops webhooks. Trigger on phrases like "Loops API", "Loops SDK", "create a campaign via API", "update email message LMX", "create a theme via API", "create a workflow via API", "add a workflow node", "Loops webhook", "send a Loops event from my app", "add a contact to Loops in a webhook", "send a transactional email from backend code", or any time the user wants to integrate Loops into their app, backend, webhook, or automation. Do not trigger for CLI or shell-only requests.
Use this skill when the user wants to review, audit, improve, or plan email sending best practices. This includes deliverability, inbox placement, sender reputation, consent, list hygiene, subject lines, preview text, preference centers, onboarding emails, lifecycle emails, product updates, or deciding between marketing and transactional email. It works for any email stack, but when Loops is involved, use Loops behavior and docs as the source of truth. Trigger on phrases like "email deliverability", "inbox placement", "sender reputation", "double opt-in", "unsubscribe", "subject line review", "preview text", "lifecycle emails", "onboarding emails", "product update email", "transactional vs marketing", or "email sending best practices". Do not prefer this skill for pure API implementation; use the Loops API skill for integration details.
Build feature work with high overbuilding risk. Use for new behavior, product slices, or integrations where repository reuse, strict scope, and an explicit stop condition matter.
Includes Hf Cli, Hf Cloud Aws Context Discovery, Hf Cloud Python Env Setup, Hf Cloud Sagemaker Deployment Planner, Hf Cloud Sagemaker Iam Preflight, Hf Cloud Serving Image Selection, Hf Mcp, Hf Mem, Huggingface Best, Huggingface Community Evals, Huggingface Datasets, Huggingface Gradio, Huggingface Llm Trainer, Huggingface Local Models, Huggingface Lora Space Builder, Huggingface Paper Publisher, Huggingface Papers, Huggingface Spaces, Huggingface Tool Builder, Huggingface Trackio, Huggingface Vision Trainer, Huggingface Zerogpu, Train Sentence Transformers, Transformers Js, Trl Training
Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.
Redis LangCache guidance for semantic caching of LLM responses on Redis Cloud — calling search/set via the SDK or REST API, tuning the similarity threshold, separating caches per task type, and filtering with custom attributes. Use when caching LLM completions or RAG answers to cut API cost and latency, building a cache-aside layer in front of OpenAI / Anthropic / etc., tuning hit rate vs precision, or splitting one app's LLM workloads into multiple LangCache caches.
Guide users through configuring key MongoDB MCP server options. Use this skill when a user has the MongoDB MCP server installed but hasn't configured the required environment variables, or when they ask about connecting to MongoDB/Atlas and don't have the credentials set up.
Includes Supabase, Supabase Postgres Best Practices
Working with the redis-docs MCP server (search / fetch / ask at redis.io/mcp) — how its index is shaped and how to read what it returns. Use when those tools are available and you are about to look something up in the Redis documentation, or when a result is confusing — fetch returned one short section instead of a page, several hits share one url, ids look like #sec:w1, metadata.version reads 1.0.0, a search came back empty, or ask was rate-limited or said the docs do not cover it. Also covers what redis.io does and does not index.
Writes, migrates, and fixes OpenAPI specs for Google Cloud API Gateway. Use when converting an OpenAPI 2.0 (Swagger) spec to OpenAPI 3.x, writing a new OpenAPI 3.x spec, or fixing a failed "gcloud api-gateway api-configs create", such as "extension is only supported in OpenAPI 2.x". Also use when quotas set with x-google-quota are never enforced, or when a backend receives path parameters as query parameters. Don't use for adding or debugging MCP tools (use api-gateway-mcp-server), backend lockdown or HTTP 429 tuning (use api-gateway-backend-security-and-rate-limiting), Cloud Endpoints, Apigee, or GKE Gateway API.
Rank open PRs for the automerge queue using eligibility tiers and AI judgment of meaningful fixes close to merge, including older PRs with screenshots and bounded requested changes. Exclude untrusted authors and apply the queue label only after human confirmation. Feeds om-auto-merge-buddy.
Rank open issues suitable for autofix and add the configured queue label only after human confirmation. Use for "triage issues for autofix", "mark issues cez-autofix", or "wybierz zgłoszenia do automatycznej naprawy". Proposes and labels; implementation belongs to om-auto-fix-issue.
Secures and rate limits backend services behind Google Cloud API Gateway across OpenAPI 2.0 and OpenAPI 3.0.x API configurations, including MCP-enabled gateways. Use when configuring API key or JWT authentication, locking down Cloud Run or Cloud Run functions backends with a gateway service account, reading authenticated claims from X-Apigateway-Api-Userinfo, setting per-project request quotas, or diagnosing HTTP 429 and HTTP 500 Service Control Quota errors. Do not use for Apigee, GKE Gateway API, Cloud Load Balancing custom domain setup, or LLM model routing.
Includes 13c Metabolic Flux, Alphagenome, Analytical Method Validation, Autoskill, Benchling Integration, Bgpt Paper Search, Biopython, Bioservices, Bulk Rnaseq, Cellprofiler, Cellxgene Census, Citation Management, Clinical Decision Support, Clinical Reports, Consciousness Council, Database Lookup, Deepspot M, Deeptools, Dhdna Profiler, Dnanexus Integration, Etetoolkit, Exa Search, Experimental Design, Exploratory Data Analysis, Folklore Variant Evidence, Generate Image, Genomic Coordinates, Genomic Intelligence, Get Available Resources, Ginkgo Cloud Lab, Glycoengineering, Hugging Science, Hypothesis Generation, Imaging Data Commons, Infographics, Iso Standards Readiness, Lab Hardware Cad, Labarchive Integration, Latchbio Integration, Latex Posters, Literature Review, Marine Carbonate Chemistry, Markdown Mermaid Writing, Market Research Reports, Markitdown, Matplotlib, Molecular Dynamics, Ncats Arax, Neuropixels Analysis, Nwb Conversion, Omero Integration, Ontology Term Resolution, Open Notebook, Opentrons Integration, Optimize For Gpu, Pacsomatic, Paper Lookup, Paperzilla, Parallel Web, Pathogen Variant Surveillance, Pathway Enrichment, Peer Review, Phylogenetics, Pkpd Modeling, Polars Bio, Pptx Posters, Primer Design, Protocolsio Integration, Pylabrobot, Pytorch Lightning, Qiime2 Amplicon, Relsa Severity Assessment, Research Grants, Research Lookup, Scholar Evaluation, Scientific Brainstorming, Scientific Critical Thinking, Scientific Schematics, Scientific Slides, Scientific Visualization, Scientific Writing, Scikit Bio, Scikit Learn, Scikit Survival, Scvi Tools, Stable Baselines3, Statistical Analysis, Statistical Power, Statsmodels, Timesfm Forecasting, Torch Geometric, Transformers, Treatment Plans, Umap Learn, Uncertainty And Units, Usfiscaldata, Venue Templates, Waypoint Bio, What If Oracle, Zarr Python
Configure singleton documents in a Sanity Studio using the document.singletons registry. Use when a developer wants a fixed-id document (settings, navigation, footer) edited in place, hidden from the default content list, with no "create new" or "duplicate" affordances — or when migrating a userland singleton implementation or a third-party singleton plugin (e.g. sanity-plugin-singleton-management) to the first-class API.
Provides guidance on the new System.Diagnostics.Process APIs introduced in .NET 11: Process.Run, Process.RunAndCaptureText, Process.StartAndForget, Process.ReadAllText/Bytes/Lines, KillOnParentExit, InheritedHandles, and StartDetached. USE FOR: starting, orchestrating, or capturing output from external processes in applications targeting net11.0 or later. DO NOT USE FOR: applications targeting .NET 10 or earlier, or basic pre-.NET 11 Process.Start usage without new APIs.
Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, OAuth server for MCP or third-party OAuth clients, passkeys, MFA, trusted domains, invalid domain, and @neon/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed Better Auth. A required plugin outside Managed support: self-managed Better Auth on a Neon Function or the existing app host. Also use for auth APIs in @neon/neon-js.
Includes Agent Email Inbox, Email Best Practices, React Email, Resend, Resend Cli
Add, configure, or review Ignite UI for Blazor Lite component support in Blazor applications. USE FOR: installing IgniteUI.Blazor.Lite or IgniteUI.Blazor.GridLite, registering AddIgniteUIBlazor() in Blazor Server, WASM, Hybrid, or split Blazor Web App projects, adding @using IgniteUI.Blazor.Controls, wiring the theme stylesheet, picking the right host page, locating the GridLite stylesheet path, explaining single-project vs split Server/Client Web App setup differences, and checking where an interactive render mode is needed for Ignite UI components to work. DO NOT USE FOR: general Blazor component authoring without Ignite UI, choosing app architecture or render mode from scratch (see create-blazor-project), JavaScript interop (see use-js-interop), authentication (see configure-auth), prerendering (see support-prerendering), or layout/component design questions that need no Ignite UI setup.
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a service, or names an API by domain.
Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.
Includes Mongodb Atlas Stream Processing, Mongodb Connection, Mongodb Mcp Setup, Mongodb Natural Language Querying, Mongodb Qe Size Estimation, Mongodb Query Optimizer, Mongodb Schema Design, Mongodb Search And Ai, Review Skill
Manages Google Analytics account and property settings, enables the Analytics Admin API via the Cloud CLI, lists accounts and properties, and manages data streams, custom dimensions, conversion events, and integrations. Use when you need to programmatically configure Google Analytics accounts, provision properties, manage data retention, configure Measurement Protocol secrets, or manage Firebase and Google Ads links.
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally sniff the source site for new endpoints). Confirms scope with the user, plans + executes the fix autonomously, scrubs PII, and opens a PR against mvanhorn/printing-press-library. Two user-in-loop checkpoints: scope after capture, PR draft before open. Trigger phrases: "amend the CLI", "submit a patch", "fix what I just dogfooded", "open a PR for this CLI", "patch this CLI", "add features to my CLI", "rename this command", "add these feeds to <cli>", "sniff for new APIs in <cli>", "amend with these ideas", "use printing-press-amend", "run printing-press-amend".
Order a private phone number in any country over the API, receive the SMS verification code, and hand the number back. Use when an agent has to pass a phone check during signup, login or account recovery, or needs a TOTP second factor computed locally.
Includes Extension To Functions Codebase, Firebase Ai Logic Basics, Firebase Analytics, Firebase App Hosting Basics, Firebase Auth Basics, Firebase Basics, Firebase Crashlytics, Firebase Firestore, Firebase Hosting Basics, Firebase Remote Config Basics, Firebase Security Rules Auditor, Firestore Rules Creation, Xcode Project Setup
Plug-in vision for text-only models. Hard rule: when a file path or URL with an image extension (.png, .jpg, .jpeg, .webp, .gif, .heic, .heif) appears anywhere in the conversation (typed by the user, injected as a `[Image: source: <path>]` line, or inside a tag) and you cannot see that image's content, run this skill on it before any other approach: no self-built OCR, no PIL, no tesseract. Also triggers on pasted-image placeholders such as `[Image #1]` and `[Unsupported Image]`. If you can actually see the image, do not use this skill. When unsure, run `modlens guard` before the first read of a session: a deny verdict means the active model has native vision and must read the image itself. Runs the modlens CLI to convert the image into structured JSON evidence: every word transcribed, layout regions, semantics, visual clues. Also use when the user asks how to install, configure, or switch modlens providers (Gemini API key, OpenAI-compatible endpoints, Claude API or Claude Code CLI).
Use this skill whenever the user wants to work with the Loops CLI from the terminal. This includes installing or updating the CLI, authenticating, storing and selecting API keys, validating credentials, and running commands for contacts, contact properties, lists, events, transactional email, campaigns, email messages, themes, components, and uploads. Trigger on phrases like "Loops CLI", "loops auth login", "loops campaigns create", "loops uploads create", "loops email-messages update", "loops themes list", "loops components get", "loops contacts create", "loops events send", "loops transactional send", "loops api-key", "loops agent-context", "brew install loops-so/tap/loops", or any time the user wants to use Loops from the shell instead of application code.
Use this skill whenever LMX is used, produced, reviewed, migrated, or modified. This includes composing campaigns, loops, lifecycle emails, or email-message bodies for the Loops editor or Content API. LMX (Loops Markup Language) is the format used for Loops email content. Trigger on phrases like "create a campaign", "generate an email", "write a welcome email", "draft a lifecycle email", "build an email template", "create an onboarding email", "copy this into LMX", "migrate this email", "convert this email to LMX", "design a new Loops email", "use imagegen for a Loops email", "use gpt-image for an LMX reference", "visual reference for a Loops email", "LMX", "Loops email", or any request to produce, copy, migrate, convert, review, or modify email body content intended for Loops. For net-new emails or major visual redesigns, follow this skill's Net-New Email Design Flow before generating or sourcing new visual assets. Source copy, existing HTML, MJML, Markdown, screenshots, and migration instructions do not bypass this skill's rules unless the user explicitly overrides a specific rule. Do not trigger for questions about the Loops HTTP API, SDK integration, or CLI unless email body content is also involved.
Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, transactional-email, content editing (campaigns, groups, audience segments, email messages, themes, and components), workflow graph/node mutation, and inbound Loops webhooks. Trigger on phrases like "Loops API", "Loops SDK", "create a campaign via API", "update email message LMX", "create a theme via API", "create a workflow via API", "add a workflow node", "Loops webhook", "send a Loops event from my app", "add a contact to Loops in a webhook", "send a transactional email from backend code", or any time the user wants to integrate Loops into their app, backend, webhook, or automation. Do not trigger for CLI or shell-only requests.
Use this skill when the user wants to review, audit, improve, or plan email sending best practices. This includes deliverability, inbox placement, sender reputation, consent, list hygiene, subject lines, preview text, preference centers, onboarding emails, lifecycle emails, product updates, or deciding between marketing and transactional email. It works for any email stack, but when Loops is involved, use Loops behavior and docs as the source of truth. Trigger on phrases like "email deliverability", "inbox placement", "sender reputation", "double opt-in", "unsubscribe", "subject line review", "preview text", "lifecycle emails", "onboarding emails", "product update email", "transactional vs marketing", or "email sending best practices". Do not prefer this skill for pure API implementation; use the Loops API skill for integration details.
Build feature work with high overbuilding risk. Use for new behavior, product slices, or integrations where repository reuse, strict scope, and an explicit stop condition matter.
Includes Hf Cli, Hf Cloud Aws Context Discovery, Hf Cloud Python Env Setup, Hf Cloud Sagemaker Deployment Planner, Hf Cloud Sagemaker Iam Preflight, Hf Cloud Serving Image Selection, Hf Mcp, Hf Mem, Huggingface Best, Huggingface Community Evals, Huggingface Datasets, Huggingface Gradio, Huggingface Llm Trainer, Huggingface Local Models, Huggingface Lora Space Builder, Huggingface Paper Publisher, Huggingface Papers, Huggingface Spaces, Huggingface Tool Builder, Huggingface Trackio, Huggingface Vision Trainer, Huggingface Zerogpu, Train Sentence Transformers, Transformers Js, Trl Training
Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.
Redis LangCache guidance for semantic caching of LLM responses on Redis Cloud — calling search/set via the SDK or REST API, tuning the similarity threshold, separating caches per task type, and filtering with custom attributes. Use when caching LLM completions or RAG answers to cut API cost and latency, building a cache-aside layer in front of OpenAI / Anthropic / etc., tuning hit rate vs precision, or splitting one app's LLM workloads into multiple LangCache caches.
Guide users through configuring key MongoDB MCP server options. Use this skill when a user has the MongoDB MCP server installed but hasn't configured the required environment variables, or when they ask about connecting to MongoDB/Atlas and don't have the credentials set up.
Includes Supabase, Supabase Postgres Best Practices
Working with the redis-docs MCP server (search / fetch / ask at redis.io/mcp) — how its index is shaped and how to read what it returns. Use when those tools are available and you are about to look something up in the Redis documentation, or when a result is confusing — fetch returned one short section instead of a page, several hits share one url, ids look like #sec:w1, metadata.version reads 1.0.0, a search came back empty, or ask was rate-limited or said the docs do not cover it. Also covers what redis.io does and does not index.
Writes, migrates, and fixes OpenAPI specs for Google Cloud API Gateway. Use when converting an OpenAPI 2.0 (Swagger) spec to OpenAPI 3.x, writing a new OpenAPI 3.x spec, or fixing a failed "gcloud api-gateway api-configs create", such as "extension is only supported in OpenAPI 2.x". Also use when quotas set with x-google-quota are never enforced, or when a backend receives path parameters as query parameters. Don't use for adding or debugging MCP tools (use api-gateway-mcp-server), backend lockdown or HTTP 429 tuning (use api-gateway-backend-security-and-rate-limiting), Cloud Endpoints, Apigee, or GKE Gateway API.
Rank open PRs for the automerge queue using eligibility tiers and AI judgment of meaningful fixes close to merge, including older PRs with screenshots and bounded requested changes. Exclude untrusted authors and apply the queue label only after human confirmation. Feeds om-auto-merge-buddy.
Rank open issues suitable for autofix and add the configured queue label only after human confirmation. Use for "triage issues for autofix", "mark issues cez-autofix", or "wybierz zgłoszenia do automatycznej naprawy". Proposes and labels; implementation belongs to om-auto-fix-issue.
Secures and rate limits backend services behind Google Cloud API Gateway across OpenAPI 2.0 and OpenAPI 3.0.x API configurations, including MCP-enabled gateways. Use when configuring API key or JWT authentication, locking down Cloud Run or Cloud Run functions backends with a gateway service account, reading authenticated claims from X-Apigateway-Api-Userinfo, setting per-project request quotas, or diagnosing HTTP 429 and HTTP 500 Service Control Quota errors. Do not use for Apigee, GKE Gateway API, Cloud Load Balancing custom domain setup, or LLM model routing.
Includes 13c Metabolic Flux, Alphagenome, Analytical Method Validation, Autoskill, Benchling Integration, Bgpt Paper Search, Biopython, Bioservices, Bulk Rnaseq, Cellprofiler, Cellxgene Census, Citation Management, Clinical Decision Support, Clinical Reports, Consciousness Council, Database Lookup, Deepspot M, Deeptools, Dhdna Profiler, Dnanexus Integration, Etetoolkit, Exa Search, Experimental Design, Exploratory Data Analysis, Folklore Variant Evidence, Generate Image, Genomic Coordinates, Genomic Intelligence, Get Available Resources, Ginkgo Cloud Lab, Glycoengineering, Hugging Science, Hypothesis Generation, Imaging Data Commons, Infographics, Iso Standards Readiness, Lab Hardware Cad, Labarchive Integration, Latchbio Integration, Latex Posters, Literature Review, Marine Carbonate Chemistry, Markdown Mermaid Writing, Market Research Reports, Markitdown, Matplotlib, Molecular Dynamics, Ncats Arax, Neuropixels Analysis, Nwb Conversion, Omero Integration, Ontology Term Resolution, Open Notebook, Opentrons Integration, Optimize For Gpu, Pacsomatic, Paper Lookup, Paperzilla, Parallel Web, Pathogen Variant Surveillance, Pathway Enrichment, Peer Review, Phylogenetics, Pkpd Modeling, Polars Bio, Pptx Posters, Primer Design, Protocolsio Integration, Pylabrobot, Pytorch Lightning, Qiime2 Amplicon, Relsa Severity Assessment, Research Grants, Research Lookup, Scholar Evaluation, Scientific Brainstorming, Scientific Critical Thinking, Scientific Schematics, Scientific Slides, Scientific Visualization, Scientific Writing, Scikit Bio, Scikit Learn, Scikit Survival, Scvi Tools, Stable Baselines3, Statistical Analysis, Statistical Power, Statsmodels, Timesfm Forecasting, Torch Geometric, Transformers, Treatment Plans, Umap Learn, Uncertainty And Units, Usfiscaldata, Venue Templates, Waypoint Bio, What If Oracle, Zarr Python
Configure singleton documents in a Sanity Studio using the document.singletons registry. Use when a developer wants a fixed-id document (settings, navigation, footer) edited in place, hidden from the default content list, with no "create new" or "duplicate" affordances — or when migrating a userland singleton implementation or a third-party singleton plugin (e.g. sanity-plugin-singleton-management) to the first-class API.
Provides guidance on the new System.Diagnostics.Process APIs introduced in .NET 11: Process.Run, Process.RunAndCaptureText, Process.StartAndForget, Process.ReadAllText/Bytes/Lines, KillOnParentExit, InheritedHandles, and StartDetached. USE FOR: starting, orchestrating, or capturing output from external processes in applications targeting net11.0 or later. DO NOT USE FOR: applications targeting .NET 10 or earlier, or basic pre-.NET 11 Process.Start usage without new APIs.
Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, OAuth server for MCP or third-party OAuth clients, passkeys, MFA, trusted domains, invalid domain, and @neon/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed Better Auth. A required plugin outside Managed support: self-managed Better Auth on a Neon Function or the existing app host. Also use for auth APIs in @neon/neon-js.
Includes Agent Email Inbox, Email Best Practices, React Email, Resend, Resend Cli
Add, configure, or review Ignite UI for Blazor Lite component support in Blazor applications. USE FOR: installing IgniteUI.Blazor.Lite or IgniteUI.Blazor.GridLite, registering AddIgniteUIBlazor() in Blazor Server, WASM, Hybrid, or split Blazor Web App projects, adding @using IgniteUI.Blazor.Controls, wiring the theme stylesheet, picking the right host page, locating the GridLite stylesheet path, explaining single-project vs split Server/Client Web App setup differences, and checking where an interactive render mode is needed for Ignite UI components to work. DO NOT USE FOR: general Blazor component authoring without Ignite UI, choosing app architecture or render mode from scratch (see create-blazor-project), JavaScript interop (see use-js-interop), authentication (see configure-auth), prerendering (see support-prerendering), or layout/component design questions that need no Ignite UI setup.
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a service, or names an API by domain.
Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.
Includes Mongodb Atlas Stream Processing, Mongodb Connection, Mongodb Mcp Setup, Mongodb Natural Language Querying, Mongodb Qe Size Estimation, Mongodb Query Optimizer, Mongodb Schema Design, Mongodb Search And Ai, Review Skill
Manages Google Analytics account and property settings, enables the Analytics Admin API via the Cloud CLI, lists accounts and properties, and manages data streams, custom dimensions, conversion events, and integrations. Use when you need to programmatically configure Google Analytics accounts, provision properties, manage data retention, configure Measurement Protocol secrets, or manage Firebase and Google Ads links.
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally sniff the source site for new endpoints). Confirms scope with the user, plans + executes the fix autonomously, scrubs PII, and opens a PR against mvanhorn/printing-press-library. Two user-in-loop checkpoints: scope after capture, PR draft before open. Trigger phrases: "amend the CLI", "submit a patch", "fix what I just dogfooded", "open a PR for this CLI", "patch this CLI", "add features to my CLI", "rename this command", "add these feeds to <cli>", "sniff for new APIs in <cli>", "amend with these ideas", "use printing-press-amend", "run printing-press-amend".
Order a private phone number in any country over the API, receive the SMS verification code, and hand the number back. Use when an agent has to pass a phone check during signup, login or account recovery, or needs a TOTP second factor computed locally.
Includes Extension To Functions Codebase, Firebase Ai Logic Basics, Firebase Analytics, Firebase App Hosting Basics, Firebase Auth Basics, Firebase Basics, Firebase Crashlytics, Firebase Firestore, Firebase Hosting Basics, Firebase Remote Config Basics, Firebase Security Rules Auditor, Firestore Rules Creation, Xcode Project Setup
Plug-in vision for text-only models. Hard rule: when a file path or URL with an image extension (.png, .jpg, .jpeg, .webp, .gif, .heic, .heif) appears anywhere in the conversation (typed by the user, injected as a `[Image: source: <path>]` line, or inside a tag) and you cannot see that image's content, run this skill on it before any other approach: no self-built OCR, no PIL, no tesseract. Also triggers on pasted-image placeholders such as `[Image #1]` and `[Unsupported Image]`. If you can actually see the image, do not use this skill. When unsure, run `modlens guard` before the first read of a session: a deny verdict means the active model has native vision and must read the image itself. Runs the modlens CLI to convert the image into structured JSON evidence: every word transcribed, layout regions, semantics, visual clues. Also use when the user asks how to install, configure, or switch modlens providers (Gemini API key, OpenAI-compatible endpoints, Claude API or Claude Code CLI).
Use this skill whenever the user wants to work with the Loops CLI from the terminal. This includes installing or updating the CLI, authenticating, storing and selecting API keys, validating credentials, and running commands for contacts, contact properties, lists, events, transactional email, campaigns, email messages, themes, components, and uploads. Trigger on phrases like "Loops CLI", "loops auth login", "loops campaigns create", "loops uploads create", "loops email-messages update", "loops themes list", "loops components get", "loops contacts create", "loops events send", "loops transactional send", "loops api-key", "loops agent-context", "brew install loops-so/tap/loops", or any time the user wants to use Loops from the shell instead of application code.
Use this skill whenever LMX is used, produced, reviewed, migrated, or modified. This includes composing campaigns, loops, lifecycle emails, or email-message bodies for the Loops editor or Content API. LMX (Loops Markup Language) is the format used for Loops email content. Trigger on phrases like "create a campaign", "generate an email", "write a welcome email", "draft a lifecycle email", "build an email template", "create an onboarding email", "copy this into LMX", "migrate this email", "convert this email to LMX", "design a new Loops email", "use imagegen for a Loops email", "use gpt-image for an LMX reference", "visual reference for a Loops email", "LMX", "Loops email", or any request to produce, copy, migrate, convert, review, or modify email body content intended for Loops. For net-new emails or major visual redesigns, follow this skill's Net-New Email Design Flow before generating or sourcing new visual assets. Source copy, existing HTML, MJML, Markdown, screenshots, and migration instructions do not bypass this skill's rules unless the user explicitly overrides a specific rule. Do not trigger for questions about the Loops HTTP API, SDK integration, or CLI unless email body content is also involved.
Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, transactional-email, content editing (campaigns, groups, audience segments, email messages, themes, and components), workflow graph/node mutation, and inbound Loops webhooks. Trigger on phrases like "Loops API", "Loops SDK", "create a campaign via API", "update email message LMX", "create a theme via API", "create a workflow via API", "add a workflow node", "Loops webhook", "send a Loops event from my app", "add a contact to Loops in a webhook", "send a transactional email from backend code", or any time the user wants to integrate Loops into their app, backend, webhook, or automation. Do not trigger for CLI or shell-only requests.
Use this skill when the user wants to review, audit, improve, or plan email sending best practices. This includes deliverability, inbox placement, sender reputation, consent, list hygiene, subject lines, preview text, preference centers, onboarding emails, lifecycle emails, product updates, or deciding between marketing and transactional email. It works for any email stack, but when Loops is involved, use Loops behavior and docs as the source of truth. Trigger on phrases like "email deliverability", "inbox placement", "sender reputation", "double opt-in", "unsubscribe", "subject line review", "preview text", "lifecycle emails", "onboarding emails", "product update email", "transactional vs marketing", or "email sending best practices". Do not prefer this skill for pure API implementation; use the Loops API skill for integration details.
Build feature work with high overbuilding risk. Use for new behavior, product slices, or integrations where repository reuse, strict scope, and an explicit stop condition matter.
Includes Hf Cli, Hf Cloud Aws Context Discovery, Hf Cloud Python Env Setup, Hf Cloud Sagemaker Deployment Planner, Hf Cloud Sagemaker Iam Preflight, Hf Cloud Serving Image Selection, Hf Mcp, Hf Mem, Huggingface Best, Huggingface Community Evals, Huggingface Datasets, Huggingface Gradio, Huggingface Llm Trainer, Huggingface Local Models, Huggingface Lora Space Builder, Huggingface Paper Publisher, Huggingface Papers, Huggingface Spaces, Huggingface Tool Builder, Huggingface Trackio, Huggingface Vision Trainer, Huggingface Zerogpu, Train Sentence Transformers, Transformers Js, Trl Training
Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.
Redis LangCache guidance for semantic caching of LLM responses on Redis Cloud — calling search/set via the SDK or REST API, tuning the similarity threshold, separating caches per task type, and filtering with custom attributes. Use when caching LLM completions or RAG answers to cut API cost and latency, building a cache-aside layer in front of OpenAI / Anthropic / etc., tuning hit rate vs precision, or splitting one app's LLM workloads into multiple LangCache caches.
Guide users through configuring key MongoDB MCP server options. Use this skill when a user has the MongoDB MCP server installed but hasn't configured the required environment variables, or when they ask about connecting to MongoDB/Atlas and don't have the credentials set up.
Includes Supabase, Supabase Postgres Best Practices