pbuckles22/tester
.cursor/skills/tester/SKILL.md
Black-box tests, test-first for core logic, and continuous test runs. Use when adding or changing tests or app logic. Run your project’s test command after changes; keep suite green.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add pbuckles22/URLAutoRefresher testerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 2:23 AM9.7s1 file scanned
SKILL.md
- name:
- tester
- description:
- Black-box tests, test-first for core logic, and continuous test runs. Use when adding or changing tests or app logic. Run your project’s test command after changes; keep suite green.
Tester — Project
Use this skill when writing or running tests, or when touching app logic or new behavior. First action when adding new behavior: Read this skill and TEST_TDD.md, then write a failing test at the appropriate tier(s) before production code.
Role
- Black-box tests: Assert on behavior (public API: inputs and outputs). Do not depend on implementation details.
- Test-first (both tiers): See TEST_TDD.md. Tier 1: Vitest —
npm test→ red, then code → green. Tier 2: Playwright —npm run test:e2e(afternpm run build) → red, then code → green. Use Tier 2 whenever behavior spans the real browser or extension surfaces. - TDD loop: (1) Tier 1 red/green if logic is unit-testable. (2) Tier 2 red/green if the feature needs the browser/extension. (3) Document if needed. (4)
npm run cibefore merge. - Continuous: Run tests after each small step. Keep the suite green. CI runs the same checks in GitHub Actions.
Source of truth
- What to test: TEST_TDD.md.
- Test plan (two tiers): TEST_PLAN.md.
Related Skills
pbuckles22/visual-match
tools
VerifiedTrustedCommunity
Match UI graphics to reference examples (examples/ screenshots and specs). Use when drawing or changing visuals so the result matches the examples without back-and-forth.
SKILL.mdUpdated Apr 16, 2026
pbuckles22/ui-ux
content-media
VerifiedTrustedCommunity
UI/UX review and alignment. Use when writing or reviewing screens, animations, haptics, layout, or design tokens; or when adding/changing UX to match project requirements and accessibility.
SKILL.mdUpdated Apr 16, 2026
pbuckles22/techwriter
development
VerifiedTrustedCommunity
Creates and edits project documentation for both public and internal audiences. Use when writing or updating README.md, AGENT_HANDOFF (or AGENTS.md), CONTRIBUTING, or internal docs (e.g. PM_PLAN, DEV_GUIDE, TEST_TDD, DESIGN_SYSTEM). Covers structure, tone, and what to include for each doc type.
SKILL.mdUpdated Apr 16, 2026
pbuckles22/tech-debt-evaluator
development
VerifiedTrustedCommunity
Assess and prioritize technical debt (code, architecture, tests, docs, performance). Use when planning refactors, sprint planning, or evaluating codebase health.
SKILL.mdUpdated Apr 16, 2026