Skip to content
TrustedSkillsbeta
Back to all skills

Clojure Review

Checked
microck·vlatest·backend

Reviews Clojure code for style, common errors, and potential improvements using microck's established best practices.

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 microck/ordinary-claude-skills --skill clojure-review -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

microck

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

    Only contacts known or declared hosts: github.com.

    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.

    Hosts contacted

    github.comsource host

  • 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 microck/ordinary-claude-skills at 1056d293d4.

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

Commit
1056d293d4
Manifest
skills_all/clojure-review/SKILL.md
Scanned
6 files, 477 lines
Copies in repo
3 — 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

The microck-clojure-review skill allows an AI agent to review Clojure code. It can analyze and provide feedback on existing Clojure programs, helping identify potential issues or areas for improvement. This skill is designed to assist developers in maintaining and enhancing their Clojure codebase.

When to use it

  • Code Quality Assurance: Use the skill to automatically check a new feature branch for common Clojure coding errors before merging into the main development line.
  • Refactoring Assistance: Have the agent review a complex function or module to suggest more concise or efficient implementations.
  • Learning and Education: A junior developer can use it to get feedback on their Clojure code, accelerating learning.
  • Legacy Code Analysis: Review older Clojure projects to identify areas that could benefit from modernization or optimization.

Key capabilities

  • Clojure code review
  • Analysis of existing programs
  • Feedback and suggestions for improvement

Example prompts

  • "Review this Clojure function: [paste code here]"
  • "Can you analyze this Clojure program for potential performance bottlenecks?"
  • "Give me feedback on the style and clarity of this Clojure module."

Tips & gotchas

The skill's effectiveness depends on providing clear and complete Clojure code snippets. While it can identify common issues, it may not understand complex domain-specific logic without additional context.