Loading...
Loading...
Found 4,064 Skills
Test, commit, and push in one atomic workflow. Runs Go and Python tests, commits with conventional message, pushes to current branch.
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
Conduct a comprehensive accessibility audit against WCAG guidelines with severity ratings and remediation steps.
Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time".
Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.
Run adversarial browser tests against code changes. Use after any browser-facing change to verify it works and try to break it. Prefer this over raw browser tools (Playwright MCP, chrome tools).
A skill to improve test code quality based on the test principles from Google's "Software Engineering at Google". It supports creating new tests, reviewing and refactoring existing tests. Must be used when users make requests such as: "Write tests", "Add tests", "Review test code", "Refactor tests", "Improve test quality", "Check if test principles are followed", "Use good test writing practices", "I want tests for this method", "Insufficient test cases", "Review tests", "Increase coverage". Actively trigger this skill for any test-related work even if the skill name is not explicitly mentioned. It has three subcommands: review (test code review), refactor (refactoring existing tests), write (creating new tests).
Set up and run unit, integration, and E2E tests for Chrome extensions. Covers Jest mocks for chrome.* APIs and Puppeteer E2E with real Chrome.
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
This skill should be used when a developer is ready to implement a GitHub Task issue and needs to read the full spec hierarchy (Task + Feature + Epic), explore the codebase, produce a concrete Technical Approach with real file paths, and drive TDD implementation against Gherkin scenarios. Triggers on phrases like "implement task
Revolut X grid trading strategy. Use when the user asks to "backtest a grid strategy", "optimize grid parameters", "run a grid bot", "grid trading", "dry run grid", or runs revx strategy grid commands. Grid run is a long-running background process.
Agent-ergonomic browser automation with token-efficient accessibility tree snapshots and combined operations