Skip to content
TrustedSkillsbeta
Back to all skills

Perl Lint

Checked
jamie-bitflight·vlatest·backend·MIT

Perl Lint analyzes your Perl code for potential errors and style issues, boosting code quality and maintainability.

Install on your platform

This skill no longer installs under the name perl-lint. jamie-bitflight/claude_skills is deleted or private, so it cannot be installed from.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

jamie-bitflight

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 jamie-bitflight/claude_skills at 02ac82cd70.

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

Scanned
2 files, 267 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 perl-lint skill provides static analysis and code style checking for Perl scripts. It identifies potential errors, stylistic inconsistencies, and adherence to best practices within Perl codebases. This helps improve code quality, maintainability, and reduces the likelihood of runtime issues.

When to use it

  • Code Review: Use it to automatically check Perl code submitted as part of a pull request or during development.
  • Automated Builds: Integrate perl-lint into your CI/CD pipeline to enforce coding standards before deployment.
  • Learning Perl: Newcomers can use this skill to understand and adhere to common Perl coding conventions.
  • Legacy Code Cleanup: Apply it to older Perl codebases to identify areas for improvement and modernization.

Key capabilities

  • Static analysis of Perl scripts
  • Code style checking
  • Identification of potential errors
  • Adherence to best practices

Example prompts

  • "Lint this Perl script: [script content]"
  • "Check the code style of this Perl program: [program content]"
  • "Analyze this Perl file for errors and suggest improvements: [file content]"

Tips & gotchas

This skill requires a working Perl environment to be available. The specific linting rules applied may depend on the configuration used, so familiarize yourself with common Perl style guides.