- Home
- Skills
- Testing & Debugging
- moses staff
moses staff
Automated test case design and execution from requirements, PDFs, and screenshots with mandatory approval gates.
Free
Works with the AI Agents you already use
moses staff
Example session with this skill installed
I'm attaching the PDF for the new 'User Profile' feature. Create a test workbook and include happy paths for image uploads and negative cases for invalid file types.
- Read your context and instructions
- Compiled the moses staff
- Generated the UI component
I have analyzed the 'User Profile' PDF. I extracted 12 business rules regarding image dimensions, file extensions (JPG/PNG), and permission levels for 'Standard' vs 'Admin' roles.
Test Case Workbook: user_profile_feature_v1.xlsx
The workbook includes a full traceability matrix and a Jira-ready staging sheet.
| Sheet Name | Content Summary |
|---|---|
| Test Cases | 15 cases covering upload, deletion, and permission constraints. |
| Coverage | Maps requirements R-01 through R-12 to specific test IDs. |
| Suggestions | 2 notes regarding missing 'Cancel' button behavior in the source. |
| Jira Import | Standard CSV format for Xray/Zephyr import. |
Case Preview: TC-004 - Upload Invalid File Type
- Precondition: User is logged in and on the Profile Settings page.
- Steps: 1. Click 'Edit Profile'. 2. Select 'Upload Photo'. 3. Select 'document.pdf'. 4. Click 'Save'.
- Expected Result: Error message "Unsupported file format" appears; profile remains unchanged.
Next steps
- Download and review
user_profile_feature_v1.xlsx. - The test-case workbook is ready. Do you approve executing this exact version?
- If yes, identify the permitted test environment and provide or confirm any required access and test data.
user_profile_feature_v1.xlsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Manual test case creation from fragmented requirements is slow and error-prone. This skill automates the extraction of business rules and edge cases from your project documentation to produce professional, execution-ready test suites.
What it does
- Requirement extraction: Pulls actors, business rules, and acceptance criteria from PDFs, screenshots, and text files.
- Coverage mapping: Generates a traceability matrix linking test cases back to specific requirement IDs or source pages.
- Workbook generation: Produces a multi-sheet
.xlsxfile containing executable test cases, coverage gaps, and Jira-ready import data. - Test design: Derives happy paths, negative scenarios, boundary value analysis, and state transition tests based on source evidence.
- Controlled execution: Operates behind a strict approval gate, only running tests against permitted environments after manual sign-off.
How it works
- Analyze source: Supply your PRD, user stories, or UI mockups for automated extraction of business logic.
- Review design: The agent builds a comprehensive Excel workbook following professional QA standards.
- Approve gate: Review the delivered workbook and provide explicit approval for execution in a specific environment.
- Execute & report: The agent runs the approved cases and updates the workbook with status, evidence, and defect details.
Frameworks & tools
Uses standard Excel .xlsx structures and follows professional QA methodologies. Compatible with Jira, Xray, and Zephyr via standardized CSV/XLSX import templates.
Why this beats prompting it yourself
Generic prompts often invent missing requirements or hallucinate UI elements. This skill enforces a strict boundary between stated behavior and inference, ensuring every test case is rooted in project evidence while maintaining a mandatory human-in-the-loop approval gate for execution.
Use cases
- Sprint planning: Rapidly turn a new user story screenshot into a verified test suite.
- Regression testing: Map existing legacy documentation to a fresh set of executable test cases.
- Jira migration: Prepare bulk-import files for Xray or Zephyr from unstructured PDF requirements.
Known limitations
Does not support direct API mutation or system changes without explicit environment access and user approval. Visual verification is limited to OCR and image analysis capabilities.
Requires explicit approval before any execution. Does not support universal direct Jira API sync; uses staging views for import. Writing is in English unless otherwise requested.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 3 days ago
- Free with an Agensi account
Requires