Claude Skills by jeremylongshore

'Execute Mistral AI chat completions with streaming, multi-turn, and

'Execute Mistral AI embeddings, function calling, and RAG pipelines.

'Optimize Mistral AI costs through model selection, token management,

'Implement Mistral AI PII handling, data retention, and GDPR/CCPA compliance

'Collect Mistral AI debug evidence for support tickets and troubleshooting.

'Deploy Mistral AI integrations to Vercel, Docker, and Cloud Run platforms.

'Configure Mistral AI enterprise access control and workspace management.

'Create a minimal working Mistral AI chat completion example.

'Execute Mistral AI incident response procedures with triage, mitigation,

'Install and configure the Mistral AI SDK with authentication.

'Configure Mistral AI local development with hot reload, testing, and

'Execute migration to Mistral AI from OpenAI, Anthropic, or other providers.

'Configure Mistral AI across development, staging, and production environments.

'Set up comprehensive observability for Mistral AI with metrics, traces,

'Optimize Mistral AI performance with caching, batching, and latency

'Execute Mistral AI production deployment checklist and rollback procedures.

'Implement Mistral AI rate limiting, backoff, and request management.

'Implement Mistral AI reference architecture with best-practice project

'Apply production-ready Mistral AI SDK patterns for TypeScript and Python.

'Apply Mistral AI security best practices for secrets, prompt injection,

'Analyze, plan, and execute Mistral AI SDK upgrades with breaking change

'Implement Mistral AI async patterns, batch API, agents, and event-driven

'Use when setting up CI/CD pipelines that validate Navan API integrations,

'Diagnose and fix common Navan API errors with targeted fix procedures.

'Manage the complete Navan travel booking lifecycle via REST API.

'Manage Navan expense reporting, transaction data, and ERP synchronization.

'Use when optimizing travel spend with Navan''s policy engine, analyzing

'Extract and transform Navan booking and transaction data using pagination,

'Implement incremental sync strategies for Navan BOOKING and TRANSACTION

"Use when collecting diagnostic data from a Navan API integration \u2014\

'Use when deploying Navan integrations with ERP systems (NetSuite, Sage

'Configure Navan admin roles, travel policies, approval workflows, and

'Manage Navan users, departments, cost centers, and approval chains via

'Make your first Navan API call to retrieve trip and user data.

"Use when responding to Navan platform incidents \u2014 flight cancellations,\

'Set up OAuth 2.0 authentication for the Navan REST API.

'Set up a local development environment for Navan API integrations with

"Use when planning or executing a migration from SAP Concur or legacy\

'Set up dev/staging/prod environment separation for Navan integrations

'Use when setting up monitoring, logging, and alerting for Navan API

"Use when optimizing Navan API call patterns for high-volume integrations\

"Use when validating production readiness for a Navan API integration\

'Implement adaptive rate-limiting for the Navan REST API with exponential

"Use when designing a production Navan API integration architecture \u2014\

'Build a typed API wrapper around Navan REST endpoints since no official

'Secure Navan API credentials with OAuth 2.0 best practices, SSO/SAML,

"Use when handling Navan API changes in production \u2014 defensive coding\

'Set up webhook listeners for real-time Navan event notifications.

Use when standard Notion troubleshooting fails or you are chasing intermittent API errors — deep debugging for response inspection, permission chain tracing, property type mismatches, pagination edge cases, and block nesting limits. Trigger with phrases like "notion deep debug", "notion permission trace", "notion property mismatch", "notion pagination bug", "notion nesting limit".

Use when you are choosing or scaffolding how an app talks to Notion via the API — deciding between a headless CMS (blog/content site), a task tracker (project management), a knowledge base (wiki), a form-submission handler, or a data-pipeline source, and wiring the database schema plus integration code. Trigger with phrases like "notion cms", "notion headless blog", "notion task tracker", "notion wiki", "notion form handler", "notion data pipeline".