Acceptance-test newly added features using browser automation, happy-path flows, screenshots, UX notes, and a written report. Use when asked to test a feature, verify a recent UI change, or check whether an app workflow works.
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add SDiamante13/dotfiles --skill test-feature --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Test Feature?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sdiamante13-test-feature)More formats (shields.io, HTML) on the badges page.
---
name: test-feature
description: Acceptance-test newly added features using browser automation, happy-path flows, screenshots, UX notes, and a written report. Use when asked to test a feature, verify a recent UI change, or check whether an app workflow works.
---
# Feature Acceptance Testing
Use the user's configured browser automation tool to perform acceptance testing on recently added features.
## Testing Process
1. **Get Application URL**: Ask the user for the URL of the application to test
2. **Handle Authentication**: If login screens are encountered, ask the user for guidance
3. **Test Happy Paths**: Run through all main user flows for the new features (not intensive QA, just sensible "does this work" testing)
4. **Identify Issues**: Document any features not working as expected
5. **UX/UI Review**: Note any UX/UI improvements that could be made
6. **Generate Report**: Create a comprehensive test report
## Report Format
The report should include:
- List of all features that are not working as expected
- UX/UI improvement suggestions
- Save location: Current directory with naming format: `test-report-{feature-name}-{YYYY-MM-DD-HH-MM}.md`
## Execution
Use the browser automation tool to:
- Navigate through the application
- Test all happy path scenarios
- Capture screenshots of issues
- Document findings in a structured report
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or "compress memory file"
