Skip to content
TrustedSkillsbeta
Back to all skills

Temporal Python Testing

Checked
wshobson·vlatest·backend·MIT

Helps with Python, testing as part of developing backend services and APIs 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 wshobson/agents --skill temporal-python-testing -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

wshobson

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 wshobson/agents at 46891e7e60.

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

Scanned
5 files, 1,841 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

The temporal-python-testing skill enables AI agents to perform testing tasks related to Python code within a Temporal workflow context. It supports writing, executing, and validating unit tests, integration tests, or test suites that are compatible with Temporal's distributed task orchestration framework.

When to use it

  • You need to validate the correctness of Python functions used in Temporal workflows.
  • You're developing or maintaining a Temporal-based application and want automated testing capabilities.
  • Your team requires consistent test execution across multiple workers or environments managed by Temporal.

Key capabilities

  • Integration with Temporal's workflow execution model
  • Support for writing and running Python unit tests
  • Compatibility with Temporal's task queue and activity worker architecture

Example prompts

  • "Write a unit test for the process_order function in my Temporal workflow."
  • "Run all integration tests for the inventory_service module using Temporal workers."
  • "Validate that the checkout_activity correctly handles exceptions in a Temporal workflow."

Tips & gotchas

  • Ensure your Python environment has Temporal SDK and testing libraries installed.
  • Test workflows may require specific task queue configurations to execute properly.