gameskill

Captures game-development session learnings as reusable SKILL.md files for future agent sessions.

66|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/SummerEngine/summer --skill gameskill-summerengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gameskill
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/gameskill
Command: npx skills add https://github.com/SummerEngine/summer --skill gameskill-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game-development sessions often produce hard-won lessons (working shaders, engine quirks, bug fixes) that vanish when the session ends, forcing the next agent to rediscover them. This Skill turns those learnings into durable, reusable skills stored in the project, user, or Summer library scope. ## Core Features & Use Cases - Scoped skill placement: Writes captured skills to the project skills directory, the user's agent skills directory, or the Summer library depending on how broadly the lesson applies. - Deduplication via library search: Probes existing bundled skills with summer_search_library or summer skills list so it extends an existing skill instead of duplicating it. - Quality filter and style rules: Captures only non-obvious, general learnings with the reasoning behind them, following strict formatting rules (YAML frontmatter, no dates, no project names). - Use Case: After a session where you fixed a Godot 4.x signal gotcha and tuned a spawning pattern, invoke this Skill to draft a new SKILL.md in .claude/skills/, confirm the plan, and commit it with the game so the next agent starts with that knowledge. ## Quick Start Ask the agent to capture the learnings from this game-development session into a reusable skill and commit it to the project.

Frequently Asked Questions about gameskill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save session learnings as a reusable skill?

Invoke the gameskill workflow at the end of a session. It recaps non-obvious learnings, checks existing skills to avoid duplication, drafts a SKILL.md with YAML frontmatter, and writes it to the project, user, or Summer library scope after your confirmation.

Where should a captured skill be stored?

Prefer the narrowest scope: the game project's skills directory by default, the user's agent skills directory for machine-wide lessons, and the Summer library only for lessons general enough for every Summer user. Library changes require running the registry generator and validator.

Which AI agents does this skill support?

It supports Claude Code, Cursor, Windsurf, and Codex. Each agent has its own skills directory convention, such as .claude/skills/ for Claude Code and .agents/skills/ for Codex, and summer skills install --scope project shows the exact path.

What kinds of learnings are worth capturing as a skill?

Capture learnings that are non-obvious and general: working shader code, GDScript idioms, bug root causes and fixes, Godot 4.x quirks, spawning or AI patterns, measured performance fixes, and asset workflows. Skip one-off code, already-documented facts, and personal preferences.

What happens if a session has nothing worth capturing?

The Skill explicitly says so rather than manufacturing content. It reports that the session was tactical with no durable learnings, since shipping noise degrades the skill library for future agents.