Skip to content
TrustedSkillsbeta
Back to all skills

Clojure Review

Checked
metabase·vlatest·backend

Analyzes Clojure code for style, potential errors, and best practices, suggesting improvements aligned with Metabase standards.

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

metabase

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 metabase/metabase at 674c8b8dc6.

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

Commit
674c8b8dc6
Manifest
.claude/skills/clojure-review/SKILL.md
Scanned
1 file, 161 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 analyzes Clojure code to ensure adherence to Metabase's internal style guide and, optionally, a community-provided style guide (if CLOJURE_STYLE_GUIDE.adoc exists in the working directory). It flags violations of these guidelines and suggests improvements. The tool focuses on identifying issues; it avoids providing positive feedback or confirming correctness.

When to use it

  • Reviewing pull requests containing Clojure code changes.
  • Ensuring new Clojure code aligns with Metabase's coding standards.
  • Identifying potential style and organizational issues in existing Clojure codebases.
  • Automating parts of the code review process.

Key capabilities

  • Checks compliance with the Metabase Clojure style guide.
  • Optionally checks against a community Clojure style guide (CLOJURE_STYLE_GUIDE.adoc).
  • Validates naming conventions (kebab-case, function endings).
  • Verifies documentation standards (Markdown formatting, TODO comments with author and date).
  • Enforces code organization rules (private variables, line length limits).
  • Checks test structure and naming.
  • Ensures correct module patterns are used.
  • Validates REST API conventions (response schemas, route names).
  • Verifies MBQL usage guidelines.
  • Confirms database model and table naming conventions.

Example prompts

  • "Review this Clojure code for style violations."
  • "Check this pull request against the Metabase Clojure style guide."
  • "Analyze this file for adherence to coding best practices."

Tips & gotchas

  • The skill will not flag missing parentheses, as these are handled by a separate linter.
  • Ensure CLOJURE_STYLE_GUIDE.adoc is present in the working directory if you want it to check against the community style guide.
  • Focus on addressing the flagged issues; avoid trivial comments or confirmations of correctness.