tool-agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web appl...
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web appl...
Copy text to the system clipboard. Use when user asks to copy something, send to clipboard, or similar requests.
Review technical recommendations before presenting them to the user. Use BEFORE suggesting config changes, optimizations, refactors, or architecture decisions. Spawns a subagent to challenge assumptions and fil...
Review pull requests and uncommitted code changes. Use when user asks to review a PR, review changes, review uncommitted code, review a diff, or similar code review requests. Activates for phrases like "review...
Enforce TDD when fixing bugs - write a failing test first, then make it pass. Use when about to fix a bug, correct broken behavior, or resolve an issue in production code. Activates for phrases like "let me fix...
Skill on how to write a task. Use when user asks you to write a task (for Asana, Linear, Jira, Notion and equivalent). Also activates when user says "create task", "write task", or similar task creation workflo...
Write Ruby on Rails specs with RSpec following best practices for unit tests, request specs, feature specs, and job specs. Use when writing or modifying RSpec test files for Rails applications.
Stage and commit git changes with conventional commit messages. Use when user wants to commit changes, or asks to save their work, even when committing your own work after completing a task. Also activates when...
Use when the user asks you to interact, work, read, create or update tasks in ai-notes/**/*/todo.{md,txt} files, or when user asks you to look at the "todo file".
Persistent memory for AI coding agents. USE WHEN user says "save context", "remember this", "checkpoint", "resume session", "prepare for compaction", "wrap up", OR when starting work on a project that may span...
Run unit tests for the API Service and Analyzers. Use this to verify business logic, individual components, and code analyzers.
Guide for creating and registering a new agent skill.
Create a new event-sourced aggregate with proper Apply methods, event handling, and Marten configuration. Use this when adding a new domain entity that needs event sourcing.
Deploy the BookStore application to a Kubernetes cluster using Aspire-generated manifests. Use this for Kubernetes deployments (AKS, EKS, GKE, etc.).
Guide for adding a new write operation (command/mutation) to the Backend. Focuses on Event Sourcing, Wolverine commands, and Projections.
Guide for adding a new feature to the Web Frontend (Blazor), focusing on Reactive State, Optimistic Updates, and Cache Invalidation.
Debug Server-Sent Events (SSE) notification issues when real-time updates aren't working. Use this when mutations don't trigger frontend updates.
Create integration tests for API endpoints with SSE event verification and TUnit patterns. Use this when you need to test a new endpoint.
Clean and rebuild the solution to ensure a fresh state. Use this when the user faces transient build errors or stale artifacts.
Debug HybridCache and Redis caching issues when data isn't being cached or invalidated correctly. Use this when cache hit/miss rates are wrong.
Deploy the BookStore application to Azure using Aspire and azd. Use this to ship the application to production.
Rollback a failed deployment to the previous working version. Use this when a deployment causes issues in Azure or Kubernetes.
Strict verification for new features. Runs compilation, formatting, and all tests to ensure the "Definition of Done".
Guide for adding a new read operation (query) to the Backend. Focuses on Marten queries, Projections, Caching, and Pagination.
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.