Skip to content
TrustedSkillsbeta
Back to all skills

Qa Checklist

Checked
svenja-dev·vlatest·testing

This QA Checklist skill generates structured checklists for testing software or processes, ensuring thoroughness and reducing errors.

Repository

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 svenja-dev/claude-code-skills --skill qa-checklist -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

svenja-dev

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 svenja-dev/claude-code-skills at 4771c8e872.

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

Commit
4771c8e872
Manifest
skills/qa-checklist/SKILL.md
Scanned
1 file, 215 lines
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 checklists based on provided requirements or user stories. It helps ensure comprehensive testing coverage by creating structured lists of test cases and expected results. The generated checklists are designed to be adaptable and can cover various software development stages, from unit tests to integration testing.

When to use it

  • New Feature Development: Generate a checklist before starting implementation to define necessary test scenarios.
  • Bug Fix Verification: Create a targeted checklist to ensure the fix addresses all aspects of the reported issue.
  • User Story Validation: Confirm that user stories are thoroughly tested and meet acceptance criteria.
  • Regression Testing: Quickly generate checklists for regression testing suites based on existing features or changes.

Key capabilities

  • Generates QA checklists from requirements.
  • Creates test cases with expected results.
  • Adaptable to various software development stages (unit, integration).
  • Supports user story validation.

Example prompts

  • "Create a QA checklist for the 'user login' feature."
  • "Generate a checklist based on this user story: As a user, I want to be able to reset my password."
  • “Develop a test plan and checklist to validate the new payment processing integration.”

Tips & gotchas

The quality of the generated checklist depends heavily on the clarity and detail provided in the input requirements or user stories. Provide as much context as possible for best results.