Skip to content
TrustedSkillsbeta
Back to all skills

Generate Tests

Checked
clear-solutions·vlatest·testing·MIT

Automatically generates comprehensive test cases from clear, concise solution descriptions to ensure robust software quality.

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 mavka-ai/unit-tests-skills --skill generate-tests -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

clear-solutions

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 clear-solutions/unit-tests-skills at 66d5aa34b5.

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

Scanned
23 files, 2,627 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 unit tests for code. It can produce test cases based on function signatures and docstrings, helping to ensure code quality and identify potential issues early in the development process. The generated tests are designed to cover various scenarios and edge cases.

When to use it

  • You have a new function or method you want to thoroughly test before integration.
  • You need to quickly create a baseline set of unit tests for existing code.
  • You're refactoring code and want to ensure the changes don’t introduce regressions.
  • You are working on a project with limited testing resources and need automated assistance.

Key capabilities

  • Generates test cases from function signatures.
  • Utilizes docstrings to inform test creation.
  • Supports various scenarios and edge cases in tests.

Example prompts

  • "Generate unit tests for this Python function: def add(x, y): return x + y."
  • "Create a set of tests for the following JavaScript code snippet: function calculateArea(width, height) { ... }"
  • “Write tests covering edge cases for this Go function with these docstrings.”

Tips & gotchas

The quality of generated tests depends heavily on clear and comprehensive docstrings in your code. Ensure docstrings accurately describe the expected behavior and inputs/outputs of functions for optimal results.