Skip to content
TrustedSkillsbeta
Back to all skills

Test Analyze

Checked
laurigates·vlatest·testing·MIT

Helps with testing, analysis as part of testing, debugging, and quality assurance workflows.

Repository

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 laurigates/claude-plugins --skill test-analyze -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

laurigates

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 laurigates/claude-plugins at 45d1d7dcf6.

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

Commit
45d1d7dcf6
Manifest
testing-plugin/skills/test-analyze/SKILL.md
Scanned
2 files, 472 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, Test Analyze, helps AI agents analyze test results from various testing frameworks and create a systematic plan for fixing identified issues. It parses test result files, categorizes problems by type and severity, and uses a planning tool (Zen planner via MCP) to break down fixes into actionable steps. Finally, it delegates these fix tasks to specialized subagents based on the nature of the issue.

When to use it

  • After running unit tests to identify and address code failures.
  • Following integration testing to pinpoint issues between different system components.
  • When conducting accessibility audits using Playwright or similar tools, ensuring WCAG compliance.
  • To analyze security scan results (e.g., OWASP ZAP) and prioritize remediation efforts.
  • After performance tests (Lighthouse, k6) to identify bottlenecks and areas for optimization.

Key capabilities

  • Test Result Parsing: Supports XML, JSON, HTML, and text formats.
  • Issue Categorization: Classifies issues by type (accessibility, unit, integration, e2e, security, performance) and severity.
  • Fix Planning: Leverages a planning tool via MCP to create structured fix strategies.
  • Subagent Delegation: Automatically routes tasks to specialized subagents like code-review, security-audit, system-debugging, and documentation agents.
  • Test Type Detection: Can automatically detect the type of tests being analyzed if not explicitly specified.

Example prompts

  • /test:analyze ./test-results/ --type accessibility
  • /test:analyze ./coverage/junit.xml --type unit --focus authentication
  • /test:analyze ./test-output/

Tips & gotchas

  • The results-path parameter is required to specify the location of test results.
  • While the skill attempts to auto-detect the test type, providing it explicitly with --type can improve accuracy and ensure correct subagent delegation.