Loading...
Loading...
Found 2,162 Skills
Deterministic, offline testing of CrewAI crews and flows with pytest: a stub BaseLLM (shipped in references/stub_llm.py) that drives text, structured output and tool calls with no API key, asserting on the prompts crewai built, testing guardrails and flow routing, what `crewai test` really does, event listeners for debugging, and the exact tracing/telemetry env var values. Use when writing tests for a crewai project, mocking or stubbing the LLM, writing a custom BaseLLM, seeing `TypeError: ... call() got an unexpected keyword argument 'from_task'`, `ValueError: OPENAI_API_KEY is required` in CI, `TraceGrantError` in pytest, running `crewai test`, adding a BaseEventListener, or setting CREWAI_TRACING_ENABLED / CREWAI_DISABLE_TELEMETRY / OTEL_SDK_DISABLED.
Pytest discipline for writing, reviewing, and fixing Python tests — what deserves to be a committed test, deterministic concurrency testing, fixture isolation, mocking boundaries, and suite structure. Triggers on writing or reviewing pytest tests, designing fixtures, parametrizing cases, mocking or patching, debugging flaky or order-dependent tests, xfail/skip decisions, and pytest configuration.
Document a solved problem as one searchable file in the project's docs/solutions/<category>/ so future sessions (and insistir's learnings researcher) find it instead of re-solving it. Three parallel read-only subagents extract context, root cause and fix, and prevention; you write the single file. Use right after a non-trivial fix is confirmed: "that worked", "it's fixed", "problem solved", "document this fix", "write up the solution", "compound this", "ya funcionó", "quedó arreglado", "documenta la solución". NOT for trivial fixes (typos, obvious one-liners), problems still unresolved (keep debugging first), or general docs, READMEs and changelogs.
Build durable backend AI agents with the eve framework. Use when creating, editing, or debugging an eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals.
Plans a version-by-version Infrahub upgrade path and scores each release's breaking changes against the user's repository and instance, producing UPGRADE_PLAN.md. TRIGGER when: planning an Infrahub upgrade, asking what breaks between two versions, checking upgrade impact before a maintenance window, asked to "just run the upgrade", updating or extending an existing UPGRADE_PLAN.md after the target release or the repository moved, debugging a plan that missed a breaking change. DO NOT TRIGGER when: auditing a repo against best practices, querying live data, designing schemas, collecting diagnostics after a failed upgrade, switching between the Community and Enterprise editions. ALWAYS pass the user's request verbatim as args, versions, pasted schema, deployment, and edition included: this skill runs in a forked context and cannot see the parent conversation.
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
Installing, loading and unloading SAS packages with the SAS Packages Framework (SPF) and the SASPAC archive - the packages fileref rules, %installPackage / %loadPackage / %helpPackage / %unloadPackage, version pinning. Use when installing a package such as sasjscore, or debugging an install that reports rc=20006 or a missing package zip.
Build, update, and verify a Prismatic Code Native Integration (CNI), including local checks and iterative platform testing. Use for new integration requirements, ongoing CNI development, and debugging flow executions. For assessing or replacing an existing non-Prismatic integration system, prefer prismatic-migrate when available.
ALWAYS use when writing code that imports "vue-router", "vue-router/vite", "vue-router/auto-routes", or "vue-router/experimental". Consult for debugging, best practices, or modifying vue-router, vue router, router, file-based routing, typed routes, data loaders.
Swift 6 and SwiftUI code rules for macOS apps, including concurrency, state, SwiftData, AppKit bridges, and fixes for common compiler errors. Use when writing, reviewing, or debugging Swift code in a Mac app, or on concurrency, Sendable, or "not in scope" errors.
Use when adding snippet support to a CloudCannon site, configuring MDX components, Hugo shortcodes or Eleventy shortcodes and includes for the Content Editor, debugging snippet round-trip issues, or setting up inline HTML snippets in markdown content.
Designs, engineers, and validates enterprise Gemini platform architectures. Use when designing multi-project hierarchies (Host, Central Governance Hub, Runtime Spoke, Tool/MCP Spoke), configuring Agent Gateway, authoring Agent Connectivity Templates (ALL_TRAFFIC vs PRIVATE_RANGES_ONLY), deploying Secure Web Proxy (SWP) with Policy-Based Routing (PBR) or Cross-Cloud mTLS Egress Hubs, configuring Private CA TrustConfig with Internal ALB + Serverless NEG, implementing Unified Access Policies (UAP Policy V2 CEL) and Semantic Governance (SGP), configuring 3P IdP Token Exchange (EntraID/Ping/Okta via ext_proc + STS) or Agent Identity Auth Manager (SPIFFE), enforcing Model Armor Floor Settings and Fail-Closed guardrails, deploying Cross-Project Registry sync, binding ADK agents on Agent Runtime, or executing Day-2 lifecycle operations. Don't use for read-only live log triage or incident diagnosis, or generic Google Cloud Identity and Access Management (IAM) debugging.