Use when working with MapleStory assets — how to look up, compose, and render characters, mobs, maps, skills, items, or sprites via maple-lookup MCP.
Teach your agent MapleStory.
Skills NEXPACE publishes for MapleStory Universe builder work — and the game-production tooling that goes with them. One command, on Claude Code, Codex, Gemini, and Kimi.
Claude Code
/plugin marketplace add NEXPACE-Limited/msu-skillsskills CLI
npx skills add NEXPACE-Limited/msu-skillsCodex · Gemini · Kimi
curl -fsSL https://raw.githubusercontent.com/NEXPACE-Limited/msu-skills/main/install.sh | bashSame skills, same files, whichever you run. The channels differ only in what happens to the MCP server — see Install below.
What’s inside
Three plugins, one per coupling boundary
A plugin that needs no credential never acquires one. That is why each gets its own root, its own version, and its own colour here.
msu
Skills and an MCP server for building on MapleStory Universe game data. The bundled maple-lookup MCP server searches the MSU Open API for characters, mobs, maps, skills, items, and sprites; the skills cover how that data is structured, how to choose between candidates, and how to turn it into something that renders. This plugin owns the MSU Builder OpenAPI key, and other NEXPACE plugins build on it instead of copying its skills.
game-tools
Quality checks and fixes for a game that already runs, on any engine or platform. It covers the parts of a game that are not features: how the controls feel, whether the numbers are balanced, whether the same input always gives the same result, whether the UI fits every screen and input device, whether the sound plays on every browser and phone, whether a new player understands what to do, and whether the text works in other languages. It also ships an in-game panel for changing values while playing, instead of another edit-and-rebuild round. Published by NEXPACE alongside the MSU builder skills.
msu-statusline
A Claude Code status line for MapleStory Universe builders. It reads the MSU Builder notice board and keeps the newest notice under the prompt as a clickable link, so an announcement about maintenance, an API change, or a deadline arrives without leaving the terminal. Segments are toggled individually and it wraps an existing status line rather than replacing it. No credential required.
All skills · 13
What each one does
These sentences are the product. Your agent reads them to decide whether to load the skill — so they are written to be matched, and shown here exactly as written.
Use when a MapleStory asset request resolves to more than one plausible candidate: a look described by colour, style, or mood instead of an exact name or ID (a black cap, a white tee, a monster that suits this map), a maple-lookup search returning several close matches, or the user asking to preview, compare, or choose between assets before they are used.
Read the rest
Builds a local page the user picks from; when it was not invoked by name, it asks first.
Checks, repairs, or sets up a browser game's audio: its sound settings and whether sound actually plays under each browser's conditions.
Read the rest
Use when a game is silent, or goes silent, on a phone, in Safari, inside an iframe or an in-app browser while it plays elsewhere; when sound works for the builder but not for players; when music does not start, loops with a gap, or keeps playing in a hidden tab; when volume, mute, or sound settings are missing, ignored on some device, or forgotten between sessions; when the user asks to add sound or music to a game; or when a pre-release audio pass is requested. Reports observed versus inferred findings and applies fixes only on confirmation.
Reviews and tunes game balance across difficulty and progression curves, session pacing, option or strategy trade-offs, and reward economies.
Read the rest
Use when players report that a game is too hard, easy, short, long, or grindy; a weapon, upgrade, or strategy dominates; damage, health, spawn, drop, price, or progression values need tuning; or a requested pre-release balance pass has not been validated. Establishes the target experience, measures the relevant model, and reports or applies specific number changes with before-and-after evidence.
Audits a game's UI and interaction across supported viewports, aspect ratios, pixel densities, orientations, and input capabilities.
Read the rest
Use when mobile, tablet, desktop, controller, keyboard, pointer, or touch support is being checked; UI clips, overlaps, blurs, or overflows; controls are unreachable or hard to use; resizing or orientation changes break layout; or an explicit pre-release device-coverage pass is requested. Reproduces each issue on the relevant target and reports severity, evidence, exact trigger conditions, and fixes while distinguishing observed from source-inferred findings.
Use when creating any game or interactive toy, when adding gameplay/UI features to one, when the builder asks for value tweaks in any language (too fast/slow, too big/small, a bit more/less, move it left/right/up/down, can't hit it, my tap doesn't register, hitbox, feels floaty/heavy/off, easier/harder, change X from N to M, 'don't rebuild — just fix this'; 너무 빨라요/느려요, 버튼이 안 눌려요, 판정이 이상해요, 히트박스, 이것만 고쳐줘), or when a message contains a [TUNING] or [ERRORS] block.
Read the rest
Once loaded, stays in force for every subsequent message in the session without being re-mentioned. Ships a live in-game tuning panel with every game so builders adjust values themselves instead of burning chat round-trips.
Audits nondeterministic game behavior and flaky execution.
Read the rest
Use when the same initial state and inputs produce different outcomes, a test fails intermittently or only under load, behavior differs by frame rate or machine, a replay diverges, or lockstep peers desynchronize. Establishes the required determinism boundary, reproduces and measures variance, isolates randomness, timing, async or thread ordering, state leakage, unordered iteration, and numeric drift, then reports verified causes and implements and stress-tests fixes only when requested.
Use when a game's controls feel stiff, floaty, heavy, slippery, unresponsive, or unfair; when players miss jumps they thought they made, snag on platform corners, lose inputs pressed during another action, or get hit by grazes; when a platformer, runner, or action game is being built or polished and its input and movement handling was never reviewed; or when the user asks for a game-feel pass or names coyote time, jump buffering, variable jump height, gravity tuning, corner correction, acceleration, or input buffering.
Read the rest
Audits, proposes, and applies only what the user confirms.
Audits, adds, or reworks a game's first-time-player tutorial.
Read the rest
Use when players cannot identify the controls, goal, failure conditions, or a non-obvious rule; new players quit before completing the core loop; onboarding presents too much at once; or an explicit tutorial or first-run improvement is requested. Separates first-action essentials from later guidance, prefers in-flow or staged first-run teaching, provides a skippable fallback and reusable help, and verifies behavior from clean, completed, and skipped states.
Sets up or repairs localization for a game: player-facing string extraction, locale catalogs, draft target-locale translations, fallback and locale selection, runtime switching, plural and parameter formatting, glyph coverage, and translation-safe layouts.
Read the rest
Use when the user requests another locale or localization-ready architecture; existing translations, fallback, pluralization, locale detection, or switching are broken; or translated text overflows or renders missing glyphs. Follows the project's engine and existing localization system and marks generated translations for human review.
Claude Code only — a status line is a Claude Code concept and this skill does nothing on another CLI.
Read the rest
Reads and changes what the MSU status line shows. Use when the user wants to turn a status-line segment on or off, change polling, title width, label, colours, icon, colour cycling or timestamp, or asks what their MSU status line is currently set to. Editing the settings file by hand is the same operation and belongs here too.
Claude Code only — a status line is a Claude Code concept and this skill does nothing on another CLI.
Read the rest
Puts the newest MSU Builder notice in the Claude Code status line, and repairs it. Use when the user asks to install, enable, set up, re-install or repair the MSU status line, wants MSU notices or announcements shown under the prompt or in the terminal, or reports that the MSU status line is blank, stale, or gone after an update. Wraps a status line that is already configured rather than replacing it. Taking it back out is `msu-statusline-uninstall`.
Claude Code only — a status line is a Claude Code concept and this skill does nothing on another CLI.
Read the rest
Takes the MSU status line back out, restores whatever status line was there before it, and uninstalls the plugin when that is what was asked for. Use when the user wants to remove, uninstall, delete, disable or get rid of the MSU status line or the msu-statusline plugin, wants their old status line back, or asks what the install left on their machine.
Install
Three channels, one source
The SKILL.md files are the only source and ship verbatim everywhere. Channels differ only in what happens to the MCP server.
Claude Code
Add this repository as a marketplace, then install a plugin from it.
MCP automatic — bundled, key via prompt
/plugin marketplace add NEXPACE-Limited/msu-skills/plugin install msu@msu-skillsskills CLI
Offers every catalogued plugin’s skills at once. --skill narrows it to one.
MCP manual — set it up from the values on the MCP page
npx skills add NEXPACE-Limited/msu-skillsCodex · Gemini · Kimi
No Node.js or checkout needed — the installer pulls a temporary source snapshot and removes it.
MCP best effort — prints the Codex snippet, runs mcp add for the rest
curl -fsSL https://raw.githubusercontent.com/NEXPACE-Limited/msu-skills/main/install.sh | bashcurl -fsSL https://raw.githubusercontent.com/NEXPACE-Limited/msu-skills/main/install.sh | bash -s -- --plugin msuImportant notes
Terms that travel with the skills
- MSU Resource Skills are reference instructions for using MSU game resources supplied through the MSU Open API. They do not provide the resources, operate your AI agent, or generate outputs themselves.
- Use of MSU Resource Skills, Resource MCP, and the MSU Open API is subject to the MSU API Terms, Builder Terms, EULA, applicable policies, and applicable laws.
- AI-generated outputs may be inaccurate, incomplete, non-compliant, or infringing. Review, test, and validate generated code, resource selections, API calls, and final app behavior before use.
- Keep MSU Builder OpenAPI keys, MCP connections, wallet or account access, and user data secure. Do not expose credentials in prompts, logs, repositories, or untrusted tools.
- Do not redistribute, resell, sublicense, reverse engineer, extract, scrape, or use Resource Skills or accessed MSU resources to train, fine-tune, develop, improve, or benchmark AI or machine-learning models or competing services, except as expressly permitted.