Find agent skills by outcome

In TODO_api-tester.md

include:

PromptBeginner5 minmarkdownQuality: 28

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

regressions and real-world failures go undetected

- Testing only happy paths: Skipping error scenarios

edge cases

PromptBeginner5 minmarkdownQuality: 28

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

authentication

k6 (Load Testing

Performance Scripting)

- Leverage k6 stages for gradual ramp-up

sustained load

- Verify error responses are consistent

structured

- Run chaos tests in staging first

then graduate to production with limited blast radius

- Test edge cases: empty responses

maximum payload sizes

- [ ] Security testing completed: injection

authentication

- Use realistic user behavior patterns

not synthetic uniform requests

- [ ] Resilience tested: circuit breakers

graceful degradation

- [ ] All endpoints tested under baseline

peak

- [ ] Response time percentiles (p50

p95

- Compile test results into structured report with metrics

bottlenecks

Coding & Debugging

After completing API testing

verify:

- Test webhook delivery

retry behavior

- Define success criteria: target response times

throughput

- Information disclosure in error responses: stack traces

internal paths

- Authentication weaknesses: token leakage

missing expiration

- Resource Utilization: CPU <70% at expected load

memory stable without unbounded growth

- Inadequate retry logic: no retries

or retries without backoff causing retry storms

Coding & Debugging

- Throughput: Read-heavy APIs >1000 RPS per instance

write-heavy APIs >100 RPS per instance

- Error Rates: 5xx errors <0.1%

4xx errors <5% (excluding 401/403)