Skip to content
TrustedSkillsbeta
Back to all skills

Test

Checked
parcadei·vlatest·testing·MIT

Evaluates AI model responses against predefined test cases to measure accuracy and identify areas for improvement.

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 parcadei/continuous-claude-v3 --skill test -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

parcadei

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 parcadei/continuous-claude-v3 at d07ff4b06b.

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

Commit
d07ff4b06b
Manifest
.claude/skills/test/SKILL.md
Scanned
1 file, 213 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 is a placeholder or experimental entry within the parcadei/continuous-claude-v3 registry, currently lacking specific functional descriptions or capabilities in its source metadata. It serves as a test artifact rather than a fully documented tool for AI agents.

When to use it

  • Do not use this skill for production tasks due to missing documentation.
  • Use only if you are the author (parcadei) debugging the registry entry itself.
  • Avoid relying on this for any specific AI agent workflow until details are published.

Key capabilities

  • None explicitly defined in the current source content.
  • Listed under the "other" category with 129 install counts, indicating potential community interest despite lack of info.
  • Associated with the continuous-claude-v3 environment.

Example prompts

  • "What does the parcadei-test skill actually do?"
  • "Can I use this test skill to run a continuous integration task?"
  • "How do I configure parcadei/continuous-claude-v3/test for my agent?"

Tips & gotchas

  • Prerequisites: None listed, but expect limitations due to incomplete metadata.
  • Limitations: Without explicit capabilities, assume this skill may not function as intended or could be deprecated. Always verify with the author before deployment.