← Smart Chess:Train+Learn to winCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
changed
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.
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":217}]
Compare saved observations
Download comparison JSONFull technical diff · 1 changed fields
changed /included_files
BEFORE
[]
AFTER
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 217
}
]Full snapshot data
{
"description": "Identify the likely opening family from the current Chess app move history and explain its practical plans. Use when the user asks what opening was played, how the opening developed, where play left familiar theory, or what plans to remember next time. Treat names and ECO codes as heuristic because the app exposes no opening database.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 217
}
],
"name": "opening-debrief",
"skill_md_contents": "---\nname: opening-debrief\ndescription: Identify the likely opening family from the current Chess app move history and explain its practical plans. Use when the user asks what opening was played, how the opening developed, where play left familiar theory, or what plans to remember next time. Treat names and ECO codes as heuristic because the app exposes no opening database.\n---\n\n# Opening Debrief\n\n## Inputs\n\nUse the early portion of the current widget's model-visible SAN and coordinate `moves`, plus the current `fen` when it helps explain the resulting pawn structure. Use the user's experience level to choose vocabulary and depth.\n\nIf no moves have been played, explain that there is no opening sequence to classify. If only a few half-moves are available, identify broad opening principles or a family rather than forcing a precise name.\n\n## Workflow\n\n1. Quote the relevant opening sequence in SAN.\n2. Identify the most likely opening family or named variation.\n - State confidence when the move order is short, unusual, or compatible with transpositions.\n - Mention at most one plausible alternative name when ambiguity materially helps.\n3. Explain the defining pawn structure, development pattern, and king-safety choices.\n4. Give the typical practical plans for White and Black in the resulting structure.\n5. Identify the first instructive decision for White. Call it a departure from theory only when sufficiently confident; otherwise describe it as a practical choice.\n6. Finish with two or three priorities the user can remember in a future game.\n\n## Output\n\nUse this structure:\n\n- **Opening sequence**\n- **Likely opening**\n- **Position character**\n- **Plans for both sides**\n- **Remember next game**\n\n## Boundaries\n\n- Do not imply access to an opening database, live theory, or Stockfish analysis.\n- Omit an ECO code unless the user requests one and the classification is highly confident; label any supplied code as tentative.\n- Do not invent missing moves or claim that a move is the first theoretical error without reliable evidence.\n- Do not call `start-game` or alter the current game.\n"
}SHA-256 of public snapshot: cb91a937d68506ccf4fa5b2125ff1e394cf46f8d0bb1a1d2a1a269ec84353a3b