Skip to content
TrustedSkillsbeta
Back to all skills

Testing

Checked
oliver-kriska·vlatest·testing·MIT

Automates rigorous software testing using Oliver Kriska's methodologies, identifying bugs and ensuring quality code.

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 oliver-kriska/claude-elixir-phoenix --skill 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

oliver-kriska

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 oliver-kriska/claude-elixir-phoenix at 19791bb7dc.

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

Scanned
15 files, 1,758 lines
Copies in repo
3 — all of them scanned
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 provides automated testing capabilities, likely focusing on Elixir and Phoenix applications. It allows users to execute tests within a development environment and analyze results, streamlining the software development lifecycle. The specific details of its testing framework are not provided in the source content.

When to use it

  • Automated Regression Testing: Run existing test suites after code changes to ensure no regressions have been introduced.
  • Continuous Integration Pipelines: Integrate with CI/CD systems to automatically execute tests on every commit or pull request.
  • Testing New Features: Quickly verify the functionality of newly developed features within a Phoenix application.
  • Debugging and Troubleshooting: Isolate and reproduce bugs by running specific test cases.

Key capabilities

  • Elixir testing support
  • Phoenix framework integration
  • Automated test execution
  • Result analysis

Example prompts

  • "Run the unit tests for the authentication module."
  • "Execute all integration tests in the /api directory."
  • "Show me the results of the last test run, highlighting any failures."

Tips & gotchas

This skill likely requires an environment with Elixir and Phoenix already set up. The specific testing framework used (e.g., ExUnit) may need to be configured within that environment for optimal performance.