usecases.sh
usecases.sh
Research & Learning

Analyze your chess games into a commented video

A Claude Code user built a skill that takes his spoken notes and a lichess game, runs Stockfish, and returns a commented video of the game in about an hour, at roughly $15 of tokens per game.

Done with

What they did

brumar started with two experiments: whether Claude could play chess from board images rather than PGN notation, and whether Claude plus Stockfish could explain a game. Over several Claude Code sessions that grew into a set of skills. He records audio notes about what he was thinking during a game, gives a loose instruction such as analyze my last lichess game, and the agent fetches the game, runs Stockfish on the positions, writes commentary that answers the questions he asked himself out loud, and renders a video of the game with arrows and markers. Earlier versions produced annotated PGNs and a lichess-style HTML page; the video came last after several rounds of fixes. The code, the README and the SKILL.md files were themselves generated with Claude Code.

How it went

It works and he now only consumes the video output. A game takes about an hour to analyze and, from the session logs, around $15 at API prices. He says the result is not perfect, that he had to push the system toward positional analysis and it still shies away from it, and that only a much stronger player could judge the plans it proposes. He found no sycophancy: Stockfish anchors the verdicts, so Claude cannot tell him a bad move was good. One commenter who had tried the same idea on an earlier Opus could not get Claude to use Stockfish usefully and planned to test the skill.

Worth knowing

It burns tokens, so check your quota first. Chess players in the thread argued that LLMs play at roughly 1300 Elo and have no real understanding, that tactical lines are all Stockfish can anchor, and that this is a hack rather than a product; the author largely agreed and calls it a proof of concept. Whether watching a commented video teaches as much as working through the engine lines yourself was disputed.

Try it withClaude Code

Analyze my last game on [lichess / chess.com] for user [me]. Fetch the PGN, run [Stockfish] on every position to find the evaluation swings and the best alternatives, and read my notes in [notes.txt / this audio transcript] about what I was thinking at the key moments. Write commentary that explains each mistake in plain language, compares it with the line I was considering, and names the plan each side should have followed. Then render it as [an annotated PGN and HTML page / a video with arrows]. Show me the list of critical moments before you write the full commentary.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

All Research & Learning use cases

Every entry is something a person reported doing with an agent, rewritten in our words, with a link to where they said it. Found across the web every hour; reviewed before it ships.

Maintained by an agent that uses One for every integration it touches.