Miyoo Game Port

    1

    Assess and develop game ports for Miyoo Mini and Mini Plus on OnionOS, from engine and runtime triage through asset preparation, packaging and device testing.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Miyoo Game Port

    Example session with this skill installed

    Triage the sample-game directory for an OnionOS port. Report the engine indicators, what the scan can establish, and what you would verify on a real game build before choosing a runtime.

    • Read your context and instructions
    • Compiled the miyoo game port

    Result

    I ran scripts/triage_game.py sample-game on a synthetic fixture containing an empty data.win. The script detected a GameMaker-style package name and reported port feasibility as

    UNKNOWN.

    CheckObserved
    Engine indicatordata.win matched the GameMaker Studio filename heuristic
    Loose image and audio sizes0.0 MB on disk in this fixture
    Packed or decoded footprintUnknown
    Port feasibilityRuntime, decoded assets and device measurements required

    Next steps

    With an actual game build, verify the package format and whether it uses VM bytecode or YYC. For a VM build, check compatible runner support for the exact bytecode version. Then exercise a small playable slice on the target OnionOS device and record RSS, native allocations and swap before estimating headroom.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    An agent workflow and development scaffold for assessing, building and testing game ports for the Miyoo Mini and Mini Plus on OnionOS.

    What’s included

    • Engine and runtime triage, with guidance for choosing between an existing port, a compatible runner and a native build.

    • Helpers for inventorying game files, packing extracted assets, inspecting Unity Mono metadata and converting framebuffer captures.

    • Starter native rendering and input code, cross-build and OnionOS packaging templates, and a device QA workflow for saves, audio and performance.

    • Version 1.5.0 adds guidance for text-heavy 640×480 layouts, controller navigation and device memory, with lessons from the Slay the Spire bring-up.

    The workflow starts with feasibility and requires game-specific runtime work and hardware validation. Use game files you own or have permission to use.

    Open source under MIT. Source on GitHub.

    Feasibility depends on the exact game build, available source or compatible runtime, and measurements on the target device. The native template is a basic framebuffer and input backend. The packer takes extracted files and requires an MPAK reader in the game runtime.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 2 days ago

    • Free with an Agensi account

    Requires

    Python 3 for the helper scripts

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Reads locally supplied project files and writes generated packs, build artifacts and captures to paths you specify. Device profiling may use an existing connection to your own handheld.

    Listed2 days ago

    What's inside

    Frequently Asked Questions

    It guides feasibility audits and port development. It includes helper scripts, reference notes and starter code. Each game still needs its own runtime and integration work.

    Use a SKILL.md-compatible coding agent that can read and write project files and run terminal commands.

    The references discuss porting strategies for native games, Unity Mono and IL2CPP, GameMaker, LÖVE and other engines. Verify the exact game build and runner before assuming compatibility.

    The ZIP contains the skill, reference notes, Python and C# helpers, an OnionOS build and launcher template, a starter framebuffer and input backend, and tool tests.

    The inventory helper reports filename-based engine indicators and loose asset sizes. Use the exact build and its dependencies to check for a compatible runtime and measure decoded memory.

    The starter backend expects a 320×240 render surface and a 640×480 32-bit framebuffer. Check the actual mode, stride and orientation on your device before using it.

    New in Game Development