Testing

Name: Testing
Author: thebeardedbearsas

Checked

thebeardedbearsas·vlatest·testing·MIT

Automates regression test execution and reporting across multiple environments using configurable parameters and detailed analysis.

Repository

Install on your platform

This skill no longer installs under the name testing. SKILL.md frontmatter is not valid YAML, so the skills CLI skips it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-15. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

thebeardedbearsas

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 29 Sept 2026

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 thebeardedbearsas/claude-craft at 99c1ee30cb.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 99c1ee30cb
Manifest: .claude/skills/testing/SKILL.md
Scanned: 4 files, 595 lines
Copies in repo: 2 — 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, "testing," provides automated testing capabilities. It allows users to execute tests and receive results, facilitating quality assurance and validation processes. The skill is designed to streamline testing workflows and improve overall software reliability through automated checks.

When to use it

Automated Regression Testing: After code changes or updates, run regression tests to ensure existing functionality remains intact.
Unit Test Execution: Execute unit tests for individual components of a system to verify their correctness.
Integration Test Validation: Validate the interaction between different modules or systems through integration testing.
Continuous Integration/Continuous Delivery (CI/CD) Pipelines: Integrate automated testing into CI/CD pipelines for rapid feedback and deployment.

Key capabilities

Test Execution
Result Reporting
Automated Testing

Example prompts

"Run the regression test suite."
"Execute all unit tests in the 'authentication' module."
"Validate the integration between the payment gateway and order processing system."

Tips & gotchas

This skill requires a properly configured testing environment with defined test cases. Ensure that dependencies are met before initiating test execution to avoid errors or unexpected results.