← Smart Chess:Train+Learn to winCONTENT HISTORY
WHAT CHANGED
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
Supporting file metadata differs
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Save Smart Chess:Train+Learn to win and check future changes in Following.
Up to 3 plugins free · no card required.
All fields and original values.
Supporting files
Before
Sep 30, 2026 · 22:45 UTC
[]
After
Sep 30, 2026 · 23:19 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":234}]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
No SKILL.md text changes between these observations.
Full technical diff · 1 changed fields
changed /included_files
BEFORE
[]
AFTER
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 234
}
]Full snapshot data
{
"description": "Explain the purpose and consequences of the latest move in the current Chess app game. Use when the user asks why Stockfish or White played that move, what changed, what the move threatens, or how to respond. Ground the answer in the latest model-visible SAN and coordinate move plus the current position, without claiming access to Stockfish's reasoning.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 234
}
],
"name": "explain-last-chess-move",
"skill_md_contents": "---\nname: explain-last-chess-move\ndescription: Explain the purpose and consequences of the latest move in the current Chess app game. Use when the user asks why Stockfish or White played that move, what changed, what the move threatens, or how to respond. Ground the answer in the latest model-visible SAN and coordinate move plus the current position, without claiming access to Stockfish's reasoning.\n---\n\n# Explain Last Chess Move\n\n## Inputs\n\nUse the current widget's model-visible `moves`, `fen`, `turn`, `inCheck`, and `phase`. Treat the final entry in `moves` as the latest move and use both its SAN and coordinate fields.\n\nIf the history is empty, explain that no move has been played yet. If the state is missing, ask for the move or current position.\n\n## Workflow\n\n1. Name the latest move and identify which side played it. If the user's wording names the wrong side, clarify gently.\n2. Explain its immediate board effects:\n - movement, capture, check, promotion, or castling\n - newly attacked, defended, opened, or blocked lines\n - material or king-safety changes visible from the position\n3. Describe one or two likely tactical or strategic purposes. Use language such as “likely,” “appears to,” or “one point is” when explaining Stockfish's move.\n4. Identify the most important threat or consequence for the side to move.\n5. When it is White's turn, offer a practical response idea. Give a concrete move only when confident it is legal; otherwise describe the plan or candidate set.\n\n## Output\n\nUse four short parts:\n\n- **Move**\n- **What changed**\n- **Likely idea**\n- **What to watch now**\n\nAdapt the depth to the user's level and question.\n\n## Boundaries\n\n- Do not claim access to Stockfish evaluation scores, search lines, or internal intent.\n- Do not call a move best, forced, winning, or a blunder without evidence available in the position.\n- Do not invent prior moves or hidden analysis.\n- Do not control the board or call `start-game`.\n"
}SHA-256 of public snapshot: ee50d7153984cd090890974d119a2a08133823bdbbeb963932da83e35e3ee671