quality analyst

    1

    Turn requirements into traceable test cases and execute risk-based QA across API, web, and unit layers.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    quality analyst

    Example session with this skill installed

    Write a test case document for the new user login feature. Requirements include email validation, password masking, and a maximum of 5 failed attempts. Use sequential TC IDs.

    • Read your context and instructions
    • Compiled the quality analyst

    I have analyzed the login feature requirements and generated a traceable test case document. The suite covers positive authentication, input validation, and security constraints.

    Test Case Specification: User Login Feature

    IDTitlePriorityStepsExpected Result
    TC-001Successful LoginHigh1. Navigate to /login.<br>2. Enter valid email.<br>3. Enter valid password.User is redirected to the dashboard.
    TC-002Email Format ValidationMedium1. Enter "invalid-email" in email field.<br>2. Trigger blur or submit.System displays error: "Please enter a valid email address."
    TC-003Password MaskingHigh1. Type characters into the password field.Characters are obscured by dots or asterisks.
    TC-004Account Lockout - ThresholdHigh1. Enter valid email.<br>2. Enter wrong password 5 times.Account is locked; error message "Too many attempts" appears.
    TC-005Empty CredentialsLow1. Click "Login" with empty fields.Form validation prevents submission; fields highlighted.
    TC-006Session PersistenceMedium1. Log in successfully.<br>2. Close browser.<br>3. Reopen browser to /dashboard.User remains authenticated (if 'Remember Me' was active).

    Next steps

    • Review the expected error strings to ensure they match the frontend localization files.
    • Provision synthetic test users in the staging database for TC-004 execution.
    • Confirm if a CAPTCHA is triggered alongside the lockout in TC-004.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Translating requirements into rigorous test suites is a bottleneck for most development teams. This skill automates the transition from user stories and acceptance criteria to comprehensive test documentation and live execution. It eliminates the guesswork in test planning by mapping requirements directly to risk-based scenarios including positive, negative, and boundary cases.

    What it does

    • Requirement Mapping converts user stories and acceptance criteria into traceable test cases without modifying the original intent.
    • Test Case Authoring generates structured Markdown documentation with clear steps, observable expected results, and metadata.
    • Risk-Based Coverage identifies critical paths, authorization checks, failure recovery, and regression scenarios.
    • Execution Reporting runs automated or manual checks using repository tools and reports results with evidence separate from specifications.
    • Environment Safety ensures tests run in non-production environments using synthetic data to protect PII and credentials.

    How it works

    1. Analyze Sources by reviewing the supplied story, requirements, project instructions, and implementation details.
    2. Design Scenarios by mapping requirements to positive, negative, and boundary flows while maintaining traceability.
    3. Draft Documentation using a standardized Markdown format with sequential IDs like TC-001.
    4. Execute and Verify by selecting appropriate testing tools (API, browser, or unit) to run checks and capture observed outcomes.

    Frameworks & tools

    This skill is framework-agnostic and adapts to your repository's existing testing infrastructure. It integrates with browser-based testing, API clients, and standard unit/integration runners like Jest, Pytest, or Playwright.

    Why this beats prompting it yourself

    Standard prompts often hallucinate expected behavior or fail to distinguish between a test plan and an execution report. This skill enforces strict traceability, handles edge cases like authorization and recovery, and ensures PII safety by defaulting to synthetic data.

    Use cases

    • Generate a full regression suite for a new feature based on its PR description.
    • Validate API endpoints against boundary conditions and negative inputs.
    • Document manual QA steps for internal stakeholders before a release.
    • Verify bug fixes by executing targeted checks and providing evidence.

    Known limitations

    Does not support production environments or real customer PII. Requires pre-existing test data or approval for synthetic data generation.

    Requires clear requirements or acceptance criteria to avoid TBD markers. Cannot execute tests without access to compatible local or CI testing tools and a non-production environment.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 15 days ago

    Permissions

    No special permissions declared or detected

    Listed15 days ago

    What's inside

    Frequently Asked Questions

    The skill generates structured Markdown test cases (TC-001, etc.) including positive/negative scenarios, boundary checks, and execution reports with evidence logs. It also generates the actual test scripts compatible with your chosen framework like Playwright or Pytest.

    This skill is framework-agnostic and adapts to your existing repository infrastructure. It can interface with common web, API, and unit testing tools including Jest, Pytest, Playwright, and standard REST clients.

    The Quality Analyst is designed for most autonomous AI agents that have file-system and environment access. Once added to your agent's library, it requires access to your project's requirements documentation or PR descriptions to begin mapping test cases.

    For security, this skill is restricted to non-production environments and uses synthetic data for all test execution. It is programmed to avoid real PII (Personally Identifiable Information) and requires pre-approved test data configurations to ensure your credentials remain safe.

    Unlike basic prompts, this skill enforces strict traceability between your requirements and test outcomes. It ensures that every acceptance criterion is mapped to a specific test case, preventing the 'hallucinated' results or missed edge cases common in generic AI interactions.

    New in Testing & Debugging