Build a small, coherent opening repertoire that fits your style and level — the few lines actually worth learning, plus the plans and traps behind them.
SkillScore100Maintained
Automatic
◆Tutoring & Education pack
Last verified 8/31/2026
What it changes
Passed 24 of 24 test cases with the skill, and 21 of 24 without it.
Without skill88%
With skill100%
Checks it passed that the model alone missed
The response identifies tactical traps to avoid.
The response details the forced tactical check sequence leading to smothered mate.
The response provides a structured study roadmap separating immediate study from later additions.
3 fixed21 passed either way0 still failing0 broke
Pass-rate lift
+13 pp
Tokens
+3%
Agent turns
0%
Response time
-15%
Model gemini-3.6-flashMeasured 8/31/2026v124 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
I am analyzing a tactical puzzle: White has a Queen on g6, Knight on f7, Black's King is trapped on h8 with a Rook on f8. Is there a forced smothered mate in 3 moves starting with Nf7+? Walk me through the exact forcing check sequence.
What was checked, without and with the skill
Checked
Without skill
With skill
The response details the forced tactical check sequence leading to smothered mate.
Missed
Passed
The response refrains from generating an opening repertoire recommendation.
Passed
Passed
case-06 · gemini-3.6-flash · 8/31/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md60 linessingle file
Chess Opening Coach
Most improving players lose games not in the opening but by drowning in opening theory they don't understand. This builds a small repertoire — a handful of coherent lines that suit how you like to play — and teaches the ideas behind them, so you reach playable middlegames you understand instead of memorizing twenty moves you'll forget.
What This Skill Produces
A compact repertoire — one main choice for White, and answers for Black vs 1.e4 and 1.d4, sized to your level
The ideas, not just moves — the plan behind each opening: pawn breaks, piece placement, where your pieces belong
Traps both ways — the common tricks to avoid falling for and the ones you can use
Move-order essentials — the few critical points where accuracy matters, and where you can play on understanding
A study path — what to learn first and what to add later, so it stays small
Required Inputs
Ask for these if not provided:
Rating/level — rough strength (beginner, club, intermediate) — sets how much theory is worth it
Style — attacking/tactical, solid/positional, or "just something reliable"
Colors & gaps — do you want White, Black, or both; anything you already play
Time — how much you'll realistically study
Trouble spots — openings you keep losing against
Framework: Small, Understood, Coherent
Fit the style. Recommend openings that suit how the player likes games to go — an aggressive player will hate a dry, maneuvering system.
Teach plans over moves. For each opening, give the middlegame plan and typical pawn breaks so they know why, not just what.
Keep it small. A few reliable lines beat a sprawling repertoire — depth of understanding over breadth of memorization.
Cover the real replies. Address the responses they'll actually meet at their level, not obscure grandmaster theory.
Know the traps. Flag the common early tricks (both to avoid and to spring) that decide games at club level.
Output Format
Repertoire: [level] · style: [x] · [colors]
As White: [opening] — plan: [pawn breaks / piece setup]. Key point: [where accuracy matters].
As Black vs 1.e4: [defense] — main idea: […].
As Black vs 1.d4: [defense] — main idea: […].
Traps to know: [avoid: … / use: …].
Study first → later: [the 2–3 lines to learn now] → [what to add once comfortable].
Write a CI/CD pipeline playbook for a service or team. Use when asked to document a CI/CD pipeline, write a deployment process, define release gates, document build and test stages, or create a deployment guide. Produces a structured playbook covering pipeline stages, environment definitions, deployment gates, rollback procedures, and on-call responsibilities.