Discover Databases skills, compare source repositories and read the instructions for each workflow.
Deploy application changes via GitOps workflow. Updates manifests in Git, triggers Flux reconciliation, and verifies deployment. Use for safe, auditable deployments. Keywords: deploy, gitops, flux, reconcile, r...
List all pods in a specific namespace with their status. Used to get an overview of workload health. Keywords: list pods, namespace, pod status, workload overview, pod health.
Restart a pod stuck in CrashLoopBackOff. Use when pod has crashed 3+ times and a restart might resolve transient issues. Keywords: crashloop, restart, pod failure, container crash, pod stuck, pod crashing.
Get resource usage metrics for nodes and pods. Uses Kubernetes metrics server to retrieve CPU and memory usage. Use for capacity planning or investigating resource issues. Keywords: resource usage, CPU, memory,...
Diagnose storage and persistent volume issues. Checks PVC binding, storage class configuration, and volume mount status. Use when pods are stuck pending due to volume issues. Keywords: PVC, PV, storage, volume,...
Check Flux CD GitOps sync status. Verifies Kustomizations, HelmReleases, and GitRepositories are synced and healthy. Use for deployment verification and troubleshooting. Keywords: flux, gitops, sync, kustomizat...
Scale a deployment to a specified number of replicas. Used for both scaling up (to handle load) and scaling down. Keywords: scale, replicas, deployment, statefulset, horizontal scaling, pod count.
Check resource usage (CPU, memory) for pods. Used to identify pods consuming excessive resources. Keywords: pod resources, cpu, memory, consumption, metrics, resource usage, top pods.
Get deployment health and replica status. Checks if deployment has desired replicas, available pods, and recent rollout status. Use to verify deployments are healthy. Keywords: deployment status, replica count,...
Collect recent Kubernetes events to identify issues. Events reveal warnings, errors, and state changes. Keywords: events, warnings, errors, cluster activity, state changes, recent events.
Get overall cluster health status. Checks node readiness, system pod health, and control plane components. Use for periodic health checks or incident investigation. Keywords: cluster health, node status, cluste...
Track and analyze usage metrics with timestamped logging
Use when implementing critical user workflows that span multiple pages/components - tests complete journeys end-to-end using Page Object Model, user-centric selectors, and condition-based waiting; use sparingly...
Run the project's test suite and fix any failures. If no test runner is configured, sets up best-in-class testing infrastructure for the project's language/framework. Ensures all tests pass before completion.
Use when creating new skills, editing existing skills, testing skills with pressure scenarios, or verifying skills work before deployment - applies TDD to process documentation by running baseline tests, writin...
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure fir...
Use when implementing UI components, design systems, or responsive layouts - verifies visual correctness through screenshot comparison and DevTools verification; prevents shipping broken UI
Use when implementing any UI - verifies accessibility compliance through automated testing (axe-core), keyboard navigation, screen reader verification, and Lighthouse audits; legally required and ensures inclus...
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without unders...
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling; prefer event-based waiting when available (WebSockets, EventEmi...
Fuzzing Rust projects with cargo-fuzz and libFuzzer for finding bugs through automated input generation.
Property-based testing for stronger coverage than example tests - roundtrip, idempotence, invariants.
Write the test first, watch it fail, write minimal code to pass. The Iron Law of TDD.
Use when testing ALTO protocol and finding issues. Run protocol tests, analyze artifacts, find issues, classify, and optionally fix. Invoked via /alto-test-protocol in dev mode.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.