Skip to content
TrustedSkillsbeta
Back to all skills

Qa Test Generate

Checked
parhumm·vlatest·testing

Helps with testing, code generation as part of agent workflows workflows.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add parhumm/jaan-to --skill qa-test-generate -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

parhumm

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned parhumm/jaan-to at 3d44bff6a8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 757 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill generates QA test cases based on provided requirements or user stories. It can produce a variety of tests, including positive and negative scenarios, boundary conditions, and edge cases. The generated tests aim to ensure comprehensive coverage and identify potential issues in software development.

When to use it

  • Software Development: Quickly generate initial test suites for new features or modules.
  • Requirement Analysis: Validate the completeness and clarity of requirements by generating test cases that expose ambiguities.
  • Agile Teams: Support sprint planning and execution by automating test case creation.
  • Test Automation: Create a foundation for automated testing frameworks.

Key capabilities

  • Generates QA test cases
  • Supports positive and negative scenarios
  • Identifies boundary conditions
  • Creates edge case tests

Example prompts

  • "Generate test cases for the user story: As a user, I want to be able to reset my password."
  • "Create test cases based on these requirements: [paste requirements here]"
  • “Give me negative test cases for an email login form.”

Tips & gotchas

The quality of generated tests depends heavily on the clarity and completeness of the input requirements or user stories. Providing detailed information will yield more effective test cases.