Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for security researchers, CTF players, reverse engineers, malware analysts, and incident-response teams who need a Claude Code / Codex / Hermes Agent skill bundle that auto-detects the host platform and routes reverse-engineering tasks to the right toolchain (Ghidra, IDA Pro, radare2, GDB, objdump, strings, binwalk, etc.); for AI-agent developers building security-research workflows who nee
Who should use it
Who should skip it
Pass on zhaoxuya520/reverse-skill if your environment cannot support the access controls and sandboxing this risk profile requires.
About this signal
zhaoxuya520/reverse-skill is tracked by RepoRadar as a reverse-engineering skill router in the MIT AI Agent workflow router and tool-orchestrat section. It was first seen on 2026-06-25 and last updated on 2026-06-25. The current verdict is 'try now' with a Silver tier and review needed setup difficulty. zhaoxuya520/reverse-skill leads on novelty (10.0) and momentum (10.0); its lowest signal is setup ease (6.5), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned zhaoxuya520/reverse-skill a composite score of 7.8 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 5289.0 and never affects the composite score or tier. The risk label of 'medium' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Risk explanation
Medium risk: use sandboxing, least privilege, and explicit review before connecting sensitive data or accounts.