Skip to content
TrustedSkillsbeta
Back to all skills

Openharmony Error Detection

Checked
mengfei0053·vlatest·testing

Detects and reports errors within OpenHarmony systems, proactively identifying issues for faster troubleshooting and improved stability.

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 mengfei0053/skills --skill openharmony-error-detection -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

mengfei0053

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 mengfei0053/skills at ce8613de19.

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

Commit
ce8613de19
Manifest
skills/openharmony-error-detection/SKILL.md
Scanned
1 file, 365 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 helps identify and analyze errors within OpenHarmony projects. It can pinpoint error locations, suggest potential causes based on common patterns, and provide basic debugging steps. The tool aims to accelerate the troubleshooting process for developers working with OpenHarmony's codebase.

When to use it

  • When encountering unexpected behavior or crashes in an OpenHarmony application.
  • During code reviews to proactively identify potential error sources.
  • For new developers onboarding to an OpenHarmony project who need assistance understanding error messages.
  • To automate initial triage of reported bugs and errors.

Key capabilities

  • Error identification within OpenHarmony projects
  • Analysis of error locations
  • Suggestion of potential causes based on common patterns
  • Provision of basic debugging steps

Example prompts

  • "Analyze this error log from my OpenHarmony application: [paste error log]"
  • "I'm seeing a crash in module X. Can you suggest possible causes?"
  • "What are the most common errors encountered when developing for OpenHarmony?"

Tips & gotchas

The skill’s effectiveness is dependent on providing clear and complete error logs or descriptions of the issue. It offers basic debugging steps; more complex issues may require deeper investigation using standard development tools.