Skip to content
TrustedSkillsbeta
Back to all skills

Code Checker

Checked
openharmonyinsight·vlatest·backend

This Code Checker analyzes your code for potential issues, improving quality and reducing bugs – a valuable tool for developers.

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 openharmonyinsight/openharmony-skills --skill code-checker -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

openharmonyinsight

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 openharmonyinsight/openharmony-skills at 5ae988cab6.

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

Commit
5ae988cab6
Manifest
skills/code-checker/SKILL.md
Scanned
5 files, 1,335 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 code-checker skill analyzes code snippets for potential errors, stylistic issues, and adherence to coding standards. It can identify common programming mistakes like syntax errors, logic flaws, and inefficient code patterns. This helps improve the quality and maintainability of software projects by proactively catching problems early in the development process.

When to use it

  • Debugging assistance: When you're stuck on a bug and need a fresh perspective on your code.
  • Code review automation: To automatically flag potential issues during code reviews, reducing manual effort.
  • Learning best practices: To understand how to write cleaner, more efficient code by identifying areas for improvement.
  • Ensuring coding standards compliance: To verify that a codebase adheres to established style guides and conventions.

Key capabilities

  • Error detection
  • Style analysis
  • Coding standard checks
  • Code pattern identification

Example prompts

  • "Check this Python code for errors: [paste code snippet]"
  • "Analyze this JavaScript function for potential performance issues: [paste code snippet]"
  • "Does this C++ code follow best practices?"

Tips & gotchas

The effectiveness of the code-checker skill depends on providing clear and complete code snippets. It may not be able to identify all possible errors without context from a larger project.