SkillAgentSearch skills...

gm-accept

Present final results to the user for acceptance. Shows evaluation results, evaluator screenshots, and asks for confirmation. Explicit invocation only — use /gm-accept.

Install / Use

npx skills add RandallLiuXin/GodotMaker --skill gm-accept

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Category

Other

Supported Platforms

Universal

Our assessment of gm-accept

gm-accept scores 85/100 on our quality scale, 205th of 328 Other skills we index.

Its SKILL.md is 4.7 KB long, well organised into 17 sections with 2 code examples: a solid amount of guidance for an agent.

It has 562 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 26 days ago, so gm-accept is actively maintained.
  • Our last check on 2026-11-04 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

gm-accept compared with similar skills

All 4 of these similar skills score higher than gm-accept; compare them before choosing.

SkillScoreStarsUpdatedFormat
gm-accept (this skill)by RandallLiuXin8556226d agoSKILL.md
Agent-Reachby Panniantong100113.0k10d agoCLAUDE.md
algorithmic-artby anthropics100177.9k57d agoSKILL.md
pptxby anthropics100177.9k57d agoSKILL.md
prospectingby coreyhaines3110060.1k7d agoSKILL.md

Frequently asked questions

How do I install gm-accept?
Run npx skills add RandallLiuXin/GodotMaker --skill gm-accept. The install tabs above show the steps for each supported agent.
Which AI agents does gm-accept work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is gm-accept safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is gm-accept still maintained?
The repository was last updated 26 days ago, so gm-accept is actively maintained.

name: gm-accept description: | Present final results to the user for acceptance. Shows evaluation results, evaluator screenshots, and asks for confirmation. Explicit invocation only — use /gm-accept. disable-model-invocation: true

GodotMaker Accept

$ARGUMENTS

You are presenting the current tag's completed work to the user for acceptance. This is a per-tag gate — accepting now does NOT mean the whole game is done; it means this tag (vX.Y.Z) is ready to be sealed, archived, and git-tagged by /gm-finalize. The user can choose to continue to the next tag (/gm-gdd again) or stop the project here.

Session Setup

FIRST ACTION — before anything else: Write accept to .godotmaker/current_role. Do this on every invocation, even when the file already contains accept (for example an idempotent re-entry) — reading the file is not a substitute. The write must actually happen and must be your first action.

Resume Check

Read .godotmaker/stage.jsonl (treat as empty if missing) — each line is {"role": X, "ts": Y}. Also read .godotmaker/evaluation.json.

  • If no event with role == "evaluate" exists anywhere in the file OR evaluation.json does not exist → STOP. Tell user to run /gm-evaluate first.
  • If evaluation.json result is "reject" → STOP. Tell user to run /gm-fixgap first.
  • If the last event has role == "accept" AND its decision == "accept" → STOP. Tell the user:

    "Accept already recorded at {timestamp}. Recommended next: /gm-finalize. If you need to redo this step or have other plans, just tell me."

  • Otherwise → proceed (re-invocation is valid if the previous accept event recorded a fix or done decision).

Process

1. Gather Results

Read these files:

  • .godotmaker/evaluation.json — evaluator results (mandatory)
  • PLAN.md — task completion status
  • MEMORY.md — stable architecture decisions and project constraints
  • GDD.md — original requirements

2. Collect Screenshots

Do NOT capture new screenshots. Use the screenshots already captured by the Evaluator:

  • Look in e2e/screenshots/ for scene_{name}.png files
  • These correspond to reference images in references/scene_{name}.png
  • If no evaluator screenshots exist, note this as a gap

3. Present to User

Format a clear summary:

## Tag Summary — {Tag from PLAN.md}

**Project:** {name}
**Tag delivers:** {one-liner from ROADMAP.md entry for this tag}

### What This Tag Built
- {N} new systems, {M} new components added in this tag
- Tag mechanics delivered: {Tag Mechanics list from PLAN.md, all PASS per evaluation.json `tag_mechanics`}
- Inherited mechanics still passing: {list each `<prev>-MN: pass` from evaluation.json `inherited_mechanics`}

### Test Results
- Unit tests: {from gm-verify results or PLAN.md}
- E2E suite: {evaluation.json `e2e_tests.passed`/`e2e_tests.total` — single suite covering both this tag's mechanics and inherited mechanics}

### Evaluation Result: APPROVED
- Mandatory checks: all passed
- Visual checks: {summary}
- Gameplay issues: {from evaluation.json, or "none"}

### Known Limitations
- {from evaluation minor_issues}

### How to Run
{instructions}

### Screenshots
{show evaluator screenshots side-by-side with references}

### What's Next
- After /gm-finalize this tag will be archived to docs/tags/{Tag}/ and `git tag {Tag}` will be created.
- Remaining tags in ROADMAP.md: {list of unshipped tags}
- To start the next tag, re-run /gm-gdd; to stop here, just don't.

4. Ask for Decision

Use AskUserQuestion to ask:

  • Accept → I'll record acceptance and recommend /gm-finalize.
  • Fix issues → tell me what to fix and I'll dispatch /gm-fixgap.
  • Done for now → progress is saved; you can resume any time."

Do NOT proceed until the user replies. Their reply drives the When Done branch below.

When Done

Always append a trace event to .godotmaker/stage.jsonl recording the user's decision, regardless of which branch was chosen. From the project root run:

python tools/append_stage_event.py accept --decision=<accept|fix|done>

This appends a {"role": "accept", "ts": "<server-generated UTC>", "decision": "<accept|fix|done>"} line. Do NOT hand-write the JSON or the timestamp — the helper exists so the timestamp comes from the system clock, not your own output.

Then: git add -A && git commit -m "chore(accept): <Tag> <decision>".

Then, based on the decision:

  • accept → Inform the user: Accepted. Recommended next: /gm-finalize
  • fix → Inform the user to run /gm-fixgap with specific fix instructions
  • done → Inform the user: Progress saved; resume any time

Note: only events with decision == "accept" count as the role having truly completed for /gm-finalize's prerequisite check. The fix and done events are kept as audit trail.

Related Skills

View on GitHub
GitHub Stars562
CategoryOther
Updated26d ago
Forks50

Languages

Python

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium