Super gaming 3d media
Gaming, 3D, and media: engines, 3D web, animation, audio/video tooling.From its SKILL.md
npx -y skills add arpitexplores/super-gaming-3d-mediaAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, 347 tokens by cl100k_base, as published. Nobody here has run it
Super Gaming / 3D / Media
Overview
Build game systems, 3D experiences, and media pipelines with clear constraints.
User Intent Examples
- "Need help with Game Development for my product/site."
- "Create a plan for Three.js & 3D Web."
- "Audit or improve Video/Media Tooling."
Workflow
- Define platform, performance targets, and content type.
- Select engine or rendering stack.
- Design assets, interaction, and performance budget.
- Implement animation/audio/video workflows.
- Test on target devices and optimise.
- Document asset pipeline and build steps.
Minimal Intake Questions
- Primary goal or outcome
- Scope (pages, systems, teams, or timeframe)
- Constraints (tools, budget, timeline)
Output Format
- Platform and stack choice
- Asset and interaction plan
- Performance budget
- Media pipeline steps
- Testing checklist
Routing Map (Modules)
- Game Development ->
references/modules/game-development.md - Three.js & 3D Web ->
references/modules/threejs-skills.md - Video/Media Tooling ->
references/modules/videodb.md
Bundled References
references/modules/scripts/assets/agents/
Compatibility Notes
- If any module references slash commands or tool-specific paths, translate them into plain-language steps.
- Keep outputs platform-agnostic unless the user specifies a specific tool, stack, or agent.
Guardrails
- Test performance on target hardware.
- Avoid large assets without compression plan.
- Separate render pipeline from game logic.
What ships with it: 13 files
1288.8 KB alongside SKILL.md
agents/
- openai.yaml182 B
examples/
- README.md532 B
references/
- modules/game-development.md1142.0 KB
- modules/threejs-skills.md42.6 KB
- modules/videodb.md90.7 KB
- CHANGELOG.md554 B
- .gitignore23 B
- INSTALL.md2.5 KB
- LICENSE1.0 KB
- product.json862 B
- PUBLISHING.md765 B
- README.md7.1 KB
- VERSION6 B
Gives 0 of the 12 instructions most video audio skills give in 347 tokens
Counted across 622 of the 795 authors here whose files we hold, read 2026-08-07
- Read individual rule files for detailed explanationsin 21 of 622, across 10 files
- Render final videoin 13 of 622, across 6 files
- Use WAV PCM 16kHz mono audio formatin 12 of 622, across 3 files
- Use this skill when dealing with Remotion codein 11 of 622, across 4 files
- Save generated audio to a WAV filein 11 of 622, across 4 files
- Handle conversion errors gracefullyin 10 of 622, across 6 files
- Add captions to videos alwaysin 10 of 622, across 4 files
- Generate music from text descriptions using MusicGenin 9 of 622, across 2 files
- Do not skip pipeline layersin 9 of 622, across 3 files
- Do not make one tool do everythingin 9 of 622, across 3 files
- Use Azure Document Intelligence for complex PDFsin 9 of 622, across 4 files
- Never ask the user to paste their full API keyin 9 of 622, across 3 files
Said here and by no other author read
- Define platform, performance targets, and content type
- Select engine or rendering stack
- Design assets, interaction, and performance budget
- Implement animation, audio, and video workflows
- Test on target devices and optimise
- Document asset pipeline and build steps
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.