Skip to content
TrustedSkillsbeta
Back to all skills

Lint

Checked
aaddrick·vlatest·backend·Apache-2.0

Lint analyzes code for potential errors, stylistic issues, and best practices, improving code quality and maintainability.

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 aaddrick/claude-desktop-debian --skill lint -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

aaddrick

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 aaddrick/claude-desktop-debian at 0c02014612.

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

Commit
0c02014612
Manifest
.claude/skills/lint/SKILL.md
Scanned
1 file, 48 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

The lint skill enables AI agents to perform static analysis and code quality checks on source files. It identifies syntax errors, style violations, and potential bugs to ensure code meets specific standards before execution or review.

When to use it

  • Before committing changes to a version control repository to prevent introducing regressions.
  • During the development workflow to provide immediate feedback on coding style inconsistencies.
  • When integrating new libraries or frameworks to verify compatibility with existing project rules.
  • As part of a continuous integration pipeline to automate quality assurance checks.

Key capabilities

  • Executes linting tools against provided codebases or files.
  • Reports specific issues categorized by severity (e.g., errors, warnings).
  • Validates adherence to language-specific style guides and best practices.
  • Supports multiple programming languages depending on the underlying toolchain.

Example prompts

  • "Run a full lint check on my current Python project directory."
  • "Identify any ESLint violations in this JavaScript file before I commit it."
  • "Check this Rust code snippet for clippy warnings and formatting issues."

Tips & gotchas

Ensure the AI agent has access to the necessary linter binaries or can invoke them via shell commands within its environment. Some complex projects may require specific configuration files (like .eslintrc or .clippy.toml) to be present for accurate analysis.