Pre-install eval
analyzing-android-malware-with-apktool Eval report.
A machine-readable install decision for agents: task fit, Trust Score, Audit Score, install safety, permission surface, and a concrete validation plan before this skill touches a workspace.
manual review
Test manually in an isolated workspace and compare against safer alternatives.
Required gates
Checks an agent must pass before install
Task fit
70
Task fit is weak; compare alternatives before selecting.
- Evaluate analyzing-android-malware-with-apktool before installing it in an agent workflow
- security
- Coding agents workflows; Claude Code teams; teams that value GitHub adoption signals
Install path
92
Install handoff is available.
- npx skills add tradecatlabs/vibe-coding-cn --skill analyzing-android-malware-with-apktool
Install command safety
92
standard package or runtime install path
- npx skills add tradecatlabs/vibe-coding-cn --skill analyzing-android-malware-with-apktool
Trust score
72
Good trust signals with a few areas worth checking before rollout.
- Strong shortlist
- 16K GitHub stars
- Apache-2.0
Audit score
81
Needs review
- Financial research output is not financial advice; require human review before any live investment decision
Agent safety gate
53
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- Test manually in an isolated workspace and compare against safer alternatives.
- High-risk permission hints: Shell or command execution
License clarity
86
Apache-2.0
- Apache-2.0
Permission surface
62
shell or command execution, network or browser access
- Shell or command execution: high
- Network access: medium
- Filesystem access: medium
Validation plan
What the agent should do next
- 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
- 2Install in an isolated workspace or sandbox with no production secrets available.
- 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
- 4Compare the selected skill against at least one alternative when the eval status is review or failed.
- 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.
Do not use when
Conditions that require another skill
- teams that need a vendor-supported SLA
- production agents without a repository review
- SKILL.md lacks explicit usage examples for the provided agent.py CLI and does not document how to install dependencies beyond listing them.
- High-risk permission hints: Shell or command execution
- Financial research output is not financial advice; require human review before any live investment decision
- The skill does not clearly define limitations, edge cases, or failure modes, such as behavior with malformed APKs, obfuscated DEX files, or very large samples.
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
warn76
Public metadata needs stronger README/SKILL.md context
Recent maintenance
pass88
2mo since push
Alternatives available
pass82
Alternative skills are available for comparison.