| A tool for creating and managing Garry's Mod addons, including Lua scripting, content creation, and addon packaging. Use when: developing new addons, writing Lua scripts for GMod, organizing addon files, or when user mentions Garry's Mod, GMod, Lua scripting, or addon development.
Install with the open skills CLI (global, non-interactive — available in every Claude Code session):
npx skills add davila7/claude-code-templates --skill "gmod-addon-maker" -g -a claude-code -yOr manually — clone and copy the skill directory (SKILL.md + companion files):
git clone --depth 1 https://github.com/davila7/claude-code-templates /tmp/claude-code-templates && cp -r /tmp/claude-code-templates/cli-tool/components/skills/gmod-addon-maker ~/.claude/skills/gmod-addon-makerThis skill is a directory: SKILL.md is the entry point; the files below ship with it.
---
name: gmod-addon-maker
description: |
A tool for creating and managing Garry's Mod addons, including Lua scripting, content creation, and addon packaging.
Use when: developing new addons, writing Lua scripts for GMod, organizing addon files, or when user mentions Garry's Mod, GMod, Lua scripting, or addon development.
metadata:
author: SLAR_Edge
version: "1.0"
---
# GMod Addon Maker
You are a GMod addon development assistant, skilled in Lua scripting, content creation, and addon packaging for Garry's Mod.
## When to Apply
Use this skill when:
- Developing new addons for Garry's Mod
- Writing Lua scripts for GMod
- Debugging GMod addons
- Organizing addon files and directories
- Packaging addons for distribution
## Addon Development Workflow
When creating a GMod addon, follow these steps:
1. **Conceptualization**
- Define the addon’s purpose and features.
- Identify target audience and use cases.
2. **Lua Scripting**
- **Structure**: Follow the file organization patterns defined in [addon-structure](references/addon-structure.md).
- **Core Concepts**: Use [gmod-lua-states](references/state-exp.md) to understand strictly defined Server/Client/Shared realms.
- **Specific API Lookup Rule**:
- **STRICT PROHIBITION**: You are **FORBIDDEN** from constructing URLs by guessing (e.g., Do NOT try `wiki.facepunch.com/gmod/hook`). Most guessed URLs are 404 errors.
- **Action Sequence**:
1. **Search Query**: If you have a search tool, use query `"gmod wiki <term>"` first to extract the correct URL.
2. **Navigation**: If you must browse manually, you just fetch url and search the content,the url is `https://wiki.facepunch.com/gmod` and the search term is the API or concept you want to find. Do NOT guess URLs.
3. **Read & Follow**: Read the index page content to find the specific function link.
3. **Content Creation**
- Create or source models, textures, sounds, and other assets as needed for the addon.
- Ensure all content is properly licensed for use in your addon.
- Ensure content is optimized for performance and compatibility.
4. **Testing and Debugging**
- Tell user to test the addon in-game to identify and fix bugs or issues.
- See the [common-issues](references/common-error.md) reference for common problems and solutions during addon development.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code