Skip to content
TrustedSkillsbeta
Back to all skills

Testing

Checked
lobehub·vlatest·testing

Automates model performance evaluation against LobeHub datasets, streamlining testing workflows and ensuring consistent results.

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 lobehub/lobehub --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

lobehub

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 lobehub/lobe-chat at 0b22b7f532.

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

Commit
0b22b7f532
Manifest
.agents/skills/testing/SKILL.md
Scanned
6 files, 706 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 automates model performance evaluation against LobeHub datasets, streamlining testing workflows and ensuring consistent results. It utilizes vitest to run tests within various project locations (webapp, packages, desktop) and provides guidance on best practices for writing effective and maintainable tests. The tool focuses on behavior-driven development and encourages targeted mocking strategies.

When to use it

  • To automatically execute unit tests across different parts of a codebase.
  • When verifying the performance of models against specific LobeHub datasets.
  • During development to ensure new code changes don't break existing functionality.
  • As part of a continuous integration/continuous delivery (CI/CD) pipeline for automated testing.
  • To quickly run a subset of tests, focusing on recently modified files or specific test categories.

Key capabilities

  • Runs vitest tests in specified locations (src/**/*.test.ts(x), packages/*/**/*.test.ts, apps/desktop/**/*.test.ts).
  • Provides guidance on preferred mocking techniques (e.g., vi.spyOn over vi.mock).
  • Includes test structure examples and mock patterns for browser APIs and direct dependencies.
  • Offers detailed guides for specific testing scenarios like database model, Electron IPC, Zustand store actions, agent runtime E2E, and desktop controller testing (accessible via references/).
  • Provides advice on handling failing tests – whether to fix or delete based on the reason for failure.

Example prompts

  • "Run the tests in the packages/database directory."
  • "Execute only the tests that have passed so far, specifically targeting the file at '[file-path]'."
  • "Run the unit tests for the webapp component."

Tips & gotchas

  • Avoid running bun run test as it executes all tests (over 3000), which takes approximately 10 minutes. Use more targeted commands instead.
  • Ensure that new tests pass a type check by running bun run type-check.
  • Prioritize behavior testing over implementation details to create more robust and maintainable tests.