godot-api
Skill120 starsChanged 7 months agoMITView on GitHub
Look up Godot engine class APIs — methods, properties, signals, enums. Use when you need to find which class to use or look up specific API details.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- RandallLiuXin/GodotMakeredited, first seen Apr 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- RandallLiuXin/GodotMaker★ 55515% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Read ${CLAUDE_SKILL_DIR}/doc_api/_common.md — index of ~128 common classes
- Very specific: line 18
If the class isn't there, read ${CLAUDE_SKILL_DIR}/doc_api/_other.md
- Very specific: line 19
Read ${CLAUDE_SKILL_DIR}/doc_api/{ClassName}.md — full API with descriptions for all methods, properties, signals, constants, and virtual …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Godot API Lookup
$ARGUMENTS
How to answer
- Read
${CLAUDE_SKILL_DIR}/doc_api/_common.md— index of ~128 common classes - If the class isn't there, read
${CLAUDE_SKILL_DIR}/doc_api/_other.md - Read
${CLAUDE_SKILL_DIR}/doc_api/{ClassName}.md— full API with descriptions for all methods, properties, signals, constants, and virtual methods - Return what the caller needs:
- Specific question (e.g. "how to detect collisions") → return relevant methods/signals with descriptions
- Full API request (e.g. "full API for CharacterBody3D") → return the entire class doc
GDScript syntax reference: ${CLAUDE_SKILL_DIR}/gdscript.md — language syntax, patterns, and recipes. Read when the caller asks about GDScript syntax, idioms, or common patterns (input handling, tweens, state machines, etc.).
Bootstrap if doc_api is empty: bash ${CLAUDE_SKILL_DIR}/tools/ensure_doc_api.sh
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.