Skip to content
TrustedSkillsbeta
Back to all skills

Integration Test Writer

Checked
matteocervelli·vlatest·testing·MIT

Helps with integration, testing 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 matteocervelli/llms --skill integration-test-writer --full-depth -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

matteocervelli

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 matteocervelli/llms at 1e1f2089eb.

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

Scanned
1 file, 797 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 Integration Test Writer skill generates test cases for software integrations. It can create tests based on API documentation or existing code, ensuring that different systems work together correctly. This helps automate testing and improve the reliability of integrated applications.

When to use it

  • API integration: Generate test suites for new APIs your agent needs to interact with.
  • Code refactoring: Create tests after modifying existing integration points in a codebase.
  • Automated workflows: Develop comprehensive tests for automated processes that involve multiple services.
  • Regression testing: Quickly generate regression tests when changes are made to integrated systems.

Key capabilities

  • Test case generation from API documentation
  • Test case generation from existing code
  • Support for various integration scenarios

Example prompts

  • "Generate integration tests for the Stripe API, focusing on payment processing."
  • "Create test cases based on this Python code snippet that integrates with a database."
  • "Write tests to verify the interaction between our CRM and email marketing platform."

Tips & gotchas

The quality of generated tests depends heavily on the clarity and completeness of the API documentation or existing code provided. Ensure these sources are accurate for best results.