Build Playwright tests that reproduce browser interactions, organize reusable page operations, and run checks automatically. Investigate tests that fail inconsistently, and save screenshots, videos, and execution traces to help diagnose failures.
- Testing login and search flows
- Organizing reusable page operations
- Investigating intermittent test failures
affaan-m/ECC☆ 283.7KUpdated Oct 16, 2026
Write and review C# and .NET tests using xUnit examples. Covers unit tests, mocks that replace dependencies, API and database integration tests, reusable test data, and project organization to check behavior and outcomes.
- Adding tests for C# services
- Testing ASP.NET Core APIs
- Checking database persistence
affaan-m/ECC☆ 283.7KUpdated Oct 16, 2026
Write Django and Django REST Framework tests with pytest-django, starting with tests before implementation. Covers test data generation, simulated external services, model and API checks, and coverage reports showing which code the tests exercise.
- Developing Django features by writing tests first
- Testing API authentication and input validation
- Generating reusable test data
affaan-m/ECC☆ 283.7KUpdated Oct 16, 2026
Check a Django application before a pull request or deployment. Review its environment, code quality, database changes, tests, vulnerabilities, and configuration, then produce a phased pass/fail report identifying issues that need fixes.
- Checking a Django pull request
- Reviewing database migrations
- Checking test coverage targets
affaan-m/ECC☆ 283.7KUpdated Oct 16, 2026
Trace button clicks and form actions through each state change to uncover conflicting updates, unintended resets, and asynchronous timing problems. Report where the final screen behavior differs from what the user expects, with specific fixes.
- Investigating buttons that appear to do nothing
- Checking shared state after a major refactor
- Auditing critical user flows before release
affaan-m/ECC☆ 283.7KUpdated Oct 16, 2026
Measure web page speed, API response times, and build or test duration. Save baseline measurements as JSON tracked in Git, then compare results before and after changes to identify performance regressions and assess launch targets.
- Comparing performance before and after a code change
- Investigating reports that a page feels slow
- Checking performance targets before launch
affaan-m/ECC☆ 283.7KUpdated Oct 16, 2026
Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.
- Comparing coding agents on real development tasks
- Evaluating a new tool or model before adoption
- Checking performance after agent updates
affaan-m/ECC☆ 283.7KUpdated Oct 16, 2026
Have an AI agent assess its completed work for accuracy, completeness, clarity, actionability, and conciseness. Receive a scorecard with evidence, an average score, and prioritized improvements tied to the original request.
- Assess code after a multi-file implementation
- Check deliverables after a multi-step workflow
- Evaluate a design document or written analysis
affaan-m/ECC☆ 283.7KUpdated Oct 16, 2026
Add regression tests to AI-assisted code changes so previously found bugs are checked automatically. Test required API fields and sandbox response contracts, then run tests and builds before AI review to catch recurring omissions and inconsistent behavior.
- Add regression tests after fixing a bug
- Check required API response fields
- Review sandbox and production response consistency
affaan-m/ECC☆ 283.7KUpdated Oct 16, 2026
Test deployed web pages through browser automation. Check forms, login flows, loading and responsiveness metrics, visual changes at three screen widths, and accessibility issues, then receive a report with fixes and a release verdict.
- Testing a feature deployed to staging or preview
- Checking forms and login flows before release
- Comparing layouts at three screen widths
affaan-m/ECC☆ 283.7KUpdated Oct 16, 2026
Test an authorized web application, map its exposed pages and inputs, and verify suspected vulnerabilities with reproducible evidence. Produce a security report covering confirmed findings, their impact, reproduction steps, and suggested fixes.
- Check a staging web application for vulnerabilities
- Verify whether a suspected vulnerability is reproducible
- Compile evidence and fixes into a security report
NousResearch/hermes-agent☆ 255.2KUpdated Oct 19, 2026
Find personal information exposed on data brokers and people-search sites, then manage removal requests for consenting individuals. Tracks submissions, checks whether listings disappear, schedules repeat scans, and collects steps that require human help.
- Finding sites exposing personal information
- Managing removal requests for a consenting family member
- Checking progress and verifying removals
NousResearch/hermes-agent☆ 255.2KUpdated Oct 19, 2026
Test how API-accessible language models respond to attempts to bypass safety filters. The skill covers prompt templates, input transformations, parallel response comparisons, and Hermes configuration, with automated scoring of refusals, answer quality, and speed.
- Evaluating model resistance to safety-filter bypass attempts
- Comparing responses to transformed inputs
- Comparing refusals, answer quality, and speed across models
NousResearch/hermes-agent☆ 255.2KUpdated Oct 19, 2026
Set up the 1Password CLI and use stored passwords or API keys in commands and configuration templates. Choose an authentication method, retrieve secret references, and pass credentials to processes through environment variables.
- Installing and configuring the 1Password CLI
- Running commands with stored API keys
- Filling configuration templates with stored secrets
NousResearch/hermes-agent☆ 255.2KUpdated Oct 19, 2026
Investigate suspected malicious changes in open-source software on GitHub by comparing repository history, APIs, and archives. Attempt to recover deleted evidence, identify signs of compromise, and produce a report separating verified facts from hypotheses.
- Investigate suspicious commits or workflow changes
- Attempt to recover commits hidden by rewritten history
- Trace possible credential leaks
NousResearch/hermes-agent☆ 255.2KUpdated Oct 19, 2026
Test an app from the perspective of a frustrated, less technical user. Find confusing steps and barriers, separate actionable usability problems from personal complaints, and produce screenshots, suggested fixes, and prioritized tickets.
- Reviewing usability before a launch or demo
- Checking the experience of a new user
- Finding friction in signup and subscription flows
NousResearch/hermes-agent☆ 255.2KUpdated Oct 19, 2026
Guide development through test-driven development (TDD): write a test, confirm it fails, add minimal code, then clean up. Apply this cycle to features and bug fixes while checking that existing behavior still passes its tests.
- Adding features with tests written first
- Reproducing a bug in a test before fixing it
- Refactoring while keeping tests passing
NousResearch/hermes-agent☆ 255.2KUpdated Oct 19, 2026
Check code changes before committing with security scans, tests, linting, and an independent agent review. Compare failures against the previous baseline, then use a separate agent to fix reported problems and repeat verification.
- Checking feature changes before a commit
- Scanning added code for secrets and injection risks
- Separating new test failures from existing failures
NousResearch/hermes-agent☆ 255.2KUpdated Oct 19, 2026
Explore a web app in the browser to find functional, visual, and usability issues. The skill organizes screenshots, console errors, and reproduction steps into a Markdown bug report, with findings grouped by severity and category.
- Explore key user flows before release
- Check forms with valid, invalid, and empty input
- Document layout issues and JavaScript errors
NousResearch/hermes-agent☆ 255.2KUpdated Oct 19, 2026
Independently reviews deliverables handed over through Kanban, checks them against acceptance criteria and test evidence, and records an approval, actionable change request, or escalation when a human decision or external prerequisite is needed.
- Reviewing deliverables against acceptance criteria
- Rechecking corrections after a change request
- Returning reproducible defects to the implementer
NousResearch/hermes-agent☆ 255.2KUpdated Oct 19, 2026
Test local web applications with Playwright, a browser automation tool. Check frontend functionality, investigate interface behavior, capture screenshots, and inspect browser logs, with a helper script that manages one or more application servers during testing.
- Checking buttons and forms in a local web app
- Investigating interface problems with screenshots and logs
- Testing with both frontend and backend servers running
anthropics/skills☆ 182.2KUpdated Oct 10, 2026
Review a codebase for bugs, security risks, failures under expected load, missing tests, slow paths, and unnecessary code. Receive prioritized findings with concrete failure cases, small proposed fixes, and the consequences of leaving each issue unresolved.
- Assess the quality of an inherited codebase
- Find risks under expected concurrent usage
- Identify unnecessary code and dependencies
DietrichGebert/ponytail☆ 167.6KUpdated Oct 18, 2026
Plan a paid evaluation with predefined success criteria, comparison groups, decoy items, and stopping rules. Rehearse without spending, then run a three-item paid pilot and use its spending table to inform approval.
- Define evaluation criteria before spending
- Rehearse an evaluation at zero cost
- Check spending with a three-item paid pilot
garrytan/gstack☆ 136.9KUpdated Oct 19, 2026
Audit an existing test suite to find low-value or duplicate tests and code kept solely for those tests. Receive findings for review, with changes limited to batches you explicitly approve.
- Reviewing the value of existing tests
- Finding duplicate tests
- Finding code kept only for tests
garrytan/gstack☆ 136.9KUpdated Oct 19, 2026