By moonbitlang
Build, test, and refactor MoonBit projects with agent-assisted workflows for FFI bindings, formal specifications, proof-carrying code, and migration from OCaml.
Guides agents through complete, maintainable MoonBit bindings for C/C++ libraries, from upstream source survey through vendoring, safe API design, documentation tests, and ASan validation. Use when creating or hardening MoonBit native FFI bindings, wrapping C APIs, vendoring C sources into native-stub, or turning a C library into a MoonBit package.
Guide for writing, refactoring, and testing MoonBit projects. Use when working in MoonBit modules or packages, organizing MoonBit files, using moon tooling (build/check/run/test/doc/ide etc.), or following MoonBit-specific layout, documentation, and testing conventions.
Guide for writing MoonBit bindings to C libraries using native FFI. Use when adding extern "c" declarations, writing C stubs with moonbit.h, configuring native-stub and link.native in moon.pkg, choosing
Extract formal spec and comprehensive test suites from existing MoonBit implementations. Use when asked to "extract spec from implementation", "generate tests from code", or "create spec-driven tests for existing package". Analyzes existing code to produce spec.mbt with `declare` keyword stubs and organized test files (valid/invalid).
Use this skill when the user needs help solving MoonBit language, code, compiler diagnostic, package, toolchain, backend, FFI, test, or "does MoonBit have X?" questions. Use it even when MoonBit is only implied by .mbt files, moon.mod.json, moon.pkg.json, moon commands, wasm/js/native targets, or mooncakes packages. This skill helps choose the right MoonBit source of truth, discover APIs with moon ide, avoid stale assumptions, and validate fixes.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Agent Skills are folders of instructions, scripts, and resources that AI agents can discover and use to perform at specific tasks. Write once, use everywhere.
Install all skills to the portable universal skills directory:
npx skills@latest add moonbitlang/skills -g --agent universal --skill "*" --copy -y
This installs one copy under ~/.agents/skills/.
Install all skills for Codex with the skills CLI:
npx skills@latest add moonbitlang/skills -g --agent codex --skill "*" --copy -y
Install all skills for Claude Code:
npx skills@latest add moonbitlang/skills -g --agent claude-code --skill "*" --copy -y
List the skills available in this repository:
npx skills@latest add moonbitlang/skills --list
Install one skill by name:
npx skills@latest add moonbitlang/skills -g --agent codex --skill moonbit-orientation --copy -y
Each skill lives in its own directory under skills/.
If you do not want to use npx, clone the repository and copy the skill directories manually:
git clone https://github.com/moonbitlang/skills.git
cd skills
mkdir -p ~/.agents/skills
for skill in skills/*; do
[ -f "$skill/SKILL.md" ] || continue
rsync -a --delete "$skill/" "$HOME/.agents/skills/$(basename "$skill")/"
done
Installable skills are committed as regular directories under skills/. Do not
use submodules or symlinks for installable skill entries; npx skills expects
to find real skills/<name>/SKILL.md files after a normal clone.
Some skills are vendored from upstream repositories. Their sources are listed in
skills.sources.json. To refresh them:
./scripts/sync-upstream-skills.py
npx skills@latest add . --list
git diff --check -- . ':(exclude)skills/**'
git diff
Skills listed in skills.sources.json are mirrored from their upstream
repositories. Change those skills upstream rather than editing the vendored copy
here; the sync script replaces each listed skill directory with the upstream
contents.
The same sync path also runs daily in GitHub Actions and opens a pull request when upstream skill contents change.
License files are kept inside individual skill directories when upstream
provides them. For vendored skills without a local license file, check the
source repository listed in skills.sources.json.
npx claudepluginhub moonbitlang/skills --plugin moonbit-skillsIntegrated Rust development skills for multiple domains (UI, Robotics, etc.)
Meta-plugin that installs all skills from all plugins in the marketplace
Skill synchronization and management for Claude Code, Codex, GitHub Copilot, and Cursor. Provides 27 MCP tools for validation, sync, intelligence, and tracing.
Skill discovery and installation assistant — find and install the right skills for your project
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls