Skip to content
TrustedSkillsbeta
Back to all skills

Ktlint

Checked
cyanxiao·vlatest·backend

Ktlint analyzes code for style issues and potential bugs, helping developers maintain consistent quality and catch errors early.

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 cyanxiao/skills --skill ktlint -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

cyanxiao

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 cyanxiao/skills at 3bffda8b0b.

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

Scanned
1 file, 69 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

ktlint is a tool that automatically checks Kotlin code style and formatting. It enforces consistent coding standards, identifies potential issues, and helps maintain clean and readable codebases. This skill can be used to lint existing Kotlin projects or integrated into development workflows for continuous style checking.

When to use it

  • Enforcing Code Style: Ensure all developers on a team adhere to the same Kotlin formatting rules.
  • Automated Formatting: Automatically format Kotlin code to match predefined style guidelines, reducing manual effort.
  • Code Review Assistance: Quickly identify and address style violations during code reviews.
  • Project Setup: Configure new Kotlin projects with consistent coding standards from the start.

Key capabilities

  • Kotlin code style checking
  • Automatic formatting of Kotlin code
  • Enforcement of predefined style guidelines

Example prompts

  • "Lint this Kotlin file: [file path]"
  • "Format this Kotlin code according to standard conventions."
  • "Check the style of my project and report any violations."

Tips & gotchas

  • ktlint requires a basic understanding of Kotlin programming.
  • The skill's effectiveness depends on having clearly defined coding style guidelines.