Individual skill
input-mapper
Manage Godot input action mappings in project.godot. Use when adding input actions, changing key bindings, setting up controls for a new genre, or validating that all referenced actions exist. Use it while implementing mechanics or changing the project's controls.
plugins/shared/loom/skills/godot/input-mapper/SKILL.md
Source commit 7cf9b229d22656ac28cb6fa47d26bb6230155b0a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,451
- Repository last updated
- Nov 3, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,867 bytesreferences/serialization.mddoc · 3,856 bytes
Read excerpt
# Input Mapper
$ARGUMENTS
Read the GDD or user request, determine which input actions are needed,
and write the correct `[input]` section entries into `project.godot`.
## Step 1 — Extract Required Actions
Source actions from one of:
1. **GDD Mechanics table** — each mechanic implies input actions
(e.g., "Player can jump" → `jump` action).
2. **Genre preset** — use a preset from Step 3 as a starting point.