菜单
Get a hint for the current challenge in Learn Docker & K8s. Provides progressive hints (1=direction, 2=specific, 3=near-answer). Use when the user is stuck, asks for help, says "hint", "help me", "I'm stuck", or "I don't know what to do".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Start or resume the Learn Docker & K8s interactive game. Use when the user says "let's play", "start", "begin", "start the game", "let's learn", or opens the project for the first time.
Show the player's current progress in Learn Docker & K8s. Displays completed chapters, current position, and overall stats. Use when the user asks "where am I", "what have I done", "show progress", or "status".
Clean up Docker resources created by the Learn Docker & K8s game. Removes all learn-* containers, networks, volumes, and images. Use when the user wants to clean up, reset, or free disk space.
Monitor player engagement and adapt the learning experience. Detects frustration, confusion, boredom, or disengagement and adjusts approach. Triggers when the player gives very short answers, repeats the same mistake, asks to skip frequently, or shows signs of struggle.
Check if the system is ready for the Learn Docker & K8s game. Verifies Docker, Docker Compose, kubectl, kind, disk space, and port availability. Use when the user asks about requirements, setup, or environment issues.
Move to the next lesson or challenge in Learn Docker & K8s. Use when the user says "next", "continue", "move on", "what's next", or finishes a lesson/challenge.
| name | hint |
| description | Get a hint for the current challenge in Learn Docker & K8s. Provides progressive hints (1=direction, 2=specific, 3=near-answer). Use when the user is stuck, asks for help, says "hint", "help me", "I'm stuck", or "I don't know what to do". |
| argument-hint | [1|2|3] |
Read .player/progress.yaml to find the current chapter and challenge. Then read the corresponding challenge file from curriculum/chXX-*/challenges/XX-*.md.
Check what hint level was last given. If $ARGUMENTS specifies a level (1, 2, or 3), use that. Otherwise:
General direction without specifics. Points them toward the right concept. Example: "Think about how Docker containers find each other on a network..."
Narrows down to the specific tool or concept. Example: "Check which network your containers are connected to. There's a Docker command that inspects networks..."
Almost the answer but lets them connect the final dot.
Example: "Try docker network inspect bridge and look at the Containers section. Your containers need to be on the same user-defined network."
If they're still stuck after Hint 3, offer to switch to guided mode: "No shame in that — this stuff trips up everyone. Want me to walk through it with you step by step?"
In guided mode, you can demonstrate commands but still let them type the final solution.
