Lua — game scripting, metatables, coroutines
Expert Lua development for embedded and game scripting — metatables and metamethods, coroutine pipelines, closures and module patterns, performance tricks (table preallocation, avoiding string concatenation in loops), and a code-review checklist
- What
- Expert Lua development for embedded and game scripting — metatables and metamethods, coroutine pipelines, closures and module patterns, performance tricks (table preallocation, avoiding string concatenation in loops), and a code-review checklist
- Cost
- Free
- Needs
- a Lua codebase (game, embedded script host, or similar) the agent can read and work on — the skill is an expert methodology, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @mindrally's expert Lua skill: write idiomatic, high-performance Lua for embedded scripting and games. Covers metatables and metamethods (operator overloading, `__index`/`__newindex` fallback chains), coroutine-based pipelines for cooperative multitasking, closures and the module pattern (`local M = {}`), functional helpers, performance patterns (preallocate tables with known sizes, avoid string concatenation in loops, cache table lookups, use `ipairs` for arrays), common pitfalls (1-based indexing, `nil` semantics, global pollution, `pcall` error handling), and a code-review checklist (idiom correctness, performance hotspots, error paths). Honest caveats: guidance only — the agent needs a Lua codebase (game, embedded script host) to apply it to; the repo contains nothing but this skill (nothing else to audit in the source). Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Lua codebase (game, embedded script host, or similar) the agent can read and work on — the skill is an expert methodology, not software to install Install "Lua — game scripting, metatables, coroutines" for me. It gives my agent @mindrally's Lua playbook: metatables and metamethods (operator overloading, __index/__newindex chains), coroutine pipelines for cooperative multitasking, closures and the module pattern (local M = {}), functional helpers, performance patterns (table preallocation, avoiding string concatenation in loops, cached lookups, ipairs for arrays), common pitfalls (1-based indexing, nil semantics, global pollution, pcall error handling), and a code-review checklist for idiom correctness, performance and error paths. Apache-2.0-licensed. Repository: https://github.com/mindrally/skills/blob/main/lua/SKILL.md 1. Fetch the SKILL.md file from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "lua". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my Lua codebase; nothing else — it's an expert methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.