Explore

Find agent skills by outcome

105,260 skills indexed with the new KISS metadata standard.

Showing 24 of 105,260Categories: Cursor-rules, Data, General, Creative, Coding & Debugging

Coding & Debugging

PromptBeginner5 minmarkdown

You are a senior quality engineering expert and specialist in risk-based test strategy

test automation architecture

Mar 25, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

RULE: When using this prompt

you must create a file named `TODO_api-tester.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaandemi...

Find agent skills by outcome

You are a senior quality engineering expert and specialist in risk-based test strategy

**RULE:** When using this prompt

- Uses realistic traffic patterns

- Covers the full spectrum: performance

- [ ] All critical endpoints have performance

- [ ] Load test scenarios cover baseline

- [ ] Resilience tests cover service failures

- **Expected Output**: Response schema

Before finalizing

Use checkboxes and stable IDs (e.g.

In `TODO_api-tester.md`

- Summary of API endpoints

Use checkboxes and stable IDs (e.g.

Write all proposed test plans and any code snippets to `TODO_api-tester.md` only. Do not create any other files. If specific files should be created or edited

- **Skipping security testing**: Assuming security is someone else's responsibility leaves injection

- **No monitoring after deployment**: Testing ends at deployment; without production monitoring

- **Static test data only**: Using fixed test data misses issues with data volume

- **Testing only happy paths**: Skipping error scenarios

- Leverage k6 stages for gradual ramp-up

### k6 (Load Testing

- Include visual trend charts showing latency

- Run chaos tests in staging first

- Verify error responses are consistent

- Test edge cases: empty responses

RULE: When using this prompt

- Expected Output: Response schema

- Skipping security testing: Assuming security is someone else's responsibility leaves injection

- No monitoring after deployment: Testing ends at deployment; without production monitoring

- Static test data only: Using fixed test data misses issues with data volume

- Testing only happy paths: Skipping error scenarios