MSW AI Coding Plugins - Setup Guide¶

Source: msw-git/msw-ai-coding-plugins-official via skills.sh - 119.4K combined installs across 18 indexed listings; snapshot 2026-10-28 (Oct 28 morning sweep)

GitHub: MSW-Git/msw-ai-coding-plugins-official - 38 stars, no license file (GitHub reports no license and the license endpoint returns 404), branch main, last pushed 2026-10-06, 14 SKILL.md directories at plugins/<plugin>/skills/<name>/SKILL.md across two Claude Code plugins

Category: Game development for the MapleStory Worlds platform, driven from an AI coding tool

Quality Tier: 🟡 Beta - small official set from a single publisher, 38 GitHub stars, no license file, 14 of the 18 indexed listings present in the tree, six skills sampled by the three auditors and all clean

MapleStory Worlds (MSW) is Nexon's 2D game creation platform, where worlds are built from .map, .model, .ui and .mlua files inside a Maker workspace. This repository is the publisher's public release source for AI-assisted MSW creation, split into two Claude Code plugins: msw-maker-base-skill, which carries thirteen skills covering platform rules, scripting, entities, UI, combat and resource search, and msw-maker-content-skill, which currently carries one skill for reusable player attack systems. The marketplace and base plugin descriptions are Korean with an English README, and every skill is written to be read by an agent before it touches a file.

The coverage is unusually concrete for a 38-star repository. msw-general is a routing and rulebook skill that every other skill depends on, and it states the platform invariants that an agent would otherwise learn by breaking them: user scripts exist as a .mlua plus .codeblock pair, .codeblock is generated by Maker refresh and never by hand, .d.mlua API definitions are read only, and the default sprite left on a new entity counts as unfinished work. The rest of the set fans out from there, and the skills cross-reference each other by name rather than repeating content.

One drift fact belongs up front. The install index records 18 listings, while the current tree holds 14 SKILL.md directories: 14 of the 18 listings have a matching directory and 4 do not (msw-costume 23 installs, msw-ui-template 7, msw-behaviourtree-creator 1, msw-behaviourtree-spec-builder 1). What those four contain cannot be confirmed from the current tree, so this guide does not describe them.

Installation¶

The README documents the plugin route only: install or load the repository as a plugin source in an AI coding tool, then enable msw-maker-base-skill for MSW projects and add content skills separately when a project needs them. The marketplace manifest at .claude-plugin/marketplace.json names itself msw-ai-coding-plugins-official and declares both plugins, which is what the Claude Code commands below are built from:

claude plugin marketplace add msw-git/msw-ai-coding-plugins-official
claude plugin install msw-maker-base-skill@msw-ai-coding-plugins-official
claude plugin install msw-maker-content-skill@msw-ai-coding-plugins-official

Because the repository is served through skills.sh, the CLI is the shorter path for agents that read a skill directory directly:

npx skills add msw-git/msw-ai-coding-plugins-official

For Hermes there is no plugin loader, so the tree is the install source. Each directory under plugins/<plugin>/skills/ holds one SKILL.md with its own references/ folder, and copying the ones you want is equivalent to a per-skill install:

git clone --depth 1 https://github.com/msw-git/msw-ai-coding-plugins-official.git
cp -R msw-ai-coding-plugins-official/plugins/msw-maker-base-skill/skills/msw-general ~/.hermes/profiles/corpusiq/skills/

Two runtime dependencies decide whether the set is useful. The skills expect a valid MapleStory Worlds local workspace, and several of them call the msw-maker-mcp MCP server: msw-search uses its mlua_api_retriever and mlua_document_retriever tools, msw-general drives the ModelBuilder for .model files, msw-ui-system ships the UI builder and lint scripts, and the base plugin's hooks call maker_refresh_workspace after every edit. Register that server before expecting the retrieval and builder skills to work. MCP setup is not documented in the README; the skills point to the official creator docs at https://maplestoryworlds-creators.nexon.com/ko/docs?postId=1368 when a call fails.

What It Provides¶

Skill	Installs	Use For
msw-general	9,989	Foundation for any MSW task: platform and workspace rules, folder metadata, the `.mlua` plus `.codeblock` pair, the `.model` template catalog for monsters, NPCs, terrain and map objects, SortingLayer and coordinate rules, and the ECS and ID conventions the other skills assume.
msw-scripting	9,977	Authoring `.mlua` scripts and debugging them: annotations such as `@Component`, `@Logic` and `@ExecSpace`, lifecycle and exec spaces, property sync, the event system, build-log inspection and an error-classification loop before edits.
msw-defaultplayer	9,977	Tuning the default player through the ModelBuilder: movement speed, jump force, HP, camera and gravity, plus the per-map-mode movement components and revive behaviour.
msw-search	9,967	Finding what the workspace does not contain: API detail and guide lookups through the msw-mcp retrievers, and REST search for sprites, animations, sounds, resource packs and avatar items to obtain a RUID.
msw-combat-system	9,948	Wiring the attack to hit pipeline: the damage model, i-frames, knockback, hit stop, camera shake, sprite flash, hit and death effects, damage skins and a monster AI finite state machine.
msw-avatar	9,947	Costume slots and the three-layer avatar animation chain, including the four-level distinction between state key, action state name, body action enum and sprite action ID, and the legacy and action-sheet mapping systems.
msw-painter	9,871	Drawing a sprite when search finds nothing suitable: SVG, Canvas or HTML pixel art rendered to PNG and uploaded for a sprite RUID, in a chunky pixel or maple cartoon style.
msw-packages	9,843	Checking the official MSWPackages catalog before writing a standard system by hand: toast, leaderboard, inventory, shop, mail, quest, save data, key binding, drop table and shared UI pieces.
msw-ui-system	9,838	Building `.ui` screens: anchor, pivot and RectTransform rules, group hierarchy, layout recipes for HUD, popup, toast, inventory, scroll list and ranking, component API tables and the bundled builder and lint scripts.
msw-sprite-ruid	9,825	Assigning `SpriteRUID` and `ImageRUID` values, playing an animation clip directly in a renderer, and using the `thumbnail://` prefix so avatar items and clips render as static icons.
msw-behaviourtree	9,810	Authoring `.behaviourtree` files: scanning custom action, decorator and composite nodes into a catalog of UUIDs and property keys, then generating the node graph, blackboard and node properties.
msw-planning	7,404	Deciding what to build: guided scoping questions, the MSW genre catalog with map types and mechanic tags, and an implementation-ready GDD or roadmap, including resuming a phased build.

The remaining 6 indexed listings range from 1 to 1,566 installs. maplestory-skill-maker (1,566) is the whole of the content plugin, covering player attack and movement skills with targeting, judgment timing, damage presentation, knockback and projectile behaviour, and msw-ui-kit (1,432) supplies themed UI part palettes and screen digests. The other four have no directory in the current tree: msw-costume (23), msw-ui-template (7), msw-behaviourtree-creator (1) and msw-behaviourtree-spec-builder (1).

Why This Matters for Hermes Agents¶

Game creation on a proprietary engine is the case where a general coding agent fails most quietly. MSW is not Unity or Godot: the file formats are Maker-specific, the script language is .mlua with its own annotation set, and a script only runs once a generated .codeblock exists beside it. An agent working from general knowledge will produce plausible Lua that the engine never loads, and the run will look like a permissions problem.

This suite closes that gap with rules rather than samples. msw-general opens with a read-order rule, then states the invariants in the imperative: read the builder protocol before mutating a .map, .model or .ui, never hand-write a .codeblock, never edit .d.mlua, and gather every mutated file type before starting. Those are exactly the constraints a model would otherwise skip in the interest of finishing.

The retrieval dependency is the second gain. msw-search routes API questions to the MCP retrievers instead of trusting memory, and msw-packages sends the agent to the official package catalog before it writes a leaderboard or an inventory from scratch. On a platform that ships prebuilt systems, checking the catalog first is the difference between a working shop and a hand-rolled one that fights the engine.

There is also a habit worth copying. msw-painter treats an empty or default sprite as a defect and gives the agent a fallback path to produce one, and msw-scripting asks for the build log to be read and classified before edits. Both push the agent toward verifying the artifact rather than the diff.

Usage¶

You say	What happens
"Start a MapleStory Worlds project for a tower defence map"	msw-general loads the platform rules and the model template catalog, msw-planning narrows the scope into a GDD, and the agent reads the builder protocol before it writes any `.map` or `.model` file.
"Add a chase monster that damages the player on contact"	msw-general picks a monster pattern, msw-combat-system wires the attack to hit pipeline with i-frames and knockback, and msw-search finds a sprite and sound to attach instead of leaving the default.
"The script compiles but nothing happens at runtime"	msw-scripting reads the build log, classifies the error, checks that the `.codeblock` pair was regenerated by refresh, and only then edits the `.mlua`.
"Build an inventory screen with a grid and a tooltip"	msw-ui-system picks a layout recipe, msw-ui-kit supplies themed frames and slots by RUID, and msw-sprite-ruid renders each item icon through the thumbnail prefix.
"I need a projectile skill with a cooldown and a cast lock"	maplestory-skill-maker builds the skill entry, targeting and judgment timing, the cooldown and hotkey wiring, and the monster presentation that goes with it.
"Give this NPC a behaviour tree that patrols and then chases"	msw-behaviourtree scans the project's custom nodes, assembles the tree with blackboard variables and node properties, and self-validates parent and child consistency.
"Find me a background track and a hit sound"	msw-search queries the resource API for sounds, returns candidates with RUIDs, and applies the chosen ones to the entities that need them.

Verification¶

The layout is one level deeper than most skill repositories: plugins/<plugin>/skills/<name>/SKILL.md, on branch main. Probe the paths before installing, since the plugin wrapper is easy to forget. These three returned 200 when this guide was written:

for p in plugins/msw-maker-base-skill/skills/msw-general/SKILL.md \
         plugins/msw-maker-base-skill/skills/msw-scripting/SKILL.md \
         plugins/msw-maker-content-skill/skills/maplestory-skill-maker/SKILL.md; do
  curl -sL -o /dev/null -w "%{http_code} $p\n" \
    "https://raw.githubusercontent.com/msw-git/msw-ai-coding-plugins-official/main/$p"
done

Read the foundation skill and the scripting skill before installing the set, because the read-order rules they impose change how the agent behaves on every later turn:

https://raw.githubusercontent.com/msw-git/msw-ai-coding-plugins-official/main/plugins/msw-maker-base-skill/skills/msw-general/SKILL.md
https://raw.githubusercontent.com/msw-git/msw-ai-coding-plugins-official/main/plugins/msw-maker-base-skill/skills/msw-scripting/SKILL.md

After install, confirm what actually landed. The frontmatter name should match the directory name, which is also the name the install index uses:

ls ~/.hermes/profiles/corpusiq/skills | grep -E '^msw-'
head -3 ~/.hermes/profiles/corpusiq/skills/msw-general/SKILL.md

A directory without a references/ folder is an incomplete copy: most of the depth in these skills lives in reference files, and msw-general reads several of them in full as a precondition to edits.

Security¶

skills.sh verdicts for sampled skills (verified 2026-10-28) - re-check the security pages on skills.sh before production use:

Skill	Gen Agent Trust Hub	Socket	Snyk
msw-general	Pass	Pass	Pass
msw-scripting	Pass	Pass	Pass
msw-defaultplayer	Pass	Pass	Pass
msw-search	Pass	Pass	Pass
msw-combat-system	Pass	Pass	Pass
msw-avatar	Pass	Pass	Pass

The six sampled skills are all clean on all three auditors, but the install surface is wider than a skill folder. The base plugin ships hooks/hooks.json, and those hooks run Node scripts at session start, on every prompt, before tool use and after edits: mlua-session-start.cjs, inject-agents-md.cjs, skill-router-reminder.cjs, skill-read-guard.cjs, structured-file-guard.cjs, mlua-diagnose-post-tool-use.cjs, skill-log.cjs and mcp-log.cjs, twelve .cjs files in total under scripts/. They are an install-time behaviour change when the plugin is loaded in Claude Code: a guard can block Bash reads of skill files and block direct reads or writes of .model and .ui files, and the loggers write session logs. Read those scripts before enabling the plugin in an environment where hook failures would matter. On the Hermes copy route the hooks do not come along, so the guardrails and the automatic diagnostics are lost as well.

There is no LICENSE file in the repository and the GitHub license endpoint returns 404, so the default all rights reserved position applies: you have no stated grant to redistribute these skills or ship them inside a product. Installing them for local agent use is a different question from republishing them, and only the publisher can grant the second.

The write surface at run time is your game project. msw-maker-mcp exposes a refresh tool that regenerates .codeblock and folder metadata, the builders rewrite .model, .map and .ui files, and the collector scripts under scripts/ in several skills shell out for asset and API lookups. Point the agent at a workspace you can revert, keep it in version control, and read the skill's referenced builder protocol before the first mutation rather than after.

Integration with CorpusIQ¶

CorpusIQ is the connector layer that lets AI assistants read the systems a business already runs on - accounting, payments, CRM, email, files and analytics - and answer with the source named. It is read-only by design: it retrieves data and never writes to, or acts in, a connected system, which is what makes it safe to point at live accounts.

This page is part of the CorpusIQ directory, the reference we maintain for the MCP server and agent-skill ecosystem. Run alongside CorpusIQ, a third-party server like this one can be combined with a company's own business data in a single answer.

See what CorpusIQ connects

Limitations¶

Snapshot data, verified 2026-10-28: 119,426 combined installs across 18 indexed listings; 38 GitHub stars; no license file; last pushed 2026-10-06. Counts drift over time.
The install index outruns the tree: 18 indexed listings against 14 SKILL.md directories, so 4 listings have no counterpart in the current tree (msw-costume, msw-ui-template, msw-behaviourtree-creator, msw-behaviourtree-spec-builder). Their content could not be confirmed and is not described here.
No license file means no explicit permission to reuse or redistribute. The repository is source-available by default copyright, not open source, so confirm terms with the publisher before bundling the skills into anything you ship.
The set assumes the msw-maker-mcp server and a local MapleStory Worlds workspace. Without them the search, builder and refresh paths degrade, and the MCP setup itself is not documented in the README.
Hooks and their behaviour are Claude Code specific. Installed through the plugin route they add session-start, prompt-time and tool-time Node scripts; copied into a Hermes skills directory they do not, so the guard rails and automatic mlua diagnostics only exist on the plugin path.
The manifests and several skill bodies are Korean, including the marketplace descriptions. Descriptions here are condensed from the skills' own English frontmatter and reference headings, not from translation of the Korean prose.

Pro Tips¶

Install msw-general first and make the agent read it before anything else. It is the router: it names which sibling skill owns a task, and the other twelve skills assume its file-workflow rules are already in context.
Ask for the read list before the diff. Every skill here opens with a mandated read step, so asking which reference files were loaded catches the case where the agent skipped the builder protocol and wrote a file format by guesswork.
Keep the MCP server running and check refresh results. .codeblock files are generated, not authored, and a script that never appears in the build log is usually a missing refresh rather than a syntax error.
Prefer msw-packages and msw-search before writing code. The platform ships official packages and a resource API, and a hand-written leaderboard or a blank sprite is the most common way an MSW project looks unfinished.
Treat the four unmatched listings as unavailable until you find them. Point the agent at the fourteen directories that exist rather than letting it guess at a skill name the index still counts.

← Skills Catalog | Skills Marketplace → Powered by CorpusIQ