solitaire-analytics

Analyze raw Klondike Solitaire AI export logs from this repo (data/raw/solitaire-ai-log-*.json or files dropped in /Users/chayut/Downloads/) and deliver a kill-or-continue verdict. Use this whenever the user shares a solitaire-ai-log path, asks "should I kill this session?", asks whether a board is solvable, asks to ingest a new export, or wants to update data/DATASET_NOTES.md with findings from a new harvest. The user is running an active harvest pipeline and needs the early-termination signal — not a postmortem after the session stalls further.

Refresh and push the public Hugging Face dataset chayuto/klondike-llm-decisions after the corpus grows. Use this whenever the user wants to "publish the dataset", "update HF", "push to Hugging Face", "refresh the dataset", "re-publish klondike-llm-decisions", or bump the public corpus after a harvest has been ingested. It runs the regenerate, validate, push, verify, record flow end to end: regenerate the publish shards, gate them by id+field, upload only the changed Parquet shards, round-trip verify against the Hub, then append a Push-history row to the canonical log and update the recall memory. The cached HF token is usually invalid (temp tokens get revoked after each push), so the skill expects the user to supply a fresh WRITE token inline and reminds them to revoke it afterwards. This skill is for the PUBLISH step only; bringing new harvester exports into the corpus first is the solitaire-ingest skill's job. ALSO use it for a card-only change (edit the generator, re-push just data/publish/README.md) or to

Triage and ingest the Klondike harvester's terminal and snapshot export files (solitaire-win-*.json and solitaire-game-*.json, usually paired with a solitaire-ai-log-*.json) into the training corpus. Use this whenever the user drops one or more harvester export files and wants them ingested, cataloged, or added to the dataset / corpus / manifest, or says things like "ingest these wins", "ingest WINS", "add this harvest", "catalog this game", or pastes solitaire-win- / solitaire-game- paths. It triages FIRST (terminal-win vs terminal-loss vs mid-game pending-snapshot) before any deep analysis, reads model / build / prompt attribution per file because the harvester mixes models and builds across time, and routes each session to the right ingest and DATASET_NOTES action. ALSO use this skill when the user reports that pending sessions were killed (e.g. "all killed", "I killed those") after an ingest: the operator-kill flow turns the already-ingested ai-logs into terminal loss-by-kill records and adjudicates each

Use this skill for ANY situation involving LLM prompts, response schemas, or LLM misbehavior diagnosis. Trigger eagerly — do not wait for the user to say "audit". USE IMMEDIATELY when (1) the user pastes a prompt, system prompt, response schema, few-shot example, or JSON template for any reason; (2) the user describes ANY LLM misbehavior — model loops, repeats itself, ignores instructions, keeps apologizing, drifts, picks wrong from a numbered list, hallucinates JSON keys, gives identical answers to different inputs, infinite loops, parroting; (3) the user is writing a new system prompt or response schema for production; (4) the user mentions "review/audit/critique/improve/evaluate/check/look at" anywhere near a prompt; (5) the user asks about structured outputs, JSON mode, function calling, few-shot examples, reasoning trail, history accumulation, chain-of-thought, or schema design; (6) the user names a model (Claude/GPT/Gemma/Gemini/DeepSeek/o-series/Llama) alongside a behavior problem. Produces a severity-