Agent skill

Scenario Godot Vfx

by scenario-labs in scenario-labs/skills

A skill your agent uses when making or fixing particle effects and game feel in Godot 4.7: GPUParticles3D or GPUParticles2D explosion, fireball projectile with trail, impact, sparks, smoke…

MITAuto-check passedGame Development

Install Scenario Godot Vfx

skills CLI
$ npx skills add scenario-labs/skills --skill scenario-godot-vfx -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install scenario-labs/skills scenario-godot-vfx --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/game-engines/godot/scenario-godot-vfx .claude/skills/scenario-godot-vfx && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
scenario-godot-vfx
GitHub stars
946
Token cost
~5.3k tokens
SKILL.md length
2,176 words
Files
24 (incl. scripts, references)
Skills in repo
146
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when making or fixing particle effects and game feel in Godot 4.7: GPUParticles3D or GPUParticles2D explosion, fireball projectile with trail, impact, sparks, smoke…

  • Works in 8 steps: An effect is layers, and the head of a… → Particle settings fail silently, so… → visibility_aabb is both culling and the… → …
  • Fixing particle effects and game feel in Godot 4.7: GPUParticles3D
  • SKILL.md covers Stance (the expert delta), Establish first, Workflow and Expert checklist (state these…, plus 6 more sections
  • Calls npx

What it does

Scenario Godot Vfx is an agent skill from scenario-labs/skills. Use when making or fixing particle effects and game feel in Godot 4.7: GPUParticles3D or GPUParticles2D explosion, fireball projectile with trail, impact, sparks, smoke, shockwave, ribbon trails, sub-emitters, particle collision, color curve does nothing, particles pop out or vanish, effect too heavy on mobile, CPUParticles fallback for Compatibility or web, overdraw, hit-stop, freeze frame, screen shake, juice.

Its SKILL.md is about 5.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 29 other files, including scripts and reference files (for example `references/critique.md`, `references/expert-notes.md` and `references/gui-paths.md`).

It sits in Game Development, covering Game development. It works with Godot. The repository describes itself as: Get production-ready images, video, audio, and 3D from any AI agent: skills that pick the right model, price before spending, and keep characters and brands consistent through… The licence is MIT.

When your agent uses it

  • Fixing particle effects and game feel in Godot 4.7: GPUParticles3D
  • GPUParticles2D explosion
  • Fireball projectile with trail
  • Particle collision

Example prompts

  • “/scenario-godot-vfx”

Requirements

  • Node.js

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. An effect is layers, and the head of a projectile is not particles. A projectile is head, tail and sparks; the head is a shader mesh with…
  2. Particle settings fail silently, so audit them in code. Color and alpha curves do nothing without vertex_color_use_as_albedo; scale curves…
  3. visibility_aabb is both culling and the collision area (Godotneers cZ5Ang_Ji8E 00:45:28). Measure it rather than guessing: on 4.7.2…
  4. Tier by renderer, never by amount_ratio. amount_ratio hides particles and saves nothing (GPUParticles3D docs; Bonkahe BUa-mKHEPUM…
  5. Particles do not touch physics. Gameplay hits come from a ray swept every physics tick; particle collision needs GPUParticlesCollision…
  6. Juice is code you can test. Hit-stop lowers Engine.time_scale and waits on a timer that ignores it, then restores 1.0 (Mostly Mad…
  7. Judge frames, not the inspector. Render windowed with --fixed-fps 60, so frame k is t = k/60 s, at 0.03 to 2.2 s, and look at one contact…
  8. A trail that follows a node is a particle shader trick. Pin the particle to EMISSION_TRANSFORM[3].xyz in start() and process(), with no…

What it can do on your machine

Read from SKILL.md and the folder at commit f6f8ab7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 9 files in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scenario Godot Vfx loads about 5.3k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 109 tokens; SKILL.md has 2,176 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~5.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~19k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from scenario-labs/skills at commit f6f8ab7, republished under its MIT licence (© scenario-labs). 2,176 words, ~5,333 tokens.

Download SKILL.mdSave it as .claude/skills/scenario-godot-vfx/SKILL.md (or your agent's skills folder). This skill also uses 23 other files; get the full folder from GitHub.
name
scenario-godot-vfx
description
Use when making or fixing particle effects and game feel in Godot 4.7: GPUParticles3D or GPUParticles2D explosion, fireball projectile with trail, impact, sparks, smoke, shockwave, ribbon trails, sub-emitters, particle collision, color curve does nothing, particles pop out or vanish, effect too heavy on mobile, CPUParticles fallback for Compatibility or web, overdraw, hit-stop, freeze frame, screen shake, juice.
license
MIT

Godot VFX

Target: Godot 4.7.2.stable, macOS Apple Silicon.

Expert level here means effects built as layers of small systems, every silent particle failure caught by a script before anyone looks, and every claim about look or cost backed by frames captured at exact times and by measured overdraw and GPU time per renderer. The agent builds effects in code, renders them windowed, and looks at contact sheets. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.

REQUIRED BACKGROUND: scenario-godot-expert (gd_env, gd_run, gd_review, AgentKit, GD_MAX slots, windowed vs headless).

Stance (the expert delta)

  1. An effect is layers, and the head of a projectile is not particles. A projectile is head, tail and sparks; the head is a shader mesh with scrolling noise and HDR color above 1 (Le Lu 74XywaLGO5Q 00:00:34, 00:08:05). An explosion is flash, fire, smoke, sparks, debris, shockwave and light, each a small system made by duplicating a working one and changing a few values (Brackeys htRjt505sPg 00:02:30, 00:13:27). A one-particle system is fine for a shockwave ring (00:18:02).
  2. Particle settings fail silently, so audit them in code. Color and alpha curves do nothing without vertex_color_use_as_albedo; scale curves do nothing on a particle billboard without billboard_keep_scale; trails need trail_enabled, a Ribbon or Tube trail mesh and use_particle_trails (Godotneers cZ5Ang_Ji8E 00:09:44, 00:32:54; Brackeys 00:23:44). A sub-emitter's own amount is a global cap (Godotneers yKoGuBGZatY 00:44:48) and its AABB is not inherited (cZ5Ang_Ji8E 01:06:19). vfx_audit.gd flags all of these.
  3. visibility_aabb is both culling and the collision area (Godotneers cZ5Ang_Ji8E 00:45:28). Measure it rather than guessing: on 4.7.2, capture_aabb() pads particle positions by the draw mesh's longest axis and ignores per-particle scale (measured: Flash quad 2 m gave a 4 m box; a ring scaled to 4.5 m still gave 2 m) [added]. fit_aabb corrects for scale and must run inside the level, because debris without its colliders falls 8 m through the world.
  4. Tier by renderer, never by amount_ratio. amount_ratio hides particles and saves nothing (GPUParticles3D docs; Bonkahe BUa-mKHEPUM 00:01:18). Lower amount per tier and drop the layers the renderer cannot draw. Compatibility drops decals with no warning, and logs warnings for trails and sub-emitters (measured) [added].
  5. Particles do not touch physics. Gameplay hits come from a ray swept every physics tick; particle collision needs GPUParticlesCollision nodes, and the step per tick is speed / fixed_fps, with fixed_fps 30 by default (Godotneers cZ5Ang_Ji8E 00:44:23, 00:47:17).
  6. Juice is code you can test. Hit-stop lowers Engine.time_scale and waits on a timer that ignores it, then restores 1.0 (Mostly Mad Jwv9t5zFlqI 00:00:32, 00:01:37). Shake comes from smooth noise with decay (Mostly Mad pG4KGyxQp40 00:00:39); trauma squared and a 3D camera offset are [added].
  7. Judge frames, not the inspector. Render windowed with --fixed-fps 60, so frame k is t = k/60 s, at 0.03 to 2.2 s, and look at one contact sheet per renderer. Overdraw comes from DEBUG_DRAW_OVERDRAW with a measured per-layer calibration, and GPU time from the Vulkan driver (Metal reports 0 on macOS) [added].
  8. A trail that follows a node is a particle shader trick. Pin the particle to EMISSION_TRANSFORM[3].xyz in start() and process(), with no forces (Octodemy iPCzOe-S9EQ 00:05:42).

Establish first

InputChangesDefault
Target rendererswhich layers exist (trails, decals, sub-emitters)Forward+ desktop, Mobile phones, Compatibility web
2D or 3Dnode family, collision (LightOccluder2D vs GPUParticlesCollision3D)3D
Camera distance and screen sharequad sizes, overdraw budgetgameplay camera 4 to 10 m
Frame budget for VFXamounts per tierunder 2.5 ms GPU for six bursts at 720p on the dev Mac [added]
Lookunshaded additive vs lit smoke (Le Lu e_6ZA-xa_DQ 00:07:23)stylized, unshaded fire, alpha-blended smoke
Spawning modelfree-on-done vs pooledfx_burst frees itself; done signal for pools

Workflow

  1. Project and kit. Clone Base3D, gd_vfx.install(P) copies tooling to addons/agentkit/vfx/, and shaders and runtime scripts to res://vfx/ (they ship with the game). Read project.godot. GATE: 3d/physics_engine="Jolt Physics" and the intended renderer/rendering_method are present as text; vfx_selftest.gd:compile reports 0 errors over 10 scripts (check_all skips addons/agentkit/).
  2. Build per tier in code. gd_vfx.build(P, "high"|"mobile"|"low") saves explosion_, impact_, fireball_, shot_ and burst_stage_<tier>.tscn from vfx_recipes.gd. Specs are dictionaries (VB.emitter); curves and ramps become CurveTexture and GradientTexture1D (HDR when a channel exceeds 1); shared textures live in res://vfx/tex/*.tres (Brackeys 00:15:04: never embed). GATE: build ok, no captured errors. Kit layers: fireball (stretched SphereMesh head with fx_fire_head, noise minus gradient, HDR; inverted-Fresnel fx_soft_core; world-space eroded puffs driven by INSTANCE_CUSTOM.y, onetupthree N9ilhL8JFes 00:05:38; velocity sparks; ribbon via fx_trail_follow and an OmniLight3D, both off on low); explosion (flash, fire, depth-sorted smoke, colliding sparks, Face-Y ring, debris with a 30 Hz smoke sub-emitter on high, light, scorch Decal except low); fx_projectile (ray swept every tick, impact on the hit normal, frees itself after its trail dies).
  3. Static audit. gd_vfx.audit(P, scene, tier, level). GATE: 0 errors for the matching tier. Warnings are read and either fixed or written down. Prove the audit catches problems once on broken.tscn (21 findings, 4 errors).
  4. Fit AABBs in context. gd_vfx.fit_aabb(P, "res://vfx/burst_stage_high.tscn", node="Explosion", play_method="Explosion:play", write=True, out=effect_scene). GATE: old_encloses_live true for every emitter, and the timeline aabb_check reports nothing outside.
  5. Look at it, per renderer. gd_vfx.timeline(P, scene, times=[0.03,0.1,0.2,0.35,0.6,1.0,1.5,2.2], renderer=..., trigger="none", extra={"play_method": "Explosion:play", "aabb_check": True}); for the projectile, extra={"hold": "Fireball"}. Open the contact sheet. GATE: no all-black, all-white or uniform flags. By eye: the flash reads first, fire turns to smoke, nothing pops, the ring fades, sparks bounce on the floor, the scorch stays, and the head reads as fire with its tail behind it.
  6. Fallback. For Compatibility, use the low tier (no ribbon, decal, light or sub-emitter), or gd_vfx.to_cpu for a CPUParticles3D twin. GATE: read the lost list (collision, sub-emitters, trails, particle shaders, alpha_curve baked into the ramp, align mode) and render the twin in gl_compatibility.
  7. Budget. gd_vfx.overdraw(...) per tier, and gd_run.profile_scene(stress scene, size=(1280,720), driver="vulkan"). GATE: p99 layers and GPU p95 inside the numbers below, low tier lighter than high.
  8. Behavior. Run vfx_selftest.gd: lifecycle (node count back to baseline after 5 spawns), projectile (one hit, explosion spawned, everything freed) and juice (time_scale restored, shake bounded and back to 0). GATE: all ok.

Expert checklist (state these in the plan)

  • Complete code in the deliverable: paste the vfx_recipes.gd specs and fx_fire_head.gdshader, not prose; readers may lack the kit.
  • Replay with restart(), not emitting = true (docs).
  • Deterministic frames: use_fixed_seed, then speed_scale = 0, restart(), request_particles_process(t). Two seeks to 0.4 s were pixel-identical; without a fixed seed they differed by 0.50 (P13).
  • Fire into smoke in one system: premultiplied blend (BLEND_MODE_PREMULT_ALPHA, texture imported with Premultiply Alpha): low alpha adds, high alpha mixes; fade with black and alpha 0 (Brackeys 30:56 to 32:39). Measured over gray: alpha 0 brightened it, alpha 1 replaced it (P13).
  • Smoke LOD: fx_smoke_lod.gdshader maps a black-to-white color ramp to mip 0 to 8 of one noise texture, so the puff diffuses almost free; color moves to a uniform (Le Lu e_6ZA-xa_DQ 16:40 to 24:20). Detail spread fell from 0.10 to 0.0 over life on all three renderers (P13).
  • Duplicating a system: Brackeys' "Make Unique Recursive, but never the texture" is duplicate(true) in 4.7.2: embedded curves become unique, external .tres textures stay shared (P13). Keep the mesh shared and the material in material_override (Brackeys 13:59 to 15:04).
  • Billboard plus direction: Align Y conflicts with billboards; use transform_align Z Billboard + Y to Velocity (Brackeys 27:07).
  • Layered transparents flicker: offset the nodes first, then sorting_offset (Brackeys 29:57).
  • TAA ghosting: DRAW_ORDER_INDEX (the 3D default) is the only order with motion vectors; keep it for opaque particles (docs).
  • Preprocess runs the shader fixed_fps times per preprocessed second and can stall the GPU; never on one-shots (docs, audit preprocess_one_shot).
  • Near-camera quads: distance_fade_mode Pixel Alpha fades by distance without a depth read; proximity fade softens intersections.
Show full SKILL.md (873 more words)Show less

Numbers

ValueRelative toSource
Head HDR color (2, 1.3, 0.6); sparks (2, 1.3, 0.5); spark lifetime 0.3 sglow threshold 1.0Le Lu 00:08:05, 00:28:15
Head render priority 2 over the core's 1; inverted Fresnel power 4 to 5nested transparent meshesLe Lu 00:18:25
Shockwave: 1 particle, 0.4 to 0.5 sone-shot burstBrackeys 00:18:34
Tunnel step = v_max / fixed_fps; fixed_fps 30 by defaultthinnest colliderGodotneers 00:47:17, docs
collision_base_size default 0.01 mvisible particle sizeGodotneers 00:57:27
Child amount at least parent amount x per-event count (AT_END, AT_COLLISION, AT_START); CONSTANT mode: parent amount x Hz x child lifetimesub-emitter capGodotneers 00:44:48 (per event); CONSTANT derived [added], both in link_sub_emitter
sub_emitter_frequency is in Hz: dots 1/f m apart at 1 m/smeasured 4 and 10 Hzlive V10
Overdraw per layer: 0.070 linear luma (Forward+, Mobile); 36.6/255 raw (Compatibility, saturates past 6)DEBUG_DRAW_OVERDRAW PNGlive V11 [added]
Explosion p99 layers at the 0.6 s peak: high 4.9 to 5.9, low 2.3 to 3.3 (seeds vary)640x360 view at about 5 mlive V11, 3 runs
GPU p95, 1280x720, M5 Max via Vulkan, machine shared with other Godot jobs: stage alone 1.0 to 2.3 ms; six looping explosions: high 3.4 to 4.0, mobile tier 2.1 to 2.7, low 1.2 msthe framelive V12, 3 runs
Particle counts, explosion / fireball: high 208 / 57, mobile 48 / 35, low 34 / 22tier scale 1.0 / 0.6 / 0.4kit [added]
Hit-stop 0.05 time scale for 0.08 s; shake 0.30 x 0.22 m at trauma 1, decay 1.8/sthe camera[added], typical range in Mostly Mad note
Smoke ramp about 0.06 linear for mid gray on Forward+; x3.6 on Compatibilitythe same framelive V5 [added]

Quality gates

Measurable:

  • Audit: 0 errors for the tier. Kit compile: 0 parse errors. Project file has Jolt and the chosen renderer.
  • AABB: every emitter's live box inside visibility_aabb at every captured time.
  • Lifecycle: node count equals the baseline after N spawns, and done fires N times with no safety timeouts.
  • Projectile: one hit at the expected time (12 m at 14 m/s gives 0.867 s, frame 52) and nothing left in the tree.
  • Juice: Engine.time_scale is 1.0 after single and overlapping stops, with no early restore; shake offset at most the maximum and exactly 0 at the end.
  • Overdraw p99 and GPU p95 per tier against the table. Compatibility logs show the expected warnings and no unexpected ones.

Visual (contact sheets of at most 1600 px; rubric in references/critique.md): flash then fire then smoke, no popping, readable silhouette at gameplay distance, ring fades, sparks bounce, the trail follows the head, the explosion is oriented to the surface normal, and each tier holds up on its renderer.

Common mistakes

MistakeWhat it looks likeFix
Vertex color offwhite quads, curves ignoredvertex_color_use_as_albedo
Keep scale off on a particle billboardscale curve ignoredbillboard_keep_scale
Trail without use_particle_trailschopped flat piecesset it on the trail mesh material
Child amount under the capsub-emitter trails thin outlink_sub_emitter computes the cap
Default 8 m AABBeffect pops out, collisions stopfit_aabb in the level
collision_base_size larger than the spawn heightdebris stuck at the origin (measured: 0.5 m of travel instead of 10 to 12 m)spawn above the collider
amount_ratio used as the mobile tierno savinglower amount
emitting = true to replayone-shot sometimes skippedrestart() (docs)
Freeing the projectile on hitworld-space trail vanishes at oncestop emitters, wait for the trail to die, then free
convert_from_particles on view-depth sorting"Index p_order = 3 is out of bounds", sorting lostVB.to_cpu maps draw order
Same colors on every renderersmoke near black on Compatibilityretune the low tier on Compatibility
Profiling on Metalgpu_ms 0driver="vulkan"

Handoffs

  • Receives hit events (point, normal, pooling) from scenario-godot-gameplay, budgets from scenario-godot-performance-export, glow and environment from scenario-godot-rendering-lighting.
  • Delivers res://vfx/*.tscn per tier, res://vfx/shaders and runtime (fx_burst, fx_projectile, Juice), audit JSON, sheets, overdraw and GPU tables.
  • Asks scenario-godot-shaders for new surface shaders (dissolve, water, distortion), scenario-godot-audio for impact sounds, and scenario-godot-2d for 2D effect integration.

Godot 4.7 notes

  • capture_aabb() pads by the draw mesh's longest axis and ignores particle scale (4.7.2, measured).
  • CPUParticles3D.convert_from_particles copies draw_order as a raw integer, but the enums differ: GPU view depth is 3, CPU view depth is 2. CPUParticles3D has no alpha_curve (4.7.2, measured).
  • Compatibility logs "Particle trails are only available when using the Forward+ or Mobile renderer" and "does not support particle sub-emitters"; decals disappear with no warning.
  • Headless draws nothing, so captures need a windowed run. On macOS, Metal reports GPU time as 0; use --rendering-driver vulkan.
  • Curve enforces min_value and max_value since 4.4, so widen the range for scale curves above 1. AgX arrived in 4.4. Glow defaults changed in 4.6 (intensity 0.8 to 0.3): retune older effects.
  • Particle shaders use start() and process(); a Godot 3 vertex() writing VELOCITY fails.
  • The trail sections refresh bug (Octodemy, 4.7 era) and Godotneers' 4.2 trail and SDF bugs: not yet run on 4.7.2.

References

© scenario-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 23 other files (scripts, references) in skills/game-engines/godot/scenario-godot-vfx of scenario-labs/skills.

  • SKILL.md
  • references/critique.md
  • references/expert-notes.md
  • references/gui-paths.md
  • references/procedures.md
  • references/sources.md
  • scripts/agentkit/vfx/fx_looper.gd
  • scripts/agentkit/vfx/runtime/fx_burst.gd
  • scripts/agentkit/vfx/runtime/fx_projectile.gd
  • scripts/agentkit/vfx/runtime/juice.gd
  • scripts/agentkit/vfx/shaders/fx_erode.gdshaderinc
  • scripts/agentkit/vfx/shaders/fx_erode_add.gdshader
  • scripts/agentkit/vfx/shaders/fx_erode_mix.gdshader
  • scripts/agentkit/vfx/shaders/fx_fire_head.gdshader
  • scripts/agentkit/vfx/shaders/fx_smoke_lod.gdshader
  • … and 9 more

Open the folder on GitHubat commit f6f8ab7

Compare with similar skills

Scenario Godot Vfx next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scenario Godot Vfx compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Godot Vfx this skillscenario-labs/skills946—~5.3kAutomated safety check: PassMIT
Godot Gdscript Patterns925236118/AlphaAgent10310 repos~5kAutomated safety check: PassMIT
2D Map and Scene Generator0x0funky/agent-sprite-forge4.4k—~2.9kAutomated safety check: PassMIT
Godot UI Integrationzimo-xiao-zheng/godot-ui-integration285—~1.5kAutomated safety check: PassMIT
Godot Wechat Minigame Adaptergodothub/godot-minigame187—~1.5kAutomated safety check: PassMIT
AI Game Art Pipelineybuild-ai/ai-game-art-pipeline-skill297—~1.1kAutomated safety check: PassMIT

Similar skills

  • Godot Gdscript Patterns

    925236118/AlphaAgent

    Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization.

    103 GitHub starsUsed in 10 repos~5k tokens
    Game DevelopmentAuto-check passed
  • 2D Map and Scene Generator

    0x0funky/agent-sprite-forge

    Plans and builds 2D game maps and scenes, from tilemaps and parallax backgrounds to HD-2D plates, with collision checks, a playable HTML preview and Tiled, Godot or LDtk export.

    4.4k GitHub stars~2.9k tokensUpdated 5 days ago
    Game DevelopmentAuto-check passed
  • Godot UI Integration

    zimo-xiao-zheng/godot-ui-integration

    Build or revise Godot UI from an approved design, separated art, or a visual reference when scene structure, gameplay binding, and runtime visual verification all matter.

    285 GitHub stars~1.5k tokensUpdated 1 mo ago
    Game DevelopmentAuto-check passed
  • Godot Wechat Minigame Adapter

    godothub/godot-minigame

    Apply the bundled self-contained Godot WeChat Mini Game adapter kit to an official Godot checkout.

    187 GitHub stars~1.5k tokensUpdated 25 days ago
    Game DevelopmentAuto-check passed
  • AI Game Art Pipeline

    ybuild-ai/ai-game-art-pipeline-skill

    Provider-neutral open-source skill for planning and producing game-runtime art assets and animation: static props/icons, canonical character sheets, combat sprites, 3D/video motion references…

    297 GitHub stars~1.1k tokensUpdated 3 mo ago
    Game DevelopmentAuto-check passed
  • MCP Driver

    RandallLiuXin/GodotMaker

    Runtime debugging and live project inspection via godot-mcp.

    550 GitHub starsUsed in 1 repo~1.1k tokens
    Game DevelopmentAuto-check passed

More from scenario-labs/skills

All 146 skills in this repo
  • Scenario Blender Grease Pencil

    scenario-labs/skills

    A skill your agent uses when drawing or animating with Grease Pencil in Blender 5.x from Python: 2D or 2.5D illustration, frame-by-frame animation, a cutout or part-based 2D character, strokes with…

    946 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Scenario Blender Hair

    scenario-labs/skills

    A skill your agent uses when grooming hair or fur in Blender with hair curves, such as a character hairstyle, animal fur, procedural fur in geometry nodes, or hair cards and mesh hair for games.

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when lighting, rendering or compositing in Blender: light a character, product or hero shot, interior at dusk or night, three-point or motivated lighting, sun and sky, HDRI…

    946 GitHub stars~5k tokensUpdated yesterday
    Auto-check passed
  • Scenario Chatgpt Pet Create

    scenario-labs/skills

    A skill your agent uses when creating a ChatGPT pet or Codex pet with Scenario: hatching an animated companion from a text idea, a character, mascot or brand cue, or reference photos and art; making…

    946 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Scenario Godot Animation

    scenario-labs/skills

    A skill your agent uses when animating characters or scenes in Godot 4.7: AnimationPlayer clips and RESET, AnimationTree state machines and blend spaces built in code, Mixamo or glTF import, loop…

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • Scenario Godot Audio

    scenario-labs/skills

    A skill your agent uses when adding or fixing sound in Godot 4.7: audio buses and effects, volume sliders, 'too many sounds', combat audio with hundreds of enemies, sounds clipping or distorting, 3D…

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Scenario Godot Vfx

What does Scenario Godot Vfx do?

A skill your agent uses when making or fixing particle effects and game feel in Godot 4.7: GPUParticles3D or GPUParticles2D explosion, fireball projectile with trail, impact, sparks, smoke…. Scenario Godot Vfx is an agent skill from scenario-labs/skills.7: GPUParticles3D or GPUParticles2D explosion, fireball projectile with trail, impact, sparks, smoke, shockwave, ribbon trails, sub-emitters, particle collision, color curve does nothing, particles pop out or vanish, effect too heavy on mobile, CPUParticles fallback for Compatibility or web, overdraw, hit-stop, freeze frame, screen shake, juice.

When should I use Scenario Godot Vfx?

Scenario Godot Vfx fits situations like: fixing particle effects and game feel in Godot 4.7: GPUParticles3D; GPUParticles2D explosion; fireball projectile with trail; particle collision.

How do I install Scenario Godot Vfx in Claude Code?

Run `npx skills add scenario-labs/skills --skill scenario-godot-vfx -a claude-code`. Or copy the skill folder (skills/game-engines/godot/scenario-godot-vfx in scenario-labs/skills) into .claude/skills/scenario-godot-vfx in your project. Claude Code loads it when a task matches its description.

How do I install Scenario Godot Vfx in Codex?

Run `npx skills add scenario-labs/skills --skill scenario-godot-vfx -a codex`. Or copy the skill folder (skills/game-engines/godot/scenario-godot-vfx in scenario-labs/skills) into .agents/skills/scenario-godot-vfx in your project. Codex loads it when a task matches its description.

Can I use Scenario Godot Vfx in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add scenario-labs/skills --skill scenario-godot-vfx -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenario-godot-vfx, .gemini/skills/scenario-godot-vfx, .github/skills/scenario-godot-vfx and .opencode/skills/scenario-godot-vfx in your project.

What does Scenario Godot Vfx need to run?

Going by SKILL.md and its folder, Scenario Godot Vfx needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Scenario Godot Vfx access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Scenario Godot Vfx safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Scenario Godot Vfx use?

Scenario Godot Vfx is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scenario Godot Vfx use?

About 5.3k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.

What are the alternatives to Scenario Godot Vfx?

Skills that share tags, products or a category with Scenario Godot Vfx: Godot Gdscript Patterns (925236118/AlphaAgent, 103 stars), 2D Map and Scene Generator (0x0funky/agent-sprite-forge, 4.4k stars), Godot UI Integration (zimo-xiao-zheng/godot-ui-integration, 285 stars) and Godot Wechat Minigame Adapter (godothub/godot-minigame, 187 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenario Godot Vfx?

scenario-labs (a GitHub organization) maintains it in scenario-labs/skills, which has 946 GitHub stars. The repository holds 146 skills in this directory. The repository was last updated on October 10, 2026.

Source: scenario-labs/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.