Reconstruct interfaces, SWI tables, and state machines from RISC OS module binaries.
npx skills add https://github.com/gerph/riscos-agent-skills --skill riscos-re
Please help me install this Agent Skill. Skill: riscos-re Source: https://github.com/gerph/riscos-agent-skills/tree/main/skills/riscos-re Command: npx skills add https://github.com/gerph/riscos-agent-skills --skill riscos-re
Reconstruct functionality, interfaces, and state machines from RISC OS module binaries, to understand legacy behavior or reimplement in C.
Supply a RISC OS module binary and I will guide you through reconstructing its functionality.
High-intent search queries and answers about installing and using this skill.
To reverse-engineer a RISC OS module binary, you analyze its module header, extract interface definitions, and map dispatch tables and SWIs to reconstruct functionality and state machines for reimplementation.
Extracting SWI tables and state machines involves analyzing module binaries to identify external entry points, map software interrupts, and document state handling to enable a faithful C reimplementation.
You can reimplement legacy RISC OS modules in C by first reverse-engineering the binary to document interfaces, SWI dispatch tables, and state machines into a repeatable reimplementation plan.
Yes, identifying the module header is the first step to extracting interface definitions, as it allows you to map external entry points and analyze dispatch tables for reverse-engineering.
gerphBuild, test, and debug PyModules for RISC OS Pyromaniac.
saajunaidMap legacy database tables and columns to a new schema.
nolanvenholaAudit cross-file symbolic references and replace hardcoded operands in Zeliard TASM assembly source.
gmcabritaAutomate binary reverse engineering with Ghidra's headless analyzer.
