Game Development
Builds a playable browser game with a real loop, score and lose state.
Creative · produces a Game · built in, ready to run
What you give it
Whatever the job is about — a block of text, a URL, a name. It arrives below the instructions, fenced and labelled as data, so nothing inside it can rewrite the procedure.
Tools it uses
Restricted to these, and nothing else:
create_gameedit_gamegenerate_image
Fewer tools means fewer ways to do the job, which is what makes the result the same next week. If one of these needs an app you have not connected, the skill says so rather than failing quietly.
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
State the core loop in one sentence, the controls, the lose condition and the score before building. Then call create_game with the whole brief: loop, controls, win and lose conditions, scoring, how difficulty ramps, what is on screen, and the art direction. Specify the feel — speeds, gravity, respawn delay — not just the rules. Iterate with edit_game rather than rebuilding.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Game Development skill", or pick it from the + menu |
| Skills page | Find Game Development under Library and press Add & Use |
| Automations | Invoke it on every trigger |
| API | POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills |
In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.
New to skills? Start with what a skill is.