Auditing Pre Release Security
ListedAutomates pre-release security audits, identifying vulnerabilities and compliance gaps before deployment with onekeyhq's AI agent.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
1k-auditing-pre-release-security, not the name it is listed under, so the command below uses that name.- 1
Run this in your project
terminal$ npx skills add onekeyhq/app-monorepo --skill 1k-auditing-pre-release-security -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
onekeyhq
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.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No pipe-to-shell installers: failed
Runs code fetched at install time in 1 place.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
What it found
- .skillshare/skills/1k-auditing-pre-release-security/SKILL.md:143tells the user to run: remote script piped into a shell(in the instructions, not code)
- [ ] Flag remote script execution patterns (curl|bash, remote downloads)
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.
Pinned to a commit: passed
Scanned onekeyhq/app-monorepo at eba5185761.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- eba5185761
- Scanned
- 2 files, 323 lines
About this skill
What it does
This skill automates pre-release security audits by comparing two Git references (e.g., tags, branches, or commit SHAs). It identifies potential vulnerabilities and compliance gaps introduced between these points in time. The audit focuses on source code changes, dependency updates, newly added packages, and risks within CI/CD workflows. The output is a detailed security report written in Chinese Markdown.
When to use it
- Before releasing a new version of your software (e.g., comparing
v1.0.0torelease/v1.1.0). - When merging a feature branch into the main development line to assess potential security regressions.
- After significant dependency updates to ensure stability and identify any unexpected behavior changes.
- To proactively check for misconfigurations in CI/CD pipelines (e.g.,
.github/workflowsfiles).
Key capabilities
- Compares two Git references to detect changes between them.
- Analyzes source code diffs for security regressions.
- Identifies dependency updates and checks lockfile determinism.
- Examines newly introduced packages within
node_modules. - Scans CI/CD workflows (including Expo/EAS configurations) for potential risks.
- Generates a Chinese Markdown report with a unique filename including the compared references.
Example prompts
- "Audit security changes between tag v1.2.3 and branch main."
- "Compare commit SHA abcdef0 to commit SHA 1234567 for pre-release security issues."
- “What are the security differences between release/candidate-1 and release/candidate-2?”
Tips & gotchas
- The skill requires you to explicitly provide both Git references (BASE_REF and TARGET_REF). If only one is provided, it will prompt for the missing reference.
- Reports are generated in Chinese Markdown and include the referenced commit SHAs in the filename to prevent overwrites.
- The skill prioritizes security by redacting any potentially sensitive information (e.g., API keys) from its output.