Skip to content
TrustedSkillsbeta
Back to all skills

Pytest

Checked
manutej·vlatest·testing

Pytest helps you write and run automated tests for your Python code, ensuring quality and catching bugs early.

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 manutej/luxor-claude-marketplace --skill pytest -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

manutej

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 manutej/luxor-claude-marketplace at 1861cc9720.

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

Scanned
3 files, 4,872 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 enables AI agents to execute pytest commands directly within their environment, allowing them to run test suites and verify code correctness. It streamlines the testing workflow by removing the need for manual command-line invocation during development cycles.

When to use it

  • Automatically validate logic changes before committing code to a repository.
  • Run regression tests after an AI agent generates or modifies a function.
  • Verify that new dependencies do not break existing test cases.
  • Execute full test suites as part of a continuous integration simulation.

Key capabilities

  • Runs pytest commands natively in the agent's shell context.
  • Executes specific test files or individual test functions.
  • Reports pass/fail status and output logs directly to the conversation.

Example prompts

  • "Run all tests in the tests/ directory and summarize any failures."
  • "Execute the unit tests for the new user authentication module I just wrote."
  • "Run pytest with verbose output to see detailed error messages for the failing case."

Tips & gotchas

Ensure your project has a valid pytest.ini or pyproject.toml configuration file, as the agent relies on standard project structures to locate tests. If tests fail due to missing environment variables, provide those details in the prompt context before re-running.