Skip to content
TrustedSkillsbeta
Back to all skills

Openharmony Security Review

Checked
openharmonyinsight·vlatest·security

Helps with security, code review as part of implementing security and authentication workflows.

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 openharmony-security-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

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/openharmony-security-review/SKILL.md
Scanned
1 file, 401 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 performs automated security reviews specifically tailored for OpenHarmony-based systems. It analyzes codebases and configurations to identify vulnerabilities, ensuring compliance with the OpenHarmony security standards before deployment.

When to use it

  • Before integrating third-party modules into an OpenHarmony application to prevent supply chain attacks.
  • During the CI/CD pipeline to automatically flag insecure coding patterns in HarmonyOS projects.
  • When preparing a device image for public release to verify adherence to platform security guidelines.
  • To audit permission declarations and ensure minimal privilege escalation risks in system services.

Key capabilities

  • Automated vulnerability detection within OpenHarmony codebases.
  • Validation against specific OpenHarmony security compliance rules.
  • Identification of insecure configuration settings in HarmonyOS environments.
  • Reporting on potential privilege escalation vectors.

Example prompts

  • "Run a full security review on my new OpenHarmony smart home application module."
  • "Check this HarmonyOS project for common vulnerabilities and misconfigurations before I merge it."
  • "Analyze the permission model in this system service to ensure it follows OpenHarmony best practices."

Tips & gotchas

Ensure your codebase is fully compatible with the current OpenHarmony version, as the review logic targets specific framework behaviors. This tool focuses on static analysis; it cannot detect runtime exploits or network-based attacks that require live testing environments.