Skip to content
TrustedSkillsbeta
Back to all skills

Testing Clojure Cljs

Checked
riatzukiza·vlatest·backend

Automates Clojure & Clojurescript unit/integration tests, generating reports and identifying potential issues quickly.

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 riatzukiza/devel --skill testing-clojure-cljs -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

riatzukiza

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 riatzukiza/devel at 80a95e5638.

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

Scanned
2 files, 572 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 enables AI agents to write and execute tests for Clojure and Clojurescript projects. It can generate test code based on project structure, run existing tests, and report results. This allows automated verification of code functionality and helps ensure software quality in Clojure-based environments.

When to use it

  • Automated Testing: Integrate testing into a CI/CD pipeline for continuous validation.
  • Code Refactoring: Verify that changes haven't introduced regressions during refactoring efforts.
  • New Feature Development: Quickly create and run tests as you build new features in Clojure or Clojurescript projects.
  • Project Onboarding: Generate a baseline of tests for an existing project to understand its current state.

Key capabilities

  • Test generation
  • Test execution
  • Result reporting

Example prompts

  • "Generate unit tests for the core.clj namespace."
  • "Run all tests in the project and report any failures."
  • "Create a test suite for the function calculate-total in shopping.cljs."

Tips & gotchas

This skill requires a Clojure/Clojurescript development environment to be set up correctly. Ensure that Leiningen or similar build tools are available and configured before using this skill, as it relies on them for test execution.