Loading...
Loading...
Found 507 Skills
Use when creating, writing, fixing, or reviewing tests in a Flutter project. Covers unit tests, widget tests, integration tests, Riverpod provider testing, and Mockito mocking. Provides Given-When-Then patterns, layer isolation strategies, and test setup for GetIt, SharedPreferences, and FakeDatabase.
Optimize provider selection, routing, and credit usage across 150+ enrichment sources for company/contact intelligence.
This skill should be used when creating a new runtime provider for the vx tool manager. It provides complete templates, code generation, and step-by-step guidance for implementing Provider and Runtime traits, including URL builders, platform configuration, test files, provider.toml manifest, system package manager fallback, and optionally project analyzer integration for language-specific tools. Use this skill when the user asks to add support for a new tool/runtime in vx.
Use when nestJS dependency injection with providers, modules, and decorators. Use when building modular NestJS applications.
Debugs and fixes Terraform errors systematically. Use when encountering Terraform failures, state lock issues, provider errors, syntax problems, or unexpected infrastructure changes. Includes debugging workflows, error categorization, common GCP-specific issues, and recovery procedures.
Flutter state management patterns — decision tree for setState, Provider, Riverpod, and BLoC with concrete examples and testing strategies
Test Riverpod providers and widgets; ProviderContainer.test, unit tests, widget tests with ProviderScope, tester.container(), mocking with overrides, container.listen for auto-dispose, awaiting .future. Use when writing unit or widget tests for Riverpod code, mocking providers, or testing with overrides. Use this skill when the user asks about testing Riverpod, mocking providers, or ProviderContainer in tests.
Migrate from package:provider to Riverpod; ChangeNotifierProvider, ProxyProvider to ref.watch, context.watch to ref.watch, ConsumerWidget, incremental migration, family and autoDispose. Use when the user is migrating from Provider to Riverpod, or asks about Provider vs Riverpod, or how to replace ProxyProvider/ChangeNotifierProvider.
Provisions and manages Neo4j Aura instances via CLI (aura-cli v1.7+) or REST API. Use when creating, pausing, resuming, resizing, or deleting AuraDB Free/Professional/Business Critical/VDC instances; downloading credentials; scripting CI/CD pipelines; polling async status; or using the Terraform neo4j/neo4j-aura provider. Covers auth setup (client credentials OAuth2), credential lifecycle (download once — never recoverable), instance type selection, region codes, and Python provisioning scripts. Does NOT handle Cypher queries — use neo4j-cypher-skill. Does NOT cover Graph Data Science algorithms — use neo4j-gds-skill or neo4j-aura-graph-analytics-skill. Does NOT cover neo4j-admin/cypher-shell — use neo4j-cli-tools-skill.
Use to design provider sequences, throttling logic, and credit policies for enrichment waterfalls.
Uses Riverpod for state management in Flutter/Dart. Use when setting up providers, combining requests, managing state disposal, passing arguments, performing side effects, testing providers, or applying Riverpod best practices.
Get verified emails and phones for contacts found by people-search. Takes LinkedIn profiles from the Extruct people table and enriches them via contact enrichment providers like Prospeo or Fullenrich. Supports single-provider and waterfall modes. Outputs a contact CSV ready for email-generation. Triggers on: "get emails", "find emails", "enrich contacts", "email finder", "get phone numbers", "enrich people", "contact enrichment", "verify emails", "email enrichment".