Loading...
Loading...
Found 397 Skills
Use when managing multiple environments with Pulumi stacks for development, staging, and production deployments.
Run /check-bitcoin, then fix the highest priority Bitcoin issue. Creates one fix per invocation. Invoke again for next issue. Use /log-bitcoin-issues to create issues without fixing.
Use when writing infrastructure-as-code with Pulumi using programming languages for cloud resource provisioning.
Use when managing Helm values files and configuration overrides for customizing Kubernetes deployments.
Publish @autumnsgrove/groveengine to npm with proper registry swap workflow. Use when releasing a new version of the engine package to npm.
Analyze failed GitHub Action jobs for a pull request.
Manage Tailscale tailnet via CLI and API. Use when the user asks to "check tailscale status", "list tailscale devices", "ping a device", "send file via tailscale", "tailscale funnel", "create auth key", "check who's online", or mentions Tailscale network management.
Monitors awesome-copilot releases for drift against the amplihack integration. Checks latest commits on github/awesome-copilot via the GitHub API and reports whether the local integration is current or has drifted behind upstream changes. Use when auditing integration freshness or before updating awesome-copilot features.
This skill should be used when the user asks to "write a Tiltfile", "configure Tilt", "set up live update", "debug Tilt", "add a resource to Tilt", "optimize Tilt builds", "view Tilt logs", "restart a Tilt resource", or mentions Tiltfile, tilt up, tilt ci, tilt down, live_update, docker_build, custom_build, k8s_resource, local_resource, or Kubernetes local development with Tilt.
Complete fullstack development mastery covering modern web architectures, automation tools, AI integration, and production deployment practices
Use when optimizing GitLab CI/CD pipelines for performance, reliability, or maintainability. Covers pipeline optimization and organizational patterns.
Guides users through writing, validating, and operationalizing Non-Functional Requirements (NFRs), Service Level Objectives (SLOs), Service Level Indicators (SLIs), and fitness functions. This skill should be used when a user wants to define or review NFRs for a system, translate NFRs into SLOs/SLIs, or generate automatable fitness functions (performance tests, ArchUnit-style architecture tests, availability checks, recovery drills) that validate a system against its non-functional requirements.