← Smart Chess:Train+Learn to winCONTENT HISTORY

Update to Smart Chess:Train+Learn to win

Snapshot Sep 30, 2026 · 23:19 UTC · version 3.0.0

Collection source: not recorded for this historical snapshot. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED · RULE-BASED ANALYSIS

Supporting file metadata differs

Newly listed paths: agents/openai.yaml. This compares saved file lists, not package contents; a different collection source can change the list.

Observed in package metadata. These changes alone do not establish a new customer-facing feature.

Supporting files

Before

[]

After

[{"relative_path":"agents/openai.yaml","size_in_bytes":250}]

Compare saved observations

Download comparison JSON
Full technical diff · 1 changed fields

changed /included_files

BEFORE
[]
AFTER
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 250
  }
]
Full snapshot data
{
  "description": "Recommend an appropriate Stockfish difficulty for a rematch and start a fresh Chess app game after the user authorizes it. Use when the user wants to play again, make the next game easier or harder, or adjust the level based on how the previous game felt. Use only the registered start-game tool and integer levels from 0 through 20.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 250
    }
  ],
  "name": "adaptive-chess-rematch",
  "skill_md_contents": "---\nname: adaptive-chess-rematch\ndescription: Recommend an appropriate Stockfish difficulty for a rematch and start a fresh Chess app game after the user authorizes it. Use when the user wants to play again, make the next game easier or harder, or adjust the level based on how the previous game felt. Use only the registered start-game tool and integer levels from 0 through 20.\n---\n\n# Adaptive Chess Rematch\n\n## Inputs\n\nUse the current widget's model-visible `difficulty`, `moves`, `phase`, and `outcome` when available. Give the user's explicit assessment of the previous game's difficulty more weight than the result alone.\n\n## Choose the Level\n\n1. Honor an explicit requested level from 0 through 20.\n2. For a relative request, start from the current difficulty and use a conservative adjustment:\n   - Move by 1 level for a slightly easier or harder game.\n   - Move by 2 levels when the user says the game was clearly overwhelming or far too easy.\n   - Keep the same level when the game felt competitive.\n3. Clamp the recommendation to the inclusive 0–20 range.\n4. Do not infer a large adjustment from one win, loss, draw, or resignation. If the user has not described how the game felt, ask one concise calibration question or recommend staying close to the current level.\n\n## Start the Rematch\n\n1. State the proposed level and one short reason.\n2. Treat a direct request such as “make it harder and play again” as authorization. Otherwise, ask for confirmation before starting.\n3. Call `start-game` with:\n   - `difficulty`: the chosen integer from 0 through 20\n   - `reason`: an optional concise explanation of the user's rematch request\n4. After the call, briefly confirm the level. Let the returned widget provide the fresh game.\n\n## Boundaries\n\n- Use the tool name `start-game` exactly. Do not invent tool arguments.\n- Expect the tool's structured content to contain only `difficulty`.\n- Do not claim to modify, resume, or unfreeze the previous widget; every call creates a new game.\n- Remember that the user is always White and moves first.\n- Do not promise that a level maps to a formal player rating.\n"
}

SHA-256 of public snapshot: 72a5d477f5a2aa72dd75cd0f7cdbae52f6e48ce98577944613995e4cc6d4ff8e